You want to make sure the SAP PI/PO Server can process the MessageObject.You want to make sure the SAP PI/PO Server can process the MessageObject.You experienced problems with the MessageObject and want to find the root cause of the problems.Name | Description |
url | String that contains the URL of the SAP PI/PO Server to which you want to send the outbound MessageObject. |
auth | Optional. Document Type that contains authorization information, the service submits if the SAP PI/PO Server specified in the url field is protected. type. Type of authentication the service uses when it submits this request. Currently, only basic authentication is supported. If you are accessing a protected resource, set type to Basic.user. User name the service uses to log in to the SAP PI/PO Server.pass. Password the service uses to log in to the SAP PI/PO Server. |
SAP:MessageHeader | Document Type that contains the message header of the outbound MessageObject. The Document Type must comply with the syntax and semantics of the SAP XML Message Format as described in the SAP XML Message Format white paper. |
payload | Document Type that contains the payload of the outbound MessageObject. |
Name | Description |
SAP:MessageHeader | Document Type that contains the message header of the reply MessageObject. The message header might be different than it was for the outbound MessageObject. |
SAP:ErrorHeader | Optional. Document Type that contains a description of the technical error, if a technical error occurred. The Document Type contains these fields: SAP:Code. Error code that consists of a category and an ID, separated by a period (for example, ROUTING.NO_RECEIVER_CASE_BE) See the SAP PI/PO Server documentation for a complete list of error codes.SAP:Text. Error message text. See the SAP PI/PO Server documentation for a complete list of messages. |
payload | Optional. Document Type that contains the results from the business partner, if you sent the outbound MessageObject synchronously. |