EAP: Payment Posting creates incorrect InterUnit Escheatment accounting entries (Doc ID 1926450.1)

Last updated on MARCH 18, 2016

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Payment Posting creates incorrect Accounting entries for an InterUnit Escheatment.
 
Expect the Accounting entries created for an InterUnit Escheatment to match the Accounting entries that are created for an InterUnit Cancelled Payment.  However, this is not the case.  The InterUnit Escheatment entries do not match the InterUnit Cancelled Payment entries.  As a result, once Journal Generator is run to create a Journal for the Escheated Payment, the Journal fails Combination Edits on the GL side since the chartfield combinations are not valid combinations on the GL side.

STEPS
1.  Installation Options > Payables page setup has Posting Method = Detail Offset Method
2.  General Ledger Definition > Inter/IntraUnit page setup has Inheritance Defaults defined for Operating Unit, Fund, Class and Project
3.  Ledger Groups > Balancing page setup has the following ChartFields checked:
Business Unit:  The fields for "Balance" and "Use Affiliate" are checked
Operating Unit:  The fields for "Balance" and "Use Affiliate" are checked
Fund Code:  The fields for "Balance" and "Use Affiliate" are checked
Project:  The field for "Balance" is checked
4.  ChartField Inheritance is setup for all of the Payables Inheritance Groups
5.  Accounting Entry Template page setup has the Escheatment Liability defined for Account, Fund, Operating Unit, Dept, Program and Class
6.  External Account is setup for the Cash - AP for Account, Operating Unit, Fund, Program and Class
7.  Voucher is created with the following chartfields populated:  Account, Operating Unit, Fund, Dept, Program, and Class
8.  Voucher is manually paid through the Voucher > Payments page
9.  Run Payment Posting for the Payment
10.  Cancel the Payment
11.  Run Payment Posting for the Cancelled Payment
12.  Voucher is manually paid the 2nd time through the Voucher > Payments page
13.  Run Payment Posting for the 2nd Payment
14.  Escheat the Payment
15.  Run Payment Posting for the Escheated Payment
16.  Review the Accounting entries created for the Cancelled Payment and the Escheated Payment
17.  Notice that the Chartfield Combinations do not match

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms