R12 : Canceling PO Without Canceling Backing Requisition Results in Error INSERT_PACKET_CREATE_EVENT-020: ORA-01400: cannot insert NULL into ("PO"."PO_BC_DISTRIBUTIONS"."ENTERED_AMT")
(Doc ID 1553897.1)
Last updated on FEBRUARY 14, 2025
Applies to:
Oracle Purchasing - Version 12.1.3 to 12.2.6 [Release 12.1 to 12.2]Information in this document applies to any platform.
Symptoms
When attempting to cancel a PO line with backing requisition, without cancelling the requisition, error occurs.
INSERT_PACKET_CREATE_EVENT-020: ORA-01400: cannot insert NULL into ("PO"."PO_BC_DISTRIBUTIONS"."ENTERED_AMT") Cause: A SQL error has occurred in INSERT_PACKET_CREATE_EVENT. The SQL error is ORA-01400: cannot insert NULL into ("PO"."PO_BC_DISTRIBUTIONS"."ENTERED_AMT"). Action: Take note of both this error number and the actions you were trying to perform. Contact your system administrator for further assistance.
Your Budgetary Control action completed with exceptions.
null
Your Budgetary Control action completed with exceptions.
User-Defined Exception in Package PO_Document_Cancel_PVT Procedure cancel_document:004
Steps to reproduce issue:
1. Query Purchase Order in BWC
2. Choose line to cancel
3. Do not enable option to cancel backing requisition
4. Submit change
5. Error occurs
It is not necessary to be using the Buyer Work Center, for example :
1. Using Purchasing Responsibility Navigate to Purchase Order summary and query for the concerned PO (Status = Approved, Reserved).
2. Go to Tools > Control, choose Cancel PO, enter GL Date , then click OK.
3. The following message appears:
APP-PO-14160: Document action not completed successfully
Cause: You attempted to perform a document action that is incompatible with the document status.
Action: No action required.
Important notice : If you choose the Cancel Requisition checkbox to cancel PO and PR together, the issue does not occur. For more details, please check : Cannot Cancel Purchase Order PO Shipment Due to Error : APP-PO-14160: Document Action Not Completed Successfully 3003667.1.
Cause
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
Symptoms |
Cause |
Solution |
References |