My Oracle Support Banner

EGL9.2:Journals Uploaded Using Spreadsheet Journal Import (JRNL1_WS) Contain Lines From a Different Journal (Doc ID 2834868.1)

Last updated on NOVEMBER 21, 2024

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
*** Checked for currency - 20 June 2023 ***

Symptoms

After the recent upgrade to Image 38 and PeopleTools 8.58.10, journals uploaded using spreadsheet journal import (JRNL1_WS) contained lines from a different journal completely unrelated and uploaded by a different person.

This happens when uploading journal that triggers the GL_JRNL_UPLD process (ex: having 2500 lines) that fails (ex: combo edit, balancing error, etc.).
Then, followed by another upload which may have lesser lines and gets validated successfully.  However, this 2nd journal will contain lines that are from previous journal.

Steps to replicate:

1.  Set up Process Definition to trigger GL_JRNL_UPLD process in the Process Scheduler.
2.  Check Define Options and Defaults in JRNL1_WS, ensure Edit Journal(s) option is selected.
3.  1st Journal:
      - Enter Journal Header Details.
      - Enter Journal Line Details.
         3000 lines
         3 BUs (US003, US004, CAN01)
         Encircled are the invalid chartfield combinations.
4.  Click Import Now, enter User Credentials (GLS2) and click OK.
5.  Ignore message:  Journal lines do not contain header BU rows, continue.
     Click Ok.
        Process Instance = 234598
        Run Status = Success
 
    *** Result:  Imported 0 journal due to combo edit error which was expected as there were indeed invalid CF combinations in the Spreadsheet Journal lines.

6.  2nd Journal:
      - Enter Journal Header Details.
      - Enter Journal Line Details.
         2700 lines
         3 BUs (US004, CAN01, AUS01)
         This time, all chartfields are with valid combinations
7.  Enter User Credentials (MGR2).
8.  Ignore message: Journal lines do not contain header BU rows, continue.
      Click Ok.
      Process Instance = 234600
      Run Status = Success
    
    *** Imported 0 journal due to combo edit error which was ‘not’ expected as :
         - All CFs used in 2nd journal are valid combinations.
         - 2nd journal only has 2700 lines, and the combo errors were in Lines 2990 and 3000, which were from the 1st journal.

See replication steps here.

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
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.