Last updated on JANUARY 05, 2016
Applies to:Oracle Retail Demand Forecasting - Version 13.0 and later
Oracle Retail Advanced Inventory Planning - Version 13.0 and later
Information in this document applies to any platform.
Checked for relevancy on 3-Dec-2013
On Retail Demand Forecasting (RDF) 126.96.36.199, there are four issues that have been identified with the rdf_e_rms.ksh script.
1. The script generates the forecast files from only one domain at a given point of time. It is not designed to extract forecasts from all the RDF local domains and then provide a final forecast file that is concatenated with the forecasts from each of the local domains.
2. The measures that are used to extract forecasts are hard coded as appf01xb and appf06xb. As the measures are configurable in RDF, and the forecasts need not necessarily be stored in appf01xb and appf06xb, it does not fit each customer's requirements. Ideally the script should be configurable or parametrized to specify the correct measures while extracting forecasts.
3. The weekly forecast file should be generated at the week/store/sku level in order to be loaded into Advanced Inventory Planning (AIP), but the script generates a date ID for the week field instead of the Retail Predictive Application Server (RPAS) week ID (WNN_YYYY).
4. A new script has been created to extract the daily/weekly standard deviations from RDF (rdf_e_aipcumint.ksh), as the standard deviation extraction logic and format in the script rdf_e_rms.ksh was problematic. But the script rdf_e_rms.ksh still has the logic to extract standard deviation. This should, in fact, be made obsolete in rdf_e_rms.ksh.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms