Oracle® Retail Insights Cloud Service Suite Implementation Guide Release 16.0.203 E90412-01 |
|
![]() Previous |
![]() Next |
Retail Insights supports Merchandise Financial Planning (MFP) at three possible combinations of three different hierarchies (Merchandise Hierarchy, Organization Hierarchy, and Calendar Hierarchy). These possible combinations can be configured during the installation. However, the front-end rpd file has to be modified to match the configuration.
Before making any changing to the rpd file, copy the original files to a different directory in case you need to refer to them at a later date:
Perform the following procedure to modify the rpd file::
Before modifying, rename the existing rpd file on the server. Do not overwrite.
Get the merchandise hierarchy level, organization hierarchy level, and calendar level that are set up for option1, option2, and option3. This information can be found in the database table C_ODI_PARAM.
Open the rpd file in offline mode using the administration tool.
Double-click the physical table that you want to modify. The Physical Table dialog appears.
Click the Foreign key tab. You will see all the foreign keys that are associated with this physical table. These foreign keys are named by the dimension level name, such as SBC for merchandise hierarchy at subclass level. The following screen is an example for W_RTL_MFPOP_PRODUCT1_LC1_T1_F (before the configuration is done).
Remove all unrelated foreign keys and keep the foreign keys whose levels are defined for that specific option (from step 1) and click OK. The following screen shows the unused foreign keys removed. This is for the case when option 1 is defined at the item/location/day level. The foreign key Fact_W_RTL_MFPOP_PROD1_LC1_T1_F_COMPANY is reserved for the case when company level is used for organization hierarchy. The physical tables that need to be modified include: .
Fact_W_RTL_MFPCP_PRODUCT1_LC1_T1_F
Fact_W_RTL_MFPOP_PRODUCT1_LC1_T1_F
Fact_W_RTL_MFPCP_PRODUCT2_LC2_T2_F if option 2 is set
Fact_W_RTL_MFPOP_PRODUCT2_LC2_T2_F if option 2 is set
Fact_W_RTL_MFPCP_PRODUCT3_LC3_T3_F if option 3 is set
Fact_W_RTL_MFPOP_PRODUCT3_LC3_T3_F if option 3 is set
Under the BMM layer, expand Core Business Model, and expand logic table Fact - Retail Planning. Expand Sources and you will see all logical table source used by planning. There are six logical table source used by Merchandise Financial Planning with flexible options. There are two tables for option1, two tables for option2, and two tables for option3. All their names contain string "MFP"
If the option2 is not defined, then disable all logical table sources used by option 2 or option 3. If option 2 is defined, but option 3 is not, then disable all logical table sources used by option 3. To disable the logical table source, double-click the logical table source that you want to disable, click the General tab, and then check the Disabled checkbox.
Set content for each logical table source (maximum of 6) used by merchandise flexible planning. You need to do this for every merchandise financial planning logical table source that is not disabled.
Double-click the logic table source that you want to set.
Click the Content tab.
Select Logical Level for Logical Dimension Date Retail Fiscal Calendar, Retail Organization As Was, and item. The valid values for fiscal calendar are Fiscal Day Detail, Fiscal Week, Fiscal Period, Fiscal Quarter, or Fiscal Year. The valid values for organization are Location, Channel, or Company. Company is used when the organization hierarchy level is set at company level in the configuration. The valid values for merchandise hierarchy (item) are Product Detail if the level is set at item, subclass, class, department, group, and division.
Click OK. The screen below is an example when the option is set at item/location/day level.
Save the rpd file and exit.
Upload the rpd file to the BI Setver and bounce the BI services.