My Oracle Support Banner

R12.2 Wrong Encumbrance Accounting Entries For Prepayment Matched To Purchase Order (Doc ID 2096514.1)

Last updated on MARCH 29, 2021

Applies to:

Oracle Payables - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Accounting Issues in AP

ACTUAL BEHAVIOR
---------------
Encumbrance Accounting entries Prepayment matched to purchase order is wrong:

a. ACCOUNTING_CLASS_CODE=PURCHASE_ORDER--> ENTERED_DR=0//ENTERED_CR=99
b. ACCOUNTING_CLASS_CODE=RFE -->ENTERED_DR=198//ENTERED_CR=99

EXPECTED BEHAVIOR
-----------------------
All Accounting should be according to the SLA setup for Encumbrance Accounting

a. ACCOUNTING_CLASS_CODE=PURCHASE_ORDER--> ENTERED_DR=99//ENTERED_CR=99
b. ACCOUNTING_CLASS_CODE=RFE -->ENTERED_DR=99//ENTERED_CR=99

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enter and account prepayment invoice
2. Enter and account standard invoice
3. Apply Prepayment to standard invoice

4. Wrong accounting for PO and RFE for Prepayment Applications:


BUSINESS IMPACT
-----------------------
Due to this issue, users cannot rely on Encumbrance Accounting entries.

Changes

 Upgrade  from 12.1.3 to 12.2.4

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
Changes
Cause
Solution
References


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