9 Dynamic Planning Configuration

Retail Insights supports Planning at four levels for five different hierarchies (Merchandise Hierarchy, Organization Hierarchy, and Calendar Hierarchy, Supplier Hierarchy,Product attributes). 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 as follows:

Configure Planning Levels

First Create a wallet for executing Planning configuration script for Weblogic Username/Password and RPD Username/Password. RPD Username can be set to "RI_RPD" since RPD does not have a username specifically. Passing WebLogic alias and RPD alias as an argument while running script connects to WebLogic user and executes the configuration script to deploy the RPD with the RPD alias provided.

Note:

Reuse the wallet already created by the Installer if exists else create wallet using the steps below.

Create a Wallet

Perform the following steps to create a wallet:

Set the JAVA_HOME environment variable.

Navigate to the following directory:

cd <STAGING_DIR>/ori/installer/ori/Build/orpatch/deploy/retail-public-security-api/bin

Add execute permission to the save_credential.sh scripts in above location
```
chmod +x save_credential.sh.
```
Create an alias for the WebLogic and RPD user by running save_credential.sh with the following arguments:
```
./save_credential.sh  -a <alias_name> -u <username> -l </location/wallet/dir> -p <Partiton_Key>
```
Where:
- <alias_name>: Alias Name for the User
- <username>: Username
- </location/wallet/dir>: Location where wallet needs to be created
- <Partiton_Key>: RI Partition Key
For example:
```
./save_credential.sh  -a WEBLOGIC-ALIAS -u wlsadmin -l/u01/retail/ri/wallet -p RI_KEY
 
./save_credential.sh  -a RPD-ALIAS -u RI_RPD -l /u01/retail/ri/wallet -p RI_KEY
```

Run PlanningConfigurationScript.sh

Perform the following steps to run PlanningConfigurationScript.sh:

Navigate to the following directory

cd  <RETAIL_HOME>/ra_obiee_source_code/OBIEE_BAR_Deployment

Unzip the "OBIEE_BAR_FILE_DEP.zip" file in the above path.
Run the PlanningConfigurationScript.sh with the following arguments:
```
./PlanningConfigurationScript.sh RETAIL_HOME OBIEE_HOME PLANNING_CONFIG_HOME MODE WEBLOGIC_USER_ALIASNAME RPD_ALIAS_NAME WALLET_PATH PARTITON_KEY
```
Where:
- 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, PlanningConfigurationScript.sh are placed
- MODE: File mode (f) or Database Mode (d)
- WEBLOGIC_USER_ALIASNAME: Alias name of WebLogic user created in wallet
- RPD_ALIAS_NAME: Alias name of RPD user created in wallet
- WALLET_PATH: Path where wallet is created
- PARTITON_KEY: RI Partition Key

Database Mode

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

Planning Configuration PARAM_NAME list

RI_PLAN1_CAL_LEVEL,
RI_PLAN1_ORG_LEVEL
RI_PLAN1_PROD_LEVEL
RI_PLAN1_SUPP_LEVEL
RI_PLAN1_ATTR_LEVEL
RI_PLAN2_CAL_LEVEL
RI_PLAN2_ORG_LEVEL
RI_PLAN2_PROD_LEVEL
RI_PLAN2_SUPP_LEVEL
RI_PLAN2_ATTR_LEVEL
RI_PLAN3_CAL_LEVEL
RI_PLAN3_ORG_LEVEL
RI_PLAN3_PROD_LEVEL
RI_PLAN3_SUPP_LEVEL
RI_PLAN3_ATTR_LEVEL
RI_PLAN4_CAL_LEVEL
RI_PLAN4_ORG_LEVEL
RI_PLAN4_PROD_LEVEL
RI_PLAN4_SUPP_LEVEL
RI_PLAN4_ATTR_LEVEL

FLEX_FACT Configuration PARAM_NAME list

RI_FLEXFACT_ATTR1_LEVEL
RI_FLEXFACT_CAL_LEVEL
RI_FLEXFACT_ORG_LEVEL
RI_FLEXFACT_PROD_LEVEL
RI_FLEXFACT_SUPP_LEVEL

Note:

FLEX_FACT Configuration supports all configuration levels supported by planning configuration.
Above FLEX_FACT Configuration PARAM_NAME list values should be set in C_ODI_PARAM table for FLEX_FACT Configuration and only Planning Configuration PARAM_NAME list values should be set for Planning Configuration.
PlanningConfigurationScript.sh script is used for both FLEX_FACT and Planning Configurations.

The following values are valid for the C_ODI_PARAM table PARAM_VALUE for above PARAM_NAME:

Organization:

COMPANY
CHAIN
AREA
REGION
DISTRICT
LOCATION
CHANNEL
PRICE_ZONE
ALL

Product:

CMP
DIV
GRP
DEPT
CLS
SBC
ITEM
ITEM LEVEL1
ALL

Calendar:

YEAR
HALFYEAR
QUARTER
PERIOD
WEEK
DAY

Supplier:

SUPPLIER
PARENT_SUPPLIER
ALL

Product Attributes:

STYLE
FLAVOR
SCENT
FABRIC
SIZE
C ( C denotes Color)
B (B denotes Brand)

Note:

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

File Mode (f)

In File Mode user has to first set Planning levels in the file properties.txt in the path where OBIEE_BAR_FILE_DEP.zip is unzipped, then run PlanningConfigurationScript.sh script with MODE argument f.

Note:

FLEX_FACT Configuration requires setting of only FLEX_FACT levels in properties.txt and for planning only planning levels should be set.

Figure 9-1 Properties.txt File

Note:

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

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

Organization:

COMPANY
CHAIN
AREA
REGION
DISTRICT
LOCATION
CHANNEL
PRICE ZONE
ALL

Product:

CMP
DIV
GRP
DEPT
CLS
SBC
ITEM
ITEM LEVEL1
ALL

Calendar:

YEAR
HALFYEAR
QUARTER
PERIOD
WEEK
DAY

Supplier:

SUPPLIER
PARENT_SUPPLIER
ALL

Product Attributes:

STYLE
FLAVOR
SCENT
FABRIC
SIZE
C (C denotes Color)
B (B denotes Brand)

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
Executes jar file to modify RPD reading planning levels from properties.txt (file mode) or C_ODI_PARAM table (Database Mode).
Uploads modified RPD (default.rpd).