| Oracle Retail AI Foundation Cloud Services Implementation Guide Release 23.1.101.0 F76898-04 |
|
 Previous |
 Next |
| Oracle Retail AI Foundation Cloud Services Implementation Guide Release 23.1.101.0 F76898-04 |
|
Previous |
Next |
This chapter describes the major application configuration points, including:
|
Note: Since AA is distinct from the other applications, much of what is described here is not applicable for AA. For clarity, AA implementation, configuration, operations and data model are described separately in Chapter 8, "Affinity Analysis.". |
|
Note: For more information, see Oracle Retail AI Foundation Cloud Services Administration Guide. |
For authorization, the applications have been built with role-based access. Access to application user interface components is done by assigning application roles. Application roles are defined as part of the application and deployed as part of the installation process. Application roles are mapped to enterprise roles during initial environment provisioning. Enterprise roles exist as LDAP groups in OID. Refer to the Oracle Retail AI Foundation Cloud Service User Guide for the definition of standard user roles.
This section provides detailed instructions on setting up enterprise-level user management using Oracle WebLogic 12c with Enterprise Manager. The user management configuration is handled using the WLS Console and the WLS Enterprise Manager (EM).
The roles listed in Table 15-1 are required to update the configurations in the data management section of the application. For more information, see Oracle Retail AI Foundation Cloud Services Administration Guide.
Table 15-1 Data Management Configuration Roles
| Roles | Access to Application Configuration |
|---|---|
|
ANALYTIC_EXPERT_JOB |
CDT |
|
ANALYTIC_EXPERT_JOB |
DT |
|
FORECAST_MANAGER_JOB |
ASO |
|
CLUSTERING_ADMINISTRATOR_JOB |
AC |
|
CUSTOMER_SEGMENT_ADMINISTRATOR_JOB |
CS |
|
ATTRIBUTE_EXTRACTION_JOB |
AE |
|
RETURN_LOGISTICS_JOB |
RL |
|
SOCIAL_ANALYTICS_JOB |
SA |
|
PRICING_ADMINISTRATOR_JOB |
PRO |
|
MARKET_BASKET_ANALYSIS_JOB |
MBI |
This section provides details about application configurations that can be modified as part of a deployment. The list of configurations is limited to those settings that most likely need to be reviewed and adjusted before the applications are used. Some configuration points cannot be adjusted after initial setup, so a careful review of the configurations should be done. For a complete list of configurable values, see the complete list of configuration values in RSE_CONFIG.
Any installation configuration must be set before the application is initialized with data and used.
|
Note: Before beginning any advanced customization, you must consult with development. |
The RSE_CONFIG table is a generic table that contains various application configurations. The DESCR column describes the configuration and provides any relevant information regarding what each specific configuration controls. The APPL_CODE column is a useful filter to organize the configurations by the application module.
The following application abbreviations are used
AE - Attribute Extraction
CDT - Customer Decision Trees
CIS - Advanced Clustering
DT - Demand Transference
IO - Inventory Optimization
MBA - Affinity Analysis
PMO - Forecasting
PRO - Offer Optimization
RL - Return Logistics
RSE - Retail Science Platform (generic configurations)
SA - Social Analytics
SPO - Size Profile Optimization
SO - Space Optimization
The PARAM_NAME is the name of the configuration.
The PARAM_VALUE is the value currently associated with the configuration.
The CONFIGURABLE_FLG column indicates whether the configuration is safe to change.
The UPDATEABLE_FLG column is used to control whether application code is able to update the configuration.
|
Note: Use caution when changing a value that the application code can update after the application has started to be used. |
The RSE_CONFIG_CODE table is an extension table to the RSE_CONFIG table. It allows for overrides of certain configurations when an additional qualifier is present. All descriptions for the columns in RSE_CONFIG apply here as well. The additional column CONFIG_CODE allows overriding a value for a specific qualifier. Application code does not always support the use of these configurations, but Affinity Analysis, for example, uses this to set up configurations for different hierarchy levels.
The following is a list of configurations that can be adjusted. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='RSE'.
Table 15-2 Generic Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
CAL_PERIOD_LEVEL |
4 |
This is the calendar hierarchy level that is used to drive the processing (installation configuration). |
Usually this value should be set to the Fiscal Week level of the Fiscal Calendar. The number 4 refers to the fourth level in RSE_HIER_LEVEL table. This cannot be adjusted after initial setup. |
|
CMGRP_HIER_TYPE |
1 |
The hierarchy ID to use for the CM Group (installation configuration). |
If an alternate hierarchy is to be used, then this configuration must specify that hierarchy type. Otherwise it must reflect the primary product hierarchy type. The value represented here relates to the ID in RSE_HIER_TYPE. This cannot be adjusted after initial setup. |
|
CMGRP_LEVEL_ID |
5 |
The hierarchy level ID that contains the level of the product hierarchy where the CM Group level exists (installation configuration). |
Once the CMGRP_HIER_TYPE is configured, this level must be set to indicate the level of the hierarchy (RSE_HIER_LEVEL) that defines the categories. |
|
PRIMARY_LANGUAGE_CODE |
EN |
The name of the language code to use for all RSE data sourced from RI (installation configuration). |
Data values stored in the database are not multi-language capable, and are not affected by the UI language settings, like the UI labels are. This setting must select the language code for which data should be shown in the UI. |
|
RA_FISCAL_CAL_ID |
1240 |
ID of the calendar to use from RI since RI supports multiple calendars (installation configuration). |
This value must match the ID of the desired fiscal calendar loaded into W_MCAL_PERIOD_DS.MCAL_CAL_ID. |
|
CHAIN_LEVEL_DESC |
CHAIN |
The description to use for any top level hierarchy element when one must be manually created. |
This description must be adjusted if a different description for the top level of the hierarchy is desired. |
|
DEFAULT_LOCALE |
en_US |
The default locale to use for rendering elements that cannot support multiple locales. |
Adjust this value so that it contains the correct LOCALE setting for most users of the application. |
|
DISPLAY_DATE_FORMAT |
Mon dd, yyyy |
The default date mask to be used by UI. |
Adjust this so that the format of dates can be displayed as desired. |
|
FAKE_CUST_DAY_TXN_THRESHOLD |
10 |
The maximum daily transaction threshold to identify a fake customer. |
This setting must be adjusted to the maximum number of daily transactions that a normal customer usually has. This allows all other customers with higher transactions counts to be excluded from processing. |
|
UI_TZ |
America/New_York |
Timezone for display. Must match SELECT tzname FROM V$TIMEZONE_NAMES. |
This setting must be adjusted so that it contains a proper time zone setting indicating where most users run the UI. |
The following is a list of configurations that can be adjusted for the Advanced Clustering application. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='CIS'.
Store Exclusion can be used to filter and identify which stores are to be excluded for Clustering. To enable this functionality, EXCLUDE_LOC_ATTR is set by specifying a SHORT_DB_NAME from the RSE_BUSINESS_OBJECT_ATTR_MD BOAM) table in RSE_CONFIG. This can be configured via the Control and Tactical Center. Locations in RSE_LOC_ATTR table with the BUSINESS_OBJECT_ATTR_MD_ID value similar to the ID of from BOAM table, which is configured in the config table, will be excluded.
For example, EXLUDE_LOC_ATTR of RSE_CONFIG is set to CFA_ATTRIB_2345 as its value. A check is performed to fetch the ID from the BOAM table that contains this SHORT_DB_NAME. This ID is then used to obtain all locations from the RSE_LOC_ATTR table. These locations are then flagged to be excluded from clustering.
Table 15-3 AC Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
PERF_CIS_APPROACH |
CDT |
The approach to use for performance-based clustering. Available options are CDT and DT. |
If the CDT application is in use, then this configuration must be set to CDT, which will result in the use of attribute groups for product attribute clustering. Otherwise, it must be set to DT, which will result in the use of the top raw attribute values. This cannot be adjusted after initial setup. |
|
ATTR_NAME_SEPARATOR |
- |
The separator character(s) to use to separate the different components of the attribute names in CIS_TCRITERIA_ATTR. |
Adjust this value if a different separator is desired in the UI for attribute names built from multiple values. This cannot be adjusted after initial setup. |
|
CIS_CONTR_SLS_SRC_COLUMN |
SLS_AMT |
Source column for contribution BI chart sales values. SLS_AMT, SLS_QTY, PROFIT_AMT are the allowable values. |
Adjust this value as needed so that the BI shows contributions based on the desired sales column. |
|
CIS_CONTR_X_SRC_COLUMN |
SLS_AMT |
Source column for the x axis of the contribution BI chart. SLS_AMT, SLS_QTY, PROFIT_AMT are the allowable values. |
Adjust this value as needed so that the BI shows contributions based on the desired sales column. |
|
CIS_CONTR_Y_SRC_COLUMN |
SLS_QTY |
Source column for the y axis of the contribution BI chart. SLS_AMT, SLS_QTY, PROFIT_AMT are the allowable values. |
Adjust this value as needed so that the BI shows contributions based on the desired sales column. |
|
CIS_DFT_PIVOT_LVL |
6 |
Default pivot level to show in explore data. |
This configuration indicates the lowest level of the organization hierarchy (see rse_hier_level) that should be shown in the Explore Data pivot table. A value of 6 allows store locations to be visible, but this can be adjusted to a higher level if this level of detail is not desired. |
|
CIS_IDX_AVG_SRC_COLUMN |
SLS_AMT |
Name of the column to use for index-to-average BI calculations. SLS_AMT, SLS_QTY, PROFIT_AMT are the allowable values. |
Adjust this value as needed so that the BI shows index to averages based on the desired sales column. |
|
CIS_NUMERIC_DFT |
0 |
Default attribute value for numeric. |
This can be adjusted so that attributes without a value are displayed with the desired value. This cannot be adjusted after initial setup. |
|
CIS_STRING_DFT |
UNKNOWN |
Default attribute value for string. |
This can be adjusted so that attributes without a value are displayed with the desired value. This cannot be adjusted after initial setup. |
|
CIS_VARIABILITY_IDX_SRC_COLUMN |
SLS_AMT |
Name of the column to use for variability index BI calculations. SLS_AMT, SLS_QTY, PROFIT_AMT are the allowable values. |
Adjust this value as needed so that the BI shows variability indexes based on the desired sales column. |
|
DEFAULT_NUM_ATTR_VALUE |
15 |
Constant for number of discrete values allowed for store attribute clustering. |
Any attribute that has more than this number of distinct categorical values is not available for use as an attribute. |
|
DEFAULT_STR_CATEGORICAL_ATTR |
UNKNOWN |
Default string description for row added in cis_tcriteria_attr_type_value table for unmatched grouping. |
This can be adjusted so that attributes without a value are displayed with the desired value. This cannot be adjusted after initial setup. |
|
EXCLUDE_LOC_ATTR |
CFA_ATTR5_2345 |
Contains the name of a SHORT_DB_NAME from RSE_BUSINESS_OBJECT_ATTR_MD table that is used to exclude specific stores that are in RSE_LOC_ATTR to be excluded from AC processing. |
Setting this configuration to NULL disables the Store Exclusion interface. |
|
INSIGHT_BI_SALES_AMT_MARGIN |
N |
Flag to show sales BI based on sales amount and margin. |
Either INSIGHT_BI_SALES_AMT_MARGIN or INSIGHT_BI_SALES_AMT_UNIT can be assigned a Y so that the BI displays the BI using the desired columns. |
|
INSIGHT_BI_SALES_AMT_UNIT |
Y |
Flag to show sales BI based on sales amount and units |
- |
|
MAX_HIST_WEEK_CNT |
104 |
The maximum number of weeks that must be selectable by the UI when processing historic data. |
- |
|
MAX_ITEMS_IN_GRAPH_CLUSTER_DETAIL |
-1 |
Maximum number of clusters to be displayed in cluster details graph. |
A value of -1 results in an unlimited number of values. Adjust if necessary. |
|
MAX_ITEMS_IN_GRAPH_CLUSTER_LIST |
-1 |
Maximum number of clusters to be displayed in cluster list graph. |
A value of -1 results in an unlimited number of values. Adjust if necessary. |
|
MNG_RUN_NO_WKS |
26 |
Display run for past n weeks. |
- |
|
PERF_ATTR_TOPN_COUNT |
3 |
The number of attribute values to be used per product category for performance-based clustering. |
If PERF_CIS_APPROACH configuration is DT, then this configuration will limit the number of attribute values to this number of values with the greatest sales. |
|
PERF_NUM_WEEKS_FOR_SLS_SHARE |
16 |
The number of weeks to be used while calculating the sales share for the product attributes. |
- |
|
PERF_NUM_WEEKS_FOR_TOPN_CALC |
16 |
The number of weeks to be used while identifying the top n attributes |
- |
|
SELECT_ALL_MERCH_NODES |
N |
Flag to identify if all (or only first) merchandise node(s) to be selected by default. |
- |
|
SUMM_CAL_ALL_LVL |
N |
Flag to identify whether performance summarization allowed at all available calendar levels. |
- |
|
SUMM_MERCH_ALL_LVL |
N |
Flag to identify whether performance summarization allowed at all available merchandise levels. |
- |
The following is a list of configurations that can be adjusted for the ASO application. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='SO'. Note that the WebLogic server must be rebooted whenever a configuration change is made for it to take effect. It is recommended that you make all configuration changes at the same time so that you only need to reboot once.
Table 15-4 ASO Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
SO_LOC_HIER_TYPE |
2 |
The hierarchy ID to use for location (installation configuration). |
To use an alternate location hierarchy for ASO, adjust this configuration accordingly. |
|
SO_PROD_HIER_TYPE |
1 |
The hierarchy ID to use for the product (Installation configuration). |
To use an alternate product hierarchy for ASO, adjust this configuration accordingly. |
|
ALRT_LESS_THAN_PCT_USED_SPACE |
0.8 |
An alert will be triggered if the run optimization results use less space than the value specified by this global parameter. |
- |
|
ALRT_LESS_THAN_SERVICE_LEVEL_AMT |
0.80 |
An alert will be triggered if the run optimization results have a sales service level lower than the value specified by this global parameter. |
- |
|
ALRT_LESS_THAN_SERVICE_LEVEL_QTY |
0.80 |
An alert will be triggered if the run optimization results have a quantity service level lower than the value specified by this global parameter. |
- |
|
ALRT_MORE_THAN_CNT_PRODUCT_DROPPED |
10 |
An alert will be triggered if the run optimization results dropped more products than the value specified by this global parameter. |
- |
|
ALRT_MORE_THAN_PCT_PRODUCT_DROPPED |
0.2 |
An alert will be triggered if the run optimization results dropped a percentage of product higher than the value specified by this global parameter. |
- |
|
ALRT_NO_FEASIBLE_SOLUTION |
0 |
An alert will be triggered if the run optimization results have no results. |
- |
|
ALWAYS_REVIEW_MAPPING_RES_FLG |
N |
Default value is N. A Y flag indicates that a user mapping review is always required (regardless of results or errors). A N flag triggers a review based on other flags and conditions. |
- |
|
CAPACITY_RANGE_UNITS |
25 |
Capacity range units used by SO Solver. This parameter value maps to a CRU row with this value ID within so_prod_constr_range_values table. |
- |
|
DEFAULT_BAY_MERGE_CONSTR_FLG |
N |
Default indicator for the use of merging bays constraint. |
- |
|
DEFAULT_BLOCKING_CONSTR_FLG |
Y |
Default indicator for the use of blocking constraint. |
- |
|
DEFAULT_SPACING_CONSTR_FLG |
Y |
Default indicator for use of spacing constraint. |
- |
|
DEFAULT_USABLE_SPACE_CONSTR_FLG |
N |
Default flag indicating if space constraint must be used. |
- |
|
DEFAULT_USABLE_SPACE_CONSTR_PCT |
1 |
Default usable space constraint percentage. |
- |
|
DEMAND_DISTRIBUTION |
Normal |
Demand distribution used by SO Solver. |
- |
|
DFLT_HORIZONTAL_BLOCKING_FLG |
N |
A Y value in this flag indicates the analytics that combining adjacent attribute blocks should be done (when possible). |
- |
|
DFLT_REPL_CASEPACK |
1 |
Default replenishment parameter for casepack. |
- |
|
DFLT_REPL_FACINGS_LIFT |
0 |
Default facing lift. |
- |
|
DFLT_REPL_SHELF_PARAM |
0 |
Default shelf replenishment parameter. |
- |
|
DFLT_REPL_SHELF_TT |
2 |
Default replenishment type. |
- |
|
DFLT_REPL_TYPE |
2 |
Default replenishment type. |
- |
|
DFLT_SHELF_THICKNESS |
1 |
This is the default shelf thickness that is used by the POG-shelf interface to create the initial-bottom shelf for empty shelf fixtures. |
- |
|
GV_DAYS_TO_VALIDATE_WO_CHANGES |
21 |
Number of days without direct changes the validation process considers data objects for validation. |
- |
|
GV_RESULT_DETAIL_LEVEL |
SUMMARY |
Level of detail for each validation that is used to produce the results (DETAIL:rows for every failure or SUMMARY: a row at the data object level). |
- |
|
GV_VALIDATION_SECTIONS_TO_RUN |
ASSORTMENT_POG_MAPPING_DS |
Global validations are executed for the selected data objects. ASSORTMENT, POG, MAPPING and DS (Display Style). |
- |
|
MAX_CAPACITY_RANGE |
80 |
Maximum capacity range used by SO Solver. |
- |
|
MAX_HEIGHT_RANGE |
72 |
Maximum height range used by SO Solver. |
- |
|
MAX_NUMBER_OF_FACINGS |
5 |
Maximum number of facings used by SO Solver. |
- |
|
MAX_NUM_OPT_LOC_BLOCK |
10 |
Maximum number of blocks per optimization location. |
- |
|
MAX_SHELF_THICKNESS |
2.5 |
This is the maximum shelf thickness that can be used for shelf fixture edits. |
- |
|
MAX_STACK_DFLT_LIMIT |
5 |
The default maximum stack limit that is used for display styles that have a missing value. |
- |
|
MIN_CAPACITY_RANGE |
0 |
Minimum capacity range used by SO Solver. |
- |
|
MIN_HEIGHT_RANGE |
0 |
Minimum height range used by SO Solver. |
- |
|
MIN_NUMBER_OF_FACINGS |
1 |
Minimum number of facings used by SO Solver. |
- |
|
MIN_SHELF_DEPTH |
2 |
This is the minimum shelf depth that can be used for shelf fixture edits. The maximum shelf depth is defined by the fixture depth. |
- |
|
MIN_SHELF_THICKNESS |
0.5 |
This is the minimum shelf thickness that can be used for shelf fixture edits. |
- |
|
MIN_SHELF_VERTICAL_GAP |
2.5 |
This is the specific smallest allowable vertical offset (SAVO) value. Ensure that any edit action leaves at least this much space between shelves. |
- |
|
MNG_ASSORT_NO_WKS |
52 |
Display assortments for past n weeks. |
- |
|
MNG_RUN_NO_WKS |
52 |
Display run for past n weeks. |
- |
|
NUMBER_OF_SIMULATED_DAYS |
1000 |
Number of simulated days used by SO Solver. |
- |
|
OPT_LOC_LVL1_NAME_STR |
All Locations |
This value is used entirely or as a prefix to generate the pogset location and optimization location top-level names. |
- |
|
OPT_LOC_LVL2_NAME_STR |
PC_ |
This value is used as a prefix to generate the pogset location and optimization location mid-level names. |
- |
|
OPT_LOC_LVL3_NAME_STR |
SC_ |
This value is used as a prefix to generate the pogset location and optimization location bottom-level names. |
- |
|
PC_SUM_CAPRANGE |
Set Capacity Range |
Capacity range label for product constraint summary. |
- |
|
PC_SUM_ELEVATION |
Elevation |
Elevation label for product constraint summary. |
- |
|
PC_SUM_ELEVRANGE |
Set Elevation Range |
Elevation range label for product constraint summary. |
- |
|
PC_SUM_FACERANGE |
Set Facing Range |
Facing range label for product constraint summary. |
- |
|
PC_SUM_FACINGS |
Facings |
Facings label for product constraint summary. |
- |
|
PC_SUM_INCLUSION |
Inclusion |
Inclusion label for Product constraint summary |
- |
|
PENALTY_PFG_MAX |
10 |
Maximum product family group penalty. |
- |
|
PENALTY_PFG_NORM |
0.15 |
Normalized value that affects how close products of the same family are placed together. |
- |
|
POGC_SUM_MERGEBAYS |
Merge Adjacent Bays |
Label to display in the UI for POG Constraint - Merge Adjacent Bays. |
- |
|
POGC_SUM_PRODSPACE |
Use Product Spacing |
Label to display in the UI for POG Constraint - Use Product Spacing. |
- |
|
POGC_SUM_SERVICELEVEL |
Set Minimum Service Level |
Label to display in the UI for POG Constraint - Minimum Service Level. |
- |
|
POGC_SUM_USABLESPACE |
Set Usable Space |
Label to display in the UI for POG Constraint - Set Usable Space. |
- |
|
POG_SET_LVL1_NAME_STR |
All Planograms |
This value is used to generate the name for the top level node on planogram list. |
- |
|
PRODUCT_INCLUSION |
2 |
Product Inclusion rule used by SO Solver. This parameter value maps to a IN row with this value ID within so_prod_constr_range_values table. |
- |
|
PRODUCT_STACKING_HEIGHT_LIMIT |
24 |
Product stacking height limit that applies as a global setting to all top products. |
- |
|
PROD_ATTR_NAME_DELIMITER |
- |
This value is used as a delimiter between the product name/descr and the attribute name/descr when setting up POG attributes. A NULL value here results in no concatenations. |
- |
|
REVIEW_DSF_ERROR_FLG |
Y |
A Y flag indicates a user review is required for DSF errors. N lets the process move forward to the next stage using the DSF available. |
- |
|
REVIEW_UNMAPPED_PROD_FLG |
Y |
A Y flag indicate a user review is required for unmapped products. N lets the process move forward to next stage eliminating unmapped products. This is not desired for products. |
- |
|
REVIEW_UNMAPPED_STORE_FLG |
Y |
A Y flag indicates a user review is required for unmapped stores. N lets the process move forward to the next stage eliminating unmapped stores. |
- |
|
SO_MIN_SERVICE_LEVEL |
0.8 |
Minimum target service level for SO optimization process. |
- |
|
SO_PROD_HIER_LEVEL_FOR_LEAF_NODE |
7 |
Product hierarchy level number for leaf node. |
- |
|
STD_ADJUSTMENT_COEFFICIENT_1 |
0.05 |
Analytical parameter. Demand standard deviation adjustment parameter 1. |
- |
|
STD_ADJUSTMENT_COEFFICIENT_2 |
0.19 |
Analytical parameter. Demand standard deviation adjustment parameter 2. |
- |
|
TOP_SHELF_STACKING_HEIGHT_LIMIT |
18 |
Top shelf stacking height limit that applies as a global setting to all top shelves. |
- |
|
UI_CONFIG_PC_RENDERED_COL_7 |
N |
UI configuration for product constraints render column 7. Default Y means column will be rendered. |
- |
|
UI_CONFIG_PC_RENDERED_COL_8 |
N |
UI configuration for product constraints render column 8. Default Y means column will be rendered. |
- |
|
UI_CONFIG_PC_RENDERED_COL_9 |
N |
UI configuration for product constraints render column 9. Default Y means column will be rendered. |
- |
|
UI_CONFIG_PC_VISIBLE_COL_1 |
N |
UI configuration for product constraints visible column 1. Default Y means column will be visible. |
- |
|
UI_CONFIG_PC_VISIBLE_COL_2 |
N |
UI configuration for product constraints visible column 2. Default Y means column will be visible. |
- |
|
UI_CONFIG_PC_VISIBLE_COL_3 |
N |
UI configuration for product constraints visible column 3. Default Y means column will be visible. |
- |
|
UI_CONFIG_PC_VISIBLE_COL_4 |
Y |
UI configuration for product constraints visible column 4. Default Y means column will be visible. |
- |
|
UI_MAX_POG_CONFIG_LENGTH |
600 |
UI configuration for maximum length bound for the Create Lengths pop-up. |
- |
|
UI_MAX_POG_CONFIG_NO_OF_BAYS |
10 |
UI configuration for maximum number of bays bound for the Create Lengths pop-up. |
- |
|
UI_MIN_POG_CONFIG_NO_OF_BAYS |
1 |
UI configuration for minimum number of bays bound for the Create Lengths pop-up. |
- |
|
UI_THRESHOLD_SL |
Y |
UI configuration for Thresholds Configurable for Service Level Formatting. |
- |
|
UI_THRESHOLD_SL_MAX |
0.85 |
UI configuration for Thresholds MAX after which color green would be shown. |
- |
|
UI_THRESHOLD_SL_MIN |
0.75 |
UI configuration for Thresholds MIN below which color red would be shown. |
- |
|
USE_OPT_DT |
N |
SO global indicator for applying DT. |
If the DT application is not in use, then this configuration should be set to an N to disable this feature. |
|
USE_SERVICE_LEVEL_CONSTRAINT |
Y |
SO global indicator for applying service level constraints. |
- |
The following is a list of configurations that can be adjusted the CDT application. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='CDT'. See Chapter 3 for more details.
Table 15-5 CDT Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
CDT_CAL_LEVEL_ID |
4 |
The hierarchy level ID that contains the level of the calendar hierarchy that CDT operates on (should equate to Week - Installation configuration). |
Normally, this configuration must be the same value as the common CAL_PERIOD_LEVEL configuration. |
|
CDT_CMGRP_LEVEL_ID |
5 |
The hierarchy level ID that contains the level of the product hierarchy that CDTs are created for (installation configuration). |
Normally, this must be the same setting as the common CMGRP_LEVEL_ID configuration. |
|
CDT_LOC_HIER_TYPE |
2 |
The hierarchy ID to use for location (installation configuration). |
This setting must be set to use either the trade area hierarchy type or the organization hierarchy type. |
|
CDT_LOC_LEVEL_ID |
4 |
The hierarchy level ID that contains the level of the location hierarchy that CDTs are created for (installation configuration). |
If CDT_LOC_HIER_TYPE is set to trade area, this must be set to a value of 2. Otherwise, it must be set to the level of the organization hierarchy for which CDT output is desired. |
|
CDT_PROD_HIER_TYPE |
1 |
The hierarchy ID to use for the CM Group (installation configuration). |
Normally, this setting must be the same value as the common CMGRP_HIER_TYPE configuration. It can either be the primary product hierarchy or an alternate product hierarchy. |
|
CDT_CALC_RAW_ATTR_SIM |
Y |
Determines whether or not to execute Raw Attribute Value Similarities routines. |
If the RI application is in use, then this setting must be set to a Y to enable calculation of data indented to be used by RI. |
|
CDT_UI_DEF_CALC_PARENT_SEGMENT_FLG |
Y |
UI default for the calculate only parent consumer segments flag. |
- |
|
CDT_UI_DEF_CALC_PARENT_TRADE_AREA_FLG |
N |
UI default for calculate only parent trade areas flag. |
- |
|
CDT_UI_DEF_CDT_SCORE_HIST_CNT |
20 |
UI default for the number of histogram buckets for the CDT scores histogram. |
- |
|
CDT_UI_DEF_DATA_FILTER_HIST_CNT |
20 |
UI default for the number of histogram buckets for the data filtering histograms. |
- |
|
CDT_UI_DEF_EXCLUDE_CUST_CNT |
1000 |
UI default for minimum require customer counts for pruning process. |
- |
|
CDT_UI_DEF_EXCLUDE_MIN_SCORE |
0.25 |
UI default for minimum CDT score required for the pruning process. |
- |
|
CDT_UI_DEF_EXCLUDE_SKU_CNT |
10 |
UI default for minimum number of SKUs for the pruning process. |
- |
|
CDT_UI_DEF_EXCLUDE_TREE_LEVEL_CNT |
2 |
UI default for minimum number of levels of the tree for the pruning process. |
- |
|
CDT_UI_DEF_LOWEST_EXPANSION_LEVEL |
15 |
UI default for lowest number of levels allowed for a tree. |
- |
|
CDT_UI_DEF_MAX_CUST_AVG_DY_TXN |
100 |
UI default for maximum number of times more than average a customer's daily transaction count can be. |
- |
|
CDT_UI_DEF_MAX_MISS_ATTR_CNT |
3 |
UI default for maximum number of missing attributes a SKU can have |
- |
|
CDT_UI_DEF_MIN_ATTR_SKU_CNT |
5 |
UI default for minimum number of SKUs assigned to an attribute, to be used by the process. |
- |
|
CDT_UI_DEF_MIN_ATTR_VALUE_SKU_CNT |
5 |
UI default for minimum number of SKUs assigned to an attribute value, to be used by the process. |
- |
|
CDT_UI_DEF_MIN_CUST_TXN_CNT |
0.01 |
UI default for minimum number of transactions required for a customer, as a percent of the average number. |
- |
|
CDT_UI_DEF_MIN_NODE_ITEM_CNT_PCT |
0.05 |
UI default for the minimum percent of SKUs required for a node of the tree before it is considered a terminal node. |
- |
|
CDT_UI_DEF_MIN_SKU_TXN_CNT |
0.01 |
UI default for minimum number of transactions required for a SKU, as a percent of the average number. |
- |
|
CDT_UI_DEF_PRUNING_HIST_CNT |
20 |
UI default for the number of histogram buckets for the pruning histograms. |
- |
|
CDT_XML_PRECISION |
4 |
Default precision of weight field in CDT XML. |
Adjust this to control the amount of precision in the generated CDT XML files. |
|
HISTOGRAM_DEFAULT_BIN_APPROACH |
C |
The default histogram bin approach (C = Custom, W = Width) |
- |
|
HISTOGRAM_DEFAULT_NUM_BINS |
7 |
The default number of bins to display for CDT histograms |
- |
|
MAX_NUM_WEEKS_FOR_SIMILARITY |
104 |
The maximum number of weeks of sales transaction data to be used by the similarity process. This prevents the process from using too much data. |
Adjust this to reduce the use of too much input data for the process. Enabling a high number of weeks will result in slower performance; however, it may be necessary if suitable data is not available in a smaller number of weeks. |
The following is a list of configurations that can be adjusted for the DT application. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='DT'.
Table 15-6 DT Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
AE_CALC_INT_LENGTH |
8 |
The number of weeks to group together for in an interval for the AE calculation. |
This setting must be adjusted according to the data quality and quantity available for a customer. Higher values improve performance; however, it limits the amount of data available to be processed. |
|
ATTRIBUTE_LIST_SEPARATOR |
- |
A separator to be used to display a list of attributes in Similarity Calculation screen. |
- |
|
CDT_SIMILARITY_AVAILABLE |
Y |
Whether CDT similarity has been made available to DT. |
If the CDT application is being used, this setting enables DT to use the similarities that CDT may have calculated. |
|
DT_CAL_LEVEL_ID |
4 |
The hierarchy level ID that contains the level of the calendar hierarchy that DT operates on (should equate to Week). |
Normally, this configuration must be the same value as the common CAL_PERIOD_LEVEL configuration. |
|
DT_CMGRP_LEVEL_ID |
5 |
The hierarchy level ID that contains the level of the product hierarchy that DTs are created for. |
Normally, this must be the same setting as the common CMGRP_LEVEL_ID configuration. |
|
DT_LOC_HIER_TYPE |
2 |
The hierarchy ID to use for location. |
This must be adjusted to trade area hierarchy or be left at the default organization hierarchy. |
|
DT_LOC_LEVEL_ID |
4 |
The hierarchy level ID that contains the level of the location hierarchy that DTs are created for. |
If DT_LOC_HIER_TYPE is set to trade area, this must be set to a value of 2. Otherwise, it must be set to the level of the organization hierarchy for which DT output is desired. |
|
DT_MDL_AP_EXP_WKS_BACK_END |
1 |
The number of weeks back from the last date that range data has been loaded for (PR_LOC_STATUS_LAST_COMPLETED_WK) to end using for model apply export. |
Adjust this and MDL_AP_EXP_WKS_BACK_START to control which weeks should be used during data export. |
|
DT_PROD_HIER_TYPE |
1 |
The hierarchy ID to use for the CM Group. |
Normally, this setting must be the same value as the common CMGRP_HIER_TYPE configuration. It can either be the primary product hierarchy or an alternate product hierarchy. |
|
DT_REMOVE_REDUNDANCY |
N |
If set to Y, then remove redundancy while calculating attribute-based similarities. |
- |
|
DT_SIM_DISPLAY_ROWNUM |
9999999 |
The number of distinct similarity values to show in the UI pop-up. Setting to a high number effectively eliminates this limit. |
- |
|
GENERIC_SEPARATOR |
A separator to be used to display a list of items, for example. SKU prod_ext_code name. |
This value is used in the UI to separate lists of items. For example, when a list of attributes is shown in the UI, they will be delimited by this value. |
|
|
HISTOGRAM_DEFAULT_BIN_APPROACH |
W |
The default histogram bin approach (C = Custom, W = Width). |
- |
|
HISTOGRAM_DEFAULT_NUM_BINS |
7 |
The default number of buckets in the contextual BIs. |
- |
|
MAX_NUM_WEEKS_FOR_ATTR_WGT |
104 |
The maximum number of weeks of input data to use for calculating attribute weights. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MAX_NUM_WEEKS_FOR_AVG_SLS |
104 |
The maximum number of weeks of input data to use for calculating the average sales. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MAX_NUM_WEEKS_FOR_FILTERING |
104 |
The maximum number of weeks of input data to use for data filtering. Setting this value lower than the other MAX_NUM_WEEKS_FOR* configurations overrides those other configurations. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MAX_NUM_WEEKS_FOR_MDL_CALC |
104 |
The maximum number of weeks that should be used during model build calculation. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MAX_NUM_WEEKS_FOR_MDL_UPDT |
104 |
The maximum number of weeks that should be used during model build update calculation. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MAX_NUM_WEEKS_FOR_SIMILARITY |
104 |
The maximum number of weeks of input data to use for calculating similarity. |
Setting this value to a higher value allows the use of more weeks of data, which will slow performance; however, enables better results for categories with infrequent sales. |
|
MDL_AP_EXP_WKS_BACK_START |
4 |
The number of weeks back from the last date that range data has been loaded for (PR_LOC_STATUS_LAST_COMPLETED_WK) to start using for model apply export. |
Adjust this and DT_MDL_AP_EXP_WKS_BACK_END to control which weeks should be used during data export. |
|
PRUNED_CATEGORIES_SEPARATOR |
, |
A separator to be used to display a list of pruned attributes in the Calculation screen. |
- |
|
UI_DEF_CALC_PARENT_CS_ONLY_FLG |
N |
The UI default for calculate only parent customer segments flag. |
- |
|
UI_DEF_CALC_PARENT_TA_ONLY_FLG |
N |
The UI default for calculate only parent trade areas flag. |
- |
|
UI_DEF_MAX_MISS_ATTR_CNT |
3 |
The maximum number of missing attributes for a SKU, before requiring it to be filtered from use. |
- |
|
UI_DEF_MIN_SKU_CNT |
10 |
The UI default for minimum number of SKUs required for a segment/store. |
- |
|
UI_DEF_MIN_SKU_TXN_LEN_PCT |
0.01 |
The UI default for minimum SKU transaction length as a percentage of the CM Group average. |
- |
|
UI_DEF_MIN_TOT_SLS_UNIT_PCT |
0.01 |
The UI default for minimum total sales units as a percentage of the CM group average. |
- |
|
WGT_CALC_INTERVAL_LENGTH |
4 |
The number of weeks to group into an interval that is then used to perform weight calculations with. |
This setting can be adjusted according to the data quality and quantity available for a customer. Higher values improve performance; however, it limits the amount of data available to be processed. |
The following is a list of configurations that can be adjusted for the Returns Logistics process. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='RL'.
Table 15-7 Returns Logistics Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
RL_NUM_TOP_CATEGORIES |
10 |
The number of top selling categories for Returns Logistics to process. |
- |
|
RL_NO_OF_SIMULATION_RUNS |
100 |
The number of simulated forecast runs to perform. |
- |
|
RL_IN_SEASON_DEMAND_WEIGHT |
0.99 |
The percentage of the in-season demand and returns rate to use. This is used to calculate the adjusted demand and returns rate. |
- |
|
RL_HISTORICAL_DEMAND_WEIGHT |
.01 |
The percentage of the historical demand and returns rate to use. This is used to calculate the adjusted demand and returns rate. |
- |
|
RL_GUR_TIMELIMIT |
60 |
GUROBI parameter. Time limit. |
- |
|
RL_GUR_THREADS |
0 |
GUROBI parameter. Number of allowed threads. |
- |
|
RL_PROCESSING_THREADS |
0 |
The number of threads to create for data processing. A value of 0 creates one thread for each machine processor. |
- |
The following is a list of configurations that can be adjusted for the AA application. This list does not include internal configuration values. All of these entries are adjusted by manipulating the corresponding rows in RSE_CONFIG where APPL_CODE='MBA'. Some of the configurations note that overrides are possible. When this is required, see the RSE_CONFIG_CODE configuration table and use the appropriate Hierarchy Level value as the PARAM_CODE to override the value for only that hierarchy level.
Table 15-8 AA Configurations
| Parameter Name | Example Value | Description | Notes |
|---|---|---|---|
|
ARM_CS_HIER_LEVEL |
SBC |
The highest level of the hierarchy to run the process for. Valid values are: CLS, SBC. |
- |
|
ARM_CS_MAX_LIFT |
100 |
The maximum lift required for an association rule. |
- |
|
ARM_CS_MAX_RULE_COUNT |
9999 |
The maximum number of rules desired for association rules. |
Affects the count of rules per set size. |
|
ARM_CS_MAX_SET_SIZE |
2 |
The maximum number of hierarchy members to include in an association rule. |
Maximum allowed is 4, although a setting this high can negatively affect performance with some datasets. |
|
ARM_CS_MIN_CONFIDENCE |
.05 |
The minimum confidence required for an association rule. |
- |
|
ARM_CS_MIN_LIFT |
.05 |
The minimum lift required for an association rule. |
- |
|
ARM_CS_MIN_REV_CONFIDENCE |
.05 |
The minimum reverse confidence required for an association rule. |
- |
|
ARM_CS_MIN_SUPPORT |
.001 |
The minimum percentage of transactions require for an association rule. |
- |
|
ARM_CS_MIN_SUPPORT_TXN_CNT |
1000 |
The minimum number of sales transactions required for creating association rules. |
- |
|
ARM_CS_WEEK_CNT |
1 |
The number of weeks that should be processed while calculating the association rules. |
Only set this to more than 1 if there is a need to reprocess weeks that would have been processed in the prior batch window. |
|
ARM_PH_MAX_LIFT |
100 |
The maximum lift required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PH_MAX_RULE_COUNT |
9999 |
The maximum number of rules desired for association rules. |
Affects the count of rules per set size. |
|
ARM_PH_MAX_SET_SIZE |
2 |
The maximum number of hierarchy members to include in an association rule. Override with PARAM_CODE of the hierarchy level name. |
Maximum allowed is 4, although a setting this high can negatively affect performance with some datasets. |
|
ARM_PH_MIN_CONFIDENCE |
.05 |
The minimum confidence required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PH_MIN_LIFT |
.05 |
The minimum lift required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PH_MIN_REV_CONFIDENCE |
.05 |
The minimum reverse confidence required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PH_MIN_SUPPORT |
.001 |
The minimum percentage of transactions require for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PH_MIN_SUPPORT_TXN_CNT |
1000 |
The minimum number of sales transactions required for creating association rules. |
- |
|
ARM_PH_TOP_LEVEL |
CLS |
The highest level of the hierarchy to run the process for. Valid values are: DEPT, CLS, SBC. |
- |
|
ARM_PH_WEEK_CNT |
1 |
The number of weeks that should be processed while calculating the association rules. |
Only set this to more than 1 if there is a need to reprocess weeks that would have been processed in the prior batch window. |
|
ARM_PROMO_HIER_LEVEL |
SBC |
The highest level of the hierarchy to run the process for. Valid values are: CLS, SBC. |
- |
|
ARM_PROMO_MAX_LIFT |
100 |
The maximum lift required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PROMO_MAX_RULE_COUNT |
9999 |
The maximum number of rules desired for association rules. |
Affects the count of rules per set size. |
|
ARM_PROMO_MAX_SET_SIZE |
2 |
The maximum number of hierarchy members to include in an association rule. Override with PARAM_CODE of the hierarchy level name. |
Maximum allowed is 4, although a setting this high can negatively affect performance with some datasets. |
|
ARM_PROMO_MIN_CONFIDENCE |
.05 |
The minimum confidence required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PROMO_MIN_LIFT |
.05 |
The minimum lift required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PROMO_MIN_REV_CONFIDENCE |
.05 |
The minimum reverse confidence required for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PROMO_MIN_SUPPORT |
.001 |
The minimum percentage of transactions require for an association rule. Override with PARAM_CODE of the hierarchy level name. |
- |
|
ARM_PROMO_MIN_SUPPORT_TXN_CNT |
1000 |
The minimum number of sales transactions required for creating association rules. |
- |
|
ARM_PROMO_WEEK_CNT |
1 |
The number of weeks that should be processed while calculating the association rules. |
Only set this to more than 1 if there is a need to reprocess weeks that would have been processed in the prior batch window. |
Oracle Retail AI Foundation Cloud Services comes packaged with resource bundles, files that contain text resources. These text resources appear throughout the application as instructions, messages, labels, errors. Retailers can customize the text resources to suit their requirement. The capability to change the text for a resource is provided through the Resource Bundles Section of Retail Home. For more information, see Oracle Retail Home Administration Guide.
Different types of notifications are sent to specific groups of users for the tasks and jobs accomplished. Retail Home provides administrators with the ability to set up groups of user roles that must receive each type of notification. For more information, see Oracle Retail Home Administration Guide.
The user interface supports multiple languages in a single instance, but the underlying database only supports a single language in an instance.
The database default language is selected at installation. Once set, there is no support for switching the database language. The application user interfaces adhere to the language setting for each user's browser. For example, to change the language for the Firefox browser:
Select Tools from the menu bar.
Select Options.
Select Choose.
Select the language to add.
The following language are supported: English, German, Greek, Spanish, French, Croatian, Hungarian, Italian, Japanese, Korean, Dutch, Polish, Brazilian Portuguese, Russian, Swedish, Turkish, Simplified Chinese, and Traditional Chinese.
Use the Manage Configuration user interface screen in order to edit the values in the configuration tables. In order to access this screen, you must be assigned the role of ADMINISTRATOR_JOB. The tables you can edit within Manage Configuration depends upon which application roles you have been assigned, as described in Table 15-1.
Once you have accessed Manage Configuration, you select, from the configuration tables available to you, the table that you want to review and edit. Note that each configuration table allows specific actions. You may or may not be able to view the table, edit some or all of the columns, or add and delete rows.
Certain of the tables in Manage Configuration are not intended for configuration but instead are provided to display data that may be useful during implementation. For each application interface file, a table is available that contains any records that have failed the data validation rules. Such tables have an extension of BAD. For example, for the rse_prod_attr_grp_value_stg.txt interface, the data is loaded into a table named RSE_PROD_ATTR_GRP_VALUE_STG. The error table is named RSE_PROD_ATTR_GRP_VALUE_BAD.
You can see all the error tables for all the interfaces via Manage Configuration. When an error occurs with an interface, yo can review the BAD table to see what records failed validation and why. Each BAD table includes the following columns: ERROR_ROWID, ERROR_ID, ERROR_DESCR, and ERROR_DT. The ERROR_ID is useful as a reference. The ERROR_DESCR provides a message to explain the validation error.
The following tables can be viewed in the Manage Configuration screen.
Table 15-9 Customer Decision Tree Configuration Tables
| Table Name | Description |
|---|---|
|
CDT_EXCLUDE |
Defines the various types of pruning filters that can be used to prevent a CDT from being used during the escalation phase of the CDT workflow. |
|
CDT_FILTER |
Defines the various types of data filters that can be used to filter sales transaction data used for the CDT calculation. |
|
CDT_VERSION |
Defines a version to collectively group together a batch of CDTs that have been created for a particular purpose. |
Table 15-10 Advanced Clustering and Customer Segmentation Configuration Tables
| Table Name | Description |
|---|---|
|
CIS_ALGORITHM_ATTR |
Defines the possible attributes for any algorithm. |
|
CIS_BUSINESS_OBJECT |
Hosts the list of applications that are registered and configured to use the clustering feature. |
|
CIS_BUSSOBJ_OBJ_ALG_XREF |
This cross reference is provided so that you can use the same algorithm to generate different cluster objectives. The same algorithm can be used to generate customer clusters as well as store clusters. At the same time it is possible to list multiple algorithms that can be used to achieve a similar objective. |
|
CIS_BUSSOBJ_TCRIT_HIER_XREF |
Specifies the possible hierarchy levels for each hierarchy type (merchandise and location) that are permitted for the combination of objective ID, business objective ID, and type criteria ID. |
|
CIS_BUS_OBJ_HIER_DEPLOY_XREF |
Identifies the business object, objectives, product hierarch types, and levels that can be selected for deployment. This ensures that only authorized types of clusters are exported to external systems (CMPO). |
|
CIS_BUS_OBJ_NESTED_TCRITERIA |
Determines the possible child cluster types for a parent cluster. |
|
CIS_BUS_OBJ_TCRITERIA_XREF |
Specifies the possible cluster types that are permitted for the combination of objective ID and business objective ID. |
|
CIS_BUS_OBJ_TCRIT_ALGO_ATTR |
Defines possible attributes for any algorithm, business objective, objective, and criteria. |
|
CIS_CLUSTER_OUTLIER_RULE |
Specifies the possible outlier rules for a type of criteria. |
|
CIS_EFFECTIVE_PERIOD |
Specifies the planning period information. |
|
CIS_ODM_SETTINGS |
Temporary storage for the data mining settings provided to ODM. You can store multiple runs of settings by using different mining functions and run IDs. To provide this data to ODM, you must write a view that provides the appropriate rows of data. |
|
CIS_SALES_TYPE |
Specifies the type of sales information - historical, forecasted, or planned. |
|
CIS_SRC_ENTITY |
Defines the different database views available for use in the various clustering implementations. These settings help control how the attributes are used throughout the system. |
|
CIS_TCRITERIA_SRC_XREF |
Cross reference to SRC_ENTITY_NAME and for the settings for Partitioning, Information for the SRC_ENTITY_NAME attributes. |
|
CIS_TCRIT_SRC_TYPE_XREF |
Describes the xref of type_criteria and sales. |
|
CIS_TYPE_CRITERIA |
List of different clustering types and criteria that can be used to generate clusters. |
Table 15-11 Demand Transference Configuration Tables
| Table Name | Description |
|---|---|
|
DT_EXCLUDE |
Defines the different types of pruning filters available to prevent a DT result from being used during the escalation phase of the DT workflow. |
|
DT_FILTER |
Defines the different types of data filters used during the DT data filtering process. |
Table 15-12 Generic Configuration Tables
| Table Name | Description |
|---|---|
|
RSE_AGGR_SRVC_CONFIG_LEVELS |
Defines the different hierarchy types and levels that must have aggregated data created as part of the hierarchy configuration. |
|
RSE_BUSINESS_OBJECT_ATTR_MD |
Defines the attributes for business objects and also provides relevant details about where from external table sources to obtain the data for this attribute. |
|
RSE_BUSINESS_OBJECT_DB_SRC |
Defines the source database objects for the attributes. |
|
RSE_CONFIG |
Provides configuration names and their values for the settings that can be changed and affect the operation of the software. |
|
RSE_CONFIG_CODE |
Provides configuration values for those configurations that can have different values, depending on how other values are configured. For example, if a configuration is required for a default error tolerance, but department 1 requires a different value, then a row here with a PARAM_CODE of 1 will enable a different value than the base configuration in RSE_CONFIG for just that department. |
|
RSE_EMAIL_CFG_DISTR |
Intersection table between the email configuration table and the email distribution list table used to resolve the many-to-many relationships. |
|
RSE_EMAIL_DISTR_LIST |
Provides the email distribution lists. |
|
RSE_EMAIL_NOTIF_CFG |
Defines the email messaging configuration. |
|
RSE_EXP_GRP |
Hosts the list of applications that are registered and configured to use the clustering application. |
|
RSE_HIER_LEVEL |
Defines the various levels for all the hierarchies. |
|
RSE_HIER_TYPE |
Defines the hierarchies that are available for use by the RSE applications. |
|
RSE_LOAD_SRVC_CFG |
Defines a data loader that can be executed through the data loading framework. |
|
RSE_LOAD_VALDT_RULES_CFG |
Defines the validation rules that a data loader performs, along with some configurable options that impact rows that fail the validation. |
|
RSE_PROC_TASK_TMPL |
Defines the templates for processing tasks used by the applications. |
|
RSE_PROC_TMPL |
Defines the processing templates for asynchronous or synchronous invocable from Java applications |
|
RSE_SRVC_CONFIG |
Defines all the database service routines that can be invoked through the database service framework in RSE. |
Table 15-13 Assortment and Space Optimization Configuration Tables
| Table Name | Description |
|---|---|
|
SO_BI_ELEMENT |
Contains configuration metadata for BI elements. |
|
SO_BI_ELEMENT_CHART |
Contains the metadata to configure BI element charts. |
|
SO_INT_TRANSFORMATION_KEY |
Used to help perform interface data transformation. The values in this table are used to align data from external sources with the data expected by ASO. It helps to isolate translation conversion issues. |
|
SO_POG_FIXTCONF_ALG_PARAM |
Stores the list of different algorithm parameters that a user can customize while running the fixture smart start process. |
|
SO_POG_FIXT_CONFIG_ALGORITHM |
Stores the list of available algorithms to perform the shelf fixture smart start process to create shelves for empty fixtures. |
|
SO_PROD_CONSTR_RANGE_VALUES |
Contains the list of product constraint values supported by the application. |
|
SO_REPL_PARAM_DESCRIPTION |
Stores the list of replenishment parameters that a user can change. These parameters have a defined list of valid values that are stored in this table so that they can be used by the UI for display. |
|
SO_RUN_OBJECTIVE_FUNC |
Contains the list of possible run objective functions that are supported by the application. |
|
SO_STACK_CAP_STYLE |
- |
The RSE_EMAIL_CFG_DISTR, RSE_EMAIL_DISTR_LIST, and RSE_EMAIL_NOTIF_CFG tables listed in the tables in Configuration Tables can be used to enable email notifications for certain batch processes. The RSE_EMAIL_NOTIF_CFG table contains a list of processes that can generate an email notification. Configurations are available for loading interface files (PROCESS_TYPE=LOAD), as well as configurations for running the automated batch processes (PROCESS_TYPE=BATCH).
The RSE_EMAIL_DISTR_LIST table is used to define email distribution lists that should receive email notifications. If all email notifications are to be sent to the same email address, then a row with a DEFAULT_FLG=Y can be used so that the distribution list is used for all email notices.
If some processes require different email recipients, then additional distribution lists can be created for those in RSE_EMAIL_DISTR_LIST. Once created there, a record can be created in RSE_EMAIL_CFG_DISTR that links the distribution list with the email notification. Any email configuration without a specific entry in RSE_EMAIL_CFG_DISTR is sent to the default distribution list.
By default, all LOAD failures trigger an email notification with details about the load that failed. Additionally, all batch processes send an email notification when the entire batch process completes. This email indicates whether the batch process was successful or if a failure occurred.
