Validate a file
Check an XML file against the built-in SAP reference and the active rules of a custom interface profile.
Open workspaceSAP / 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 data · XML responses
From a delivery to a testable response
- Upload01
- Review rules02
- Simulate03
- Download04
OBD / IBD → XML → Reference checks
Choose what you want to do
Start with a file, learn an interface, or generate a logistics response. Each action opens directly in your workspace.
Discover interface rules
Compare interface examples with a reference profile, review their differences and prepare workspace-specific rules.
Open workspaceEmulate a response
Select an OBD request, choose a test profile and generate a SHPCON response to inspect and download.
Open workspaceSpend your test window on the integration.
Manual XML edits and limited provider availability can slow a test cycle. Prepare repeatable messages in advance, keep custom interface profiles separate and take a readable report to your next SAP test.
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 guideEmulate 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 · SHPORD → SHPCON · DELVRY07 reference subset | 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.
Review the result before import
Work with synthetic data, review the generated message and validation report, then run a separate test in your SAP system. The emulator does not need a connection to the logistics provider.
Open workspace