Import Orders

When to Use

Use this process when you have to perform these tasks:

Perform an initial load of purchase orders from your legacy application to Oracle Cloud.
Import purchase orders from an external application to Oracle Cloud.
Add new lines to existing purchase orders.

Before you run the Import process, you must first load the relevant information into the appropriate interface using File-Based Date Import (FBDI).

Privileges Required

PO_IMPORT_PURCHASE_ORDER_PRIV
PO_BYPASS_PURCHASE_ORDER_APPROVAL_PRIV (required for bypassing approvals)

Specifications

Review the following before setting up this scheduled process:

Specification	Description
Job Type	Scheduled.
Frequency	You are encouraged to schedule the process to run at least once per day. The process can be run more than once per day, but you should avoid scheduling processes more frequently than necessary for your business purposes. Avoid scheduling the process on a frequency that might overlap. Allow for a lag between the end of each scheduled process and the start of the next scheduled process.
Time of Day	Choose the time of day that doesn't interfere with your daily business activity, such as at the end of the workday, after the end of shifts, after peak transaction activity, or during a lull in transaction activity.
Duration	The runtime of this process varies based on the total number of distributions of the orders being imported. File-based data import doesn't support the creation or update of purchasing documents with more than 10,000 distributions. Exceeding 10,000 distributions can cause performance issues and could lead to failures.
Compatibility	There must only be one instance of the job running at any point of time. This is automatically handled by the application. If you have to run more than one instance of this process, then consider spacing them out over a period of time.

Parameters

Parameter	Optional or Required	Description	Parameter Values	Special Combinations Required	Notes
Procurement BU	Required	Specify the name of the Procurement business unit that these documents should be imported into.	N/A	None	N/A
Default Buyer	Required	Specify the name of the buyer to be used when one isn't included in the import data.	N/A	None	N/A
Create or Update Item	Optional	Select Yes to create an item that doesn't exist or update an existing item.	No Yes	None	N/A
Approval Action	Required	Select one of the following actions: Do Not Approve: Imports the document in Incomplete status requiring manual interaction. Submit for Approval: Imports the document and submits it to the approval process after the document is imported. Bypass Approval: Imports the document in Open (approved) status without going through the approval process.	N/A	None	N/A
Import Source	Optional	Used to match against the records in the interface tables to retrieve the right set of records for processing. For example: Import Source = External Contracts. Use it in conjunction with Batch ID to identify the documents to be loaded to the application tables.	N/A	None	N/A
Batch ID	Optional	Used to match against the records in the interface tables to retrieve the right set of records for processing. For example: Batch ID = 123. Use it in conjunction with Import Source to identify the documents to be loaded to the application tables.	N/A	None	N/A
Default Requisitioning BU	Required	Specify the name of the Requisitioning business unit to be used when one isn't included in the import data.	N/A	None	N/A
Communicate Orders	Optional	Select Yes to have imported purchasing documents communicated to the supplier. Select No to not have imported purchasing documents communicated to the supplier.	N/A	None	N/A

Troubleshooting Information

You can view the status of the import orders operation on the scheduled processes UI.
The validation errors and warning messages that prevented the import orders are displayed in the error log.
After you have corrected the validation errors, you can resubmit the process.