9 Vendor Planning Configuration

Retail Insights supports Vendor Planning at four possible combinations for four different hierarchies (Merchandise Hierarchy, Organization Hierarchy, and Calendar Hierarchy, Supplier Hierarchy). These possible combinations are configurable. Planning levels need to be set in C_ODI_PARAM table before running PlanningConfigurationScript.sh script. Instructions to configure planning levels in OBIEE are below.

Configure Planning Levels

Perform the following procedure to configure the four planning levels:

1. Create the folder OBIEE_DEP inside RETAIL_HOME path.

2. Copy all files from OBIEE_BAR_FILE_DEP.zip in the <STAGING_DIR>/ori/installer/ori/aps/obiee/OBIEE_BAR_Deployment path into the RETAIL_HOME/OBIEE_DEP folder.

3. Run the PlanningConfigurationScript.sh in the RETAIL_HOME/OBIEE_DEP path with the following arguments:

   ./PlanningConfigurationScript.sh  RETAIL_HOME  OBIEE_HOME  PLANNING_CONFIG_HOME  MODE WEBLOGIC_USER_ALIASNAME RPD_ALIAS_NAME WALLET_PATH
   

   • RETAIL_HOME: Retail Home path

   • OBIEE_HOME: OBIEE Home Path

   • PLANNING_CONFIG_HOME: Path where all input xml's, properties.txt file, keyTableNames.txt file, all java files, jar files, and PlanningConfigurationScript.sh are placed.

   • MODE: File mode (f) or Database Mode (d)

   • WEBLOGIC_USER_ALIASNAME: Alias name of Weblogic user created in OBIEE wallet to retrieve Weblogic Username and Weblogic Password (WEBLOGIC_USER)

   • RPD_ALIAS_NAME: Alias name of RPD user created in OBIEE wallet to retrieve RPD Password (RPD_USER)

   • WALLET_PATH: Path where wallet is created.

Note: In each environment, before running this script, the Wallet needs to be created to store the WebLogic username, WebLogic password, RPD username, and RPD password. The RPD username can be given any name. For Wallet purposes it needs to be added but is not retrieved from the wallet. Passing WEBLOGIC_USER_ALIASNAME as an argument while running the script retrieves the WebLogic username and WebLogic password from OBIEE_WALLET through java code. Passing RPD_ALIAS_NAME as an argument while running the script retrieves the RPD Password from OBIEE_WALLET through java code. Steps to create the Wallet can be found in the following location: https://confluence.oraclecorp.com/confluence/display/OREMR/Retail+Insights+17.0.x+-+Installation+Steps+for+High+Availability

Database Mode

In database mode, the user has to first set Planning levels in the C_ODI_PARAM table then run the PlanningConfigurationScript.sh script with MODE argument d. Planning levels need to be set for below PARAM_NAME in the C_ODI_PARAM table.

• RI_PLAN1_CAL_LEVEL,

• RI_PLAN1_ORG_LEVEL

• RI_PLAN1_PROD_LEVEL

• RI_PLAN1_SUPP_LEVEL

• RI_PLAN2_CAL_LEVEL

• RI_PLAN2_ORG_LEVEL

• RI_PLAN2_PROD_LEVEL

• RI_PLAN2_SUPP_LEVEL

• RI_PLAN3_CAL_LEVEL

• RI_PLAN3_ORG_LEVEL

• RI_PLAN3_PROD_LEVEL

• RI_PLAN3_SUPP_LEVEL

• RI_PLAN4_CAL_LEVEL

• RI_PLAN4_ORG_LEVEL

• RI_PLAN4_PROD_LEVEL

• RI_PLAN4_SUPP_LEVEL

The following values are valid for the C_ODI_PARAM table:

Organization:

• COMPANY

• CHAIN

• AREA

• REGION

• DISTRICT

• LOCATION

• CHANNEL

• ALL

Product:

• CMP

• DIV

• GRP

• DEPT

• CLS

• SBC

• ITEM

• ALL

Calendar:

• YEAR

• HALFYEAR

• QUARTER

• PERIOD

• WEEK

• DAY

SUPPLIER:

• SUPPLIER

• PARENT_SUPPLIER

• ALL

Note: ALL indicates that Plan data is not at that dimension level.

File Mode (f)

In File Mode, the user has to first set Planning levels in the properties.txt file in the RETAIL_HOME/OBIEE_DEP path then run PlanningConfigurationScript.sh script with MODE argument f.

Note: While running in filemode, planning levels to be set in properties.txt should match the C_ODI_PARAM table planning level entries.

Figure 9-1 Properties.txt File

The following values are valid for the properties.txt file:

Organization:

• COMPANY

• CHAIN

• AREA

• REGION

• DISTRICT

• LOCATION

• CHANNEL

• ALL

Product:

• CMP

• DIV

• GRP

• DEPT

• CLS

• SBC

• ITEM

• ALL

Calendar:

• YEAR

• HALFYEAR

• QUARTER

• PERIOD

• WEEK

• DAY

SUPPLIER:

• SUPPLIER

• PARENT_SUPPLIER

• ALL

Note: ALL indicates that Plan data is not at that dimension level.

PlanningConfigurationScript.sh Script

The PlanningConfigurationScript.sh script executes the following three operations:

• Downloads the deployed RPD with name default.rpd to the location RETAIL_HOME/OBIEE_DEP

• Executes jar file to modify RPD reading planning levels from properties.txt (file mode) or C_ODI_PARAM table (Database Mode).

  Modifying RPD includes setting content levels in the Logical Table source for all planning dimension levels and modifying physical joins according to new content levels.

• Uploads modified RPD (default.rpd).