My Oracle Support Banner

EGL9.2: Spreadsheet Journal Import via Write To File, when run batch process GL_EXCL_BATC Get Incorrect Error When Chartfield1 Has Future Dated Inactive Row (Doc ID 2709428.1)

Last updated on MARCH 12, 2021

Applies to:

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

Symptoms

When using spreadsheet journal import Write To File, when run batch process GL_EXCL_BATC get incorrect error when Chartfield1 has future dated inactive row

The journal will not load and though batch process GL_EXCL_BATC runs to success the log file shows error of inactive Chartfield1 even though the Chartfield1 is active as of the Journal Date. When keying in online the journal does not error.

Issue only occurs when both journal date and future effective date are prior to today's date. For example -

      today's date 4/20/2020

      journal date 3/31/2020

      effective date 4/1/2020 of inactive Chartfield1 value 'CF1_A' (effective date is future to journal date)

After perform Write To File then attach output file to GL_EXCL_BATC run control,

when run the GL_EXCL_BATC process though it runs to success the log file shows error message, "Invalid Chartfield1 value CF1_A"


Steps to replicate:

1.Given that current date is 4/20/2020, set Chartfield1 values where both journal date and inactive Chartfield1 effective date are "prior" to today's date
        effdate         status     Chartfield1
     04/01/2020    Inactive      CF1_A
     01/01/1901    Active        CF1_A
2.Using JRNL1_WS, write-to-file JRNL1_WS.txt with journal date 03/31/2020
     line#   account    chartfield1    curr cd       amount
       1      500000       CF1_A        USD         125.00
       2      201000                        USD       <125.00>
3.Attach JRNL1_WS.txt to run control for General Ledger > Journals > Import Journals > Spreadsheet Journals, with the Edit Journals checkbox checked
   -then run the GL_EXCL_BATC process
4.Though process runs to success, when check the log file see the below error:
    "1239 (US001, NEXT, Journal Line No.: 1, 2020-03-31) -, - -- Errored :
      Invalid ChartField 1 value CF1_A."

Note: Issue does not replicate if use journal date and inactive Chartfield1 with effective date "after" today's date.

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.