SendOrder_Async — API Documentation

1. Overview

SendOrder_Async is a SOAP web service (WSDL-defined) used to submit order data in a fire-and-forget (asynchronous, one-way) manner.

• Target namespace: http://cpi.sap.com/demo
• Style: document
• Transport binding: http://schemas.xmlsoap.org/soap/http (standard SOAP over HTTP)
• Namespaces referenced in the WSDL:
  • p1 → http://cpi.sap.com/demo (service/schema namespace)
  • wsp → http://schemas.xmlsoap.org/ws/2004/09/policy (WS-Policy, present in the WSDL's policy attachments)
  • wsu → http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd (WS-Security Utility, present for security-related metadata)
  • wsdl → http://schemas.xmlsoap.org/wsdl/ (WSDL structural namespace)

No output message or fault message is defined for this service, consistent with its one-way, asynchronous design.

2. Operations

SendOrder_Async

3. Messages

This is the only message defined in the WSDL, and it serves as the input to the SendOrder_Async operation.

4. Data Types

Element: Order_MT

A global XML Schema element of kind element, typed by the complex type Order_DT. It carries no fields of its own — its structure is entirely defined by Order_DT.

Complex Type: Order_DT

Note: The parsed facts do not include explicit minOccurs/maxOccurs attributes for these fields. Per standard XML Schema semantics, absence of these attributes defaults to exactly one occurrence (1..1), required. Confirm against the actual XSD if optionality or repetition is needed.

5. Integration Notes

• Request payload: Consumers must send a SOAP request whose body contains a single Order_MT element (namespace http://cpi.sap.com/demo), populated with the four Order_DT fields: orderNumber, supplierForename, supplierSurname, productName — all of type string.
• SOAP Action header: Clients must set the SOAP Action HTTP header to http://sap.com/xi/WebService/soap1.1 when invoking the operation.
• No response expected: Since the operation is one-way, the consumer should not expect a SOAP response body. Successful HTTP-level acknowledgment (e.g., HTTP 202/200 with empty body, depending on the runtime) is the only confirmation of receipt at the transport level; no application-level acknowledgment message is defined in this WSDL.
• No fault handling defined: The WSDL does not declare a fault message for this operation. Error handling (e.g., malformed payloads) must be handled per the runtime/platform's default behavior (e.g., SAP CPI iFlow error handling), not via a WSDL-defined SOAP Fault.
• Transport: Use standard SOAP over HTTP (http://schemas.xmlsoap.org/soap/http) with document-style, literal encoding (implied by document style).
• Security/Policy: The presence of wsp (WS-Policy) and wsu (WS-Security Utility) namespace declarations indicates the WSDL may carry security policy assertions (e.g., transport or message-level security requirements). The parsed facts do not detail specific policy assertions — consult the raw WSDL's wsp:Policy blocks for exact security requirements (e.g., credentials, signing) before implementing a client.
• Single operation: This service exposes exactly one operation (SendOrder_Async); there is no companion synchronous or query operation defined in this WSDL.