The analysis of the Order Import interface tables does not occur for each submission of the Order Import concurrent program; you must manually submit the Order Import Statistics concurrent program prior to submitting the Order Import concurrent program if you wish to optimize interface record processing. See: Order Import Concurrent Program.
Order Import is an Order Management Open Interface that consists of open interface tables and a set of APIs. Order Import can import new, change, and completed sales orders or returns from other applications such as a legacy system. The orders may come from any source such as EDI transactions that are processed by the Oracle e-Commerce Gateway or internal orders created for internal requisitions developed in Oracle Purchasing or returns.
Order Import features include validation and defaulting, processing constraint checks, applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting the orders in the base Order Management tables. Order Management checks all the data during the import process to ensure its validity within Order Management. Valid transactions are then converted into orders with lines, reservations, price adjustments, and sales credits in the base Order Management tables. Additionally, Order Import supports calculation of tax on freight charges associated with order header and lines if you have set the Invoice Freight as Revenue system parameter to Yes. Additionally, Order Import enables payment records to be imported by specifying the payment percentage and selecting the Defer Payment Processing flag.
You can use the Order Import Correction Payments window to examine the order and optionally correct data if it fails the import process. You can use the Error Message window to determine if your data failed to import.
Each time you run Order Import, Order Management produces a summary log file (concurrent request form) of information letting you know of the total number of orders that Order Import evaluates, and succeeded or failed.
Prerequisites and Set-Up
Before using this program to import orders, you should:
Ensure that if Multi-Org Access Control is enabled, you populate the ORG_ID column on the interface records. If the column is not populated then the records will be processed for your default Org if it is set via MO: Default Operating Unit.
Set up every aspect of Order Management that you want to use with imported orders, including customers, pricing, items, and bills.
Define and enable your Order Import sources using the Order Import Sources window.
Determine if you should submit the Order Import Statistics concurrent program.
If you have Multi-Org Access Control enabled, you can use Order Import to import Orders into all Operating Units accessible to you.
The following parameters affect the operation of the Order Import program:
Item Validation Organization: Determines the organization used for validating items and bill of material structures.
Reservation Time Fence: Controls automatic reservations during scheduling.
OM: Apply Automatic Attachments: This profile option determines whether rule-based attachments are applied without user intervention.
OM: Order Lines Threshold For Large Order Processing in Order Import: This profile option indicates the minimum number of lines in an order that are considered for large order processing in Order Import. Any order that contains order lines greater than what is entered in this profile option is considered a large order.
OM: Purge Records With No Org Specified: By default it will be set to Y. If the interface table contains data with no Operating Unit specified, and you run this program without specifying an Operating Unit (or specifying one that is the same as the Default Operating Unit), and this hidden parameter is set to Y, then the program will purge records that have no Operating Units specified.
You can setup your defaulting rules which allow you to default columns in the same way as for orders entered on-line. You can pass the column value Null to Order Import if you want the defaulting rules to populate the column. However, if the column is defined as Not Null or Mandatory column and the defaulting rules fail to default the column, for any reason, Order Import displays an error message without importing the order.
Oracle Purchasing uses Order Import to transfer requisitions for internally sourced products to Order Management. Once imported, the internal sales orders are processed similar to regular sales orders.
Note: When importing internal sales orders that contain order line items that require serial numbers, Order Import requires the associated items serial control attribute be set to: Dynamic at Sales Order Issue.
Note: You can create requisitions (with same number) in two different operating units.
Returns can be imported like a regular sales order. Once imported, RMAs orders and lines are processed using the Return specific Oracle Workflows.
Order Management provides you with the ability to import ATO and PTO configurations. You must supply a order line for the model and a order line for each option you want selected. Top model line ref need to be populated for all lines including the model line for importing configurations.
For more information on importing Configurations, see Oracle Order Management Open Interfaces, APIs, and Electronic Messages Manual.
For EDI orders, you can import valid and invalid configurations, however, you will not be able to book orders with invalid configurations.
You can import changes to orders that have been imported by passing all changed data through Order Import or simply make changes in the Order Pad. You can update or delete orders, order lines, price adjustments, and sales credits. You can use change sequence numbers to control the sequence of changes you want to make to orders. When you update line level information using Order Import, the import process checks if the Calculate Price flag is populated in the interface tables and honored if populated. Else, the application fetches the calculate price flag, unit list price, and unit selling price from the existing line and imports the order with appropriate values.
You can import grouped order lines, called sets, based on certain common attributes for a new or existing orders. You can also add a line to an existing set. You will need to provide the set ID or name in the Order Import tables. If that set already exists, the line will be included in the set. If it is a Customer Preference Set, you need to enter the set code in the Customer Preference Code field and not the set name or value.
However, if the set does not already exist, a new set will be created and the line will be added to the set. In addition, if any line attribute, which is also a set attribute, does not match with the set attribute value, the set attribute value will overwrite the line attribute.
You can import new, booked or closed orders. If an order is imported with an entry status of Booked, the order is automatically eligible to progress to the next step in the workflow cycle.
Order Import ensures that all required fields for entry or booking are validated appropriately as the orders are imported. Order Import imports the order in as Entered and attempts to book it. If any of the required fields for a booked order are not supplied, Order Management retains the order in the Entered status and notifies you of the error.
Note: Inventory information does not get updated during import of the closed order. If you need to update Inventory information, you have to perform additional customizations.
You can import an order within any valid order workflow activity. The order must be at the initial activity of Entered, Booked, or Closed. Orders imported using Order Import cannot be in the middle of a workflow activity.
Order Management uses the same customer, item pricing, and bill attribute validation and logic for imported orders as for orders entered in the Sales Orders window.
You need to define items using Oracle Inventory for items to be orderable via Order Import. You also need to define bills of material in Oracle Bills of Material for models if you have any complex items that customers can order in various configurations.
Order Import provides the ability to import an item specified in the following supplier, customer or generic formats:
Supplier Specific Internal Part number
Customer Specific Item number
Generic (depending on what you have set up in Oracle Inventory as cross-references):
CLEI (Common Language Equipment Identifier)
EAN (European Article Number) code
ISBN (International Standard Book Number)
JAN (Japanese Article Number) code
UPC (Universal Product code) code
Order Import checks the processing constraints you have defined in Order Management to assure that any operation such as insert, update, and delete are acceptable by your security standards. Order Import displays an error message if it encounters a processing constraint that has been violated.
Once the data is corrected, the ERROR_FLAG for the record is updated to N. You can set the REJECT_FLAG to Y for headers and line in case your data cannot be corrected by using the Order Import Corrections window.
You can import orders with any external source defined in the Order Import Sources form. Order Import allows you to capture order information and import data into Oracle Order Management for processing. You can import orders with any entry status. Imported orders can be queried and modified using the Sales Order window in Order Management.
If you wish to import order statistics, submit the Order Import statistics concurrent program.
See: Order Import Statistics Concurrent Program.
Key Change Project
Sold To Org Id, Sold To Org, and Change Sequence are now parameters for running the Order Import Concurrent program. This will allow users to import all the Orders for a specific Customer and also enable users to import an order with a specific Change Sequence for a given Customer and Reference. These new parameters to the Concurrent program will be enabled, but will not be displayed by default.
The functionality is controlled via a new profile option called OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer. If this profile is set to Yes the new functionality will be turned on and the customer will become a part of the order import key. If this profile is set to No or not set at all (default) order import will function as it did previously.
Performance Enhancement
With the introduction of the new queueing method, Order Import will now only assign an order to a child request once that request has finished processing its previous order. This will help to maximize throughput as available child processes will always be assigned orders to process. Previously, while other processes may have completed already, orders could still be waiting in the queue of a child request that was taking longer to complete processing (perhaps because of a particularly large order). Now an order will only be assigned to a particular child request once that request is ready to process it.
The default behavior of Order Import will be the new functionality, but customers will be able to revert to the old functionality when importing orders through the Order Import Concurrent Program form by enabling the display of the new parameter "Enable Single Line Queue" and changing the value from the default of Yes to No.
Additional Considerations
If the calculate price flag is send as 'N', user of the order import/HVOP should pass the Price List, Unit Selling and List price too. If they do not pass these values import will fail.
Navigate to the Order Import Request window.
The Parameters window appears.
Select the Operating Unit from which you want to import orders. If you want to import orders across multiple operating units accessible to you do not enter a value in the field.
Order Source: Select a specific Order Import source that you have defined in the Order Import Sources window so that only records with that source are processed, or leave this parameter blank so that all enabled sources are processed for data existing in the interface tables. This field is optional.
Order Reference: You can enter the System Document Reference if you want to run Order Import for a specific order. This field is optional.
Validate Only (Yes/No): Select whether to validate only the data in the interface tables. If Yes, the order will be validated, but not imported into the base orders tables. The default value is No. This field is required.
Note: After validation, if you re-run the Order Import with No as the Validate Only option, the application does not pick up any previously validated data. To re-import the order with No as the option for Validate Only, navigate to the Corrections window and manually delete the previously generated request id so that the new request id is populated. Else, you can directly revalidate from the Corrections window and later import the order directly from the Corrections window.
Instances: Enter the number of instances (child requests) for the Order Import process. Four appears by default. This field is optional.
The Instances field is used along with large orders (orders that contain order lines that are greater than that entered on the profile option: OM: Order Lines Threshold For Large Order Processing in Order Import) and the parameter Enable Single Line Queue for Instances set to the value of No. Then when you run the Order Import process for large and small orders, the large orders are processed across multiple child requests (instances) spawned instead of a single child request. During parent request execution, the order header is created first and then all the lines are assigned to child requests which are added to the order header created through the parent request. After the lines are added successfully through child requests, the parent request resumes and the data in the interface is deleted.
Click OK, then Click Submit.
Note: Please refer to the Oracle Order Management Open Interfaces, API, & Electronic Messaging Guide for more information on hidden parameters like Default Operating Unit and how to view them in the concurrent program window.
Processing Results
Each time you run Order Import, Order Management automatically generates an Order Import processing results summary log which identifies the total number of successful and failed imported orders.
A successful completion does not always mean that the order is imported, you must rely on the order import status, for example the number of orders imported.