With what Values is the CLOSED_CODE Field populated in the PO_LINES_ALL Table For Blanket Purchase Agreements
(Doc ID 2819244.1)
Last updated on MARCH 15, 2022
Applies to:Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.
In R12 Application, the CLOSED_CODE field in PO_LINES_ALL is blank for blanket purchase agreements.
When we are creating the Blanket purchase agreement then CLOSED_CODE field is blank, if we are creating a release then also CLOSED_CODE is blank.
But in 11i Application, if we create a release against the BPA then CLOSED_CODE is being populated with OPEN status. i.e. if there is an open release then CLOSED_CODE is OPEN.
Standard Purchase Order functionality of this field is discussed in MOS Note CLOSED_CODE column in PO_HEADERS_ALL has Null value instead of OPEN (Doc ID 182002.1) which says that for autocreated purchase orders, the CLOSED_CODE will have value OPEN.
For manually entered purchase orders , the CLOSED_CODE will have value NULL.
Customer is looking for a similar explanation in case of Blanket Purchase agreement also, in what condition, CLOSED_CODE will be populated as OPEN.
Customer has performed below test cases, in each case, CLOSED_CODE is null(blank).
Case 1:- Create Requisition > Use "Auto Create Form" to convert Requisition in BPA Release > BPA Release :: CLOSED_CODE is null(blank).
Case 2:-Create Blanket Purchase Agreement > Create manual BPA Release :: CLOSED_CODE is null(blank).
Case 3:- Create Requisition > Run “Create Release” program > BPA Release :: CLOSED_CODE is null(blank).
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