Create an External Message Definition

You create an external message definition using the Manage Collaboration Message Definition task.

Take these steps:

1. In the Collaboration Messaging work area, click Manage External Message Definitions from the Tasks pane.

2. On the Manage External Message Definitions page, click Actions > Add Row and enter the required details, which are described in the next table.

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.
User Defined	Indicates that you created the 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.
Document 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 document subtype could be ProcessPurchaseOrder.
Version	The version of the messaging standard.
Identification XPath	The XPath to navigate to the document subtype specified in the XML payload. Note: If you leave the Identification XPath field blank, when the root element is the same for more than one message, Collaboration Messaging Framework searches for the Identification XPath to find the location of the document subtype in the payload to process the message. If the XPath is blank, the message isn't processed and an error is logged.
Message Identifier XPath	The XPath to navigate to the sender's message ID in the XML payload. Collaboration Messaging Framework logs the sender's message ID, which is displayed on the Manage Collaboration Messaging History page. Note: If you leave this field blank, Collaboration Messaging Framework, doesn't log the value of the sender's message identifier.
Trading Partner ID XPath	The XPath expression 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 XPath and the Trading Partner ID Type as specified by the Trading Partner ID Type XPath.
Trading Partner ID Type XPath	The XPath 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 XPath and the Trading Partner ID as specified by the Trading Partner ID XPath.