Service mappings are used to integrate Order Management with other Oracle applications by mapping attributes from a sales order to a purchase order. Service mappings enable you to pass order information from a sales order to a purchase order document, such as supplier, item, quantity, price, and so on. To use service mappings, you need three supply chain modules: Supply Chain Orchestration Cloud, Procurement Cloud, and Order Management Cloud. Supply Chain Orchestration Cloud is the module that creates and manages the purchase order document based on the sales order information. Procurement Cloud is the module that provides the functionality to manage suppliers, purchase agreements, and requisitions. Order Management Cloud is the module that captures and fulfills the sales order.
:
Use a Service Mapping to Integrate Order Management with Other Oracle Applications Overview of Order Management
[Overview of Supply Chain Orchestration]
[Overview of Procurement]

The Manage Supply executing document creation rule is the configuration that is required to enable the warehouse user to have visibility of both the Transfer Orders and the Sales Orders. This rule determines the type of supply order that is created for each demand line, such as a transfer order, a purchase order, or a work order. You can update this rule to specify the conditions and actions for creating transfer orders for internal material transfers between warehouses1. You can also use this rule to combine visibility of internal and external orders by sending transfer orders to Oracle Order Management Cloud2.
:
Manage Supply Executing Document Creation Rule
Oracle Supply Chain Management Cloud: Order to Cash Release 11 RCD

This is the correct sequence of the process to update project attributes on transfer orders using file-based data import template.A transfer order is a document that initiates the movement of material between warehouses within the enterprise1.Project attributes are the information that identifies the project, task, and expenditure type for each transfer order line2.You can use file-based data import template to update project attributes on transfer orders by following these steps3:
* SCO gets default values for the project attributes not imported: Supply Chain Orchestration (SCO) is a service that orchestrates the fulfillment of supply requests from various sources, such as sales orders, planning recommendations, or inventory replenishment. SCO gets the default values for the project attributes that are not imported from the file-based data import template. The default values are derived from the project defaulting and enrichment rules that you set up in the Manage Supply Order Defaulting and Enrichment Rules task.
* SCO performs a project accounting transaction control (PATC): SCO performs a validation of the project attributes against the project accounting transaction control (PATC) rules that you define in the Manage Project Transaction Sources task. PATC rules determine whether the project attributes are valid and consistent for each transfer order line. If the project attributes pass the validation, SCO sends them to Inventory Management for transfer order creation. If the project attributes fail the validation, SCO rejects them and logs the errors in the Supply Chain Orchestration Interface table.
* SCO sends validated attributes to Inventory Management for transfer order: SCO sends the validated project attributes along with other transfer order information to Inventory Management for transfer order creation. Inventory Management is a service that manages the flow of material within and across warehouses. Inventory Management creates the transfer order based on the information received from SCO and assigns a unique document number to it.
* Inventory management updates transfer order with new attributes: Inventory Management updates the transfer order with the new project attributes that are imported from the file-based data import template.
You can view the updated project attributes on the transfer order lines in the Manage Transfer Orders page in the Inventory Management work area.
:
Transfer Order
Project Attributes
Update Project Attributes on Transfer Orders Using File-Based Data Import
[Supply Chain Orchestration]
[Manage Supply Order Defaulting and Enrichment Rules]
[Manage Project Transaction Sources]
[Supply Chain Orchestration Interface]
[Inventory Management]
[Create Transfer Orders]
[Manage Transfer Orders]

A pricing strategy is a pricing entity that defines the overall pricing approach for a market segment. A pricing strategy consists of a header and one or more pricing segments.The header contains the general information and settings for the pricing strategy, such as the name, description, objective, business unit, default currency, start date, and end date1.When creating a pricing strategy header, the following fields are required2:
* Name: The name of the pricing strategy. It must be unique within the pricing business unit.
* Business Unit: The business unit that owns the pricing strategy. It determines the scope and visibility of the pricing strategy.
* Default Currency: The currency that is used for the pricing strategy. It is used to convert the prices of the items that are priced in different currencies.
* Start Date: The date when the pricing strategy becomes effective. It cannot be earlier than the current date.
:
Overview of Pricing Entities
Create Pricing Strategy Headers