Fusion BI Publisher - Report Delay Displaying the Latest Data (Doc ID 2239026.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Symptoms

Users have a custom BI Publisher report that generates the next available position code. After creating a new position , running the data model and generating the latest Next Available Position Code, the report generates the latest available position code.

Users created the Position 00052006 at 11:23am and verified it was in the system at 11:24am. The report did not return the next available number (00052007) until 11:37am, or a lag time of thirteen minutes. This test consisted of  refreshing the report multiples times each minute. The test was repeated after creating position 00052007 and there was a lag time of eight minutes on the second trial. Finally, there was a lag time of sixteen minutes for the third trial with position 00052008.

This lag time is too large for how the report will be used .  The business process requires that the next available position number display immediately. 

The issue can be reproduced at will with the following steps:
1. Creating a new Position.
2. Run the data model and it generates the latest Next Available Position Code immediately.
3. Notice it takes three-five minutes for the report to reflect the current data values. Sometimes it takes more time. The datamodel shows the correct value but the report does not .

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.