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 date 1 . When creating a pricing strategy header, the following fields are required 2 :

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.

References :

Overview of Pricing Entities

Create Pricing Strategy Headers

A rule that you can set on an orchestration process step that specifies the adjustments to make when an order changes. Undo, Redo, Update, Cancel, and None are each an example of a compensation pattern. For example, assume the compensation pattern for a Create Shipment step is Redo, and that this step calls the Cancel service and the Create service. If Order Management receives a change order that includes a new warehouse for this step, then it runs the Cancel service and the Create service again.

You can enable the Replan Instantly feature when you define an orchestration process. It replans the orchestration process immediately after this process completes the orchestration process step, and then displays the revised order data according to the replanning work that it does. It is recommended that you use Replan Instantly only for high priority sales orders, or with sales orders that include a jeopardy threshold of less than one day. For performance reasons, it is recommended that you do not use it with an orchestration process step that is long or complex. If Replan Instantly does not contain a check mark, then Order Management updates the planning data only during the scheduled replanning.

https://docs.oracle.com/en/cloud/saas/supply-chain-management/r13-update17d/faiom/setting-up-orchestration- processes.html#FAIOM211469

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 enterprise 1 . Project attributes are the information that identifies the project, task, and expenditure type for each transfer order line 2 . You can use file-based data import template to update project attributes on transfer orders by following these steps 3 :

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.

References :

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]

Future supply can include the supply that results from planned orders of three types: make, buy, or transfer.