Overview of Integrating Order Management with Other Oracle Applications

Integrate Order Management to send details to some other Oracle application.

Use a predefined attribute to send details, or create an extensible flexfield in Order Management to store them, then map it to some other Oracle application.

For example:

Oracle Application	Description
Oracle Receivables	Map the Purchase Order Line Number attribute on a fulfillment line in Order Management (CUSTOMER_PO_LINE_NUMBER) to the Invoice Line Level descriptive flexfieldin Oracle Receivables. Order Management doesn't come predefined to display this attribute. Create an extensible flexfield on the order header or order line in Order Management. Map this flexfield to an interface column or descriptive flexfield in Oracle Receivables. Send a concatenated value that represents the attributes of a covered item, such as Description, Start Date, or End Date, to the TranslatedDesription attribute in Oracle Receivables. Use an interface column in Oracle Receivables to send the data. Send a covered item description, such as hardware, with coverage lines. Send freight charges that apply for a covered item as a separate line so you can invoice freight by itself.
Oracle Procurement	Create an extensible flexfield on a fulfillment line in Order Management to capture the price for the item. You can send the price that you negotiate with your supplier to the purchase request in Oracle Procurement. Order Management comes predefined to send a set of attributes to your fulfillment system for a purchase order in a drop ship flow. You can use a service mapping to send an attribute that isn't predefined. For example, send a price that you negotiate with your supplier during drop ship, or send a deliver-to address to your supplier during drop ship.
Oracle Receiving	Create extensible flexfields on the fulfillment line in Order Management to capture lot details and serial details. Send these details to the receiving request in Oracle Receiving.
Oracle Shipping	Create an extensible flexfield on a fulfillment line in Order Management to capture shipment details. Send these details to a descriptive flexfield in Oracle Shipping. Use a descriptive flexfield to send details to your receiving clerk for a sales order that includes a return material authorization.

How it Works

Note

1. Capture order details, such as in a sales order that you create in Order Management.

2. Use a predefined task type in the integration step of your orchestration process to send details to your fulfillment system.

3. Did you enable the Enable Custom Payloads for Downstream Integration feature?

   Enabled	Description
   Yes	Use the service mapping. You can set up the payload to integrate with your fulfillment systems.
   No	Use the predefined SDO payload (service data object) and proceed to fulfillment. For an example that uses an SDO, see Include Price, Discounts, and Shipping Charges in Your Payloads.

4. Call the service mapping that you set up that maps attributes between Order Management and your fulfillment system.

5. Did you create an integration algorithm?

   Created an Integration Algorithm	Value
   Yes	Call it. Use the integration algorithm to do more complex logic, as necessary.
   No	Use only the service mapping to create the payload.

6. Use the service mapping and the integration algorithm to create the payload.

Note

• You set up an integration algorithm and a service mapping when you create the integration.

• An integration algorithm uses logic that's similar to a pricing algorithm.

• A service mapping that you set up for an integration uses logic that's similar to the service mapping that you set up for pricing.

• You use the Pricing Administration work area to set up the integration algorithm and the service mapping that you use for integration. However, your service mapping and integration algorithm are completely separate from Pricing. You use Pricing Administration only to leverage some of the logic that Pricing uses for its service mappings and integration algorithms.

• An integration algorithm and the service mapping that you set up for an integration doesn't affect pricing.