The Import Standard Purchase Orders program enables you to import standard purchase orders from legacy systems into Oracle Purchasing. Oracle Purchasing provides an open interface that validates the purchase order information, and then the Import Standard Purchase Orders concurrent program imports it into Purchasing.
To use this feature, you must first use a custom import program to load the data into the interface tables. Once the data is loaded, the Import Standard Purchase Orders program is run from within Oracle Purchasing to validate and create standard purchase orders.
The PO Approval workflow can be initiated automatically from the Import Standard Purchase Orders concurrent program. This eliminates the need to individually query each imported purchase order and submit it for approval. Additionally, Oracle Purchasing supports importing standard purchase orders of an approved status from legacy systems. This eliminates the need for any further approval processing for imported standard purchase orders.
In the Submit Requests window, select Import Standard Purchase Orders in the Name field.
Enter the default buyer name to be associated with the incoming documents that are not assigned to a buyer..
If a default buyer is not specified and the imported purchase order also does not have buyer information, the program will use the normal Purchasing defaulting mechanism to generate buyer information. If the buyer name provided in the interface is not valid, then the record will error out and the default buyer name will not be supplemented.
The valid response is Yes or No. If Yes, the program will also create items in the item master from those buyer part numbers in the interface data where there is no corresponding item master entry. If No, the program will not create new item master entries.
For purchase orders, you must choose either Approved, Incomplete, or Initiate Approval. The impact of this parameter on the import logic is explained in the table below:
| Document Status in Interface Table | Concurrent Program Approval Status Parameter | Resulting Document Status |
| Null | INCOMPLETE | INCOMPLETE |
| Null | APPROVED | APPROVED |
| Null | INITIATE APPROVAL | INITIATE APPROVAL |
| INCOMPLETE | INCOMPLETE | INCOMPLETE |
| INCOMPLETE | APPROVED | INCOMPLETE |
| INCOMPLETE | INITIATE APPROVAL | INITIATE APPROVAL |
| APPROVED | INCOMPLETE | APPROVED |
| APPROVED | APPROVED | APPROVED |
| APPROVED | INITIATE APPROVAL | APPROVED |
You can import Standard purchase orders with an INCOMPLETE status and then automatically initiate the PO Approval Workflow for these imported documents. Specifying a status of Incomplete or leaving the status Null in the interface data, and specifying a value of Initiate Approval for the Approval Status runtime parameter can achieve this.
Standard purchase orders can also be imported with an APPROVED status. Specifying a status of Approved in the interface data or leaving the status Null in the interface data, and specifying a value of Approved for the Approval Status runtime parameter can achieve this. The PDOI Auto Approval Process workflow process is available with the PO Approval workflow (poxwfpoa.wft). Purchasing initiates this workflow process when purchase orders are being imported in the Approved Status. This workflow process is applicable to the following types of documents: Standard, Blanket, and Contract.
Attention: If the concurrent program is executed with the Approval Status parameter INITIATE APPROVAL or APPROVED, then you must run the Workflow Background Process for Item type PO Approval with process deferred as Yes.
Enter a valid batch ID, that is a unique identifier for the group of documents in this submission. If you don't enter a Batch ID, one is generated for you when the process runs.
Select Yes or No. No is the default value. If the value is selected as Yes, then all the lines satisfying the matching conditions will be grouped to single line. Shipments will also be grouped based on the matching conditions.