XML payloads
Accepting and returning XML on a service, or sending it to one, for a counterpart that cannot speak JSON — usually a B2B partner or a system older than the extension in front of it.
Overview
No core answer is documented.
Not covered: CAP's OData and REST adapters are JSON. There is no XML content type to switch on, so the conversion happens before CAP sees the request or after it has answered.
community-only describes who provides it, not neglect: OData V4 dropped XML payloads at the protocol level, so this is a bridge to callers that stayed behind rather than a hole in the runtime.
In ABAP Cloud XML arrives as SOAP: a service consumption model calls a remote operation described by its WSDL, and a provider model answers one. The connection to the other system is set up as a communication arrangement, beside RFC connectivityRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.SAP and community, narrow by design for RFC calls.
ABAP Cloud calls a SOAP operation through a service consumption model and answers one through a SOAP provider model, each generated from a WSDL in ADT, synchronously or with an asynchronous confirmation.
Not covered: At SOAP with a WSDL. The XML shape is the service contract's, and the connection to the other system is configured separately as communication systems and arrangements; XML with no WSDL behind it is outside what the scenario read here covers.
Both entries behind this door are halves of one SAP reference scenario, and a sample demonstrates and does not provide, so core-only rests on the SOAP models that scenario names.
No community artifact is documented here.
Artifacts
Seen working
Details
Coverage
For your agent
- Ref
capability:xml-payloads- JSON
- /capabilities/xml-payloads.json
- MCP
- Connecting an agent