My Oracle Support Banner

R12: Purchasing Documents Fail Funds Check Or Going To Pre-approved Status Due To Budgetary Control Exceptions - Troubleshooting (Doc ID 603057.1)

Last updated on SEPTEMBER 20, 2021

Applies to:

Oracle Purchasing - Version 12.0.0 and later
Information in this document applies to any platform.

Purpose

This document provides the reader with detailed information on how to troubleshoot an issue encountered when the Purchasing document goes to Pre-approved status or fail funds check in encumbrance enabled environment with budgetary control exception in Release 12 SLA architecture

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Functionality
 Troubleshooting
 a) Requisitions (PR) or Purchase Orders (PO) fails funds check with   the detailed message showing 'PO_MSG_NULL_MESSAGE' on doing check funds from Tools
 b) Requisitions (PR) or Purchase Orders (PO) fails funds check with the detailed message showing 'This detail transaction fails funds check' on doing check funds from Tools
 c) Requisitions (PR) or Purchase Orders (PO) fails funds check with the detailed message showing 'This detail transaction causes a summary account to fail funds check' / 'This detail transaction fails and causes a summary account to fail funds check' on doing check funds from Tools
 d) Requisitions (PR) or Purchase Orders (PO) fails funds check with the detailed message showing 'One or more earlier pending transactions cause this transaction to fail' on doing check funds from Tools (OR) PR/PO fails funds check even though sufficient funds are shown for the budget account in Funds Inquiry screen
 e) Requisitions (PR) or Purchase Orders (PO) fails funds check with the detailed message showing 'Procedure PSA_BC_XLA_PUB.Budgetary_Control returns an error without any details to the calling procedure PO_ENCUMBRANCE_POSTPROCESSING.execute_gl_call.Please contact your support representative' on doing check funds from Tools.
 f) Requisitions and Purchase orders go to Pre-approved status with 'PO_REQAPPROVAL_ACTION.RESERVE_DOC: ORA-6512 at RESERVE_DOCUMENT' error in the workflow status
 Identify the reason for budgetary control exception for Standard Purchase Orders
 Identify the reason for budgetary control exception for Blanket Releases
 Identify the reason for budgetary control exception for Purchase Requisitions
 g) Requisitions and Purchase orders go to Pre-approved status or fails funds check due to insufficient funds even though the approver has the override limit
 Debug Logging
 Still Have Questions?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.