R12: AP: Invoices that are Validated and Accounted do not Generate Encumbrance (Doc ID 2827893.1)

Last updated on DECEMBER 10, 2024

Applies to:

Symptoms

When an invoice is created, validated and does not need an approval (WFAPPROVAL_STATUS = NOT REQUIRED), it generates encumbrance after it is validated and can be accounted.

When the invoice is created with the need for an approval (based on classic AME rules), a hold is placed on the invoice to prevent generating encumbrance and accounting.
Therefore,  the invoice stays in "NEEDS REVALIDATION" status until it is approved.
After the approver's submmit the approval, the hold on the invoice is released,  and the invoice can be then accounted.

However,  even after above process the invoices does not generate encumbrance.

Steps to Reproduce:
1 For the invoice validation

Goto  Payables Responsibility an query the invoice
Go to (B) Actions
Check Validate and hit OK

If the invoice is created with the Needs for an approval, then the Initiate Approval  OR Force approval should be checked as well.

1.2 Another option for validate the invoice is by the concurrent Request:
Payables Responsibility \ Other \ request

and Run a single request: Invoice Validation
Enter the requested parameters as needed,

2. To Check the encumbrance on the invoice
GO to view accounting from the ap_distributions_all.accounting_event_id
and it needs tobe be matching to the xla tables to see invoice accounting. 

To view encumbrance accounting , it is necessary to  match ap_distributions_all.bc_event_id
to the xla tables.


More information can be found in
R12: How To Troubleshoot Funds Check Hold Issues On Payables Invoices (Doc ID 1055606.1)

Changes

Cause

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