Define Outbound Messages for a Trading Partner Without a Service Provider

You must define outbound collaboration messages that a trading partner can send to other trading partners.

You must select the collaboration message definition that corresponds to the document that want to exchange with other trading partners. There could be multiple collaboration message definitions for a document. However, only one definition can be active at a time. And every outbound message must have a delivery method specified.

Take these steps:

1. On the Edit Trading Partner page, click the Outbound Collaboration Messages tab.

2. Click Actions > Add Row.

3. Enter or select values for the required fields: Name, Collaboration Message Definition, and Status.

4. Click Save and Close.

This table describes the fields used to define an outbound message:

Field	Description
Name	Unique name for the outbound message record.
Collaboration Message Definition	There may be multiple message definitions for a specific document, so you have to select the one you want to use. Collaboration Message Definition points to an XSL file that's used to transform the outbound message from the Oracle application message type to the external message type.
Delivery Method Name	The name of the delivery method for the outbound message. The drop-down list shows the delivery methods defined for the service provider.
Alternate Delivery Method	You can optionally specify an alternate delivery method for the outbound message. During processing, when the maximum message size for the primary delivery method is reached, Collaboration Messaging Framework processes the message using the alternate delivery method. Note: You can specify the size limitation for each delivery method type in the Setup and Maintenance work area: Manage Collaboration Messaging Configuration > General Set Up.
Attachment Location	You can specify where the outbound message is to be located: In payload: The attachment is sent as embedded binary content within the payload element of the B2B In message: The attachment is sent in the attachment element of the B2B message. MIME part: The attachment is sent as a MIME part outside of the B2B message. The options for sending attachments depend on the delivery method and the external message type that are being used to exchange messages with the trading partner or service provider.
Status	Valid values are: Active or Inactive: You can use different collaboration messages for the same document but only one of them can be active at one time. Loopback: This option enables you to process the message without actually delivering it to your trading partner so that you can test the setup.
Retention Duration	You can specify the duration for which outbound messages must be stored before they're deleted. If retention duration is defined for a service provider, it's applicable to messages exchanged with all trading partners that are set up for that service provider.
Retention Duration Unit	You can specify the unit of the retention duration in days, weeks, months, or years.
External Message Type	The definition of the XML format of the message. It's always associated with a messaging standard and a version. It's the root element of the XML payload.
Document Type	A business document created or received by Oracle Fusion applications.
Document Sub Type	A unique value to identify a message when many have the same root element.
Version	Version of the messaging standard used, for example OAG 10.1.
Messaging Standard	The messaging format standard. For example cXML.
Collaboration Object	The object for the document specified. For example, for PROCESS_PO_OUT, the collaboration object is Purchase Order.
Collaboration Business Process	The collaboration business process for the selected document. For example, PROCESS_PO_OUT is for the object Purchase Order and the collaboration business process procure to pay.