| Oracle® Retail Demand Forecasting Implementation Guide Release 16.0 |
|
 Previous |
 Next |
The following information needs to be considered before implementing RDF:
The following factors can affect hardware space requirements:
Item—Number of distinct items.
Store—Number of physical, Web, and other distinct retail outlets.
Calendar—Number of historical and future time periods in the domain. This impacts the overall size of the environment.
Workbooks—Amount of space used by workbooks. This is typically greater than the domain itself. The number of workbooks is related to the number of users.
Partitioning is done to avoid competition for resources. Building a workbook and committing data are two processes that can cause contention.
How data is partitioned has an impact on the business process. The RDF domain is defined as a global domain. For performance reasons, a single subdomain is not recommended. There should be an even distribution of users across a set of local domains. For example, men's merchandise could be in a domain, women's merchandise in a domain, and children's merchandise in a domain. When a user is committing data in the men's merchandise domain, this will not affect the users in the women's or children's domains because of the use of partitioning.
|
Note: Domain partitioning is supported only along Product hierarchy (PROD). This is a standard RPAS hierarchy. Also source levels have to be below partion dimension, that is, if using Dept for source level forecasting, you have to partition at or below Dept. |
Consider the following questions when defining the partitioning of the domain:
How do I partition to meet my business needs?
How do I partition my users?
How do I create groups of users to further partition the solution?
In the GA configuration, group is a dimension label. The group dimension is a regular dimension in the product hierarchy, which the customer can rename or delete.
One of the major purposes of partitioning in RDF is to facilitate the parallelization of the batch process.
The wise selection of partition intersections can significantly reduce the batch time. Partition intersection selection should also consider business needs in such a way that contention issues are minimized. RDF has a special restriction in partitioning. Each local domain must only have one partition dimension position.
With a new release, there are two types of patches that can affect the RDF domain:
Changes to the code in the RPAS libraries.
The configuration is not affected by this type of patch. For these types of changes, applying the patch is a straight forward process.
Changes to the configuration.
These types of changes can be more complex. If a retailer has customizations in the configuration, the customizations must be redone on the new configuration before the patch is installed.
RDF batch is typically scheduled to run end of week with the most updated feeds of sales history and foundation data. Some tasks or batch processes can be run adhoc or as needed basis.
Following is a list of typical RDF batch tasks and scheduling considerations:
Weekly activities:
Hierarchy Load
Data Load
Pre-processing
Forecast Generation
Alert Generation
Commit batch (committing workbooks saved to be committed later)
Auto Workbook build
Adhoc/as needed
AutoSource
To define workbook template security, the system administrator grants individual users, or user groups, access to specific workbook templates. Granting access to workbook templates provides users the ability to create, modify, save, and commit workbooks for the assigned workbook templates. Users are typically assigned to groups based on their user application (or solution) role. Users in the same group can be given access to workbook templates that belong to that group alone. Users can be assigned to more than one group and granted workbook template access without belonging to the user group that typically uses a specific workbook template. Workbook access is either denied, read-only, or full access. Read-only access allows a user to create a workbook for the template, but the user cannot edit any values or commit the workbook. The read-only workbook can be refreshed.
When users save workbooks, they assign one of three access permissions:
World—Allow any user to open and edit the workbook.
Group—Allow only those users in their same group to open and edit the workbooks.
User—Allow no other users to open and edit the workbook.
|
Note: If you choose to customize your permissions, keep in mind the Principle of Least Privilege which states; only give a user enough permissions to do their job and nothing more. |
|
Note: A user must have access to the workbook template in order to access the workbook, even if the workbook has world access rights. |
Table 2-1 provides guidance on what user roles should have access to each workbook.
Table 2-1 Workbook Access Based on User Roles
| Workbook | User Roles |
|---|---|
|
New Item Administration |
Forecast Analyst |
|
New Item Review |
Forecast Analyst |
|
New Item Maintenance |
Forecast Analyst |
|
Business Support Like Store |
Forecast Analyst |
|
Forecaster Like Store |
Forecast Analyst |
|
Preprocess Administration |
Forecast Analyst, Forecast Manager |
|
Source Measure Maintenance |
Forecast Analyst, Forecast Manager |
|
Floating Events Admin |
Forecast Analyst, Forecast Manager |
|
Extra Week Administration |
Forecast Analyst, Forecast Manager |
|
Short Life Cycle Maintenance |
Forecast Analyst, Forecast Manager |
|
Forecast Administration |
Forecast Analyst, Forecast Manager |
|
Forecast Maintenance |
Forecast Analyst, Forecast Manager |
|
Run Batch Forecast |
Forecast Analyst, Forecast Manager |
|
Forecast Approval |
Forecast Analyst, Forecast Manager |
|
Forecast Alert |
Forecast Analyst, Forecast Manager |
|
Forecast Delete |
Forecast Analyst, Forecast Manager |
|
Forecast Scorecard |
Forecast Analyst, Forecast Manager |
|
Interactive Forecasting |
Forecast Analyst, Forecast Manager |
|
Grouping Management |
Forecast Analyst, Forecast Manager |
|
Promotion Planner |
Forecast Analyst, Forecast Manager |
|
Promotion Management |
Forecast Analyst, Forecast Manager |
|
Promotion Maintenance |
Forecast Analyst, Forecast Manager |
|
Promo Effectiveness |
Forecast Analyst, Forecast Manager |
|
Profile Administration |
Forecast Analyst, Forecast Manager |
|
Profile Maintenance |
Forecast Analyst, Forecast Manager |
|
Run Batch Profile |
Forecast Analyst, Forecast Manager |
|
Profile Approval |
Forecast Analyst, Forecast Manager |
|
Breakpoint Administration |
Forecast Analyst, Forecast Manager |
|
Delete Cluster Run |
Forecast Analyst, Forecast Manager |
|
Cluster Review |
Forecast Analyst, Forecast Manager |
|
Generate Breakpoint Grades |
Forecast Analyst, Forecast Manager |
|
Generate Clusters |
Forecast Analyst, Forecast Manager |
For more information on security, see the Oracle Retail Predictive Application Server Administration Guide for the Fusion Client.
For more information on translation for RDF, see Chapter 12, "Internationalization".
Translation is the process of interpreting and adapting text from one language into another. For more information, refer to "Translation"
