How To Import Standard Purchase Steps
How To Import Standard Purchase Steps
How To Import Standard Purchase Steps
1
Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.
Vision Demo - How To Import Standard Purchase Orders Using the Purchase Document Open
Interface PDOI (12.2 and 12.1.3 Enhanced PDOI) (Doc ID 2014101.1)
In this Document
Goal
Solution
APPLIES TO:
GOAL
What are the steps required to import Standard Purchase Orders using the Purchasing Document Open Interface and is there
any sample sample data that can be used in a vision environment ?
This note is designed to explain the steps to import a Standard Purchase Order and to provide sample data from a Vision
environment to facilitate testing.
Please note that the scripts provided here are only sample scripts to introduce users to the functionality. More columns are
available for use in the interface tables and more data can be
imported depending on what is required. Please see the section at the end of the note for more documentation on the import
process.
The scope of this Note is defined to importing Standard Purchase Orders. The use of the Import Price Catalog program will not
be demonstrated here.
SOLUTION
NOTE: In the images below and/or the attached document, user details / company name / address / email / telephone
number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance). Any similarity
to actual persons, living or dead, is purely coincidental and not intended in any manner.Replace this with note box text.
1 - Open SQL Developer and open database connection for the environment to be used for import
WARNING : This step will delete data from the interface tables. Do not do this if others are testing any part of the purchasing
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 1/9
9/30/2019 Document 2014101.1
process as these tables are used, not only during import, but during other processes such as autocreate. This step is only to
be used during testing in test environment. Please do not delete interface data in a production environment.
Run the following statements to clear existing data from the interface tables. Please note that this may interfere with other
testing.
This step can be ignored if required. This step is only included here to clear out any data from the interface tables so as to
prevent any confusion over the results obtained by running the import program.
2. Please use the following insert statements to populate the interface tables depending on the scenario
required :
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 2/9
9/30/2019 Document 2014101.1
unit_price,
ship_to_organization_code,
ship_to_location,
line_loc_populated_flag,
need_by_date)
VALUES
(po_lines_interface_s.nextval,
po_headers_interface_s.currval,
1,
1,
'Goods',
'CM96713',
'Ea',
1,
50,
'V1',
'V1- New York City',
'N',
sysdate+1);
Upon submitting the 'Import Standard Purchase Order' concurrent program - the Group Lines parameter was No.
Also note that the PO_LINES_INTERACE.LINE_LOC_POPULATED_FLAG is set to N - as
PO_LINE_LOCATIONS_INTERFACE is not being populated.
_______________________________________________________________________________________________________
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 3/9
9/30/2019 Document 2014101.1
item,
uom_code,
quantity,
unit_price,
ship_to_organization_code,
ship_to_location,
need_by_date,
line_loc_populated_flag)
VALUES
(po_lines_interface_s.nextval,
po_headers_interface_s.currval,
1,
1,
'Goods',
'CM96713',
'Ea',
1,
50,
'V1',
'V1- New York City',
sysdate+1,
'N');
Upon submitting the 'Import Standard Purchase Order' concurrent program - the Group Lines parameter was Yes, as
there are multiple records inserted for the shipments.
Also note that the PO_LINES_INTERACE.LINE_LOC_POPULATED_FLAG is set to N - as
PO_LINE_LOCATIONS_INTERFACE is not being populated.
_______________________________________________________________________________________________________
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 5/9
9/30/2019 Document 2014101.1
po_headers_interface_s.currval,
1,
1,
'Goods',
'CM96713',
'Ea',
2,
10,
'V1',
'V1- New York City',
'Y');
commit;
Upon submitting the 'Import Standard Purchase Order' concurrent program - the Group Lines parameter was Yes, as
there are multiple records inserted for the shipments.
Also note that the PO_LINES_INTERACE.LINE_LOC_POPULATED_FLAG is set to Y - as
PO_LINE_LOCATIONS_INTERFACE is being populated.
_______________________________________________________________________
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 7/9
9/30/2019 Document 2014101.1
'USD',
57, -- Your buyer id
'Office Supplies, Inc.',
'OFFICESUPPLIES',
'V1- New York City',
'V1- New York City',
'PO_MULTI_SHIPMENT6');
commit;
Upon submitting the 'Import Standard Purchase Order' concurrent program - the Group Lines parameter was No, as
there are multiple records inserted for the shipments.
Also note that the PO_LINES_INTERACE.LINE_LOC_POPULATED_FLAG is set to Y - as
PO_LINE_LOCATIONS_INTERFACE is being populated.
REFERENCES
NOTE:1939713.1 - Purchase Order Documents Interface (PDOI) Enhancement Features and Considerations
NOTE:2013280.1 - Importing Multiple Shipments for a Standard Purchase Order (PO) Gives Error: This line cannot be grouped.
(VALUE=1)
NOTE:1982357.1 - Import Price Catalogs is Ending in Error - 'Error: This Line Cannot Be Grouped As The Matching Criteria Is
Not Satisfied. (VALUE=2)'
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=9sguwcsht_284&id=2014101.1 9/9