Define Outbound Collaboration Messages
You must define outbound collaboration messages that your service provider can send to your trading partners.
You must select the collaboration message definition that corresponds to the document that the service provider will exchange for you. There could be multiple collaboration message definitions for a document. For example, you might want to define your data mapping for a predefined message using another message definition. Remember, though, that only one definition can be active at a time. And, every outbound message must have a delivery method specified.
So let's see how we define outbound collaboration messages:
-
On the Edit Collaboration Messaging Service Provider page, go to the Outbound Collaboration Messages tab and click Actions > Add Row.
-
Enter the required values for the definition and 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:
|
Status |
Valid values are:
|
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. |