EGL9.1: Spreadsheet Journal Import(JRNL1) Produces Incorrect/Unclear Error Messages and Uploading Invalid Chartfield Values When Using Lowercase Values (Doc ID 1372019.1)

Last updated on MARCH 25, 2017

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
****Checked for relevance on 14-Sep-2014****

Symptoms

Issue:
-------

System produces incorrect/unclear error messages for Spreadsheet Journal Import, while data is entered with lower case values.

Actual Behavior:
------------------
JRNL1.xls gives incorrect/unclear error messages when using lowercase and system is uploading invalid Chartfields.

Expected Behavior:
----------------------


JRNL1.xls should give correct/clear error messages when using lowercase and system should not upload invalid Chartfields.
System should convert Lowercase values to Uppercase values for all journal line fields (same as it is now for journal header fields).

Steps To Replicate:
-----------------------

Example 1: Entering the ‘Ledger’ in lowercase (on journal lines) => ‘euro’ instead of ‘EURO’


• Define setup and journal header.
• Enter Ledger value in lower-case (euro) on journal lines.
• Upload journal.
• Error pops up.
Imported 0 journals - System ID (Unit, Journal ID, Date) Reference, Description:
Skipped journal with warning: 1002 (NLDE1, 0000000201, 2011-09-09) -, TEST GCS2: Invalid Ledger value euro.

The error message just explains that ‘euro’ isn’t valid. Very confusing for end-users, because they know this is the right ledger. When entering the ledger in lower-case on the journal header there’s no problem at all => at saving, the text is automatically changed to uppercase!

Example 2: Entering the BU in lowercase (on journal lines) => ‘nlde1’ instead of ‘NLDE1’


• Enter business unit field in lowercase on journal lines.
• Upload journal.
• Error pops up.

Imported 0 journals - System ID (Unit, Journal ID, Date) Reference, Description:
Skipped journal with warning: 1002 (nlde1, 0000000202, 2011-09-09) -, TEST GCS2: Invalid Ledger value EURO.
Skipped journal with warning: 1002 (nlde1, 0000000202, 2011-09-09) -, TEST GCS2: Invalid Account value 620000.

The error message just mentions an incorrect value for the account number and for the ledger. This is very confusing for the end-users, because the account and the ledger are correct. The real troublemaker is the lowercase BU.

When entering (part of) the BU in lowercase on the journal header, there’s no problem at all => at saving, the text is automatically changed to uppercase!

---

Example 3: Entering CHARTFIELD1 (=project) in lowercase (on journal lines) => ‘b0101’ instead of ‘B0101’


• Enter journal header and lines.
• Enter Projects (Chartfield1) in lowercase on journal lines.
• Upload journal.

Imported 1 journals - System ID (Unit, Journal ID, Date) Reference, Description:
1005 (NLDE1, 0000000206, 09/09/2011) -, TEST GCS5
This is wrong. Users should NOT be able to upload journals with incorrect chartfield values.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms