Onboard a provider without guessing its rules
Reviewed 2026-10-01 · version 1.0.0
Update owner: LSP Emulator product team
Start with a pair and a counterexample
Pair a request with its known response and record their relationship. Add a contrasting example before generalizing. In the current discovery workflow, select synthetic-delvry07 1.0.0; SOAP and inbound receipt adapters are emulation paths, not discovery options.
A difference is evidence to review
SAP distinguishes delivery message types and process actions. A changed field may instead reflect a provider extension, a scenario or incomplete examples. Review proposed rules, their scope and failed cases; source documentation is not permission to invent a universal mapping.
Test, activate, reuse
Test a draft against independent expectations, then activate an immutable version for its variant. A new simulation uses that saved version where supported. Re-evaluation creates a new run; replay retrieves the original bytes.