OctaSapien

OData Receiver Payload Preflight

Compare supplied OData V2 EDMX, an operation, resource path and XML or JSON sample locally before CPI mapping.

Maximum 512 KiB. Paste metadata you already have; no URL is fetched.

Maximum 256 KiB. XML depth and node count are also limited.

All analysis runs locally in this browser tab. Nothing is sent to OctaSapien or SAP.

Found something we could improve?
Practical usage guide

Practical usage guide

A practical workflow for OData V2 Receiver Payload Preflight

Check supplied OData V2 EDMX, operation, resource path and XML or JSON sample locally. JSON is upstream only; CPI receiver input is XML. Results do not prove SAP acceptance.

1. Prepare

Paste or upload a representative input and run the validation before using it in an interface, test or transport.

2. Review

Resolve each reported error from the first failure onward, then run the validation again until the input is clean.

3. Apply

Validate the result against the interface contract and target CPI runtime before transporting or sharing it.

Verification before operational use

  • Use representative samples without passwords, tokens, personal data or production secrets. Keep the smallest input needed to reproduce the behavior you are reviewing.
  • Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
  • Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.