E1: ENV: Object Usage Tracking Summation Is Not Collecting the Object Usage Information Based on the Timezone of the User Who Runs R98902 (Doc ID 2953997.1)

Last updated on JUNE 07, 2023

Applies to:

Symptoms

After running R98902 to add the Object Usage Tracking summation and analyzing the Peak Usage graph from Composite Page, the graph shows that the objects were no more used after a specific time, although users were connected to the JD Edwards EnterpriseOne system performing several transactions.

This issue is more notable for the users checking the graph and having a timezone set in their user profiles for which the working hours end corresponds to the UTC next day, or the working hours start corresponds to the previous UTC day.

For example:
A. For users from Eastern hemisphere for example in Tokyo which is UTC+9, they will run R98902 on May 15th at 08:00 AM JST. This will still be May 14th 11:00 PM UTC. R98902 will not summarize the new records because in UTC there is still May 14th and for example an object accessed at 10:00 AM JST on May 14th, which is May 14th, 01:00 AM UTC will not be included into summation;
B. For users in Western hemisphere for example in Honolulu which is UTC-10, they will run R98902 on May 15th at 07:00 PM HST. This will be May 16th 5:00 AM UTC. R98902 will collect new records because in UTC May 15th has passed and for example an object accessed at 1:00 PM HST on May 15th, will be summarized, but an object accessed at 4:00 PM HST on May 15th will not be summarized, so the viewer will see that after 2:00 PM HST no object is accessed.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.