Symptom
- The design-time generated XSD sequence in the OData adapter V2 and V4 does not match the runtime payload sequence.
- The discrepancy occurs after the OData backend response step, where the order of fields appears scrambled.
- The behavior was validated by running the interface in trace and comparing payloads at each step.
- No specific error message is observed; flows complete successfully.
Read more...
Environment
- Cloud Integration
- Integration Suite
Product
Cloud Integration all versions ; SAP Integration Suite all versions
Keywords
odata adapter, v2, v4, runtime payload order, xsd sequence mismatch, xml sibling order, element order not preserved, cloud integration, cpi, xpath, message mapping, xslt, design time vs runtime, trace, xml reordering , KBA , LOD-HCI-PI-CON-OD , OData Adapters , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview