My Oracle Support Banner

EEX 9.2: Expense Report Lines Charged to Different GL Business Unit Are Not Posted to the General Ledger, Because the DOC_SEQ_DATE Is Not Populated (Doc ID 2450366.1)

Last updated on FEBRUARY 08, 2019

Applies to:

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

Symptoms

Expense report lines charged to different GL Business Unit are not posted to the General Ledger, because the DOC_SEQ_DATE is not populated

An employee in business unit US001 updates the GL business unit on 1 of the 2 expense report distribution lines to business unit US003. From the expense accrual that posted to the general ledger, it fails to generate the credit the US003 liability and the appropriate expense lines in the US003 ledger because the DOC_SEQ_DATE was not populated when accruals were posted.

Steps:

1. Create and submit an expense report for approval with two expense transactions one to employees GL Unit US001 and the other to GL Unit US003.
2. Approve the expense report
3. Post Accruals.
4. Generate journals

Actual Result:

Expense report lines charged to different GL Business Unit are not posted to the General Ledger.

Expected Result:

Expense report lines charged to different GL Business Unit are posted to the General Ledger.

Please see the replication steps document for more details.  

Changes

 

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.