Why Did Elapsed Values in Workbook Get Changed Even Though There Is a Conditional Commit That Blocks from Committing Elapsed Weeks?
(Doc ID 2999684.1)
Last updated on JANUARY 29, 2024
Applies to:
Oracle Retail Merchandise Financial Planning Enterprise Edition Cloud Service - Version 23.2 and laterOracle Retail Assortment & Item Planning Enterprise Edition Cloud Service - Version 23.2 and later
Oracle Retail Demand Forecasting Cloud Service - Version 23.2 and later
Information in this document applies to any platform.
Goal
Consider the following scenario:
There is a set of measures (Sales, On Orders) that their values changed from Monday to Thursday for elapsed period (Week 1 2024) even though we did not run any batch during the week.
More specifically, the Weekly batch ran on Sunday, then on Monday numbers were looking good, but when the users rebuilt the workbook on Thursday the numbers for the elapsed week had changed. This happened only in one Category, and only one environment.
How could this happen?
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! |