How You Configure Collaboration Messaging Framework

The first configuration task you need to perform is Manage Collaboration Messaging Configuration task.

This configuration task enables the business process, procure to pay, order to cash or supply chain operations, that exchange B2B messages for and define other configuration parameters specific to the B2B documents. The Global Sender ID to identify the sender of all outbound documents is also defined in this section.

A number of predefined service providers are set up in Collaboration Messaging Framework. If you use one of these predefined service providers, all documents and messages are already set up. You need to define trading partners that reference the predefined service provider using the Manage B2B Trading Partners task. Select the documents you want to exchange. After you define your trading partners and select the documents that you want to exchange, you need to associate your trading partners to the customers and suppliers that have been set up in Oracle Fusion applications. Depending on the business process you set up, this association is made using one of these tasks:

• Set up your suppliers for your procure-to-pay process in Oracle Fusion Procurement or using the Collaboration Messaging Framework task Manage Supplier B2B Configuration for each supplier site.

• Set up your suppliers for your supplier collaboration process using the Collaboration Messaging Framework task Manage Supplier B2B Configuration for each supplier site.

• Set up your customers for your order-to-cash business process and, in particular, for ordering and shipping at the customer level using the Manage Customer Collaboration Configuration task in Collaboration Messaging Framework.

• Set up your customers for your order-to-cash business process and, in particular, for invoicing, using the Manage Customer Account Collaboration Configuration task in Collaboration Messaging Framework.

The trading partners you set up are associated with the customer or supplier and the documents that are to be exchanged with each of them are selected.

You can perform other optional setup tasks based on your needs. These include mapping your values for specific data elements within Oracle Fusion applications to the values of your trading partners for the same data elements. For example, your trading partner may use "Massachusetts" while you use "MA" for the name of the state. You can set up this mapping using the Manage Collaboration Messaging Domain Value Map task. You may also require a default value to be specified for a particular field or indicate that the field must have a value in an inbound or outbound message and you do this using the Setup Messaging Processing Rules option. You can set up B2B location codes to identify ship-to and bill-to locations for inbound order-to-cash B2B messages. The codes can be used as an alternative to providing the full ship-to and bill-to addresses. If B2B location codes are set up, then when an inbound order received has codes specified for the bill-to and ship-to locations, the addresses are identified and included in the message payload.

If you don't use one of the predefined service providers, then you need to create one using the Manage Collaboration Messaging Service Providers task, define the delivery methods, and define the inbound and outbound messages that you want to exchange.

If you want to exchange B2B messages directly with your customers and suppliers, you need to create trading partners using the Manage B2B Trading Partners task, define the delivery methods for them, and define the inbound and outbound messages that you want to exchange.

Collaboration Messaging Framework provides a number of predefined message definitions. If you want to exchange a message that's not predefined, you have to go through the setup and configuration process explained next.

You have to set up external message definitions to represent the format that you receive messages from your trading partners in or the format in which you need to send messages to them. The external messages are transformed to a common format that Collaboration Messaging Framework uses to send and receive the messages to Oracle Fusion applications. You can create a collaboration message definition to map the format of the external message definition to the Oracle Fusion format (using an XSL file). You can define the mapping of an existing message definition by duplicating the message definition and modifying the associated XSL file. Use the Export Transformation Package option from the Manage Collaboration Message Definitions task to download the XSL file.

After you create your message definitions, you can include them in the inbound and outbound collaboration messages that you define for your user-defined service provider or your trading partner.

After your setup is complete, you can verify it using the Validate Inbound Collaboration Messaging Setup and Validate Outbound Collaboration Messaging Setup tasks. You can handle the daily management of your B2B message exchange, including searching for messages, reviewing the details of particular messages such as status or errors encountered using the Manage Collaboration Messaging History task.