Use FBDI and REST API to Import Large Volumes of Sales Orders

Use the Import and Fulfill Large Volumes of Sales Orders opt-in feature with file based data import (FBDI) when you have a large volume of sales orders to import. Using them together improves efficiency and performance.

You can import:

• Standard items, models, kits, covered items, and coverage items.
• Items that you price in Pricing Administration or that you price in your source system.
• Referenced and unreferenced returns.
• Change orders and revisions. You can import only the order line or the attributes that you changed. You don't have to import the entire order or all the attributes.

Import different kinds of entities.

• Order headers, orders lines, and addresses
• Charges and charge components
• Manual price adjustments
• Extensible flexfields on the order leader and order line
• Sales credits and billing plans
• Lot serial details
• Payments
• Transaction attributes

Try it.

1. Enable the Order Management feature.
   • Go to the Setup and Maintenance work area.
   • Select the Order Management offering.
   • Click Change Feature Opt In.
   • On the Opt In page, in the row that has Order Management in the Name column, click the pencil.
   • On the Edit Features page, add a check mark to the Import and Fulfill Large Volumes of Sales Order feature.

     You can't opt out of this feature after you opt in and submit a sales order. At this point, you're committed to using the feature.

   • Click Done.
2. Enable the Order Promising feature.
   • Select the Supply Chain Planning offering.
   • Click Change Feature Opt In.
   • On the Opt In page, in the row that has Global Order Promising in the Name column, click the pencil.
   • On the Edit Features page, add a check mark to the High Volume Order Promising feature.
   • Click Done.
3. Use file-based data import to import your source orders.

The import will automatically route your import requests through REST API.

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

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

Guidelines

Apply these guidelines when you use the Import and Fulfill Large Volumes of Sales Order Opt-in Feature.

Functionality	Import Without the Feature	Import With the Feature
Apply Business Rules	The import will apply your pretransformation, product transformation, and posttransformation rules on your import data.	The import won't apply these rules. However, you can create an order management extension to implement the logic that you might normally get from these rule. If you do create an extension, then set it up to run on the On Save extension point or on the On Start of Submission Request extension point.
Create a Customer	You can create a customer during the import.	You can't create a customer during the import. You can't use the Create Customer Information Flag attribute to create a customer. If you must create a customer when you import, then we recommend that you don't enable the opt-in but instead import through file-based data import without REST API, or import only through REST API. For details about this attribute, see Import Customer Data for Your Sales Orders.
Set Default Values	The import attempts to set default values for attributes that contain customer details just like the Order Management work area does when you create a sales order. Assume you import only the Sold-to Party but not the Sold-to Contact, Ship-to Site, or Contact Point. REST API will use the value in Sold-to Party to set the default value for Sold-to Contact, Ship-to Site, and Contact Point according to your setup in Customer Data Management.	The import won't set default values for attributes that contain customer details. For details about Customer Data Management and the party model, see Overview of Displaying Customer Details on Sales Orders.
Cascade Values	The import cascades the values for attributes that contain billing and fulfillment details from the order header to the order lines just like the Order Management work area does when you create a sales order, such as ship-to attributes and bill-to attributes. The import also cascades attributes from the root line of a configured item to the child lines of that item, including values from the segment of an extensible flexfield.	The import won't cascade any of these values. Your import template must contain all of them.
Use Case Sensitive Values	The attribute values in your import don't have to use the same upper case and lower case values that the Oracle database uses.	The attribute values in your import must use the same upper case and lower case values that the Oracle database uses. For example, if the Product Number attribute in the Oracle database contains the value AS54888, then the Product Number attribute on the DOO_ORDER_LINES_ALL_INT worksheet of your import template must also contain AS54888. Your import template must not contain as54888, aS54888, As54888, and so on.
Cross-Reference Attributes	You can import your own custom values.	You can't import your own custom values. If Order Management cross-references an attribute, then your import must use the same value that the Order Orchestration and Planning Data Repository contains for that attribute. Assume you want to use a truck to ship the order line. The Order Orchestration and Planning Data Repository contains the value FEI TRUCK for the ShippingServiceLevel attribute, so the Shipping Service Level attribute on the DOO_ORDER_LINES_ALL_INT worksheet of your import template must also contain FEI TRUCK. For details, see Integrate Names and Codes Between Source Systems and Order Management.
Revise Your Sales Order	You must reimport the entire sales order, including the changes for the revision.	You only have to import the values that you're changing and a few other values that identify the order. Assume you need to update the charge component on an order line. Your payload only has to include the revised value for the charge component and a few other attributes that identify parts of the sales order, such as the line that contains the charge, and values that identify the order header.
Report Errors	Your import stops when it encounters the first error, and reports only that error.	REST API continues to process your import even after it encounters the first error, then reports all the errors that it found.