My Oracle Support Banner

R12: How to troubleshoot Funds Check Hold Issues on Payables Invoices (Doc ID 1055606.1)

Last updated on AUGUST 07, 2018

Applies to:

Oracle Payables - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.

Purpose

 

Join our growing Oracle Payables Community and learn from your peers and Oracle on how to address your unique issues in AP.


This document will step through the actions user should take to resolve "Cant Funds Check", "Encumbrance Acctg Fail" hold or Funds Check issues on a Payables Invoice.

Background
----------------
When a payables invoice is validated in an Encumbrance enabled environment,  funds reservation is done during the validation and encumbrance accounting is generated.

If there is any failure during this funds reserve process, the invoice cannot be fully validated and goes on hold. Usually, the hold is "Encumbrance Acctg Fail" or "Cant Funds Check".

Events Information
--------------------
The validation process creates two events in XLA_EVENTS for the entity (the invoice) in a budgetary control enabled environment.

One of the events is an Encumbrance event. This event had budgetary_control_flag = 'Y'. The event_id on this event  is stamped in the AP_INVOICE_DISTRIBUTIONS_ALL.bc_event_id
The second event is the actual event. This event has budgetary_control_flag = 'N'. The event_id on this event is stamped in the AP_INVOICE_DISTRIBUTIONS_ALL.accounting_event_id.

Process Information
-----------------------
The encumbrance event that is generated during validation is also processed at the same time.
Validation calls the funds reserve process that reserves funds against the accounts on the invoice from the budget. If this is successful, a header record in  XLA_AE_HEADERS and encumbrance accounting (Debit to Expense and Credit to RFE) is created in XLA_AE_LINES.

The actual event generated during the validation is processed only during Create Accounting.
The Create Accounting process generates two headers in XLA_AE_HEADERS. One header is an encumbrance header with BALANCE_TYPE_CODE = 'E' and another is for actual accounting with BALANCE_TYPE_CODE = 'A'.

The lines generated under the Actual header is the proprietary accounting (Debit to Expense and Credit to Liability). The lines generated under the Encumbrance header is the reversal of invoice encumbrance which is Cr to Item Expense and Dr to RFE.

Hence its expected that when an invoice is fully accounted, net encumbrance on the invoice should be 0.

The encumbrance generated during validation should be relieved during accounting.

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
 1. Apply Latest Rollup Patch
 2. Validate Application Accounting Definitions
 3. Cleanup the Data
 4. Funds Available Issues
   4.1 Query to use for checking funds available for an Invoice
   4.2 Post all Journals
   4.3 Missing 'S' rows in gl_bc_period_map.
   4.4 Missing 'B' rows in gl_bc_period_map.
 6. Purchase Order Encumbrance Reversal not hapenning for Custom JLD's
 6. Encumbrance Type mismatch between 11i and R12
 7. Revalidate/Cancel the invoice
 8. Debug
   8.a) FND Debug log
    8.b)  Diagnostics
 9. Analyze
References

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