EGL: After Upgrading to PUM 47, Journal Generator Is Not Updating the Journal Information on PS_VCHR_ACCTG_LINE For PAYMENT CAS Entries and Leaves the GLS_DISTRIB_STATUS = 'J'
(Doc ID 2954687.1)
Last updated on JUNE 11, 2023
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
After upgrading to 9.2 PUM Image 47, Journal Generator does not update PS_VCHR_ACCTG_LINE PAYMENT CAS entries and the GL_DISTRIB_STATUS remains with a status = "J" (creating Journals) for payments without discounts. If the payment has a discount, the Journal information is populated accordingly in PS_VCHR_ACCTG_LINE and the GL_DISTRIB_STATUS = 'D' when Journal Generator completes.
STEPS
1. General Ledger > Journals > Subsystem Journals > Accounting Entry Definition > Accounting Definition = APDEFN
a. Accounting Entry Record = VCHR_ACCTG_LINE
b. ChartField Mapping - Note, ChartField = “Allowable/Unallowable” (not a delivered option)
c. Box checked for 'Cross Product Drill Down' box but Page Name field is blank
2. General Ledger > Journals > Subsystem Journals > Journal Generator Template > Template = PAYMENT (use delivered setup)
3. Add Voucher > Accounts Payable > Vouchers > Add/Update > Regular Entry > Save > run Voucher post from the Action field on the Voucher Invoice Information page
4. Pay Voucher through Pay Cycle > Accounts Payable > Payments > Pay Cycle Processing > Pay Cycle Manager
6. Post Payment > Accounts Payable > Batch Processes > Payment > Payment Posting
7. VCHR_ACCTG_LINE query has ACCRUAL APA / DST and PAYMENT APA / CAS entries
8. Run Journal Generator > General Ledger > Journals > Subsystem Journals > Generate Jrnl from Subsystem > Accounting Definition Name = APDEFN
9. Query of VCHR_ACCTG_LINE shows Journal information is not populated for the PAYMENT CAS entries and the GL_DISTRIB_STATUS = 'J'
Changes
An upgrade was done from 9.2 PUM Image 45 to PUM Image 47.
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 |