Define Inbound Collaboration Messages

Unlike with outbound messages, you don't need to identify how an inbound message is received.

So let's see how we define inbound collaboration messages:

1. On the Edit Collaboration Messaging Service Provider page, go to the Inbound Collaboration Messages tab and click Actions > Add Row.

2. Enter the required values for the definition and click Save and Close.

This table describes the fields you use to define an inbound message:

Field	Description
Name	Unique name for the inbound message.
Collaboration Message Definition	There may be multiple message definitions for a specific document type, 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 external message to the Oracle application message type.
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.
Application Partner Code XPath	Identifies the location of an element in the XML message that contains the application partner code that's used to identify the supplier site used for processing an inbound invoice or shipment. The collaboration message definition has the Application Partner Code XPath but you can change it here.
Retention Duration	You can specify the duration for which inbound 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 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.
Sender Role	Role of the sender of the document, customer or supplier.
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.
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_INVOICE_IN is for the object Invoice and the collaboration business process procure to pay.

How You View Domain Value Maps

When you exchange messages with your trading partners, you might use different values than your trading partners for the same data element. For example, you might represent the state, Massachusetts, with its full name, while your trading partner may represent it with an abbreviation, MA. This mapping of data elements from the Collaboration Messaging Framework value to the trading partner value is defined using the Manage Collaboration Messaging Domain Value Map task.

Domain value maps are assigned within the XSL file for predefined message definitions. You can see which domain values are applicable for a message definition for a particular partner or service provider on the Edit Collaboration Messaging Service Provider page for both Outbound and Inbound messages by clicking Actions > View Domain Value Maps.