Purchase Order Open Interface Errors
(Doc ID 2593709.1)
Last updated on MARCH 20, 2023
Applies to:Oracle Purchasing - Version 12.2.4 and later
Information in this document applies to any platform.
Using Purchasing, error importing purchase orders with PDOI standard purchase order open interface
"Multiple buyer parts are found which match the specified Item Num (VALUE=&VALUE)", "Column ITEM_ID (VALUE=&VALUE) must be NULL."
The issue can be reproduced at will with the following steps:
importing Purchase Orders from an external system using the standard Purchase Order Open Interface.
The standard interface includes logic which causes our Purchase Orders to fail.
Some of the Purchase Order Lines when trying to import don't have item_ids e.g. in case they are amount based PO Lines or if they are expense PO lines.
In case no item_id is populated in the interface table, the standard interface logic tries to find and add an item_id automatically. It thereby looks at existing POs as following;
1. Interface line supplier matches Oracle purchase order line supplier.
2. Interface line supplier item number matches Oracle purchase order line supplier item number.
3. Interface line category matches Oracle purchase order line category.
4. Item which is found has a status of Active in the inventory organization associated with Operating Unit.
This logic causes the Purchase Orders to fail in the following situations;
1. In case more than one item_id is found, the interface fails with error "Multiple buyer parts are found which match the specified Item Num (VALUE=&VALUE)".
2. In case our PO line is amount based and an item_id is found, the interface fails with error "Column ITEM_ID (VALUE=&VALUE) must be NULL.".
The logic which seems to cause these issues is procedure derive_item_id in the standard interface package PO_PDOI_LINE_PROCESS_PVT.
For the above case , intentionally not populating an item_id in the interface table. Trying to to create the PO line without item and don't want the standard interface logic to find an item and that causes failures.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document