My Oracle Support Banner

GLLEZL: Journal Import Creates STAT Amounts on Accounts Without Unit of Measure (Doc ID 2782137.1)

Last updated on JUNE 05, 2021

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

When entering a journal entry manually, you cannot add a statistical quantity to an account that doesn't have a unit of measure (UOM).  This is as expected.

When a user directly populates the gl_interface table through WebADI, SQL, etc., and runs the journal import, it will enter these quantities to accounts without a UOM.  This is not desired.   This can be verified when reviewing the import Journal Entries.

Example:  Loaded gl_interface with 2 lines of data.  Used one account for which is  UOM is not defined in one of the lines. In the Journal Entry, the column  STAT_AMOUNT has a value for both the records. 

STEPS TO REPRODUCE

1. Load journal entry data directly into gl_interface table via WebADI, SQL or API, etc.
2. Run Journal Import (GLLEZL) concurrent process from General Ledger responsibility
3. Check Journal Entries and see the STAT amount on accounts that do not have UOM defined.

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.