Specify the Orchestration Process When You Import

Improve performance and decrease the time it takes to create a sales order. You can specify the orchestration process name when you import a sales order through file-based data import (FBDI) or REST API instead of having to use a rule to assign the process.

Use this feature when you know which orchestration process you want to use and don't have complex business logic that requires you to use an assignment rule to select from different orchestration processes according to attribute values from the sales order.

• If you specify the orchestration process name for any line in the sales order, then Order Management won't call the assignment rule for any line in the order. So you must specify the orchestration process name for each line in the order.

• You must use only an assignment rule to assign the orchestration process for all order lines, or assign each line in your import payload when you import. If you use an assignment rule to assign an orchestration process to a sales order, then you must use that same rule to add a new line to the same order. You can't use the rule to assign the process and then at some later time import a new line where you specify the orchestration process in your import payload.

File-Based Data Import

Use the SourceSalesOrderImportTemplate.xlsm template.

Use the Process Name column in the DOO_ORDER_LINES_ALL worksheet sheet.

To get the template, go to File-Based Data Import (FBDI) for Oracle SCM. Locate the Order Management chapter, then click Import Sales Orders.

For details, see Overview of Importing Orders Into Order Management.

REST API

Use the salesOrdersForOrderHubRequests resource.

Here's an example payload. It assigns the fulfillment line to the ManualSchedulingProcess orchestration process.

"lines":[
{
"SourceTransactionLineId":"1",
"SourceTransactionLineNumber":"1",
"SourceTransactionScheduleId":"1",
"SourceScheduleNumber":"1",
"TransactionCategoryCode":"ORDER",
…
"OrchestrationProcessName": "ManualSchedulingProcess", // <= Use this code to specify the orchestration process name
…
}
]

For details and examples, go to REST API for Oracle Supply Chain Management Cloud, then expand Order Management > Sales Orders for Order Hub.

If you use REST API, you must enable a profile option:

1. Go to the Setup and Maintenance work area, click Tasks > Search, then search for Manage Profile Options.
2. On the Manage Profile Options page, in the search results, click Actions > New.
3. On the Create Profile Option page, set the values, then click Save and Close.

   Attribute	Value
   Profile Option Code	FOM_IMPORT_VIA_REST_BACKEND
   Application	Order Management
   Module	Manage Orders
   SQL Validation	select meaning, lookup_code from fnd_lookups where lookup_type='YES_NO'
   Start Date	Today or a date in the future.

4. In the Profile Option Levels area, set the values.

   Attribute	Value
   Level	Site
   Enabled	Contains a check mark.
   Updatable	Contains a check mark.

5. Click Save and Close.
6. On the Search page, search for Manage Administrator Profile Values.
7. On the Manage Administrator Profile Values page, search for the value.

   Attribute	Value
   Profile Option Code	FOM_IMPORT_VIA_REST_BACKEND

8. In the Profile Values area, click Actions > New, set the values, then click Save and Close.

   Attribute	Value
   Level	Site
   Profile Value	Yes

Order Management Extension

If you import through REST API, then use the OrchestrationProcessName attribute in your extension to specify the orchestration process name on the order line, and use the On-Save or On Start of Submission Request extension point. For example:

line.setAttribute("OrchestrationProcessName","ManualSchedulingProcess");

For details, see Overview of Creating Order Management Extensions.