Create an External Message Definition

You create an external message definition using the B2B Message Definitions task.

Follow these steps:

1. In the Collaboration Messaging work area, select B2B Message Definitions from the Tasks pane.

2. Select the External Message Definitions tab.

3. Click Save and Close.

   The message definition name is suffixed with _CUST.

After you create an external message definition, you create a collaboration message definition and upload an XSL file for message transformation from the new external message definition to the collaboration document using the Manage Collaboration Message Definition task.

This table describes the fields you use to create an external message definition.

Field	Description
Name	The name that you give to your external message definition.
Document Type	Standards neutral representation of a message, for example, the document created or received by Oracle Fusion applications such as Process Purchase Order.
Message Type	The root element of the XML payload. It is associated with a messaging standard and version.
Messaging Standard	List of accepted message formats. You can add your own standards.
Message Subtype	The type of the root element that defines the XML format of the message, for example, the root element of the payload could be Collaboration Message and the message subtype could be ProcessPurchaseOrder.
Version	The version of the messaging standard.
Message Subtype Identification Path	The path to navigate to the document subtype specified in the XML payload. Note: If you leave the Message Subtype Identification Path field blank, when the root element is the same for more than one message, B2B Messaging searches for the Message Subtype Identification Path to find the location of the message subtype in the payload to process the message. If the path is blank, the message isn't processed and an error is logged.
Sender Message Identifier Path	The path to navigate to the sender's message ID in the XML payload. B2B Messaging logs the sender's message ID, which is displayed on the B2B Messages page. Note: If you leave this field blank, B2B Messaging doesn't log the value of the sender's message identifier.
Trading Partner ID Path	The path that identifies the location of the Trading Partner ID in an XML payload. Note: For inbound messages from Oracle B2B, if you don't specify the HTTP headers SENDER_ID and SENDER_ID_TYPE, you may include the Trading Partner ID in the payload as specified by this path and the Trading Partner ID Type as specified by the Trading Partner ID Type path.
Trading Partner ID Type Path	The path expression that identifies the location of the Trading Partner ID Type in an XML payload. Note: For inbound messages from Oracle B2B, if you don't specify the HTTP headers SENDER_ID and SENDER_ID_TYPE, you may include the Trading Partner ID Type in the payload as specified by this path and the Trading Partner ID as specified by the Trading Partner ID path.
Object Path	A path that identifies the location of the object key in an XML payload. For example, invoice number is the object key in the invoice XML file.
Reference Object Path	A path that identifies the location of the reference object key in an XML payload. For example, purchase order number is the reference object key in the invoice inbound XML file or in the shipment inbound XML file.
PO Line Path	Path that identifies order lines for process and change purchase order in an XML payload.