Use a Service Mapping to Integrate Order Management with Other Oracle Applications

Set up Order Management so it uses a view object to integrate with Oracle Receivables, Oracle Shipping, Oracle Receiving, or Oracle Procurement.

Assume you must.

• Integrate ContractStartDate in Order Management with RuleStartDate in Oracle Receivables

• Integrate ContractEndDate in Order Management with RuleEndDate in Oracle Receivables

You will modify the predefined FulfillmentIntegration service mapping so it uses these cross-references.

This topic uses example values. You might need different values, depending on your business requirements.

Try it.

1. Make sure you have the privileges that you need to administer Order Management.

2. Create a sand box. For details, see Create a Sandbox So You Can Edit Service Mappings.

3. Go to the Pricing Administration work area.

   You use the Pricing Administration work area to set up an integration algorithm, but you aren't setting up pricing. Order Management leverages the Pricing Administration work area because an integration algorithm's structure and logic is very similar to a pricing algorithm. If you sign in with:

   • Privileges That Allow You to Administer Oracle Order Management . The Pricing Administration work area displays only integration algorithms.

   • Privileges That Allow You to Administer Oracle Pricing. the Pricing Administration work area displays only pricing algorithms.

4. Click Tasks, then, under Order Management Configuration, click Manage Service Mappings.

5. On the Manage Service Mappings page, in the Name column, click FulfillmentIntegration.

   Notice the entities, such as ARInterfaceLine, and attributes, such as AccountRuleDuration. The FulfillmentIntegration service mapping comes predefined with these entities and attributes so you can use them to add attributes when you integrate Order Management with these Oracle applications.

   Oracle Application	Example Entities
   Oracle Receivables	ARInterfaceLine
   Oracle Shipping	ShipmentRequestHeader ShipmentRequestLine
   Oracle Receiving	ReceiptAdvice ReceiptAdviceLine ReceiptAdviceLineLot ReceiptAdviceLineLotWithSerials
   Oracle Procurement	PurchaseRequestHeader PurchaseRequestLine PurchaseRequestConfig

6. Click Sources.

   In this example, you examine the entity or the view object that defines the view object as FulfillLineVO, and then map an attribute of this entity or view object from the fulfillment line.

   Note that Order Management uses this hierarchy.

   Sales order header
   	fulfillLine
   		Fulfill_line Details

   ARLine is on the same level as fulfillLine.

   The Entity Mappings tab lists entities, each entity references a view object, and each entity on the Attribute Mappings tab also references one or more attributes. You will create a map that references one of these entities from this view object without using an integration algorithm.

   However, if you must map an attribute from some other entity that doesn't reside at the same hierarchy level, then you must use an integration algorithm. For example, if an attribute references an extensible flexfield from the order header or the fulfillment line, then you must use an integration algorithm.

   Other Oracle Applications use a similar hierarchy. For example, here's that hierarchy that Purchasing uses for a purchase order.

   Purchase order
   	fulfillLine
   		purchaseLine

   Here's the hierarchy that Purchasing uses for shipping.

   Shipping header
   	shipping line
   		fulfillLine
   

   Here's the hierarchy that Purchasing uses for the receiving receipt.

   Receipt header
   	ReceiptLine
   		FulfillLine
   			Lot or lot serial details

7. In the InvoiceSources - Details area, click the row that contains ARInterfaceLine in the Entity attribute.

8. In the ARInterfaceLine - Details area, add values, then click Save.

   Attribute	View Object Attribute
   RuleStartDate	ContractStartDate
   RuleEndDate	ContractEndDate

The RuleStartDate and RuleEndDate are now integrated to reference the view objects that you specified. Here's what Order Management does at run time.

• Get the value of the ContractStartDate attribute from the Order Management work area, then display it in the RuleStartDate attribute in Oracle Receivables.

• Get the value of ContractEndDate from the Order Management work area, then display it in the RuleEndDate attribute in Oracle Receivables.

You can use Expression Language (EL) in the Expression column to implement logic or a constant value. For example, you can implement this logic.

• If the value of variable x is greater than the value of variable y, then populate an attribute.