PO_REQUISITION_UPDATE_PUB.UPDATE_REQUISITION Used To Add Requisition Line Gives Error
(Doc ID 2486488.1)
Last updated on MARCH 02, 2019
Applies to:Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.
This is spin off of <Bug 28796135> - PO_REQUISITION_UPDATE_PUB API -ADDING LINE FAILING FOR DROPSHIP REQ
After the patch was applied, line was added successfully, but the attributes for the line were not updated. It seems the attribute_category isn't in the
po_requisition_update_pub.req_line_rec_type, so it can only be set in header and distributions.
Can update after, but that is the wrong way to do it, especially if wanting to submit it for approval.
The problem is simple, po_requisitions_interface_all has two fields for attribute_category called header_attribute_category and
line_attribute_category. Without these fields filled in, the attributes at header and line will not be validated properly.
If there is no attribute_category at line level in po_requisition_update_pub then the code should at least copy the value from header to line, but it doesn't do that
either. It can be updated after, but if the interface does this normally, so should this package. This package cannot be used for new requisitions
without the attribute_category at line level. This field is in the table in order to determine the transaction type so that the attributes will display in forms.
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