Map Attributes from Your Sales Order to Your Purchase Request and Purchase Order

You can use a view link to create a map between different levels of a supply order to a purchase order, such as mapping an attribute on the supply header to an attribute on the purchase request line.

Use a view link to:

• Map attributes on a work order and a sales order, including an extensible flexfield, without having to use an integration algorithm.
• Map an attribute on one level of a supply order to an attribute on another level of the sales order, purchase order, or work order. For example, map an attribute that sits on the supply order header to an attribute that sits on a sales order line.
• Map an attribute on a sales order in a back-to-back flow or to an attribute on a work order in an outside processing flow.

You can also use a predefined source in the Sources area of the SupplyOrchestration service mapping to map an entity on the supply order to an entity on a sales order, purchase order, or work order. However, you can only map a single relationship between one entity and another entity. For example, you can't use a predefined source to map between an attribute on the supply order and another attribute on the purchase order. Instead, you can use a view link to do this.

Let's say you need to map the SupplyOrderReferenceNumber attribute on the supply order in Supply Chain Orchestration to the WorkOrderNumber attribute of the work order in Oracle Manufacturing. Here's how:

1. Enter your sandbox. For details, see Create a Sandbox So You Can Edit Service Mappings.
2. Go to the Supply Orchestration work area, then click Tasks > Manage Service Mappings.
3. On the Manage Service Mappings page, click SupplyOrchestration.
4. On the Edit Service Mapping page, click Sources, then use Query By Example to filter the Source attribute for ManufactureRequestSource.
5. On the Entity Mappings tab, use Query By Example to filter the Entity attribute for WorkOrderRequest.
6. In the Attribute Mappings tab, click Create a Sandbox So You Can Edit Service Mappings, then set the values.

   Attribute	Value
   Attribute	WorkOrderNumber This is the name of the attribute that you're mapping to. In this example, you're mapping to the WorkOrderNumber attribute on the work order.
   Expression	return SupplyHeader.InterfaceSourceCode=='SCO'||'DOO'||'YPS'||'INV'?SupplyHeader.InterfaceSourceCode+'-'+SupplyHeader.SupplyOrderReferenceNumber where SupplyHeader is the name of the view link. SupplyOrderReferenceNumber is the name of the attribute on the supply order that you're mapping from. SCO is the product short code for Oracle Supply Chain Orchestration. DOO is the product short code for Oracle Distributed Order Orchestration. Distributed Order Orchestration is another name Oracle Order Management. They mean the same thing. YPS is the product short code for Oracle Supply Planning INV is the product short code for Oracle Inventory Management

This example works for Manufacturing. If you need to integrate with Procurement, you can put an expression into a time stamp descriptive flexfield on the purchase request line:

 return SupplyTrackingLine.NeedByDate;

Extensible Flexfields

If your link involves an extensible flexfield that's on the:

• Order header, then you must link to an attribute on the purchase request header.
• Order line, then you must use link to an attribute on purchase request line.