My Oracle Support Banner

EGL: Journal Generator FS_JGEN, Leaves PS_VCHR_ACCTG_LINE.GL_DISTRIB_STATUS = 'J' For PAYMENT CAS Entries Causing Out of Balance Journals (Doc ID 2962844.1)

Last updated on MARCH 12, 2024

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
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 47 and PeopleTools 8.60.05, Journal Generator process, FS_JGEN, is leaving the VCHR_ACCTG_LINE.GL_DISTRIB_STATUS = 'J' for PAYMENT CAS entries causing out of balance Journals.

STEPS

1. General Ledger > Journals > Subsystem Journals > Accounting Entry Definition > Accounting Definition = APDEFN
    a. Record = VCHR_ACCTG_LINE
    b. Record Update = VCHR_ACCTG_LINE

2. General Ledger > Journals > Subsystem Journals > Journal Generator Template > PAYMENT > Summarization tab select the following options:
    a. Select Summarize to All ChartFields
    b. Selected Account Values
    c. Retain Detail, Selected Values = 200000

3. VP1 adds a Voucher: Accounts Payable > Vouchers > Add/Update > Regular Entry
    a. Enter required information
    b. Save
    c. From Invoice Information page Action field select Voucher Post > click Run button

4. Pay voucher via Pay Cycle: Accounts Payable > Payments > Pay Cycle Processing > Pay Cycle Manager

5. Post Payment: Accounts Payable > Batch Processes > Payment > Payment Posting

6. Run Journal Generator: General Ledger > Journals > Subsystem Journals > Generate Jrnl from Subsystem
    a. Accounting Definition Name = APDEFN
    b. Template = Specify or leave blank

7. When Journal Generator completes, created journal is out of balance

8. Query VCHR_ACCTG_LINE for the voucher in question
    a. DST_ACCT_TYPE = CAS shows GL_DISTRIB_STATUS = 'J'
    b. All other rows for this voucher has GL_DISTRIB_STATUS = 'D'

NOTE: In the Steps above, User Details/Company Name/Address/Email/Telephone Number represent a fictitious sample (based upon made-up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

Upgraded from 9.2 PUM Image 31, Tools 8.57.05 to 9.2 PUM Image 47, Tools 8.60.05

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.