Retail Demand Forecasting: Cloning FAQ's
(Doc ID 735424.1)
Last updated on APRIL 13, 2021
Applies to:Oracle Retail Demand Forecasting - Version 12.1 and later
Oracle Retail Predictive Application Server - Version 12.1 and later
Information in this document applies to any platform.
Checked for relevance 6-Aug-2010
Checked for relevance 20-Jan-2012
Checked for relevance July-2013
This high-level document outlines and answers some commonly asked questions regarding the Cloning functionality made available in Oracle Retail Demand Forecasting (RDF), version 12.1.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Questions and Answers|
|What is Cloning?|
Why develop the cloning process?
How does cloning differ from Like SKU/Sister Store (“pre-cloning”) functionality?
When should Cloning be considered instead of Like SKU/Sister Store functionality?
What other functional details are important regarding Cloning?
Is item/location assignment and mapping performed from the primary domain or the local domains? What about the act of cloning itself?
Can cloning be performed from within a workbook rather than in batch?
How is the cloning workbook created?
Can a higher level in the merchandise hierarchy than SKU be cloned (for instance, DEPT)?