Example of an Outbound Mapping Service: Initiator (Sender)
If you are the initiator/sender and are implementing a version of the OrderCreate process, the outbound mapping service might look like the following figure. For further explanation, see the text that follows the figure.
Example of an Outbound Mapping Service: Initiator/Sender
Under the Pipeline Out heading, in the documents\Payload IData object, the OrderCreate not in parentheses is the IData object, or Chem eStandards payload, being sent to the trading partner and the OrderCreate in parentheses is the IS document type that defines the Chem eStandards payload. The name of the IData object is case sensitive.
Important:
As a general convention, the name of the IData object should be the same (including the case) as the name of the IS document type. If not, the validation on the receiver's end will fail. Using the above figure as an example, the receiver's Chem eStandards‐compliant server will expect the name of the incoming Chem eStandards payload to have a Chem eStandards name of OrderCreate.
