{"ref":"capability:xml-payloads","page":"/capabilities/xml-payloads","json":"/capabilities/xml-payloads.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"xml-payloads","name":"XML payloads","domain":"protocols-and-apis","ecosystems":["cap","abap"],"universal":false,"description":"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.","short":"Accepting, returning and sending XML on a service","core_coverage":{"state":"community-only","assessed_at":"2026-09-09","where_it_stops":"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.","note":"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."},"history":[{"date":"2026-09-14","field":"description","from":"Accepting and returning XML on a CAP service, for a caller that cannot speak JSON — usually a B2B partner or a system older than the extension in front of it.","to":"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.","reason":"The description named a CAP service, which is false for ABAP Cloud consuming and exposing SOAP; the wording now covers a service in either ecosystem and the calling side as well as the answering one."},{"date":"2026-09-14","field":"ecosystems","from":"cap","to":"cap, abap","reason":"SAP-samples' abap-platform-refscen-flight-soap-client and abap-platform-refscen-flight-soap-server consume and expose SOAP services from ABAP Cloud, which is XML exchanged with a system that does not speak JSON."}],"coverage_by_ecosystem":{"abap":{"state":"core-only","assessed_at":"2026-09-14","what_core_does":"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.","where_it_stops":"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.","note":"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.","sources":[{"url":"https://github.com/SAP-samples/abap-platform-refscen-flight-soap-client","title":"abap-platform-refscen-flight-soap-client — README","checked":"2026-09-14","quote":"SOAP service consumption models are used for the outgoing SOAP messages, and a SOAP provider model is used for handling an asynchronous confirmation message."},{"url":"https://github.com/SAP-samples/abap-platform-refscen-flight-soap-server","title":"abap-platform-refscen-flight-soap-server — README","checked":"2026-09-14","quote":"The sample scenario demonstrates how to consume and expose SOAP services in ABAP Cloud."}]}},"framing_by_ecosystem":{"abap":{"description":"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 connectivity](capability:rfc-connectivity) for RFC calls."}},"drafted_with_ai":true},"sap_delivery":{"door":"cap","all":null,"by_flavor":{"node":null,"java":null}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:neoimpulse-cap-js-xml-protocol","name":"@neoimpulse/cap-js-xml-protocol","json":"/artifacts/neoimpulse-cap-js-xml-protocol.json","ecosystem":"cap","origin_ring":"independent"}],"samples":[{"ref":"artifact:sap-samples-abap-platform-refscen-flight-soap-server","name":"abap-platform-refscen-flight-soap-server","json":"/artifacts/sap-samples-abap-platform-refscen-flight-soap-server.json"},{"ref":"artifact:sap-samples-abap-platform-refscen-flight-soap-client","name":"SAP-samples/abap-platform-refscen-flight-soap-client","json":"/artifacts/sap-samples-abap-platform-refscen-flight-soap-client.json"}],"explained_by":[],"normative_context":[]}}