Learn an interface
Pair examples → review differences → test and activate rules. Discovery currently supports synthetic-delvry07 1.0.0. A single example is a hypothesis, not proof of a general rule.
Read the guideSAP / logistics / third-party providers
Test SAP logistics interfaces on your schedule.
Prepare a shipment or receipt confirmation, reuse reviewed provider rules and see exactly what was checked. Built for SAP consultants, integration teams and logistics testers.
Selected reference profiles · synthetic pilot data · XML responses
From a delivery to a testable response
- Upload01
- Review rules02
- Simulate03
- Download04
OBD / IBD → XML → Reference checks
Spend your test window on the integration.
Manual XML edits and partner availability can slow a test cycle. Prepare repeatable messages in advance, keep provider variants separate and take a readable report to your next SAP test. Validate the time saved in your own pilot.
Emulate a response
Choose a released profile → configure a scenario → review and download. Start without provider examples using the SOAP OBD quickstart. Saved custom rules apply to their supported profile.
Read the guideInterface compatibility
Versioned reference contracts based on public SAP documentation. Local XSD checks and source correlation run offline. SAP import is a separate result.
| Interface | Complete | Partial | Batch split | Handling units | Serials | PIC → PGI |
|---|---|---|---|---|---|---|
| IDoc outbound · DELVRY07 | Supported | Supported | Supported | Supported | Supported | Supported |
| IDoc inbound · DELVRY03 WHSORD → WHSCON | Supported | Unsupported | Supported | Supported | Supported | Unsupported |
| SOAP · Shipping Order → Shipping Advice | Supported | Unsupported | Supported | Supported | Supported | Unsupported |
| SOAP · Stock Transfer Shipment → Receipt Advice | Supported | Unsupported | Supported | Supported | Supported | Unsupported |
These profiles cover documented reference subsets with synthetic test cases. SOAP advice sends the final state; partial receipt and PIC → PGI need different interfaces. Serial cardinality is checked for EA. No SAP posting or material document number is simulated.
Know what your result proves.
Syntax, reference-contract checks, provider assumptions and SAP processing are separate evidence layers. A generated XML file does not prove that SAP accepted or posted a delivery.
Private workspaces keep your files and rule versions separate. The normal emulation path is deterministic; optional AI follows account controls.
Two ways to start
Prepare a SAP project test
Use the SOAP OBD quickstart to generate your first reference confirmation. Inspect the report, download XML and take it into your sandbox. Measure preparation time; keep the actual SAP import as separate evidence.
Repeat a mapping regression
Replay exact saved bytes after a mapping change, or create a separate re-evaluation with selected versions. Compare reports and keep the original result. Today this is a manual workspace flow; automated API and suites remain planned.
Practical notes for your next test
Questions before you start
Do I need an LSP connection?
No connection to a real provider is required for upload, emulation and download. You perform any SAP import in your own test environment. A file simulator cannot reproduce the partner network, warehouse execution or every production failure.
Which file should I download?
Use XML for a supported response message. Use canonical CSV for normalized data, report CSV for findings and TXT for a readable report. Bundles preserve message order and checksums. These CSV/TXT exports are not native provider formats; dedicated native adapters are planned.
Does a green report mean SAP posted the delivery?
No. It proves only the checks that actually ran. Import and business processing need observations from the target SAP system. Reported success remains unverified until a different authorized reviewer approves evidence for the exact artifact and configuration.
A pilot with a clear finish line
Use one workspace and synthetic data. The value notebook covers up to 100 useful runs over 1–90 days; this is a measurement limit, not a paid plan or a global run quota. Agree your profiles, partner-only scenarios and target before starting. No online payment is required.
Start a pilot