RDF: Profile-Based Forecasting Does Not Appear to Respect the Loaded Profile (Doc ID 2052081.1)

Last updated on JULY 14, 2017

Applies to:

Oracle Retail Demand Forecasting - Version 13.4.3.4 to 15.0 [Release 13.4 to 15.0]
Oracle Retail Predictive Application Server - Version 14.1.3.4 to 15.0 [Release 14.1 to 15.0]
Information in this document applies to any platform.

Symptoms

In Oracle Retail Demand Forecasting (RDF) 13.4.3.4, when the domain is set up with Profile Forecasting at the source level, the resulting forecast does not look like the profile and the saved profile is erased after forecast generation.


[Sample] Steps to Reproduce:

  1. Create Forecast Admin workbook.
  2. Open Final and Source Level Parameter worksheet and set default forecast method to ‘Profile_Based’ for source level ’10 – Class/Area/Week’.  Commit changes.
  3. From Advanced Settings (tab) > Final and Source Level Parameters worksheet, leave the Deseasonalized Demand Array measure blank.
  4. Create Forecast Maintenance workbook.
  5. In ‘1- itm/str/week-Final Final Worksheet’, make sure for the two current active DC’s that the ‘Forecast Method Override’ is set to ‘Profile Based’ and the ‘Source Level Override’ is set to ’10 – Class/Area/Week’.
  6. Commit and close the workbook.
  7. Build Profile Approval workbook.
  8. From the Final (tab) in the worksheet ‘15 – Class/Area ->Item/Store Profile Worksheet’, roll up Location to ‘all [Location]’.  
  9. Load curve profiles into RDF worksheet into ‘Adjusted Profile 15 – Class/Area -> Item/Store’ measure.
  10. Create Profile Administration workbook and make sure ‘Use Advanced Profile Features’ is set to False.
  11. Run Online Forecast New > Forecast (tab) > Run Batch Forecast [Next].
  12. Create new Profile Approval workbook.  Note that saved profiles are now missing.
  13. From the Final (tab) in the worksheet ‘15 – Class/Area ->Item/Store Profile Worksheet’, note that all the Adjusted Profiles are no longer there; same for Approved Profile.
  14. Create Forecast Approval workbook. Forecasts generated do not match entered profiles.
  15. Select 1 and 10 forecast levels.  Use the most recently generated forecast.
  16. In the Final Level worksheet, neither of the two warehouse forecasts match each other or the profile loaded for that item.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms