2 Implementation Overview
This chapter provides an overview of the implementation of Oracle Retail AI Foundation Cloud Services.
Implementation Process
This section provides details about the implementation process. It assumes that the underlying platforms have been properly implemented. This includes servers, Oracle database, RADM, and WebLogic application servers.
Note:
Data interfaces are required by the application to support the various supported modules. For details about the data interface, see the following:
Oracle Retail Analytics and Planning Cloud Services Data Interfaces
Implementation Steps
The order of steps provided here is designed to simplify the process. The advanced user may be able to change the process order or skip some steps; however, that is not recommended and not documented here.
Note:
See Configuration for details about application configurations that can be modified as part of a deployment.
Configure the Application Roles and Users
Before any user can log into any application, you must set up application roles, add users, and assign users to the correct roles. To do this, complete the steps described in Configuration.
Data Load Overview
During an implementation of any applications, several steps are required. This section provides some details about this process.
There is a script called RSE Config and RSE Master for the common data. There are similar scripts for each application (for example, there is a CIS Config and CIS Master script). All the *Config and *Master scripts are similar in nature, so this section focuses on the common one. However, the concepts apply equally to the application-specific scripts.
Edit and Load Common Seed Data
All the applications share a set of configurable parameters that must be loaded into the RSE_CONFIG table. All have default values and are configurable and editable by the administrator. This section explains how to load and, if desired, edit these parameters.
The .ctl files for common configuration data must be edited and loaded into the staging tables. This data is common to all the applications. The application-specific .ctl files are located in their own application seed_data folders (for example, orase\installer\orase16\so\db\seed_data).
Review the .ctl files in that directory and adjust any configurations needed for the environment. Some configurations cannot be changed after the application has been used; therefore, you must carefully consider the parameters listed in Table 2-1. The remainder are optional and default to reasonable valuables.
The following configuration parameters must be initialized during setup. The values for hierarchy level and type are recommended for any installation that integrates with the CMPO installation and must match for all installed applications.
Table 2-1 Mandatory Common RSE Database Configuration Parameters
| Application | Parameter | Description | Value |
|---|---|---|---|
|
RSE |
CAL_PERIOD_LEVEL |
This is the calendar hierarchy level that is used to drive RSE processing. |
4 |
|
RSE |
CHAIN_LEVEL_DESC |
The description to use for any top level hierarchy element, when one must be manually created. |
CHAIN |
|
RSE |
CMGRP_HIER_TYPE |
The hierarchy ID to use for the CMPO. Recommendation is for a normal installation with CMPO. |
1 |
|
RSE |
CMGRP_LEVEL_ID |
The hierarchy level ID that contains the level of the product hierarchy where the CMPO level exists (installation configuration). Recommendation is for a normal installation with CMPO. |
5 |
|
RSE |
MT_TZ |
The time zone that is used by application server(s), that is, by the middle-tier. It must match SELECT tzname FROM V$TIMEZONE_NAMES. |
America/New_York |
|
RSE |
PRIMARY_LANGUAGE_CODE |
The name of the language code to use for all RSE data sourced from RI. |
EN |
|
RSE |
RA_FISCAL_CAL_ID |
The ID of the calendar to use from RI (since RI supports multiple calendars). |
1240 |
|
RSE |
TRADE_AREA_HIER_TYPE |
The hierarchy ID to use for the Trade Area (installation configuration). |
6 |
|
RSE |
UI_TZ |
The time zone for display. It must match SELECT tzname FROM V$TIMEZONE_NAMES. |
America/New_York |
Perform Attribute Preprocessing for CDT and DT, as Appropriate
Product attributes are required by CDT and DT and are stored in the RADM. Attribute preprocessing is independent of the AIF database and happens in RI or flat files generated by the user. Once these tables and files are correct, you can load the resulting attributes in the AIF schema as part of the data load process.
Here are the basic attribute pre-processing steps:
-
Populate RADM with raw attribute data.
-
Optionally, perform translation.
-
Parse.
-
Cleanse and standardize.
-
Categorize and label.
-
Define the attributes.
-
Bin and group.
For details on these steps, see Attribute Processing.
Mandatory Configuration Parameters
Table 2-2 contains the mandatory configuration parameters for CDT.
Table 2-2 Mandatory CDT Configuration Parameters
| Application | Parameter | Description | Value |
|---|---|---|---|
|
CDT |
CDT_CAL_HIER_TYPE |
The hierarchy ID to use for the fiscal calendar (installation configuration). |
11 |
|
CDT |
CDT_CAL_LEVEL_ID |
The hierarchy level ID that contains the level of the calendar hierarchy that CDT operates on. (This should equate to the Week - Installation configuration). |
4 |
|
CDT |
CDT_CMGRP_LEVEL_ID |
The hierarchy level ID that contains the level of the product hierarchy that CDTs are created for (installation configuration). |
5 |
|
CDT |
CDT_CUSTSEG_HIER_TYPE |
The hierarchy ID to use for customer segment (installation configuration). |
4 |
|
CDT |
CDT_CUSTSEG_LEVEL_ID |
The hierarchy level ID that contains the level of the customer segment hierarchy that CDTs are created for (installation configuration). |
2 |
|
CDT |
CDT_LOC_HIER_TYPE |
The hierarchy ID to use for location (installation configuration). |
2 |
|
CDT |
CDT_LOC_LEVEL_ID |
The hierarchy level ID that contains the level of the location hierarchy that CDTs are created for (installation configuration). |
Best equivalent for trade area level |
|
CDT |
CDT_PROD_HIER_TYPE |
The hierarchy ID to use for the CMPO (installation configuration). The recommendation is for a normal installation with CMPO. |
1 |
|
CDT |
DEF_NUM_WEEKS_FOR_SIMILARITY |
The default number of weeks of sales transaction data to be used by the similarity process. This is used when the user does not specify time intervals. |
15 |
Table 2-3 contains the mandatory configuration parameters for DT.
Table 2-3 Mandatory DT Configuration Parameters
| Application | Parameter | Description | Value |
|---|---|---|---|
|
DT |
AE_CALC_INT_LENGTH |
The number of weeks to group together for in an interval for the AE calculation. |
4 |
|
DT |
CDT_SIMILARITY_AVAILABLE |
Whether the CDT similarity has been made available to DT. |
Y |
|
DT |
DT_CAL_HIER_TYPE |
The hierarchy ID to use for the fiscal calendar. |
11 |
|
DT |
DT_CAL_LEVEL_ID |
The hierarchy level ID that contains the level of the calendar hierarchy that DT operates on. (It should equate to week.) |
4 |
|
DT |
DT_CMGRP_LEVEL_ID |
The hierarchy level ID that contains the level of the product hierarchy that DTs are created for. |
5 |
|
DT |
DT_LOC_HIER_TYPE |
The hierarchy ID to use for location. |
5 |
|
DT |
DT_LOC_LEVEL_ID |
The hierarchy level ID that contains the level of the location hierarchy that DTs are created for. |
Best equivalent for trade area level |
|
DT |
DT_PROD_HIER_TYPE |
The hierarchy ID to use for the CMPO. |
1 |
|
DT |
PR_LOC_STATUS_LAST_COMPLETED_WK |
The last completed week for the SKU/Store ranging data copying. |
Week ID from RSE_CAL_HIER |
|
DT |
WGT_CALC_INTERVAL_LENGTH |
The number of weeks to group into an interval that is then used to perform weight calculations. |
4 |
Table 2-4 contains the mandatory configuration parameters for AC.
Table 2-4 Mandatory AC Configuration Parameters
| Application | Parameter | Description | Value |
|---|---|---|---|
|
CIS |
CIS_DFLT_CALENDAR_HIER_TYPE_ID |
the default calendar hierarchy for clustering. |
11 |
|
CIS |
CIS_DFLT_LOCATION_HIER_TYPE_ID |
The default location hierarchy for clustering. |
2 |
|
CIS |
CIS_DFLT_PRODUCT_HIER_TYPE_ID |
The default product hierarchy for clustering. |
1 |
|
CIS |
PERF_CIS_APPROACH |
The approach to use for performance based clustering. The available options are CDT and DT. |
CDT |
Note:
There are no mandatory configuration parameters for MBA.
Table 2-5 Mandatory ASO Configuration Parameters
| Application | Parameter | Description | Value |
|---|---|---|---|
|
SO |
SO_CAL_HIER_TYPE |
The hierarchy ID to use for the calendar (installation configuration). |
10 |
|
SO |
SO_FISCAL_CAL_HIER_TYPE |
The hierarchy ID to use for the fiscal calendar (installation configuration). |
11 |
|
SO |
SO_LOC_HIER_TYPE |
The hierarchy ID to use for location (installation configuration). |
2 |
|
SO |
SO_PROD_HIER_LEVEL_FOR_LEAF_NODE |
The product hierarchy level number for leaf node. |
7 |
|
SO |
SO_PROD_HIER_TYPE |
The hierarchy ID to use for the product (installation configuration). |
1 |
Retail Home Integration
In a Next Gen implementation, you can view usage metric values. In order to use this feature, you must ensure that the RSE_UPDATE_USAGE_METRIC process in the Process Orchestration and Monitoring application is set up as an enabled job as part of your batch schedule. This is the process that gathers the usage metric values and saves them to the subscribed modules during onboarding. See "Process Orchestration and Monitoring" for additional details on how to set up and enable the process.