My Oracle Support Banner

LAST_UPDATE_DATE on GL_BALANCES/GL_DAILY_BALANCES Shows Stale Data For Large Batches (Doc ID 2351389.1)

Last updated on MARCH 08, 2019

Applies to:

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

Goal

When posting journal batches, it appears that the application stores the last_updated timestamp in a variable. When the data is committed to the database, this "saved" variable is used. If the batch is large and the statement took 20+ minutes to complete, the last_updated timestamp contains a value that is 20+ minutes in the past.

Currently, the last_update_date on gl_balances/gl_daily_balances tables is the timestamp corresponding to statement from:

That is right before glpfdel() module.

Another situation, would be when the last_update_date is not updated but some period_aggregate amount values have changed.

The need is to have the last_update_date column in gl_balances, respectively gl_daily_balances assigned with a value of sysdate/systimestamp so as to reflect the correct timestamp at time of completing the posting request.

Solution

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