B Database Detail Definitions

Table Definitions

CDT_APPROVED_EXP_VW

This view provides a list of approved CDTs to the CDT XML export process.

Table B-1 CDT_APPROVED_EXP_VW

Column Name	Data Type	Comments	Nullable?
CM_GRP_ID	NUMBER(10)	The FK for the Category Management group.	N
CS_LEAF_ID	VARCHAR2(4000)	The FK for the leaf node of the customer segment hierarchy, which is assigned to this CDT during the export.	Y
TA_LEAF_ID	VARCHAR2(4000)	The FK for the location/trade area hierarchy, which is assigned to this CDT during the export.	Y
ESC_RANK	NUMBER(10)	The numerical rank to use when escalation of results is required. The lower the number, the more important the rank.	N
CS_LEVEL_ID	NUMBER(4)	The hierarchy level number for the customer segment hierarchy.	N
CS_ID	NUMBER(10)	The FK for the customer segment hierarchy, which this CDT was created for.	N
TA_LEVEL_ID	NUMBER(4)	The hierarchy level number for the trade area/location hierarchy.	N
TA_ID	NUMBER(10)	The FK for the trade area/location hierarchy, which this CDT was created for.	N
CDT_ID	NUMBER(10)	The FK for the CDT to be exported.	N
CDT_VERSION_ID	NUMBER(10)	The FK for the version that this CDT was created under.	Y
CDT_VERSION_NAME	VARCHAR2(80)	The name of the version as entered in the CDT UI when this version was created.	Y
CREATED_BY_USER	VARCHAR2(255)	The name of the user who created the version and CDTs.	N
CREATED_ON_DT	DATE	The date when this CDT was created.	Y
CHANGED_ON_DT	DATE	The date when this CDT was last modified.	Y
ACTIVE_FLG	VARCHAR2(1)	A flag to indicate whether this CDT is considered active (Y) or not (N) for downstream applications like DT.	Y
APPROVED_FLG	VARCHAR2(1)	A flag to indicate whether this CDT is considered approved (Y) or not (N). Only approved CDTs should be exported by this view.	Y

CDT_ATTR_VAL_PROD_XREF_EXP_VW

This view provides the data for the Category Management application for export of products and their product attribute values.

Table B-2 CDT_ATTR_VAL_PROD_XREF_EXP_VW

Column Name	Data Type	Comments	Nullable?
MERCHANDISE_ID	VARCHAR2(80)	The external identifier for a product/SKU.	Y
ATTRIBUTE_EXTERNAL_ID	VARCHAR2(80)	The external identifier for the category-specific attribute.	N
ATTRIBUTE_VALUE_ID	VARCHAR2(80)	The external identifier for the product attribute value.	Y

CDT_ATTRIBUTE_EXP_VW

This view provides the complete set of category-specific attributes and their attribute values for an export to the Category Management application.

Table B-3 CDT_ATTRIBUTE_EXP_VW

Column Name	Data Type	Comments	Nullable?
ATTRIBUTE_VALUE_ID	VARCHAR2(80)	The external identifier for the attribute value.	Y
ATTRIBUTE_VALUE_NAME	VARCHAR2(255)	A descriptive name for the attribute value.	Y
ATTRIBUTE_EXTERNAL_ID	VARCHAR2(80)	The external identifier for the category-specific attribute.	N
ATTRIBUTE_NAME	VARCHAR2(255)	A descriptive name for the category-specific attribute.	Y

CDT_BATCH_INTERVAL_TYPE

This is the lookup table for batch interval types.

Table B-4 CDT_BATCH_INTERVAL_TYPE

Column Name	Data Type	Comments	Nullable?
INTERVAL_TYPE	VARCHAR2(1)	D=Default, S=Seasonal, P=Product-specific.	N
DESCR	VARCHAR2(40)	Description for the interval type.	Y

Notes:

This table contains the descriptions for the various interval types used within a CDT batch. This object performs no other function other than providing documentation of the different values used in the CDT_BATCH_INTERVAL table.

CDT_EXCLUDE

This table defines the different types of pruning filters that are available to exclude a CDT from being used during the escalation phase of the CDT workflow.

Table B-5 CDT_EXCLUDE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	The name of the pruning filter.	N
DESCR	VARCHAR2(255)	Descriptive text for the pruning filter.	Y
PROC_NAME	VARCHAR2(30)	Name of the process that performs this data filtering.	N
DISPLAY_SEQ	NUMBER(10)	The order in which the filters should be displayed when viewing filter statistics in the UI.	N
PROCESS_SEQ	NUMBER(10)	The order in which the filters should be executed during the filter stage.	N
ENABLE_FLG	VARCHAR2(1)	A Y/N indicator that indicates whether the filter is enabled for use.	Y

Notes:

This table can be used to customize the pruning filters that run after CDTs have been created. This allows for the flexibility in customized rules for pruning CDTs from the list of usable CDTs.

The NAME and DESCR columns are displayed in the UI if the NAME value is not found in the UI's resource bundle.

The PROC_NAME is the name of the procedure that should be executed to perform this pruning task. This routine should be implemented in either the CDT_PRUNE_T type or in a database type that extends this type and then is configured as the type to execute for the CDT_PRUNE database service.

When the pruning stage runs, this table will be referenced and each enabled filter will be executed in ascending order, based on the PROCESS_SEQ column. Therefore, this column should be unique in order to ensure consistency in the order in which the filters are executed.

The DISPLAY_SEQ column allows for displaying the filters in the UI in a different order than the order in which they may be executed. Although setting these two columns with different values might be confusing to the user, it can be done if needed.

The ENABLE_FLG can be used to exclude a filter from processing. This can be helpful if a filter is no longer deemed relevant to run. Setting this column to N will prevent further execution of the filter, although any existing filter statistics about prior executions of the filter will remain.

CDT_FILTER

This table defines the different types of data filters that are available to filter the sales transaction data used for the CDT calculation.

Table B-6 CDT_FILTER

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	The name of the data filter.	N
DESCR	VARCHAR2(255)	Descriptive text for this filter.	Y
SRVC_TYPE	VARCHAR2(30)	Service type for the implementation of the data filter.	N
SRVC_NAME	VARCHAR2(30)	Service name for the implementation for this data filter.	N
DISPLAY_SEQ	NUMBER(10)	The order in which the filters should be displayed when viewing filter statistics in the UI.	N
PROCESS_SEQ	NUMBER(10)	The order in which the filters should be executed during the filter stage.	N
ENABLE_FLG	VARCHAR2(1)	A Y/N indicator that indicates whether the filter is enabled for use.	Y

Notes:

This table contains the list of CDT Filters that can be executed against sales transaction data in order to remove outliers or any data that could lead to bad results. Although the UI has a fixed number of prompts in the data filtering stage, you can use this table offers to add or remove any filter in the data filtering workflow.

When the data filtering stage runs, this table will be referenced and each enabled filter will be executed in ascending order, based on the PROCESS_SEQ column. Therefore, this column should be unique in order to ensure consistency in the order in which the filters are executed.

The DISPLAY_SEQ column can be used for displaying the filters in the UI in a different order than the order in which they may be executed. Although setting these two columns with different values might be confusing to the user, it can be done if needed.

The ENABLE_FLG can be used to exclude a filter from processing. This can be helpful if a filter is no longer deemed relevant to run. Setting this column to N will prevent further execution of the filter, although any existing filter statistics about prior executions of the filter will remain.

The SRVC_TYPE and SRVC_NAME columns can be used for the specification of the actual implementation that performs the data filtering task. These implementations should be extensions of the CDT_FILTER_SLS_TXN_T database type. The SRVC_TYPE should be defined in the RSE_SRVC_TYPE table, and the SRVC_NAME should be defined in the RSE_SRVC_CONFIG table. Because of this configuration, this table offers the ability to run additional SKU or Customer filters.

CDT_SIM_EXP_VW

This view provides the export of product similarities calculated within the CDT application to Category Management.

Table B-7 CDT_SIM_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY1	VARCHAR2(80)	The external identifier for one half of the product pair.	Y
CUSTSEG_EXT_KEY	VARCHAR2(80)	The external identifier for the customer segment this data relates to.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external identifier for the store location this data relates to.	Y
PROD_EXT_KEY2	VARCHAR2(80)	The external identifier for the other half of the product pair.	Y
PROD_SIM	NUMBER(22,7)	The measurement of how similar the two products are to each other. The values range between values of 0 (completely dissimilar) to values of 1 (completely similar).	Y
EFFECTIVE_DT_FROM	DATE	The date this similarity value became effective.	Y
EFFECTIVE_DT_TO	DATE	The date this similarity value is effective until.	Y

CDT_VERSION

This table defines a version to collectively group a batch of CDTs that were created for a particular purpose.

Table B-8 CDT_VERSION

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	The name of the version as entered and displayed in the UI.	Y
DESCR	VARCHAR2(255)	Descriptive text for the version.	Y
CREATED_ON_DT	DATE	The date when this version was created.	Y
CREATED_BY_USER	VARCHAR2(255)	The user who created this version.	N
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether this version is considered deleted (Y) or not (N).	Y
EXTERNAL_FLG	VARCHAR2(1)	This flag identifies versions that were externally provided (Y).	Y
APPROVED_FLG	VARCHAR2(1)	This flag identifies the one version that contains all the approved CDTs (Y).	Y
CHANGED_BY_USER	VARCHAR2(255)	The user who last changed this version.	Y
CHANGED_ON_DT	DATE	The date when the version was last changed.	Y
MAX_SRC_WK_ID	NUMBER(10)	The maximum week ID of the source data for this version.	Y
MIN_SRC_WK_ID	NUMBER(10)	The minimum week ID of the source data for this version.	Y
NUM_WEEKS	NUMBER(10)	Number of weeks of data used to create this version.	Y
PROC_REQ_QUEUE_ID	NUMBER(10)	FK for the Process Request Queue last used to perform version-specific background tasks.	Y

Notes:

This table is the parent object for a collection of calculated or imported CDTs.There are two fixed versions in this table that represent the CDTs that are Approved CDTs (APPROVED_FLG=Y) and that represent the CDTs that were externally loaded into the application (EXTERNAL_FLG=Y). Only one version can have an APPROVED_FLG=Y, and only one version can have an EXTERNAL_FLG=Y, and they cannot be the same version. These two versions are created as part of a seed data file.

For all other versions, the application maintains that a given version name (NAME) can only be used once per user (CREATED_BY_USER).

The PROC_REQ_QUEUE_ID will only be populated if there is a Job Processor task running that is owned by this version.

CIS_ALGORITHM

This table holds the possible algorithms used in Clustering.

Table B-9 CIS_ALGORITHM

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	This is the name of the algorithm that is registered for use (for example, BaNG).	N
DESCR	VARCHAR2(200)	Descriptive text for the algorithm.	Y
ALG_CODE	VARCHAR2(200)	This identifies the program/procedure or required call that is needed to call the algorithm. More technical information is required to identify and execute every call.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y) or if it is a historical row (N).	Y
CREATED_BY_USER	VARCHAR2(255)	The name of the user who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	The date when this record was created.	N
CREATED_BY_USER	VARCHAR2(255)	The name of the user who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	The date when this record was last changed.	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y

Notes:

This table holds the possible algorithms used in Clustering.

CIS_ALGORITHM_ATTR

This table defines the possible attributes for any algorithm.

Table B-10 CIS_ALGORITHM_ATTR

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(100	PK for this table.	N
NAME	VARCHAR2(50)	This is the name of the clustering algorithm attribute. There are some specific attributes per algorithm. (For example, BaNG uses attributes such as distance metric, converge factor, and number of iterations.)	N
KEYWORD_NAME	VARCHAR2(50)	This field contains the attribute/property name recognized internally by the application code. This value is used within the code to identify the property and must be provided with the correct case and format recognized within the code.	Y
DESCR	VARCHAR2(200)	Descriptive text for the algorithm.	Y
ALGORITHM_ATTR_TYPE_ID	NUMBER(10)	Algorithm attribute type ID.	N
DFLT_VALUE	VARCHAR2(80)	Default value to be used for the attribute.	Y
ATTR_SEQ	NUMBER(5)	Sequence in which the attribute should be processed/presented.	Y
CIS_ALGORITHM_ID	NUMBER(10)	This is the algorithm ID. This field is populated only for algorithm-specific properties/attributes; otherwise, this field is null.	Y
USER_PROVIDED_FLG	VARCHAR2(1)	A value of Y indicates that the user must set this value using the UI while creating the scenario configuration.	Y
CURRENT_FLG	VARCHAR2(1)	Indicates whether this row is the most recent row (Y), or if it is a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	Indicates whether the row is considered deleted (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	The user who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	The date when the record was created.	N
CHANGED_BY_USER	VARCHAR2(255)	The user who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	The date when the record was last changed.	Y

Notes:

This table defines the possible attributes for any algorithm.

CIS_ALGORITHM_ATTR_TYPE

Different types of algorithm properties/attributes are possible; some of them apply to multiple algorithms while other are algorithm specific.

Table B-11 CIS_ALGORITHM_ATTR_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	Algorithm attribute type name.	N
DESCR	VARCHAR2(200)	Algorithm attribute type description.	Y

Notes:

Different types of algorithm properties/attributes are possible; some of them apply to multiple algorithms while others are algorithm specific. Types include Common Properties, Scale Properties, Attribute Scale Properties, and Algorithm Specific Properties

CIS_ATTR_TYPE

This table determines the possible attributes used in clustering, such as numeric or float.

Table B-12 CIS_ATTR_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	The name of attribute type.	N
DESCR	VARCHAR2(200)	Descriptive text for attribute type.	Y
GENERIC_TYPE_NAME	VARCHAR2(30)	Grouped attributes in generic name type.	Y

Notes:

This table determines the possible attributes used in clustering, such as numeric or float.

CIS_ATTR_TYPE_FN

This table determines the mathematical function that can be applied to the individual attributes based on their presence on different screens (pivot/insights).

Table B-13 CIS_ATTR_TYPE_FN

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
SQL_FN	VARCHAR2(30)	The function applied on clustering attributes in different UI screens.	Y
SQL_DESCR	VARCHAR2(300)	Descriptive text to describe the clustering function.	Y

Notes:

This table determines the mathematical function that can be applied on the individual attributes based on their presence on different screens (pivot/insights).

CIS_BUS_OBJ_HIER_DEPLOY_XREF

This table identifies the business object, objectives, product hierarchy types, and levels that are eligible to be selected for deployment. This ensures that only authorized types of clusters are exported to external systems (Category Management).

Table B-14 CIS_BUS_OBJ_HIER_DEPLOY_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	FK for the CIS_BUSINESS_OBJECT. Part of a composite FK to CIS_BUSSOBJ_OBJECTIVE_XREF. This defines the business object that is eligible for exporting.	N
OBJECTIVE_ID	NUMBER(10)	FK to the CIS_OBJECTIVE table. Part of a composite FK to the CIS_BUSSOBJ_OBJECTIVE_XREF table. This defines the objective that is eligible for being deployed.	N
PROD_HIER_TYPE_ID	NUMBER(10)	FK to RSE_HIER_TYPE, although it is expected to be limited to only hierarchy types that are related to products.	Y
PROD_HIER_LEVEL_ID	NUMBER(10)	FK to RSE_HIER_LEVEL. This defines the level of the product hierarchy within the specified product hierarchy type that is eligible for being deployed.	Y
CURRENT_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this record is considered current (Y) or not (N). Only current records are able to be considered usable.	Y
DELETE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the record should be considered deleted (Y) or not (N).	Y

CIS_BUS_OBJ_NESTED_TCRITERIA

This table is used to determine possible child cluster type(s) for a parent cluster.

Table B-15 CIS_BUS_OBJ_NESTED_TCRITERIA

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the objective.	N
TYPE_CRITERIA_ID	NUMBER(10)	FK for the type criteria.	N
CHL_TYPE_CRITERIA_ID	NUMBER(10)	The possible child criteria ID. It is mainly used for nested clustering.	N
CHL_CRITERIA_ALLWD_FLG	VARCHAR2(1)	Indicates whether the combination of parent and child is allowed in a given matrix.	Y
CURRENT_FLG	VARCHAR2(1)	Indicate whether this row is the most recent row (Y), or if it is a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	Indicates whether the row is considered deleted (Y) or not (N).	Y

Notes:

This table is used to determine possible child cluster type(s) for a parent cluster. It is mainly used in nested clustering.

CIS_BUS_OBJ_TCRITERIA_ATT_XREF

This table is a cross reference for the possible attributes based on objective, business objective, cluster type, and product.

Table B-16 CIS_BUS_OBJ_TCRITERIA_ATT_XREF

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the CIS objective.	N
TYPE_CRITERIA_ID	NUMBER(10)	Cluster types allowed for the combination of objective ID and business objective ID.	N
TCRITERIA_ATTR_ID	NUMBER(10)	This field contain the attribute ID reference from cis_tcriteria_attr table.	N
DFLT_ATTR_WEIGHT	NUMBER(18,4)	Default weight to be used for an attribute.	Y
PARTICIPATING_ATTR_FLG	VARCHAR2(1)	Identifies those attributes within the type that are considered as optimal for the clustering calculation.	Y
VALIDATING_ATTR_FLG	VARCHAR2(1)	This flag is an indicator for the type of attribute. This indicates that it is a validating attribute.	Y
INFORMATIONAL_ATTR_FLG	VARCHAR2(1)	Identifies those attributes within the type that are considered as only informational but not optimal for the clustering calculation.	Y
ATTR_SEQ	NUMBER(4)	Internal use for ordering of attributes.	Y
CURRENT_FLG	VARCHAR2(1)	Indicates whether this row is the most recent row (Y), or if it is a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	Indicates whether the row is considered deleted (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	The user who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	The date when the record was created.	N
CHANGED_BY_USER	VARCHAR2(255)	The user who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	The date when the record was last changed.	Y
PROD_HIER_ID	NUMBER(10)	This field is populated only for product attribute clustering, as the attributes do not change for other cluster types.	Y
PROD_HIER_TYPE_ID	NUMBER(10)	This field is populated only for product attribute clustering, as the attributes do not change for other cluster types.	Y
FN_STORE_LVL	NUMBER(10)	This field determines the aggregation level at store (Default=2).	Y
FN_CLUSTER_LVL	NUMBER(10)	This field determines the aggregation level at cluster (Default=2).	Y
FN_PIVOT_STORE_LVL	NUMBER(10)	This field determines the aggregation level at explore data screen (Default=2).	Y
TCRITERIA_GRP_BY_ID	NUMBER(10)	This column is used to for grouping of certain type criteria(s) for Mixed Attribute clustering.	Y
ATTR_DATE_VALUE	DATE	This field contains the provided date value for product attribute group.	Y
ATTR_NUM_VALUE	NUMBER(22,5)	This field contains the provided number value for product attribute group.	Y
ATTR_STRING_VALUE	VARCHAR2(255)	This field contains the provided string value for product attribute group.	Y
ATTR_VALUE_EXT_CODE	VARCHAR2(255)	This field contains the externally provided unique ID for this product attribute group.	Y
PROD_ATTR_GRP_ID	NUMBER(10)	Referenced product attribute ID for product attribute.	Y
PROD_ATTR_GRP_NAME	VARCHAR2(255)	Referenced product attribute group name for product attribute.	Y
PROD_ATTR_GRP_VALUE_ID	NUMBER(10)	Referenced product attribute value ID for product attribute.	Y

Notes:

This table is a cross reference for the possible attributes based on objective, business objective, cluster type and product.It also includes the information about whether the attribute is informational or participating.

CIS_BUS_OBJ_TCRITERIA_XREF

This table specifies the possible cluster types allowed for the combination of objective ID and business objective ID.

Table B-17 CIS_BUS_OBJ_TCRITERIA_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the CIS objective.	N
TYPE_CRITERIA_ID	NUMBER(10)	Type Criteria ID.	N
PRIMARY_FLG	VARCHAR2(1)	This is the primary/default cluster objective type to be used.	Y
BUS_OBJ_TCRITERIA_SEQ	NUMBER(5)	This is the sequence in which the instance should be used in cases where there are multiple instances.	Y
DEF_SCRE_THRESHOLD_PCT	NUMBER(7,4)	This is a default threshold for the score for each criteria, based on which the UI indicates if a score is below a desired threshold. If not provided, the default score threshold from RSE_CONFIG is used, which is applicable across all the criteria.	Y
OUTLIER_RULE_ID	NUMBER(10)	FK to the CIS outlier rules.	N
OUTLIER_ATTR_VALUE_1	NUMBER(7,4)	The value that defines the threshold for which a data value is considered an outlier for the criteria. If not specified, then the outlier value will be obtained from RSE_CONFIG.	Y
OUTLIER_ATTR_VALUE_2	NUMBER(7,4)	An additional value that can be used to define the threshold for which a data value is considered an outlier for the criteria. If not specified, then the outlier value will be obtained from RSE_CONFIG.	Y
OUTLIER_ATTR_VALUE-3	NUMBER(7,4)	An additional value that can be used to define the threshold for which a data value is considered an outlier for the criteria. If not specified, then the outlier value will be obtained from RSE_CONFIG.	Y
NEWSTR_RULE_ID	NUMBER(10)	FK to the CIS_NEWSTR_RULES.	N
DISABLE_ATTR_WTS	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) attribute weights.	Y
INSIGHT_LINE_GRAPH_BI	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) display line graph in insight screen.	Y
INSIGHT_SLS_CENTROID_GRAPH_BI	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) sales centroid graph in insight screen.	Y
INSIGHT_VALIDATION_GRAPH_BI	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) validation graph in insight screen.	Y
INSIGHT_SALES_GRAPH_BI	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) sales graph in insight screen.	Y
INSIGHT_STACK_GRAPH_BI	VARCHAR2(1)	A Y/N flag to enable (N) or disable (Y) stack bar graph in insight screen.	Y
INSIGHT_SHOW_LG_BI	VARCHAR2(1)	A Y/N flag to display (Y) or not display (N) display line graph in insight screen.	Y
INSIGHT_SHOW_SCG_BI	VARCHAR2(1)	A Y/N flag to display (Y) or not display (N) sales centroid graph in insight screen.	Y
INSIGHT_SHOW_VG_BI	VARCHAR2(1)	A Y/N flag to display (Y) or not display (N) validation graph in insight screen.	Y
INSIGHT_SHOW_SG_BI	VARCHAR2(1)	A Y/N flag to display (Y) or not display (N) sales graph in insight screen.	Y
INSIGHT_SHOW_SB_BI	VARCHAR2(1)	A Y/N flag to display (Y) or not display (N) stack bar graph in insight screen.	Y
SRC_TIME_PERIOD_FLG	VARCHAR2(1)	A Y/N flag to show display (Y) or not display (N) time period in definition screen.	Y
SUMM_FLG	VARCHAR2(1)	A Y/N flag to show display (Y) or not display (N) calendar summarization in definition screen.	Y
MERCH_GRP_FLG	VARCHAR2(1)	A Y/N flag to show display (Y) or not display (N) product summarization in definition screen.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
PIVOT_TBL_FLTR_FLG	VARCHAR2(1)	A Y/N to show display (Y) or not display (N) filters in UI	Y

Notes:

This table specifies the possible cluster types allowed for the combination of objective ID and business objective ID.

CIS_BUSINESS_OBJECT

This table hosts the list of application that are registered/configured to use the clustering feature. Values are provided for Life Cycle Pricing and Promotion (LCPP), Category Management (CM), and Assortment Rationalization (AR).

Table B-18 CIS_BUSINESS_OBJECT

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.
NAME	VARCHAR2(50)	This is the name of the business objects that is used to generate the clusters (for example, Store Cluster, Customer Cluster).
SHORT_NAME	VARCHAR2(10)	Short name of the business objective.
DESCR	VARCHAR2(200)	Description of the business objective.
SOURCE_ENTITY_NAME	VARCHAR2(30)	The name of the database table that provides the values for this business object.
SOURCE_COLUMN_NAME	VARCHAR2(30)	The name of the database table column that provides the values for this business object.
SOURCE_ENTITY_ALIAS	VARCHAR2(30)	An alias/abbreviation by which this source database object should be referred t0.
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).
CREATED_BY_USER	VARCHAR2(255)	User who created the record.
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.
CHANGED_VY_USER	VARCHAR2(255)	User who last changed the record.
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).

Notes:

This table hosts the list of application that are registered/configured to use the clustering feature. Values include Life Cycle Pricing and Promotion (LCPP), Category Management (CM), and Assortment Rationalization (AR).

CIS_BUSSOBJ_OBJ_ALG_XREF

This cross reference table provides the ability to use the same algorithm to generate different cluster objectives. The same algorithm can be used to generate customer clusters as well as store clusters. In addition, multiple algorithms can be listed that can be used to achieve a similar objective.

Table B-19 CIS_BUSSOBJ_OBJ_ALG_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	FK to the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the CIS Objective	N
ALGORITHM_ID	NUMBER(10)	FK for the Algorithm to be applied to business ID and objective ID.	N
PRIMARY_FLG	VARCHAR2(1)	This flag identified the primary attribute within the type.	Y
BUSSOBJ_OBJ_ALG_SEQ	NUMBER(4)	This field provides the sequence in which the specific cross reference should be used.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y

Notes:

This table provide the ability to 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, multiple algorithms that could be used to achieve similar objective can be listed.ALGORITHM_ID - Algorithm to be applied to BUSINESS_ID and OBJECTIVE_ID.

CIS_BUSSOBJ_OBJECTIVE_XREF

This table hosts the cross reference for the clustering objectives that are valid for an application. In most cases, an application will use clustering feature to achieve a single objective; however, there could be cases in which an application can perform cluster generation for multiple purposes.

Table B-20 CIS_BUSSOBJ_OBJECTIVE_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	BUSSOBJ_ID is reference to CIS_BUSINESS_OBJECT table.	N
OBJECTIVE_ID	NUMBER(10)	OBJECTIVE_ID refers to CIS_OBJECTIVE table.	N
PRIMARY_FLG	VARCHAR2(1)	This is the primary/default cluster objective to be used.	Y
BUSSOBJ_OBJ_SEQ	NUMBER(5)	This is the sequence at which the instance should be used in case there are multiple instances.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y

Notes:

This table contains cross references about which clustering objectives are valid per application.BUSSOBJ_ID refers to CIS_BUSINESS_OBJECT table.OBJECTIVE_ID refers to CIS_OBJECTIVE table. BUSSOBJ_OBJ_SEQ determines the sequence in which the instance should be used in case there are multiple instances.

CIS_BUSSOBJ_TCRIT_HIER_XREF

This table specifies the possible hierarchy levels for each hierarchy type (merchandise and location) allowed for the combination of objective ID, business objective ID, and type criteria ID.

Table B-21 CIS_BUSSOBJ_TCRIT_HIER_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the CIS objective.	N
TYPE_CRITERIA_ID	NUMBER(10)	Type Criteria ID.	N
HIER_TYPE_ID	NUMBER(10)	FK for the RSE_HIER_LEVEL table hier_type_id.	N
HIER_LVL_ID	NUMBER(4)	FK for the RSE_HIER_LEVEL table ID.	N
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y

CIS_CLUSTER_CATEGORY

This table determines the possible type of cluster types - normal, flagship, dormant etc

Table B-22 CIS_CLUSTER_CATEGORY

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	Name of the cluster category.	Y
DESCR	VARCHAR2(255)	Special Cluster - Manually Allocated, Special Cluster - Exceptional, Normal Cluster.	Y

Notes:

This table determines the possible type of cluster types, such as normal, flagship, or dormant.

CIS_CLUSTER_GROUP_BY_TYPE

This table contains the catalog for the distinct group-by options available for clustering.

Table B-23 CIS_CLUSTER_GROUP_BY_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	The name of the group by option.	Y
DESCR	VARCHAR2(80)	This entity contains the catalog for the distinct group by options available for clustering, including Group By, Location Node, Merchandise Node, Calendar Node, Location Hierarchy Level, Merchandise Hierarchy Level, Calendar Hierarchy Level.	Y

Notes:

This table keeps the catalog for the distinct group by options available for clustering, including Group By, Location Node, Merchandise Node, Calendar Node, Location Hierarchy Level, Merchandise Hierarchy Level, and Calendar Hierarchy Level.

CIS_CLUSTER_MEMBER_INT

This table contains the final stores created by the clusters approved for a given combination of location, merchandise, calendar dimension(s), and cluster criteria type.

Table B-24 CIS_CLUSTER_MEMBER_INT

Column Name	Data Type	Comments	Nullable?
CLUSTER_ID	NUMBER(10)	This column is populated by cis_cluster.id.	N
CLUSTER_LABEL	VARCHAR2(50)	This column is populated by cis_cluster.name.	N
CLUSTER_SET_ID	NUMBER(10)	This column is populated by cis_cluster_config_hdr.id.	N
STORE_LOCATION_ID	VARCHAR2(80)	This column is populated by rse_loc_src_xref.loc_ext_key.	N

Notes:

This table contains the final stores created by the clusters approved for a given combination of location, merchandise, calendar dimension(s), and cluster criteria type.

CIS_CLUSTER_OUTLIER_RULE

This table contains the possible outlier rules for a type criteria.

Table B-25 CIS_CLUSTER_OUTLIER_RULE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
TYPE_CRITERIA_ID	NUMBER(10)	FK for the type criteria.	N
OBJECTIVE_ID	NUMBER(10)	FK for the CIS objective.	N
DESCR	VARCHAR2(200)	Descriptive text to define this outlier rule.	Y
RULE	VARCHAR2(80)	This is the text to use to evaluate the rule store_count > X.X is a placeholder that is replaced by the value provided by the user or the default value set during initial installation.	Y
DFLT_LOW_VALUE	VARCHAR2(50)	This defines the minimum value for this outlier rule. For example, this can specify that a minimum of five locations are required in a cluster.	Y
DFLT_HIGH_VALUE	VARCHAR2(50)	This defines the maximum value for this outlier rule. For example, this can specify that a maximum of 50 locations are allowed in a cluster.	Y
ACTIVE_FLG	VARCHAR2(1)	This is a Y/N flag that defines whether the rule is an actively used rule (Y) or not (N).	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this row is considered a deleted row (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(200)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y

Notes:

This table contains the possible outlier rules for a type criteria.

CIS_CLUSTER_SET_EXP_VW

This view provides an exportable set of clusters to send to Category Management.

Table B-26 CIS_CLUSTER_SET_EXP_VW

Column Name	Data Type	Comments	Nullable?
EFF_START_DT	VARCHAR2(11)	The starting date when the cluster is effective.	Y
EFF_END_DT	VARCHAR2(11)	The ending date when the cluster is effective.	Y
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the product hierarchy this cluster is applicable to.	N
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the store location that belongs in this cluster.	N
CLUSTER_ID	NUMBER(10)	The identifier for the cluster.	N
CLUSTER_LABEL	VARCHAR2(50)	A descriptive name/label for the cluster.	N

CIS_CLUSTER_SET_INT

This table contains the approved clusters for a given combination of location, merchandise, calendar dimension(s), and cluster criteria type.

Table B-27 CIS_CLUSTER_SET_INT

Column Name	Data Type	Comments	Nullable?
CLUSTER_SET_ID	NUMBER(10)	This column is populated by cis_cluster_config_hdr.id.	N
CLUSTER_SET_LABEL	VARCHAR2(50)	This column is populated by cis_cluster_config_hdr.name.	N
PARENT_CLUSTER_SET_ID	NUMBER(10)	This column is populated by cis_cluster_config_hdr.parent_cluster_config_hdr_id.	N
MERCHANDISE_ID	VARCHAR2(80)	Thsi column is populated by rse_prod_src_xref.prod_ext_key.	N
LOCATION_ID	VARCHAR2(80)	This column is populated by rse_loc_src_xref.loc_ext_key.	N
EFFECTIVE_START_DATE	DATE	Start date of the given combination of clusters.	N
EFFECTIVE_END_DATE	DATE	End date of the given combination of clusters.	N

Notes:

This table contains the approved clusters for a given combination of location, merchandise, calendar dimension(s), and cluster criteria type.

CIS_CLUSTER_STATUS

This table determines the status of the cluster.

Table B-28 CIS_CLUSTER_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for the table.	N
DESCR	VARCHAR2(80)	Descriptive text for this cluster status.	Y

Notes:

This table determines the status of the cluster.

CIS_CLUSTER_TYPE

This table contains the list of the different types of possible clusters, including deployed, automatically generated, and user generated.

Table B-29 CIS_CLUSTER_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
DESCR	VARCHAR2(80)	Descriptive text for this cluster type.	Y

Notes:

This table contains the list of the different types of possible clusters, including deployed, automatically generated, and user generated.

CIS_EFFECTIVE_PERIOD

This table contains the planning period information.

Table B-30 CIS_EFFECTIVE_PERIOD

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
DESCR	VARCHAR2(80)	Descriptive text for this effective period.	Y
START_PERIOD_ID	NUMBER(10)	Start period ID in the calendar hierarchy for the period.	N
END_PERIOD_ID	NUMBER(10)	End period ID in the calendar hierarchy for the period.	N
BUSSOBJ_ID	NUMBER(10)	FK for the business object objective.	N
OBJECTIVE_ID	NUMBER(10)	FK for the objective .	N
TYPE_CRITERIA_ID	NUMBER(10)	FK for the type criteria.	N
ACTIVE_FLG	VARCHAR2(1)	This is a Y/N flag that defines whether this period is to be actively used (Y) or not (N).	Y

Notes:

This table contains the planning period information.

CIS_OBJECTIVE

This table contains the details corresponding to the different objectives that can be achieved by the clustering implementation.

Table B-31 CIS_OBJECTIVE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	This is the purpose/usage for which the cluster is created.	N
DESCR	VARCHAR2(200)	More descriptive text for this objective.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMRESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
DELETE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this record is considered deleted (Y) or not (N).	Y

Notes:

This table contains details corresponding to the different objectives that can be achieved by the clustering implementation.

CIS_SCENARIO_STATUS

This table contains the scenario status, including created, executed, approved or rejected.

Table B-32 CIS_SCENARIO_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
DESCR	VARCHAR2(80)	Descriptive text for the scenario.	Y

Notes:

This table contains the scenario status.

CIS_TCRITERIA_SRC_XREF

This table is a cross reference for SRC_ENTITY_NAME and also the settings for Participating, Informational for that SRC_ENTITY_NAME's attributes.

Table B-33 CIS_TCRITERIA_SRC_XREF

Column Name	Data Type	Comments	Nullable?
BUSSOBJ_ID	NUMBER(10)	PK for this table.	N
OBJECTIVE_ID	NUMBER(10)	PK for this table.	N
TYPE_CRITERIA_ID	NUMBER(10)	PK for this table.	N
SRC_ENTITY_NAME	VARCHAR2(30)	The name of the DB view which should be including when setting up the BOTAX table data. PK for this table	N
PARTICIPATING_ATTR_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the attributes from this DB view should be participating (Y) or not (N). Only one ATTR_FLG column can be set to a Y value.	N
VALIDATING_ATTR_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the attributes from this DB view should be validating (Y) or not (N).	N
INFORMATIONAL_ATTR_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the attributes from this DB view should be informational (Y) or not (N). Only one ATTR_FLG column can be set to a Y value.	N
CURRENT_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this row should be considered as a currently usable row (Y) or not (N).	Y
DELETE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this row is considered deleted (Y) or not (N).	Y

Notes:

This table contains the scenario status.

CIS_TCRITERIA_ATTR

This table contains all the possible attributes in clustering process.

Table B-34 CIS_TCRITERIA_ATTR

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	Name for the criteria attribute.	N
DESCR	VARCHAR2(200)	More descriptive text for the criteria attribute.	Y
SRC_ENTITY_NAME	VARCHAR2(30)	Name of table/view that holds the attribute information/value coming from Retail Analytics or an external system.	Y
SRC_COLUMN_NAME	VARCHAR2(30)	Name of the column in the Retail Analytics or external system table/view.	Y
SRC_ENTITY_ALIAS	VARCHAR2(30)	Alias of the column in the Retail Analytics or external system table/view.	Y
ATTR_TYPE_ID	NUMBER(10)	Type of the attribute.	N
DISPLAY_PERCENT	VARCHAR2(1)	Display percent symbol in BI for an attribute.	Y
DISPLAY_FORMAT_ID	NUMBER(10)	Foreign key to the RSE_DISPLAY_FORMAT table that enables the control of how the attribute should be formatted for display. NOTE: The control file expects a string that corresponds to the EXT_KEY column of the RSE_DISPLAY_FORMAT table.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
UI_DISPLAY_NAME	VARCHAR2(200)	The value to display in the UI when showing this criteria attribute.	Y
TCRITERIA_ATTR_SRC_XREF_ID	NUMBER(10)	Field contains the reference to the PK of the of the object which this attribute definition belongs to. For example, if an attribute is representative of a specific consumer segment, then this column will contain the FK to that consumer segment.	Y

Notes:

This table contains all the possible attributes in all type of clustering process.

CIS_TCRITERIA_ATTR_TYPE_VALUE

This table is used to maintain the list of valid values for ordinal and categorical attributes. The list of valid values is directly assigned to the type criteria attribute, since the valid values are different for each attribute.

Table B-35 CIS_TCRITERIA_ATTR_TYPE_VALUE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
TCRITERIA_ATTR_ID	NUMBER(10)	FK of the cis_tcriteria_attr entity.	N
ATTR_VALUE	VARCHAR2(80)	This column contains the attribute value.	Y
VALUE_SEQ	NUMBER(4)	This column contains the sequence in which the values should be used/displayed.	Y
VALUE_PRIORITY_RANK	NUMBER(4)	This column is used as a tiebreaker in cases where two values have the same number of instances and the screen.process needs to break the tie by giving preference to one value over the other.	Y

Notes:

This table is used to maintain the list of valid values for ordinal and categorical attributes. The list of valid values is directly assigned to the type criteria attribute, since the valid values is different for each attribute.

CIS_TCRITERIA_ATTR_XREF

This table contains the cross reference between attributes for the cluster types.

Table B-36 CIS_TCRITERIA_ATTR_XREF

Column Name	Data Type	Comments	Nullable?
TCRITERIA_ATTR_ID	NUMBER(10)	This field contains the possible attribute defined in clustering.	N
TYPE_CRITERIA_ID	NUMBER(10)	This field contains the cluster type defined against each clustering attribute.	N
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y

Notes:

This table contains the cross reference between attributes for the cluster types.

CIS_TYPE_CRITERIA

This table contains the list of different clustering types/criteria that can be used to generate clusters.

Table B-37 CIS_TYPE_CRITERIA

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(50)	This is the UI name of the clustering type/criteria. This is the cluster by list of values.	N
TYPE_NAME	VARCHAR2(50)	This is the static name of the clustering type/criteria. This should never be changed for display purposes.	N
DESCR	VARCHAR2(200)	More descriptive text to describe the criteria type.	Y
CODE	CHAR	Internal identification code for this clustering type/criteria.	N
DISTRIBUTION_GRP_FLG	VARCHAR2(1)	Certain attribute can be represented as a distribution (per store and/or cluster, such as with consumer segmentation). This flag helps the UI identify which attributes belong to the same distribution group (where the total value adds up to 100%).	Y
DFLT_MIN_NUM_CLUSTER	NUMBER(10)	This is the default for the minimum number of clusters expected for this cluster type.	Y
DFLT_MAX_NUM_CLUSTER	NUMBER(10)	This is the default for the maximum number of clusters expected for this cluster type.	Y
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y), or if it a historical row (N).	Y
CREATED_BY_USER	VARCHAR2(255)	User who created the record.	N
CREATED_ON_DT	TIMESTAMP(6)	Record creation date.	N
CHANGED_BY_USER	VARCHAR2(255)	User who last changed the record.	Y
CHANGED_ON_DT	TIMESTAMP(6)	Last changed date.	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y

Notes:

This table contains the list of different clustering types/criteria that can be used to generate clusters.

DT_AE_EXP_VW

This view provides all the exportable data elements needed to provide the Assortment Elasticity metric that the DT application has calculated. This view only provides results for active results.

Table B-38 DT_AE_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	The external identifier for the category this data belongs to.	Y
CUSTSEG_EXT_KEY	VARCHAR2(80)	The external identifier for the customer segment associated with this data.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external identifier for the location	Y
AE	NUMBER(22,7)	The assortment elasticity that DT has calculated.	Y
EFFECTIVE_DT_FROM	DATE	The date when this data was activated.	Y
EFFECTIVE_DT_TO	DATE	Not used.	Y

DT_ASSORT_MULT_EXP_VW

This view provides an exportable list of assortment multipliers to RDF so that the impact of assortment changes can influence RDF results.

Table B-39 DT_ASSORT_MULT_EXP_VW

Column Name	Data Type	Comments	Nullable?
EFF_START_DT	DATE	The date that this assortment multiplier is effective for use.	Y
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the product.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the store location.	Y
ASSORT_MULT	NUMBER(38,20)	The assortment multiplier associated with the product and location, as a result of changes to the assortment at the location.	Y

DT_ATTR_WGT_EXP_VW

This view provides the export data that is provided to the Category Management system for attribute weights used by the DT application.

Table B-40 DT_ATTR_WGT_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the category	Y
CUSTSEG_EXT_KEY	VARCHAR2(80)	The external ID for the customer segment	Y
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the location hierarchy/trade area	Y
ATTRIBUTE_EXTERNAL_ID	VARCHAR2(80)	The external ID for the attribute	N
ATTR_WGT	NUMBER(22,7)	The decimal weight that this attribute represents within the category/customer segment/trade area.	Y
FUNC_ATTR_IND	NUMBER	An indicator to indicate if the attribute is a functional attribute (1) or not (0). A functional attribute is one that fits a specific purpose and cannot be substituted by other products with other values for this attribute.	Y

DT_EXCLUDE

This table defines the different types of pruning filters that are available to exclude a DT result from being used during the escalation phase of the DT workflow.

Table B-41 DT_EXCLUDE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	The name of the pruning filter.	Y
DESCR	VARCHAR2(255)	Descriptive text for the pruning filter.	Y
PROC_NAME	VARCHAR2(30)	Name of the process that performs this data filter.ing	Y
DISPLAY_SEQ	NUMBER(10)	The order in which the filters should be displayed when viewing filter statistics in the UI.	Y
PROCESS_SEQ	NUMBER(10)	The order in which the filters should be executed during the filter stage.	Y
ENABLE_FLG	VARCHAR2(1)	A Y/N flag that indicates whether the filter is enabled for use.	Y

Notes:

This table can be used to customize the pruning filters that run after DT Models have been created. This allows for the flexibility in the customized rules for pruning DT Models from the list of usable Models.

The NAME and DESCR columns are displayed in the UI if the NAME value is not found in the UI's resource bundle.

The PROC_NAME is the name of the procedure that should be executed to perform this pruning task. This routine should be implemented in either the DT_PRUNE_T type, or in a database type that extends this type and then is configured as the type to execute for the DT_PRUNE database service.

When the pruning stage runs, this table is referenced, and each enabled filter is executed in ascending order based on the PROCESS_SEQ column. Therefore, this column should be unique in order to ensure consistency in the order in which the filters are executed.

The DISPLAY_SEQ column allows for displaying the filters in the UI in a different order than what they may be executed. Although setting these two columns with different values might be confusing to the user, it can be done if needed.

The ENABLE_FLG offers the ability to exclude a filter from processing. This can be helpful if a filter is no longer deemed relevant to run. Setting this column to N prevents further execution of the filter, although any existing filter statistics about prior executions of the filter will remain.

DT_FILTER

This table defines the different types of data filters that are used during the DT data filtering process.

Table B-42 DT_FILTER

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	The PK for the DT Filter.	N
NAME	VARCHAR2(80)	A name for the filter.	Y
DESCR	VARCHAR2(255)	Descriptive text to describe the filter.	Y
SRVC_TYPE	VARCHAR2(30)	The service type for the data filters implementation.	Y
SRVC_NAME	VARCHAR2(30)	The service name for the data filters implementation.	Y
DISPLAY_SEQ	NUMBER(10)	The order in which the filters should be displayed in the UI.	Y
PROCESS_SEQ	NUMBER(10)	The order in which the filters should be executed.	Y
ENABLE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the filter is enabled (Y) or not (N) when data filtering is executed.	Y

Notes:

This table contains the list of DT Filters that can be executed against baseline sales data in order to remove outliers or any data that can lead to bad results. Although the UI has a fixed number of prompts on the data filtering stage, this table offers the ability to add or remove any filter in the data filtering workflow.

When the data filtering stage runs, this table will be referenced and each enabled filter will be executed in ascending order, based on the PROCESS_SEQ column. Therefore, this column should be unique in order to ensure consistency in the order in which the filters are executed.

The DISPLAY_SEQ column allows for displaying the filters in the UI in a different order than the one they may be executed in. Although setting these two columns with different values might be confusing to the user, it can be done if needed.

The ENABLE_FLG offers the ability to exclude a filter from processing. This can be helpful if a filter is no longer deemed relevant to run. Setting this column to N prevents further execution of the filter, although any existing filter statistics about prior executions of the filter will remain.

The SRVC_TYPE and SRVC_NAME columns allow for the specification of the actual implementation that performs the data filtering task. These implementations should be extensions of the DT_FILTER_BASELINE_T database type. The SRVC_TYPE should be defined in the RSE_SRVC_TYPE table, and the SRVC_NAME should be defined in the RSE_SRVC_CONFIG table. Because of this configuration, this table offers the ability to run additional baseline sales filters.

DT_LOC_WK_EXCL_STG

This is a staging table that loads a list of locations and dates that should be excluded from Demand Transference processing. This can be useful for excluding abnormal or corrupted data points.

Table B-43 DT_LOC_WK_EXCL_STG

Column Name	Data Type	Comments	Nullable?
LOC_EXT_KEY	VARCHAR2(80)	External ID for the location.	Y
WK_END_DT	DATE	The week end date of a week to be excluded.	Y
UPDT_CODE	VARCHAR2(1)	A code to indicate how to update the target table. U=Update/Create, D=Delete existing record.	Y

DT_MDL_PROD_EXP_STG

This table is the staging table which provides a list of products that are eligible for processing Model Apply in order to receive product to product demand transferences. The values loaded here should be of the same product hierarchy which DT is associated to work with.

Table B-44 DT_MDL_PROD_EXP_STG

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	The external product identifier for the hierarchy to be included in later model apply processing.	Y

DT_ASSORT_TRANS_EXP_VW

This view provides an exportable list of assortment multipliers to AIP, so that the impact of assortment changes can influence AIP results.

Table B-45 DT_ASSORT_TRANS_EXP_VW

Column Name	Data Type	Comments	Nullable?
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the store location.	N
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the product.	N
REPL_PROD_EXT_KEY	VARCHAR2(80)	The external ID for the replacement product.	N
TRANSFER_PCT	NUMBER(38,20)	The forecasted rate of sale for this product at this location.	Y

DT_NEW_ITEM_ROS_EXP_VW

This view provides an exportable view of new items and their forecasted rate of sale to RDF.

Table B-46 DT_NEW_ITEM_ROS_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the product.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the store location.	Y
FCST_ROS	NUMBER(38,20)	The forecasted rate of sale for this product at this location.	Y

DT_NEW_ITEMS_EXP_VW

This view provides a list of items and locations for which the item is newly added to the assortment at the location. It is provided in an exportable view for use by RDF.

Table B-47 DT_NEW_ITEMS_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	The external ID for the product.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external ID for the store location.	Y
EFF_START_DT	DATE	The date when this product is considered to be added to the assortment.	Y

DT_PROD_LOC_EXCL_STG

This is the staging table for products and locations that should be excluded from DT processing, as if they were out of the assortment.

Table B-48 DT_PROD_LOC_EXCL_STG

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY	VARCHAR2(80)	External product key.	Y
LOC_EXT_KEY	VARCHAR2(80)	External id for the location.	Y
WK_FROM_DT	DATE	Week date to start the exclusion at.	Y
WK_TO_DT	DATE	Week date to end the exclusion at.	Y

DT_SIM_EXP_VW

This view provides an export of product similarities calculated within the DT application for export to Category Management.

Table B-49 DT_SIM_EXP_VW

Column Name	Data Type	Comments	Nullable?
PROD_EXT_KEY1	VARCHAR2(80)	The external identifier for one half of the product pair.	Y
CUSTSEG_EXT_KEY	VARCHAR2(80)	The external identifier for the customer segment this data relates to.	Y
LOC_EXT_KEY	VARCHAR2(80)	The external identifier for the store location this data relates to.	Y
PROD_EXT_KEY2	VARCHAR2(80)	The external identifier for the other half of the product pair.	Y
PROD_SIM	NUMBER(22,7)	The measurement of how similar the two products are to each other. The values range between values of 0 (completely dissimilar) to values of 1 (completely similar).	Y
EFFECTIVE_DT_FROM	DATE	The date this similarity value became effective.	Y
EFFECTIVE_DT_TO	DATE	The date this similarity value is effective until.	Y

PROCESS_STATUS

This table contains processing status columns for use by components that run and manage and report status.

Table B-50 PROCESS_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER	PK for this table.	N
SRVC_TYPE	VARCHAR2(30)	An optional FK for the service type, which these statuses belong to.	Y
DESCR	VARCHAR2(40)	Descriptive text to describe the status.	Y
FAILURE_FLG	VARCHAR2(1)	A flag to indicate whether the status represents success (N/F) or failure (Y/T).	Y
EXCLUSIVE_FLG	VARCHAR2(1)	Not used. Intended to identify statuses that indicate that other related steps are not suitable for simultaneous execution.	Y

Notes:

This table contains the status and the description for any batch processes. These are currently used by the service request framework, as well as the job processing framework, and also by any user batch stage processes.

The SRVC_TYPE is used to distinguish between different Service Types in the event that a custom set of statuses are required. This is for future use and is not currently used.

The FAILURE_FLG and EXCLUSIVE_FLG can be NULL or can be a Y/T value to indicate that it is considered a Failed/Exclusive status, or a N/F value to indicate that it is considered a Successful/Non-Exclusive Status. The intent behind the EXCLUSIVE_FLG is to indicate at what point the status should be considered exclusive with another status. For example, two exclusive processes can both be in a Not Running status, or both be in a Complete status, but they cannot both be in a Running status. This feature is not currently implemented.

RSE_AGGR_SRVC_CONFIG

This table is used to control varying levels of aggregation needs for different database services.

Table B-51 RSE_AGGR_SRVC_CONFIG

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK column.	N
SRVC_ID	NUMBER(10)	FK for the DB Service that uses this configuration.	N
ENABLED_FLG	VARCHAR2(1)	A flag to indicate whether this aggregation configuration is enabled (Y) for processing or not (N).	Y

Notes:

This table defines various aggregation database services and indicates whether the service should be enabled or not. The SRVC_ID column defines the database service that uses this configuration. This column should contain a compatible key as found in RSE_SRVC_CONFIG.

The ENABLE_FLG allows for temporarily disabling an aggregation process from running (ENABLED_FLG=N).

RSE_AGGR_SRVC_CONFIG_LEVELS

This table defines the different hierarchy types and levels that need to have aggregate data created as part of this aggregation configuration.

Table B-52 RSE_AGGR_SRVC_CONFIG_LEVELS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
AGGR_SRVC_CONFIG_ID	NUMBER(10)	FK for the aggregation service configuration.	N
HIER_TYPE_ID	NUMBER(10)	FK for the hierarchy type.	N
HIER_LEVEL_ID	NUMBER(4)	FK for the hierarchy level required.	N

Notes:

This table is used to define what aggregation levels are required for a specified aggregation service (AGGR_SRVC_CONFIG_ID). This AGGR_SRVC_CONFIG_ID should be compatible with data found in RSE_AGGR_SRVC_CONFIG.

The HIER_TYPE_ID and HIER_LEVEL_ID should be valid hierarchy types and levels as defined in RSE_HIER_TYPE and RSE_HIER_LEVEL.

This table should only be configured to perform aggregation for the levels that are required in the application in order to reduce the performance implications of calculating these aggregations on a weekly basis.

RSE_APP_SOURCE

This table defines the list of applications that can be used as a data source for the application components.

Table B-53 RSE_APP_SOURCE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(255)	A name of this application. This value is not changeable, as it is a reference point in the code.	Y
DESCRIPTION	VARCHAR2(255)	Some descriptive text to better describe the application.	Y

Notes:

This table defines applications that can be integrated with. For example, this application has direct integration code with Retail Analytics, and therefore an entry should be present in this table for Retail Analytics. This configuration enables the application to store integration IDs that are specific to Retail Analytics for the various dimension tables. When support for alternative integration IDs is available, then an appropriate entry must be added to this table, and then this ID could be used in the relevant RSE*SRC_XREF tables. The NAME column in this table is a fixed value, as it is possible to use this NAME to lookup the ID within the application code.

RSE_BUSINESS_OBJECT_ATTR_MD

This table defines the attributes for business objects and also contains relevant details about where to obtain the data for this attribute from external table sources.

Table B-54 RSE_BUSINESS_OBJECT_ATTR_MD

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this object.	N
BUSINESS_OBJECT_MD_ID	NUMBER	FK for the business object that this attribute belongs to.	N
BUSINESS_OBJECT_DB_SRC_ID	NUMBER(10)	The FK for the database object source table, which contains the data for this attribute.	N
NAME	VARCHAR2(50)	A name for the attribute.	N
DESCR	VARCHAR2(255)	A more descriptive name for this attribute.	Y
SHORT_DB_NAME	VARCHAR2(30)	An alias for this database column name, which can be used as the column name for this attribute value when the attribute is later used in a cross tab query.	Y
SRC_COLUMN_NAME	VARCHAR2(30)	The name of the database column that contains the values for this attribute in the source system.	N
PROD_GRP_TYP	VARCHAR2(30)	This defines the type of extended attribute (for example, ITEMDIFF or ITEMUDA) for this attribute. This value should match prod_grp_type in one of the W_RTL_ITEM_GRP#_D tables.	Y
ATTR_EXT_CODE	VARCHAR2(255)	This column contains the value of the FLEX_ATTRIB_1_CHAR column for complex attributes. It defines the Attribute code for this attribute.	Y
TL_DOMAIN_CODE	VARCHAR2(255)	For attributes that are translated, this domain code should be populated with the corresponding DOMAIN_CODE as used in the TL lookup table (normally ITEM_UDA or DIFF). A null value indicates no translation of the data is required.	Y
TL_JOIN_EXPR	VARCHAR2(255)	This column contains an expression that defines how to join to the domain lookup TL table's Domain_member_code to retrieve the proper translated attribute value.	Y
EXCLUDE_FLG	VARCHAR2(1)	A Y/N flag to indicate whether the attribute should be used by any modules (N) or whether it should be excluded from use (Y).	Y

Notes:

The purpose of this table is to define the metadata needed for copying attributes from external data sources so that they can be used in this application. These attributes are not automatically updated and do require manual definition, since the scope of attributes and the mapping of the data can vary.

The BUSINESS_OBJECT_MD_ID should be aligned with values from RSE_BUSINESS_OBJECT_MD, and the values in BUSINESS_OBJECT_DB_SRC_ID should be aligned with values from RSE_BUSINESS_OBJECT_DB_SRC.

The NAME and DESCR columns are customizable according to what the attribute value is.

The SHORT_DB_NAME, SRC_COLUMN_NAME, PROD_GRP_TYPE, ATTR_EXT_CODE, TL_DOMAIN_CODE and TL_JOIN_EXPR are all used to define how to retrieve the data from the referenced BUSINESS_OBJECT_DB_SRC table.

For attributes that are contained in a simple column, the SRC_COLUMN_NAME is the sole means for copying the attribute value to the RSE. For attributes that are stored as Item Differentiators in Retail Analytics, the PROD_GRP_TYPE is populated with a value that triggers the attribute code to use special logic to obtain the data from a different column. These types of records require a value in the ATTR_EXT_CODE to enable the process to find the correct user defined attribute record in RA.

The TL_DOMAIN_CODE and TL_JOIN_EXPR columns are present to assist with means of getting the translation values for these user defined attributes from Retail Analytics' translation table.

The EXCLUDE_FLG is used to disable the use of the attribute without requiring it to be deleted from the metadata.

RSE_BUSINESS_OBJECT_DB_SRC

This table defines the source database objects from which attributes can be found.

Table B-55 RSE_BUSINESS_OBJECT_DB_SRC

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
DB_OBJECT_NAME	VARCHAR2(30)	The name of the source database table, from which we copy attributes from.	N
KEY_COLUMN_NAME	VARCHAR2(255)	The name of the PK column for the source table.	N
DB_OBJECT_ALIAS	VARCHAR2(30)	An alias for this table. This alias can be used in the various FILTER_CLAUSE, GROUP_BY_CLAUSE, ORDER_BY_CLAUSE columns of this table.	Y
FILTER_CLAUSE	VARCHAR2(2000)	A where clause that can applied to the source table to reduce the rows to be retrieved. The WHERE keyword is not expected in this column.	Y
GROUP_BY_CLAUSE	VARCHAR2(255)	A group by expression that can be used when obtaining the attributes from this table.	Y
ORDER_BY_CLAUSE	VARCHAR2(255)	An order by clause that can be specified so that data retrieval is ordered.	Y
APP_SOURCE_ID	NUMBER(10)	FK to the application source table which provides this attribute data.	N

Notes:

This table's purpose is to define the source tables that attribute values to this application. This metadata is used by the attribute loading process to copy those attribute values from these attribute source tables.

The DB_OBJECT_NAME is a name of a database object that this application has access to and can read from a database synonym. The KEY_COLUMN_NAME defines the column that can be used to uniquely identify the business object that a given attribute value belongs to. This column should exist in the DB_OBJECT_NAME's table. The DB_OBJECT_ALIAS is the alias that can be used in the FILTER_CLAUSE column.

The FILTER_CLAUSE enables the definition of any rules for filtering out records that should not be used. This can be helpful if deleted rows need to be ignored. The GROUP_BY_CLAUSE is used when a source table contains multiple attribute columns to be obtained. In this cause the GROUP_BY_CLAUSE should contain the KEY_COLUMN, plus the alias of ATTR_VALUE,ATTRIBUTE, that the code uses to pivot the multiple columns into multiple rows.The APP_SOURCE_ID column should be related to a row in the RSE_APP_SOURCE table.

RSE_BUSINESS_OBJECT_MD

This table identifies the distinct business objects that are handled within the application (such as product, location, customer, and consumer).

Table B-56 RSE_BUSINESS_OBJECT_MD

Column Name	Data Type	Comments	Nullable?
ID	NUMBER	PK for this table.	N
NAME	VARCHAR2(80)	Internal name of the business object. This value is not changeable.	Y
DESCR	VARCHAR2(255)	Descriptive text for the business object.	Y
HIER_TABLE_NAME	VARCHAR2(30)	Name of the table that contains the hierarchy for this object.	Y
ATTR_TABLE_NAME	VARCHAR2(30)	Name of the table that contains attribute data for this object.	Y
XREF_TABLE_NAME	VARCHAR2(30)	Name of the table that contains the integration cross reference ids for external systems.	Y
TC_TABLE_NAME	VARCHAR2(30)	Name of the table that contains a transitive closure representation of the hierarchy.	Y
LOCAL_ID_NAME	VARCHAR2(30)	The name of the column that contains the internal ID in all tables other than the table specified in HIER_TABLE_NAME (which always uses ID as its internal ID column).	Y
EXT_ID_NAME	VARCHAR2(30)	Name of the column that contains the external ID for external systems in the table mentioned in the XREF_TABLE_NAME column.	Y

Notes:

This table defines the types of business objects that the application interacts with. The NAME column is a fixed value that is referenced by application code. This NAME should be unique. The HIER_TABLE_NAME, ATTR_TABLE_NAME, and XREF_TABLE_NAME and TC_TABLE_NAME defines the tables that contain the hierarchy data in this database schema. Not all hierarchies require an Attribute table (ATTR_TABLE_NAME).

The purpose of the columns that specify column names in this table is to assist with code that performs dynamic updating of this data.

RSE_CONFIG

This table contains configuration names and their values for various settings that can be changed to affect the operation of the application.

Table B-57 RSE_CONFIG

Column Name	Data Type	Comments	Nullable?
APPL_CODE	VARCHAR2(20)	An identifier for the application that this configuration affects. The application code represents a generic configuration that affects all applications.	N
PARAM_NAME	VARCHAR2(80)	The name of the configuration.	N
PARAM_VALUE	VARCHAR2(255)	The value for this configuration.	Y
CONFIGURABLE_FLG	VARCHAR2(1)	A flag to indicate whether this configuration is changeable after the application has been installed and initially configured (Y) or whether it is not expected to be changed once the application has been used (N).	N
DESCR	VARCHAR2(2000)	A description for the configuration.	Y
UPDATEABLE_FLG	VARCHAR2(1)	A flag to indicate whether this configuration value can be updated by the application code (Y) or not (N).	Y

Notes:

This table is used to store configurable keys and their values for use by the application. The APPL_CODE is expected to be one of the application identifiers for the various modules (for example, CDT, CIS, DT, MBA, RSE, and ASO). The application code indicates that the code is applicable available for use by all application modules, while other values should be limited in scope to only that application module.

The PARAM_NAME is the key by which the application looks up a configuration value. This value is a fixed value used throughout the code in order to obtain the value that is contained in the PARAM_VALUE column. This value is adjustable on a per installation basis and should be reviewed and adjusted as required so that it affects the application in the manner that is intended. Some configuration values are not expected to change once the application has completed its configuration stage and has started to run. These types of values are identifiable via the CONFIGURABLE_FLG. Values with a Y can be changed at any time, while values with a N cannot be changed without risk of breaking existing data in the application.

The UPDATEABLE_FLG identifies whether the application has the ability to adjust the PARAM_VALUE as part of the application processes. Some parameters may need to record a record that signifies when something was done, or maybe what the value was processed by a process, while there is no suitable table to hold this type of processing value. So it should be expected that parameters with an UPDATEABLE_FLG=Y can change during the course of the application processes.

RSE_CONFIG_CODE

This table contains configuration values for configurations that can have different configuration values, depending on another value. For example, if a configuration is needed for a default error tolerance, but department 1 needs 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.

Table B-58 RSE_CONFIG_CODE

Column Name	Data Type	Comments	Nullable?
APPL_CODE	VARCHAR2(20)	An identifier for the application that this configuration affects. The application code represents a generic configuration that affects all applications.	N
PARAM_NAME	VARCHAR2(80)	The name of the configuration.	N
PARAM_CODE	VARCHAR2(80)	A code that enables specification of a configuration value for a specific data value.	N
PARAM_VALUE	VARCHAR2(255)	The value for this configuration.	Y
CONFIGURABLE_FLG	VARCHAR2(1)	A flag to indicate whether this configuration is changeable after the application has been installed and initially configured (Y) or whether it is not expected to be changed once the application has been used (N).	N
UPDATEABLE_FLG	VARCHAR2(1)	A flag to indicate whether this configuration value can be updated by the application code (Y) or not (N).	Y
DESCR	VARCHAR2(2000)	A description for the configuration.	Y

Notes:

This table contains configuration values for configurations that can have different configuration values, depending on another value. For example, if a configuration is needed for a default error tolerance, but department 1 needs 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.

The APPL_CODE and PARAM_NAME values in this table are expected to also exist in the RSE_CONFIG table. Normally, there should be a PARAM_VALUE in the RSE_CONFIG table, which is used as the default value for this configuration. Only if there is a PARAM_CODE that matches the specified PARAM_CODE when the configuration is queried, will the PARAM_VALUE be retrieved from this table. Otherwise, the PARAM_VALUE will be retrieved from the RSE_CONFIG table.

Some configuration values are not expected to change once the application has completed its configuration stage and has started to run. These types of values are identifiable via the CONFIGURABLE_FLG. Values with a Y can be changed at any time, while values with a N cannot be changed without risk of breaking existing data in the application.

The UPDATEABLE_FLG identifies whether the application is allowed to adjust the PARAM_VALUE as part of the application processes. Some parameters may need to record a record that signifies when something was done, or maybe what the value was processed by a process, but no suitable table exists to hold this type of processing value. So it should be expected that parameters with an UPDATEABLE_FLG=Y can change during the course of the application processes.

RSE_CONSEG

This table contains consumer segments and interfaces directly with Retail Analytics.

Table B-59 RSE_CONSEG

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table	N
NAME	VARCHAR2(30)	A short name for the consumer segment.	N
DESCR	VARCHAR2(255)	A more descriptive name for the consumer segment.	Y
CONSEG_EXT_KEY	VARCHAR2(80)	The external key to use when interfacing with external systems.	N
CONSEG_EXT_CODE	VARCHAR2(80)	The externally visible code that can be shown in any UI components to identify the consumer segment.	Y
CONSEG_EXT_ID	NUMBER(20)	The PK for the consumer segment as found in the external system.	N
CURRENT_FLG	VARCHAR2(1)	A flag to indicate whether this row is the most recent row (Y) for a given consumer segment, or if it a historical row (N).	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether the row is considered deleted (Y) or not (N).	Y
EFF_FROM_DT	DATE	The starting date on which this record is effective on.	Y
EFF_TO_DT	DATE	The ending date that this record is effective until.	Y

RSE_DISPLAY_FORMAT_STG

This is the staging table used to load display format rules used throughout the UI.

Table B-60 RSE_DISPLAY_FORMAT_STG

Column Name	Data Type	Comments	Nullable?
APPL_CODE	VARCHAR2(3)	Application code That this display format belongs to.	Y
DESCR	VARCHAR2(255)	Description of this display format.	Y
EXT_KEY	VARCHAR2(80)	An external identifier to identify this display format entry. This value should be unique within the specified APPL_CODE.	Y
CURRENCY_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this display format should include formatting specific to currency (Y) or not (N).	Y
PCT_FLG	VARCHAR2(1)	A Y/N flag to indicate whether this display format should include formatting conventions used to display percentages (Y) or not (N).	Y
NUM_DEC_DIGITS	NUMBER(10)	The number of digits to display after the decimal point. Only applicable for numeric fields, NULL for all others.	Y
ROUNDING_MODE	VARCHAR2(30)	This column defines the rounding approach to use when rounding numeric values. Possible values include: UP, DOWN, CEILING, FLOOR, HALF_UP, HALF_DOWN, HALF_EVEN.	Y

RSE_EXCLUSIVE_PROC_TASK_XREF

This table is similar in concept to RSE_EXCLUSIVE_PROC_XREF; however, this table is for tasks instead of for entire processes. The table defines a set of tasks that are exclusive to each other and that should not be running at the same time.

Notes:

This table is not currently in use. It is expected to have references to two instances of the RSE_PROC_TASK_TMPL table in order to indicate that a task cannot be run at the same time another task is running. The pair of PROC_TASK_ID1 and PROC_TASK_ID2 columns are expected to be unique.

RSE_EXCLUSIVE_PROC_XREF

This table is intended to define exclusive processes.

Notes:

This table is not currently in use. It is expected to have references to two instances of the RSE_PROC_TMPL table in order to indicate that a process cannot be run at the same time another process is running. The pair of PROC_ID1 and PROC_ID2 columns are expected to be unique.

RSE_FAKE_CUST_STG

This staging table specifies customers who are considered to be fake customers. A fake customer is a customer who purchases too many transactions to be considered a single customer. Examples are generic store cards.

Table B-61 RSE_FAKE_CUST_STG

Column Name	Data Type	Comments	Nullable?
CUSTOMER_NUM	VARCHAR2(80)	The customer ID to be updated.	Y
FAKE_CUST_FLG	VARCHAR2(1)	A flag to indicate whether the customer should be identified as fake (Y) or not (N).	Y

Notes:

This interface allows a customer to manually define the fake customers. This interface can be used instead of (or in additional to) the automated routine that is provided to automatically detect fake customers. A fake customer is a customer who purchases an unusual number of transactions and therefore cannot be an actual person shopping individually. Fake customers must be removed from processing so that the unusual buying patterns do not interfere with the analysis of customer purchase decisions.

The CUSTOMER_NUM should be related to the W_PARTY_PER_D.CUSTOMER_NUM column.

This interface can overwrite the FAKE_CUST_FLG value for existing rows, while the automated process cannot. Therefore, if a customer is detected as a fake customer by the automated detection routine, this loader can be used to signify that the customer is not fake, and then on subsequent executions of the automated process, the customer will not be identified as a fake customer.

RSE_HIER_LEVEL

This table defines the various levels for all the hierarchies.

Table B-62 RSE_HIER_LEVEL

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(4)	ID for the level. The highest level is 1, and child levels have sequentially increasing values within each Hierarchy Type.	N
HIER_TYPE_ID	NUMBER(10)	FK to the Hierarchy Type.	N
DESCR	VARCHAR2(80)	Description for this level. For hierarchies that are copied from other systems, this value should match the value in the source system.	Y
SRC_HIER_TYPE_ID	NUMBER(10)	For alternate hierarchies, this is a FK for the primary hierarchy that this hierarchy is associated with.	Y
SRC_HIER_LEVEL_ID	NUMBER(4)	For alternate hierarchies, this is the level of the other hierarchy that this level is aligned with. This is the point at which the two hierarchies merge. All levels below this hierarchy are common between the two hierarchies.	Y
LEAF_NODE_FLG	VARCHAR2(1)	A flag to indicate if this is the lowest level of the hierarchy (Y) or not (N).	N

Notes:

For each hierarchy, it is necessary to have a list of the levels that belong to the hierarchy. The levels are fixed for the hierarchy type (HIER_TYPE_ID) and cannot be of variable depth. The highest ID for a given hierarchy type (HIER_TYPE_ID) should be the leaf level (LEAF_NODE_FLG=Y).

The HIER_TYPE_ID should be defined in the RSE_HIER_TYPE table. Within a given HIER_TYPE_ID, the IDs should range from 1 (for the highest level of the hierarchy), to the lowest level of the hierarchy, which should have the highest ID value. No gaps are allowed in the levels within a hierarchy type.

For non-primary hierarchies, it is possible to define a hierarchy that converges with the primary hierarchy. The point at which this happens should be updated so that the SRC_HIER_LEVEL_ID and SRC_HIER_TYPE_ID contain the appropriate level and hierarchy type where the data aligns with the primary hierarchy.

RSE_HIER_TYPE

This table hosts the catalog of hierarchies that are available within the application. It identifies the business objects for which the hierarchy applies. It also identifies the primary hierarchy for that object.

Table B-63 RSE_HIER_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(255)	The name of the hierarchy.	Y
DESCR	VARCHAR2(255)	A description for this hierarchy.	Y
LEAF_NODE_LEVEL	VARCHAR2(80)	The level number of the hierarchy that contains the lowest level of data. This should be the maximum ID in the RSE_HIER_LEVEL table for this hierarchy type.	Y
PRIMARY_FLG	VARCHAR2(1)	A flag to indicate whether this is the primary hierarchy (Y) for a given business object or not (N).	Y
BUSINESS_OBJECT_MD_ID	NUMBER	FK to the RSE_BUSINESS_OBJECT_MD that defines the business object this hierarchy can be used with.	N

Notes:

The purpose of this table is to define all the different hierarchies that are available throughout the system. For a given business object (BUSINESS_OBJECT_MD_ID), only one hierarchy should be considered the primary hierarchy (PRIMARY_FLG=Y). All others should not be primary (PRIMARY_FLG=N). The highest number of the RSE_HIER_LEVEL that relates to this hierarchy type should be defined in the LEAF_NODE_LEVEL column.

RSE_LIKE_LOC_STG

This is the staging table used to load the like stores for CM Group or Category.

Table B-64 RSE_LIKE_LOC_CFG

Column Name	Data Type	Comments	Nullable?
LOC_EXT_KEY	VARCHAR2(80)	External ID for the store location.	Y
LIKE_LOC_EXT_KEY	VARCHAR2(80)	External ID for the like store location.	Y
PROD_HIER_TYPE_NAME	VARCHAR2(255)	The name of the product hierarchy type associated with this store.	Y
PROD_EXT_KEY	VARCHAR2(80)	The external key to identify the product hierarchy this like store relates to.	Y
WEIGHT	NUMBER(9,4)	Weight of the like store associated with the store.	Y
EFFECTIVE_START_DT	DATE	The date of the start of the effective period.	Y
EFFECTIVE_END_DT	DATE	The date of the end of the effective period.	Y
ACTIVE	VARCHAR2(1)	This is a Y/N flag to indicate whether this like store mapping is valid or not.	Y
NEW_FLG	VARCHAR2(1)	This is a Y/N flag to indicate whether this store is new or existing store [poor history].	Y

RSE_LOAD_SRVC_CFG

This table defines a data loader that is available for execution through the data loading framework.

Table B-65 RSE_LOAD_SRVC_CFG

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this loader.	N
NAME	VARCHAR2(50)	The name of the data loader as referenced by external invocations of the loader.	N
DESCR	VARCHAR2(250)	Descriptive text that describes this data loader.	N
IMPL_NAME	VARCHAR2(30)	The name of the implementation that performs this data loading.	N
CREATED_ON_DT	DATE	The date this data loader was created.	Y
CHANGE_ON_DT	DATE	The date this record was last changed.	Y

Notes:

This table contains a list of database loader services, along with the name of the code that provides the implementation for this data loading. If necessary, the IMPL_NAMEs can be extended so that additional data loading rules are implemented. Then the name of the database type in IMPL_NAME can be changed to that name. All of the data types mentioned in IMPL_NAME must be descendants of the RSE_LOAD_SRVC_T database type.

The NAME value is a fixed value that other parts of the application reference these data loaders by and therefore is not changeable. These names should be unique.

RSE_LOAD_VALDT_RULES_CFG

This table defines the validation rules that a data loader performs, along with some configurable options that affect rows that fail this validation.

Table B-66 RSE_LOAD_VALDT_RULES_CFG

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this validation rule.	N
NAME	VARCHAR2(50)	The validation name used in the data loader to reference this validation rule.	N
LOAD_SRVC_CFG_ID	NUMBER(10)	FK for the data loader service configuration that uses this validation rule.	N
LOAD_VALDT_TYPE	VARCHAR2(1)	FK for the validation type (RSE_LOAD_VALDT_TYPE).	N
DESCR	VARCHAR2(250)	A descriptive message that appears when rows do not pass the validation rule.	N
MAX_PCT_ERRORS	NUMBER(3)	An integer representation of the percentage of rows that can fail this validation rule before the data loader aborts processing the remaining the good rows.	Y
MAX_NUM_ERRORS	NUMBER(10)	The maximum number of rows that can fail this validation rule before the data loader aborts the loading of the remaining good rows.	Y
CREATED_ON_DT	DATE	Date this validation rule was created.	Y
CHANGE_ON_DT	DATE	Date this validation rule was last changed.	Y

Notes:

This table defines validation rules that are associated with a data loading database service type. The LOAD_SRVC_CFG_ID should align with a row in the RSE_LOAD_SRVC_CFG table. The NAME column in this table is a fixed name that the application code uses to look up the validation rule, so these names cannot be changed. This NAME column must be unique.

The MAX_PCT_ERRORS and MAX_NUM_ERRORS are used to specify a threshold for ignoring failed validation rules. If the number of records that fail the validation rules are below the threshold, then the bad records are not included in the data loading process. Otherwise, the data loader will abort its data loading, and the bad records can be found in the appropriate *_BAD table.

RSE_LOAD_VALDT_TYPE

This table defines the different validation types available in a data loader.

Table B-67 RSE_LOAD_VALDT_TYPE

Column Name	Data Type	Comments	Nullable?
LOAD_VALDT_TYPE	VARCHAR2(1)	PK for this table (R=Record, C=Complex record, T=Table).	N
DESCR	VARCHAR2(50)	A description for this validation type.	N

Notes:

This table defines the list of data loading validation types, available for use by the data loading validations. This table helps provide better reporting of validation errors.

The LOAD_VALDT_TYPE column is referenced via the application code, so the values cannot be changed without impacting the application code.

RSE_POST_PROC_TMPL

This table is used to define a template for post-processing tasks for a given process task. This table is not currently in use.

Notes:

This table is not currently in use, although future releases will use this to define post-processing steps that should be invoked after a process has completed. When the process finishes with a particular status, this table enables different post-processing routines to be executed. As a result, it is possible to invoke a routine to signify to an external entity that a process has completed successfully or that the process failed.

RSE_PROC_TASK_PREREQ_TMPL

This table defines prerequisites between process tasks. This table is not currently in use.

Notes:

This table is not currently in use by the system and is reserved for future use. It can be used to define prerequisite rules for tasks in order to make sure that tasks can be run in a asynchronous manner, with rules to prevent the tasks from running before a prior task has completed.

RSE_PROC_TASK_TMPL

This table defines templates for processing tasks that are used by the applications.

Table B-68 RSE_PROC_TASK_TMPL

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
PROC_ID	NUMBER(10)	FK to the RSE_PROC_TMPL table.	N
NAME	VARCHAR2(80)	A name for this task.	N
DESCR	VARCHAR2(255)	A descriptive name for this processing task.	Y
STEP_NUM	NUMBER(4)	A sequential step number for this task, relative to its peer tasks.	Y
PARENT_ID	NUMBER(10)	FK to a parent task in this same table.	Y
EXEC_PROD_ID	NUMBER(10)	Not currently used.	Y
SRVC_TYPE_ID	NUMBER(10)	Not currently used.	Y
SRVC_NAME	VARCHAR2(30)	Not currently used.	Y
PKG	VARCHAR2(255)	The name of the package that contains the code to be executed.	Y
PROC	VARCHAR(255)	The name of the procedure that is executed for this task.	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether this record is to be considered deleted (T) or not (F).	Y
ACTIVE_FLG	VARCHAR2(1)	A flag to indicate whether this task should be considered active (T) or not (F).	Y
MAX_RUN_TIME_MIN	NUMBER(8)	Not currently used.	Y
MAX_FAILURES	NUMBER(8)	Not currently used.	Y
RESTARTABLE_FLG	VARCHAR2(1)	Not currently used.	Y

Notes:

This table defines a template of the processing tasks for a batch process. There can be a mixture actual processing tasks, and also of entries whose whole purpose is just to create a hierarchy of tasks. By having a hierarchy of tasks, it allows for concurrent operations to be performed at various points through the work flow, while at the same time, allowing dependencies to be completed before continuing with other tasks.

The ID in this table is a fixed ID and is used to associate with configuration entries in other parts of the application. The STEP_NUM indicates the sequence in which tasks run, within the specified PARENT_ID. The STEP_NUM should be unique within a given PROC_ID, PARENT_ID.

The PKG column contains a value which associates with other application code to signify what code or type of code is to be run for this step.

RSE_PROC_TMPL

This table defines processing templates for asynchronous or synchronous invocable from Java applications.

Table B-69 RSE_PROC_TMPL

Column Name	Data Type	Comments	Nullable?
PROC_ID	NUMBER(10)	PK for this table	N
APPL_ID	VARCHAR2(8)	Application identifier for this process.	Y
NAME	VARCHAR2(80)	Name of the process, as referenced by application code.	Y
DESCR	VARCHAR2(255)	Descriptive text for this process.	Y
ASYNC_FLG	VARCHAR2(1)	A flag to indicate whether this process is asynchronous (T) or synchronous (F).	Y
THREAD_LIMIT	NUMBER(4)	Not currently used.	Y
THREAD_GRP	VARCHAR2(8)	Not currently used.	Y
EXCLUSIVE_GRP	VARCHAR2(8)	Not currently used.	Y
ACTIVE_FLG	VARCHAR2(1)	A flag to indicate whether this process is active for use (T) or not (F).	Y
DELETE_FLG	VARCHAR2(1)	A flag to indicate whether this process is considered deleted (T) or not (F).	Y
MAX_RUN_TIME_MIN	NUMBER(8)	Not currently used.	Y
MAX_FAILURES	NUMBER(8)	Not currently used.	Y
RESTARTABLE_FLG	VARCHAR2(1)	Not currently used.	Y

Notes:

This table defines the templates of processes that can be invoked from the applications.

The application ID is a short identifier to indicate which application owns the task. Currently available values are CIS, CDT, DT, MBA, and ASO.

The NAME column is the name that the application uses for lookup in order to find a run-able process thread. This column must be unique within each application.

The IDs in this table are also predefined and cannot be changed. The application may do lookups for tasks either by PROC_ID or by NAME.

RSE_PROD_ATTR_GRP_VALUE_STG

This is the staging table used to load the associations of CM Groups to product attributes.

Table B-70 RSE_PROD_ATTR_GRP_VALUE_STG

Column Name	Data Type	Comments	Nullable?
PROD_HIER_TYPE_NAME	VARCHAR2(255)	The name of the product hierarchy type associated with this Attribute Group value.	Y
PROD_EXT_KEY	VARCHAR2(80)	The external key to identify the product hierarchy this product attribute group value relates to.	Y
ATTR_SHORT_DB_NAME	VARCHAR2(30)	The short name for the attribute which this product attribute group is related to.	Y
PROD_ATTR_GRP_EXT_KEY	VARCHAR2(80)	The external key to uniquely identify the product attribute group.	Y
PROD_ATTR_GRP_NAME	VARCHAR2(255)	The name for the product attribute group.	Y
PROD_ATTR_GRP_DESCR	VARCHAR2(255)	The description for the product attribute group.	Y
PROD_ATTR_VALUE_KEY	VARCHAR2(255)	The external key to uniquely identify the product attribute group value.	Y
PROD_ATTR_VALUE_NAME	VARCHAR2(255)	The name for the product attribute group value.	Y
PROD_ATTR_VALUE_DESCR	VARCHAR2(255)	The description for the product attribute group value	Y
FUNC_ATTR_FLG	VARCHAR2(1)	This is a Y/N flag to indicate whether this attribute is considered to be an attribute associated with a specific function or role (Y) or not (N).	Y

Notes:

This table defines the set of attributes and attribute values for those attributes.

The only NULLABLE columns for this interface are the PROD_ATTR_GRP_DESCR and PROD_ATTR_VALUE_DESCR columns.

The data should be joinable to RSE_PROD_SRC_XREF via the PROD_EXT_KEY, where the LEAF_FLG = Y. The PROD_HIER_TYPE_NAME should be joinable to the RSE_HIER_TYPE table on the Name column.

The values in the PROD_ATTR_GRP_EXT_KEY must be uniquely assigned to a PROD_EXT_KEY.

RSE_PROD_ATTR_VALUE_XREF_STG

This table contains the cross reference of product attribute values to the CM Group Attribute Value Groups.

Table B-71 RSE_PROD_ATTR_VALUE_XREF_STG

Column Name	Data Type	Comments	Nullable?
PROD_ATTR_VALUE_KEY	VARCHAR2(255)	External key to identify the product attribute group value this xref is for.	Y
MIN_ATTR_NUM_VALUE	NUMBER(22,5)	Minimum number value for this xref. Inclusive of this value.	Y
MAX_ATTR_NUM_VALUE	NUMBER(22,5)	Maximum number value for this xref. This value is not inclusive in this xref.	Y
ATTR_STRING_VALUE	VARCHAR2(255)	An attribute string value to associate with this attribute group value.	Y
MIN_ATTR_DATE_VALUE	DATE	Minimum date value to associate with this attribute group value. This value is inclusive.	Y
MAX_ATTR_DATE_VALUE	DATE	Maximum attribute value to include for this attribute group value. This value is not inclusive in this range.	Y
ATTR_VALUE_EXT_CODE	VARCHAR2(255)	An external attribute code to associate with this attribute group value.	Y

Notes:

This table must be joinable to the RSE_PROD_ATTR_GRP_VALUE_STG table.

This interface must be unique across all columns of this table.

The PROD_ATTR_VALUE_KEY must be joinable to data that is provided by the related RSE_PROD_ATTR_GRP_VALUE_STG table.

The MIN_ATTR_NUM_VALUE/MAX_ATTR_NUM_VALUE columns must be provided as a set, when one is provided.

The MIN_ATTR_DATE_VALUE/MAX_ATTR_DATE_VALUE columns must be provided as a set, when one is provided.

Every PROD_ATTR_VALUE_KEY that is provided by the RSE_PROD_ATTR_GRP_VALUE_STG should have some rows provided in this interface so that attribute values can be found and associated with this attribute value.

The ATTE_VALUE_EXT_CODE is expected to be joined with RA's W_RTL_ITEM_GRP1_D.

One set of value columns should be provided per row (that is, MIN_ATTR_NUM_VALUE and MAX_ATTR_NUM_VALUE but not at the same time as specifying a value for ATTR_STRING_VALUE).

RSE_SLS_PR_LC_CS_WK_STG

This is the staging table to load aggregate sales data for a product, location, customer segment, and week.

Table B-72 RSE_SLS_PR_LC_CS_WK_STG

Column Name	Data Type	Comments	Nullable?
WK_END_DT	DATE	The date of the end of the fiscal week.	Y
PROD_EXT_KEY	VARCHAR2(80)	External ID for the Product.	Y
LOC_EXT_KEY	VARCHAR2(80)	External ID for the store location.	Y
CUSTSEG_EXT_KEY	VARCHAR2(80)	External ID for the customer segment.	Y
SLS_QTY	NUMBER(38,20)	Quantity of units sold for this entity while not on promotion.	Y
SLS_AMT	NUMBER(38,20)	Global sales amount sold for this entity while not on promotion.	Y
PROFIT_AMT	NUMBER(38,20)	Amount of profit for this entity while not on promotion.	Y
SLS_PR_QTY	NUMBER(38,20)	The number of units sold that was associated with a promotion.	Y
SLS_PR_AMT	NUMBER(38,20)	The global sales currency amount that was associated with a promotion.	Y
SLS_PR_PROFIT_AMT	NUMBER(38,20)	Amount of global current profit amount for this entity that was associated with a promotion.	Y

Notes:

The data should be unique for the WK_END_DT, PROD_EXT_KEY, LOC_EXT_KEY, and CUSTSEG_EXT_KEY columns.

The WK_END_DT should be related to historical date that is within the fiscal calendar hierarchy. This interface expects the data to be provided in a weekly aggregate form, according to the definition of the week in the fiscal calendar hierarchy.

The PROD_EXT_KEY should be related to a LEAF_NODE_FLG=Y row in the RSE_PROD_SRC_XREF for the primary product hierarchy.

The LOC_EXT_KEY should be related to a LEAF_NODE_FLG=Y row in the RSE_LOC_SRC_XREF table for the primary location hierarchy.

The CUSTSEG_EXT_KEY should be related to a LEAF_NODE_FLG=Y row in the RSE_CUSTSEG_SRC_XREF table.

The SLS_QTY, SLS_AMT, and PROFIT_AMT columns should represent the sales of the product during the week period that are not attributed to a promotion.

The SLS_PR_QTY, SLS_PR_AMT, and SLS_PR_PROFIT_AMT columns should represent the sales of the product during the week period that are attributed to a promotion.

RSE_SLS_PR_LC_WK_STG

This is the staging table to load aggregate sales data for a product, location, and week.

Table B-73 RSE_SLS_PR_LC_WK_STG

Column Name	Data Type	Comments	Nullable?
WK_END_DT	DATE	The date of the end of the fiscal week	Y
PROD_EXT_KEY	VARCHAR2(80)	External ID for the Product.	Y
LOC_EXT_KEY	VARCHAR2(80)	External ID for the store location.	Y
SLS_QTY	NUMBER(38,20)	Quantity of units sold for this entity while not on promotion.	Y
SLS_AMT	NUMBER(38,20)	Global sales amount sold for this entity while not on promotion.	Y
PROFIT_AMT	NUMBER(38,20)	Amount of profit for this entity while not on promotion.	Y
SLS_PR_QTY	NUMBER(38,20)	The number of units sold that was associated with a promotion.	Y
SLS_PR_AMT	NUMBER(38,20)	The global sales currency amount that was associated with a promotion.	Y
SLS_PR_PROFIT_AMT	NUMBER(38,20)	Amount of global current profit amount for this entity that was associated with a promotion.	Y

Notes:

The data should be unique for the WK_END_DT, PROD_EXT_KEY, and LOC_EXT_KEY columns.

The WK_END_DT should be related to historical date that is within the fiscal calendar hierarchy. This interface expects the data to be provided in a weekly aggregate form, according to the definition of the week in the fiscal calendar hierarchy.

The PROD_EXT_KEY should be related to a LEAF_NODE_FLG=Y row in the RSE_PROD_SRC_XREF for the primary product hierarchy.

The LOC_EXT_KEY should be related to a LEAF_NODE_FLG=Y row in the RSE_LOC_SRC_XREF table for the primary location hierarchy.

The SLS_QTY, SLS_AMT, and PROFIT_AMT columns should represent the sales of the product during the week period that are not attributed to a promotion.

The SLS_PR_QTY, SLS_PR_AMT, and SLS_PR_PROFIT_AMT columns should represent the sales of the product during the week period that are attributed to a promotion.

RSE_SRVC_CONFIG

This table defines all the database service routines available to be invoked through the database service framework in the application.

Table B-74 RSE_SRVC_CONFIG

Column Name	Data Type	Comments	Nullable?
SRVC_ID	NUMBER(10)	PK for the database service.	N
SRVC_TYPE_ID	NUMBER(10)	FK to the service type for this service.	N
SRVC_NAME	VARCHAR2(30)	The name used to lookup this database service.	N
DESCR	VARCHAR2(255)	Description of what this database service does.	Y
SRVC_IMPL_NAME	VARCHAR2(30)	The name of the database object that implements this database service. This must be a descendant of RSE_SRVC_T.	Y
SRVC_OWNER	VARCHAR2(30)	The database schema that owns the implementation of this service.	Y
CREATED_ON_DT	DATE	Date this record was created.	Y
CHANGE_ON_DT	DATE	Date this record was last changed.	Y

Notes:

This table enables the overriding of implementations for any of the database services used by the application. The application code looks for services by the Service Type (RSE_SRVC_TYPE.SRVC_TYPE) and the Service Name (SRVC_NAME). If it is necessary to customize an implementation of any service in this table, it is possible to do so by creating new database types that extend the provided database types, and then it is possible to extend or override the existing implementation. Once a new database type is required, the SRVC_IMPL_NAME can be adjusted to refer to the new database type that performs the same functional results.

All database types defined in this table must extend the RSE_SRVC_T database type and should implement and extend this type as needed.

This table has a FK relationship with the RSE_SRVC_TYPE table (SRVC_TYPE_ID). This table should be unique across the SRVC_TYPE_ID and the SRVC_NAME.

It is also expected that the SRVC_OWNER be a single schema. Future releases will explore the ability of offering accessing code from other schemas.

RSE_SRVC_TYPE

This table defines the types of database services that a database service can belong to. In order for multiple database services to share the same service type, they should be interchangeable at run time.

Table B-75 RSE_SRVC_TYPE

Column Name	Data Type	Comments	Nullable?
SRVC_TYPE_ID	NUMBER(10)	PK for the service type.	N
SRVC_TYPE	VARCHAR2(30)	The name that is used to look up the database service type and its related services.	N
CREATED_ON_DT	DATE	Date this record was created.	Y
CHANGE_ON_DT	DATE	Date this record was change.	Y

Notes:

This table defines the types of database services that a database service can belong to. In order for multiple database services to share the same service type, they should be interchangeable at run time.

This table groups related database services together so that they can be batched together and processed in parallel with each other. For example, this might be helpful if there are four different aggregation routines that all process data in a similar manner and all have the same basic setup of parameters. By creating them all under the same service type, it is possible to queue the execution of all four routines, and the process can then process them all together by the same service request group. In a situation like this, the service request group would likely be the week to be processed, and by running them all in one pass, it enables them to all run the same week at the same time. This can be helpful on database resources, as the database can cache a single week of data and then process all steps using that week at the same time. The alternative approach is be to process each aggregation routine individually, one week at a time. But if this is done, then by the time the next aggregation routine is executed, the weeks data is probably no longer cached and must be read again.

The one limitation that exists with grouping services under the same service type is that the pre-processing and post-processing service request group routines must all be the same between all service implementations. This is normally only the case when the service routines all inherit from a common base service or if the service implementations do not actually have pre-service and post-service request group tasks.

SO_ALERT

This table hosts the list of possible alerts that can be raised by the application.

Table B-76 SO_ALERT

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the alert. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	The alert name. This value should not be used for display within the UI. It has a back end use.	Y
DESCR	VARCHAR2(200)	A short alert description.	Y
SEVERITY_ID	NUMBER(10)	Foreign key to so_alert_severity table. This field identifies the severity of the event (such as blocking or informative).	N
TYPE_ID	NUMBER(10)	Foreign key to so_alert_type table. This value identifies the type of event/exception that raised the alert (such as constraint or space).	N
ALERT_MSG	VARCHAR2(200)	Message that provides more information to the user about the problem. Sanity checker uses this value to provide the user with an action to be taken to fix an identified problem.	Y

Notes:

This is a lookup table that provides alerts supported by the application. It is referenced by other tables.The application can raise these alerts to flag the occurrence of specific events. These alerts are used to notify the user about specific situations, such as space issues and constraint problems.

SO_ALERT_SEVERITY

This table contains the list of alert severities supported by the application.

Table B-77 SO_ALERT_SEVERITY

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the alert severity. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Alert severity name. This value should not be used for display within the UI. It has a back end use.	Y
DESCR	VARCHAR2(200)	Alert severity description.	Y

Notes:

This is a lookup table that provides alert severities supported by the application. It is referenced by other tables. Values include informative, warning, and blocking.

SO_ALERT_STATUS

This table contains the list of alert status that are supported by the application.

Table B-78 SO_ALERT_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the alert status. This value is static. The list of recognized values is provided by the application.	N
Name	VARCHAR2(80)	Alert status name. This value should not be used for display within the UI. It has a back end use.	Y
DESCR	VARCHAR2(200)	Alert status description.	Y

Notes:

This is a lookup table that provides alert status supported by the application.It is referenced by other tables.Values include new, ignored, displayed, and accepted.

SO_ALERT_TYPE

This table contains the list of alert types supported by the application.

Table B-79 SO_ALERT_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the alert type. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Alert type name. This value should not be used for display within the UI. It has a back end use.	Y
DESCR	VARCHAR2(200)	Alert type description.	Y

Notes:

This is a lookup table that provides the list of alert types supported by the application. It is referenced by other tables.Values include constraints, blocking, optimization, mapping, assortment, loading, and export.

SO_ASSORT_CLUSTER_MEMBER_STG

This staging table is used for stores assigned to a specific cluster for the given assortment.

Table B-80 SO_ASSORT_CLUSTER_MEMBER_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identifies the assortment. It must match an assortment key within the assortment file.	Y
LOCATION_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
CLUSTER_KEY	VARCHAR2(80)	Internal Cat-Man cluster key. This key must match one of the cluster keys provided within the assortment cluster file.	Y
START_DT	DATE	Start date range to be used for the store to retrieve forecast data. The format must be YYYY-MM-DD.	Y
END_DT	DATE	End date range to be used for the store to retrieve forecast data. The format must be YYYY-MM-DD.	Y

Notes:

This data is mandatory.These are the stores delivered within the assortment interface, grouped within clusters. ASO expects to always receive stores grouped within clusters. If stores must be sent individually, a cluster must be created for than single store. Product list is linked directly to a store whenever the assortment type = 2 (Store). The start and end date are only included in this table for assortments delivered at the store level.

SO_ASSORT_CLUSTER_STG

This is the staging table for assortment placeholder products included within the assortment.

Table B-81 SO_ASSORT_CLUSTER_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identifies the assortment. It must match an assortment key within the assortment file.	Y
CLUSTER_KEY	VARCHAR2(80)	Cat-Man cluster key. A value that can be returned from SO to Cat-Man to uniquely identify the cluster_id.	Y
CLUSTER_NAME	VARCHAR2(80)	Name associated to the cluster. The end user should recognize this name as the cluster name seen or entered within Cat-Man	Y
START_DT	DATE	Start date range to be used for the stores within the cluster to retrieve forecast data. The format must be YYYY-MM-DD	Y
END_DT	DATE	End date range to be used for the stores within the cluster to retrieve forecast data. The format must be YYYY-MM-DD	Y

Notes:

This data is mandatory.These clusters are delivered within the assortment interface. ASO expects to always receive stores grouped within clusters. If the stores need to be sent individually, a cluster must be created for that single store. Product list is linked directly to a cluster whenever the assortment type = 1 (Cluster). Start and end dates are only included for assortments delivered at the cluster level.

SO_ASSORT_PHPROD_ATTR_STG

This is the staging table for attribute data for assortment placeholder products.

Table B-82 SO_ASSORT_PHPROD_ATTR_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identified the assortment. It must match an assortment key within the assortment file.	Y
PLACEHOLDER_PRODUCT_KEY	VARCHAR2(80)	Cat-Man product key for placeholder product specific to the assortment. It must be different from other formalized products.	Y
ATTR_NAME	VARCHAR2(50)	Name of the product attribute that is being passed. It must match a known product attribute.	Y
ATTR_VALUE	VARCHAR2(50)	Specific value that should be used for the placeholder product/attribute combination.	Y

Notes:

This data is optional.This table includes only placeholder product attributes. Attribute names must match existing attributes already available within ASO and shared with the other products.

SO_ASSORT_PHPROD_FINALIZED_STG

This is the staging table that receives finalized assortment placeholder products included within the assortment. This data is used to transform the placeholder name and ID.

Table B-83 SO_ASSORT_PHPROD_FINALIZED_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_SET_ID	VARCHAR2(80)	Unique assortment set ID. This value is used to group together multiple assortments (user requests).	N
PLACEHOLDER_PRODUCT_KEY	VARCHAR2(80)	Category Management product key for placeholder product specific to the assortment. Must be different from other formalized products.	N
FINALIZED_PRODUCT_NAME	VARCHAR2(80)	Tag that describes the finalized placeholder item.	Y
FINALIZED_PRODUCT_KEY	VARCHAR2(80)	This field must match a Product Key Definition in RSE Core. This is the external ID that is known and shared across applications. The like product key must be one of the known products also included within the assortment.	Y

SO_ASSORT_PHPROD_LIKE_PROD_STG

If a placeholder product is included in the assortment, it must appear in this feed.The following is a list of placeholder products included in the assortment. Each placeholder item must be paired with an existing product. ASO uses the next pieces of data from the existing product (like item).

• MSM-type data such as size or other product merchandising information.

• Merchandise hierarchy information (where this product sits in the hierarchy)

• Product attributes (such as what is used for DT calls)

• ASO-only data (sku/store replenishment parameters used in ASO and other SO inputs)

Product Key for placeholder items must always be different than the one for any known product.

Table B-84 SO_ASSORT_PHPROD_LIKE_PROD_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identified the assortment. It must match an assortment key within the assortment file.	Y
PLACEHOLDER_PRODUCT_KEY	VARCHAR2(80)	Category Management product key for placeholder product specific to the assortment. It must be different than other formalized products.	Y
PLACEHOLDER_PRODUCT_NAME	VARCHAR2(80)	Tag that describes the placeholder item. It is used by the UI to look at product level data.	Y
LIKE_PRODUCT_KEY	VARCHAR2(80)	This field must match a Product Key Definition in RSE Core. This is the external ID that is known and shared across applications. The like product key must be one of the known products also included within the assortment.	Y

Notes:

This data is optional if placeholder products are included.

SO_ASSORT_PRODUCT_STRCLTR_STG

This feed also includes placeholder products.

Table B-85 SO_ASSORT_PRODUCT_STRCLTR_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identifies the assortment. It must match an assortment key within the assortment file.	Y
CLUSTER_STORE_KEY	VARCHAR2(80)	This field can be either an assortment cluster key or a location key. The actual value is determined by the assortment type (If Assortment_type = 1 (ClusterAssortment key) and If Assortment_type = 2 (Store Assortment key)). The external store ID must be the one known and shared across applications	Y
PRODUCT_KEY	VARCHAR2(80)	This is the external product ID that is known and shared across applications. For placeholder products, this field contains the Category Management placeholder product key that must be different than any known product.	Y
IPI_VALUE	NUMBER(18,4)	This value can be NULL if not available.	Y
PRIORITY	NUMBER(2)	This field can take four different values, 1 = mandatory, 2 = core, 3 = optional, and -1=dropped. Records with -1 may be filtered out.	Y

Notes:

This data is mandatory.Placeholder products must also be included within this table. An assortment can be delivered either at the store or cluster level, but not both at the same time. The product key for placeholder products must always be different than the one used for any known product.

SO_ASSORT_PROLOC_FCST_STG

This feed also includes placeholder products.

Table B-86 SO_ASSORT_PROLOC_FCST_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identifies the assortment. It must match an assortment key within the assortment file.	Y
PRODUCT_KEY	VARCHAR2(80)	This is the external ID that is known and shared across applications. For placeholder products this field contains a Category Management placeholder product key.	Y
LOCATION_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
WEEKLY_PERIOD	DATE	Week start date for which the forecast is provided.	Y
DEMAND	NUMBER(18,4)	Forecast demand for the week.	Y
ERROR_TERM	NUMBER(18,4)	Not currently in use. Default to NULL.	Y

Notes:

This data is mandatory.This table receives forecast data for all the products within the assortment, including placeholder products. The forecast must cover the range of dates specified for the cluster or stores.

SO_ASSORT_PROLOC_PRICECOST_STG

This feed also includes placeholder products.

Table B-87 SO_ASSORT_PROLOC_PRICECOST_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_ID	VARCHAR2(80)	ID that identifies the assortment. It must match an assortment key within the assortment file.	Y
PRODUCT_KEY	VARCHAR2(80)	This is the external ID that is known and shared across applications. For placeholder products this field contains a Category Management placeholder product key.	Y
LOCATION_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
PRICE	NUMBER(18,4)	Product price, single currency unit determined at the configuration level. No multi-currency is allowed.	Y
COST	NUMBER(18,4)	Product cost, single currency unit determined at the configuration level. No multi-currency is allowed	Y

Notes:

This data is mandatory.The data on this table must be delivered at the product/location level. This table must include the corresponding price and cost for placeholder products (if any is included within the assortment).

SO_ASSORTMENT_FINALIZED_STG

This table contains the details about the assortment location types supported by the application.

Table B-88 SO_ASSORTMENT_FINALIZED_STG

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_SET_ID	VARCHAR2(80)	Unique assortment set ID. This value is used to group together multiple assortments (user requests)	N
PRODUCT_CATEGORY_KEY	VARCHAR2(80)	This value has to match a node in merchandise hierarchy. This is the external ID that is known and shared across applications.	Y
ASSORT_LABEL	VARCHAR2(80)	This is a user-entered field with a default value. This value is presented within the UI as the familiar label/name recognizable by the user. It can be NULL.	Y
TRADE_AREA_LABEL	VARCHAR2(80)	Category Management trading area used to extract the assortment.	Y
ASSORT_ROLE	VARCHAR2(50)	This is a Category Management data element that should be passed to ASO. ASO shows this value within BI modules. This is relevant for users when they pick the optimization objective function.	Y
ASSORT_TACTIC	VARCHAR2(100)	This is a Category Management data element that should be passed to ASO. ASO shows this value within BI modules. This is relevant for user when they pick the optimization objective function.	Y
ASSORT_GOAL	VARCHAR2(50)	This is a Cat-Man data element that should be passed to SO. SO shows this value within BI modules. This is relevant for the users when they pick the optimization objective function.	Y

SO_ASSORTMENT_LOC_TYPE

This table contains the details about the assortment location types supported by the application.

Table B-89 SO_ASSORTMENT_LOC_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the assortment location type. This value is static. The list of recognized assortment location types is provided by the application. 1-Cluster Assortment and 2-Store assortment.	N
DESCR	VARCHAR2(80)	Assortment location type description.	Y

Notes:

The application supports the delivery of assortment in two different ways, the cluster level or the store level.

SO_ASSORTMENT_REQ_TYPE

This table contains the list of possible assortment request types that can be supported by the application.

Table B-90 SO_ASSORTMENT_REQ_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the assortment request type. This value is static. The list of recognized assortment request types is provided by the application.	N
DESCR	VARCHAR2(80)	Assortment request type description.	Y

Notes:

This is a lookup table that provides assortment request types that can be supported by the application. It is referenced by other tables. Values include Optimization Request, Finalized Assortment Reporting, and Promotional Assortment.

SO_ASSORTMENT_STATUS

This table contains the list of possible status for the assortments (for example, Received, Mapped, Optimized, Processed, Accepted, Discarded, POG mapping needs review, Ready for SO, and User Re-mapping).

Table B-91 SO_ASSORTMENT_STATUS

Column Name	Data Type	Comments	Nullable?
ASSORTMENT_STATUS	VARCHAR2(10)	Unique identifier for the assortment status. This value is static. The list of recognized status is provided by the application.	N
DESCR	VARCHAR2(80)	Assortment status description.	Y
UI_DESCR	VARCHAR2(80)	Assortment status description to be used within the UI.	Y

Notes:

This is a lookup table that provides assortment status. It is referenced by other tables.

SO_ASSORTMENT_STG

This interface table contains assortment header and general information.

Table B-92 SO_ASSORTMENT_STG

Column Name	Data Type	Comments	Nullable?
ID	VARCHAR2(80)	System-generated Primary Key that is the internal assortment identifier.	Y
PRODUCT_CATEGORY_KEY	VARCHAR2(80)	This value must match a node in merchandise hierarchy. This is the external ID that is known and shared across applications.	Y
ASSORT_LABEL	VARCHAR2(80)	This is a user-entered field with a default value. This value is presented within the UI as the familiar label/name recognizable by the user. It can be NULL.	Y
TRADE_AREA_LABEL	VARCHAR2(80)	Category Management trading area used to extract the assortment.	Y
REQUEST_TYPE	NUMBER(2)	This field can accept two values: 1=Optimization Request and 2=Finalized Assortment Reporting.	Y
ASSORT_LOC_TYPE	NUMBER(2)	This field can accept two values: 1= Cluster Assortment and 2=Store Assortment. This field indicates the level at which the assortment is delivered.	Y
ASSORT_ROLE	VARCHAR2(50)	This is a Category Management data element that should be passed to ASO. ASO shows this value within BI modules. This is relevant for users when they pick the optimization objective function.	Y
ASSORT_TACTIC	VARCHAR2(100)	This is a Category Management data element that should be passed to ASO. ASO shows this value within BI modules. This is relevant for users when they pick the optimization objective function.	Y
ASSORT_GOAL	VARCHAR2(50)	This is a Category Management data element that should be passed to ASO. ASO shows this value within BI modules. This is relevant for users when they pick the optimization objective function.	Y
ASSORTMENT_SET_ID	VARCHAR2(80)	Unique assortment set ID. This value is used to group together multiple assortments (user requests).	Y

Notes:

This data is mandatory.

This staging table is used to receive assortment data from external sources. Each assortment provided must have a unique assortment_id.

SO_BAY_FIXTURE_SHELF_STG

This table describes the shelf layout in a Fixture. It is used for Shelf Fixture only.

Table B-93 SO_BAY_FIXTURE_SHELF_STG

Column Name	Data Type	Comments	Nullable?
BAY_KEY	VARCHAR2(80)	Bay external ID. Bay is a direct dependent of the planogram.	Y
FIXTURE_KEY	VARCHAR2(80)	Fixture external ID. Fixture is a direct dependent of the Bay.	Y
SHELF_KEY	VARCHAR2(80)	Shelf external ID. Shelf is a direct dependent of shelf fixture.	Y
POS_X	NUMBER(18,4)	Position of the shelf on the X axis. Origin point: bottom, left, back (within the fixture).	Y
POS_Y	NUMBER(18,4)	Position of the shelf on the Y axis. Origin point: bottom, left, back (within the fixture).	Y
POS_Z	NUMBER(18,4)	Position of the shelf on the Z axis. Origin point: bottom, left, back (within the fixture).	Y

Notes:

This table has the information about the specific shelves that are included within a given shelf fixture. This table is only populated for planograms that include shelf fixtures; data is not available within this table for pegboard or freezer chest fixtures.

SO_BAY_FIXTURE_STG

This table receives the fixture layout within a Bay. The fixture can be Shelf, Pegboard, or Freezer.

Table B-94 SO_BAY_FIXTURE_STG

Column Name	Data Type	Comments	Nullable?
BAY_KEY	VARCHAR2(80)	Bay external ID. Bay is a direct dependent of the planogram.	Y
FIXTURE_KEY	VARCHAR2(80)	Fixture external ID. Fixture is a direct dependent of the bay.	Y
POS_X	NUMBER(18,4)	Position of the fixture on the X axis. Origin point: bottom, left, back (within the bay).	Y
POS_Y	NUMBER(18,4)	Position of the fixture on the Y axis. Origin point: bottom, left, back (within the bay).	Y
POS_Z	NUMBER(18,4)	Position of the fixture on the Z axis. Origin point: bottom, left, back (within the bay).	Y

Notes:

This table contains the information about the different fixtures that are assigned to every planogram bay. There can be multiple fixtures within a bay; each fixture within a bay keeps the same layout from left to right.

SO_BI_CHART_TYPE

This table contains the list of possible BI chart types that are supported by the application.

Table B-95 SO_BI_CHART_TYPE

Column Name	Data Type	Comments	Nullable?
CHART_TYPE	VARCHAR2(15)	Unique identifier for the BI chart type. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(30)	BI chart type description.	N

Notes:

This is a lookup table that provides BI chart types that can be supported by the application. It is referenced by other tables. Values include histogram, chart, and pie.

SO_BI_ELEMENT

This table contains configuration metadata for business intelligence elements.

Table B-96 SO_BI_ELEMENT

Column Name	Data Type	Comments	Nullable?
BI_ELEMENT	VARCHAR2(30)	Unique identifier for the BI element. This value is static. The list of recognized values is provided by the application. This ID is directly referenced by the UI.	N
DESCR	VARCHAR2(50)	BI element description. This value is frequently used by the UI as a label.	N
UI_MODULE	VARCHAR2(30)	Foreign key from so_ui_module. This value identifies the BI module that makes use of the element.	N
DEFAULT_FLG	VARCHAR2(1)	Y/N Indicator that is used to identify the element within a section that should be used by the UI as a default value.	N
BI_SECTION	VARCHAR2(15)	Foreign key from so_bi_section. This value identified the BI section that uses this element.	N
DISPLAY_SEQ	NUMBER(4)	There could be multiple BI elements within the same BI section; the values might be used within UI list of values. This field indicates the sequence in which the value should be presented to the user.	N

Notes:

This is a lookup and metadata table that tracks the different business intelligence elements that require some metadata from the database. It is referenced by other tables and use by the UI to build BI sections.

SO_BI_ELEMENT_CHART

This table that contains the metadata to configure BI element charts.

Table B-97 SO_BI_ELEMENT_CHART

Column Name	Data Type	Comments	Nullable?
BI_ELEMENT	VARCHAR2(30)	Foreign key to so_bi_element.	N
CHART_TYPE	VARCHAR2(15)	Foreign key to so_bi_chart_type table	N
DEFAULT_FLG	VARCHAR2(1)	Y/N indicator if the chart should be used as a default by the UI	N
COUNT_OR_PCT	VARCHAR2(10)	Metadata value that identies if the series of data used correspond to a count or a percentage.	N
BINNING_FLG	VARCHAR2(1)	Y/N indicator if binning should be used to draw the chart,	N
MULTIPLE_SERIES_FLG	VARCHAR2(1)	Y/N indicator if multiple series of data should be used to draw the chart.	N
DFLT_BINS	NUMBER(3)	This value is only relevant for charts that allow binning. This is the default number of bins that should be used by the chart.	Y
MIN_BINS	NUMBER(3)	This value is only relevant for charts that allow binning. This is the minimum number of bins that should be used by the chart.	Y
MAX_BINS	NUMBER(3)	This value is only relevant for charts that allow binning. This is the maximum number of bins that should be used by the chart.	Y

Notes:

This is a lookup and metadata table that provides informations about the distinct options and parameters that should be used by the UI to draw charts. This object is used by development to configure BI modules.

SO_BI_SECTION

This table contains the list of possible BI sections that are configured within the UI to use metadata and configuration values from the database.

Table B-98 SO_BI_SECTION

Column Name	Data Type	Comments	Nullable?
BI_SECTION	VARCHAR2(15)	Unique identifier for the BI Section. This value is static. The list of recognized values is provided by the application. The ID is used by the UI to link BI elements and objects to specific sections of the UI.	N
DESCR	VARCHAR2(30)	BI section description.	N

Notes:

This is a lookup table that provides BI section information that can be supported by the application. It is referenced by other tables. The values in this table usually reference a section within the distinct UI trains stops.

SO_DISPLAY_STYLE_FIXTURE_STG

This is the compatibility table between display styles and fixture types.

Table B-99 SO_DISPLAY_STYLE_FIXTURE_STG

Column Name	Data Type	Comments	Nullable?
DISPLAY_STYLE_KEY	VARCHAR2(80)	Position of the fixture on the Z axis. Origin point: bottom, left, back (within the bay).	Y
FIXTURE_TYPE	VARCHAR2(80)	Fixture type that supports the display style (Shelf, Pegboard, or Freezer chest).	Y

Notes:

This is a compatibility table that defines which display styles can be used for the distinct fixture types.

SO_DISP_STYLE_ORIENTATION_STG

This table provides a cross reference between display style and product valid orientations.

Table B-100 SO_DISP_STYLE_ORIENTATION_STG

Column Name	Data Type	Comments	Nullable?
DISPLAY_STYLE_KEY	VARCHAR2(80)	External display style ID.	Y
ORIENTATION_KEY	VARCHAR2(80)	External orientation ID.	Y
DEFAULT_FLG	VARCHAR2(30)	Y indicates the orientation should be consider as the default for the display style. N indicates the orientation is valid for the display style but not a default.	Y

Notes:

This table contains the list of valid orientations for a given display style. The table includes a default orientation that should be used for each display style.

SO_DISPLAY_STYLE_STG

This table contains the list of available display styles for products.

Table B-101 SO_DISPLAY_STYLE_STG

Column Name	Data Type	Comments	Nullable?
KEY	VARCHAR2(80)	External ID that identified the display style.	Y
NAME	VARCHAR2(80)	Display style name.	Y
DESCR	VARCHAR2(80)	Display style description.	Y
DEPTH	NUMBER(18,4)	Product depth relevant to default front-0 position.	Y
HEIGHT	NUMBER(18,4)	Product height relevant to default front-0 position.	Y
WIDTH	NUMBER(18,4)	Product width relevant to default front-0 position.	Y
FINGER_SPACE_ABOVE	NUMBER(18,4)	Product gap above between same product.	Y
FINGER_SPACE_BELOW	NUMBER(18,4)	Product gap beside between same product.	Y
FINGER_SPACE_BEHIND	NUMBER(18,4)	Product gap behind between same product.	Y
INTER_PRODUCT_GAP	NUMBER(18,4)	Gap between products. This field captures gap beside between different products.	Y
MAX_STACK	NUMBER(10)	Number of items that can be stacked together; equal to 1 if not stackable.	Y
NESTING_HEIGHT	NUMBER(18,4)	Product nesting height. The product does not allow nesting if all nesting dimensions are 0.	Y
NESTING_WIDTH	NUMBER(18,4)	Product nesting width. The product does not allow nesting if all nesting dimensions are 0.	Y
NESTING_DEPTH	NUMBER(18,4)	Product nesting depth. The product does not allow nesting if all nesting dimensions are 0.	Y
COLOR	VARCHAR2(30)	Product color. It can be NULL.	Y
DISPLAY_UNITS	NUMBER(3)	For unit display style it is 1; otherwise, it is >1.	Y
TYPE	VARCHAR2(80)	Display style type. CASE, UNIT, TRAY or other display style type.	Y

Notes:

A display style defines the product physical dimensions as well as the different options that can be used to place the product within a planogram.

SO_DISPLAY_STYLE_TYPE

This table gives the discrete unit of display for a given product that are set up in MSM. Examples of display style types are: single/unit, tray, case, and pallet.

Table B-102 SO_DISPLAY_STYLE_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the display style type. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(80)	Display style type description.	Y

Notes:

This is a lookup table that provides display style types that can be supported by the application. It is referenced by other tables. This table gives the discrete unit of display for a given product that are set up in MSM. Examples of display style types are: single/unit, tray, case, and pallet.

SO_FIXTURE_DISP_CONFIG_STG

This table receives the historical planogram product data for shelf fixtures.

Table B-103 SO_FIXTURE_DISP_CONFIG_STG

Column Name	Data Type	Comments	Nullable?
DISPLAY_STYLE_KEY	VARCHAR2(80)	External ID that identifies a display style associated to a single product.	Y
BAY_KEY	VARCHAR2(80)	Bay external ID. Bay is a direct dependent of the planogram.	Y
FIXTURE_KEY	VARCHAR2(80)	Fixture external ID. Fixture is a direct dependent of the Bay.	Y
SHELF_KEY	VARCHAR2(80)	Shelf external ID. Shelf is a direct dependent of shelf fixture.	Y
ORIENTATION_KEY	VARCHAR2(80)	External ID that identifies orientation used.	Y
POS_X	NUMBER(18,4)	Position of the product on the X axis. Origin point: bottom, left, back.	Y
POS_Y	NUMBER(18,4)	Position of the product on the Y axis. Origin point: bottom, left, back.	Y
POS_Z	NUMBER(18,4)	Position of the product on the Y axis. Origin point: bottom, left, back.	Y
FACING_QUANTITY	NUMBER(5)	Number of facings of the product.	Y

Notes:

This table contains the list of products and distribution of them across historical planograms. It includes the position and orientation of the products within the planogram as well as the number of facings per products. This data is used to estimate facing lift.

SO_FIXTURE_STG

This table contains the list of fixtures within a historical planogram.

Table B-104 SO_FIXTURE_STG

Column Name	Data Type	Comments	Nullable?
KEY	VARCHAR2(80)	External fixture identifier.	Y
FIXTURE_TYPE	VARCHAR2(80)	Fixture type values can one of the following: Shelf, Pegboard or Freezer Chest.	Y
DEPTH	NUMBER(18,4)	Fixture depth.	Y
HEIGHT	NUMBER(18,4)	Fixture height.	Y
WIDTH	NUMBER(18,4)	Fixture width.	Y
VERTICAL_SPACING	NUMBER(18,4)	Vertical spacing. This value is only relevant for pegboard fixtures.	Y
HORIZONTAL_SPACING	NUMBER(18,4)	Horizontal spacing. This value is only relevant for pegboard fixtures.	Y
MAX_LENGTH	NUMBER(18,4)	Max length. This value is only relevant for pegboard fixtures.	Y
CAPACITY_X	NUMBER(18,4)	Freezer Chest Capacity X (length). This value is only relevant for freezer chest fixtures.	Y
CAPACITY_Y	NUMBER(18,4)	Freezer Chest Capacity Y (depth). This value is only relevant for freezer chest fixtures.	Y
CAPACITY_Z	NUMBER(18,4)	Freezer Chest Capacity Z (height). This value is only relevant for freezer chest fixtures.	Y

Notes:

This table contains the list of fixtures that define the historical planogram layout. Fixtures are planogram components within a Bay; each bay can include one or more fixtures.

SO_FIXTURE_TYPE

This table defines what kind of fixtures are allowed in a POG: shelf, pegboard, or freezer chest.

Table B-105 SO_FIXTURE_TYPE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the fixture type. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(80)	Fixture type description.	Y

Notes:

This is a lookup table that provides fixture types supported by the application. It is referenced by other tables. The supported fixture types are: Shelf, Pegboard and Freezer Chest.

SO_FRONT_FACING

This table contains the list of possible products sides that can be used as front facings supported by the application.

Table B-106 SO_FRONT_FACING

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the front facing side. This value is static. The list of recognized values is provided by the application.	Y
DESCR	VARCHAR2(80)	Front facing description.	Y

Notes:

This is a lookup table that provides the list of product sides that can be used as the front facings supported by the application. It is referenced by other tables.Front facing values can be: front, back, top, bottom, left, and right.

SO_GLOBAL_VALDT_STG

This table is an auxiliary table that is used within the global validation process. This table is used to meet the loader framework that requires a staging table. The loaders framework is used by the global validation process to perform validations (only).

Table B-107 SO_GLOBAL_VALDT_STG

Column Name	Data Type	Comments	Nullable?
VALDT_TBL_NAME	VARCHAR2(30)	Auxiliary column to host a table name	Y

SO_INT_TRANSFORMATION_KEY

This table is 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.

Table B-108 SO_INT_TRANSFORMATION_KEY

Column Name	Data Type	Comments	Nullable?
SO_INTERFACE	VARCHAR2(30)	This string identifies the interface that makes use of the values. That is, ASO-MSM (indicates the interface that sends data from ASO to MSM).	N
SO_DATA_ELEMENT	VARCHAR2(30)	This is the reference/name of the ASO column that is used on the numeric or text ASO value fields.	N
SO_NUM_DATA_VALUE	NUMBER(18)	This field is used if the ASO value is numeric. If the value is not numeric, this field will be set to -1.	N
SO_TEXT_DATA_VALUE	VARCHAR2(80)	This field will be used if the ASO value is text. The field will be set to X (instead of NULL) if the SO value is numeric.	N
INT_NUM_DATA_VALUE	NUMBER(18)	This field will be used if the interface value is transformed to a numeric value.	Y
INT_TEXT_DATA_VALUE	VARCHAR2(80)	This field will be used if the interface value is transformed to a text value.	Y

SO_LOC_OPTIMIZATION_LEVEL

This table contains the distinct list of possible location optimization levels.

Table B-109 SO_LOC_OPTIMIZATION_LEVEL

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for location optimization level. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Location optimization level name. This value should not be used for display within the UI; it is used by the backend.	Y
DESCR	VARCHAR2(200)	Location Optimization level description.	Y

Notes:

This is a lookup table that provides location optimization levels that can be supported by the application. It is referenced by other tables. Values include Cluster and Store.This is the level at which the optimization is performed. In some cases it is acceptable to perform optimization at a higher level (cluster). This reduces processing time in exchange for using data aggregated at the cluster level.

SO_ORIENTATION

This table describes how a products package faces the front of the fixture. The orientation has two pieces of information: what part of the package is to the front (front, back, top, bottom, left, right) and how it is rotated in degrees (0, 90, 180, 270), for a total of 24 possible orientations. How a product is oriented determines how much space it takes in the x,y,z directions on a fixture. Legal orientations are all orientations that can be used for the product.The default orientation is the legal orientation that is normally used for the product.

Table B-110 SO_ORIENTATION

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run strategy. This value is static. The list of recognized values is provided by the application. Each one of this orientation IDs is already identified and recognized to correspond to a specific front facing and rotation. The ID values should not be changed.	N
ORIENTATION_EXT_KEY	VARCHAR2(80)	Orientation external ID.	Y
ROTATION_DEGREES	NUMBER(3)	Rotation in degrees used in the specific rotation. Valid values are 0, 90, 180, and 270.	Y
FRONT_FACING_ID	NUMBER(10)	This is a foreign key to so_front_facing table. It indicates the product side that should be used as a front facing.	N

Notes:

This is a lookup table that provides orientations that can be supported by the application. It is referenced by other tables. It describes how a product's package faces the front of the fixture.The orientation has two pieces of information: the part of the package that goes to the front (front, back, top, bottom, left, right) and how it is rotated in degrees (0, 90, 180, 270), for a total of 24 possible orientations. How a product is oriented determines how much space it takes in the x,y,z directions on a fixture. Legal orientations are all orientations that can be used for the product.The default orientation is the legal orientation that is normally used for the product.

SO_ORIENTATION_STG

This table contains the list of available orientations that can be used within planograms.

Table B-111 SO_ORIENTATION_STG

Column Name	Data Type	Comments	Nullable?
KEY	VARCHAR2(80)	External identifier for the orientation.	Y
FRONT_FACING	VARCHAR2(80)	The front facing can be: front, back, top, bottom, left, right.	Y
ROTATION_DEGREE	NUMBER(3)	The rotation degree can be 0, 90, 180, 270.	Y

Notes:

This table describes how a product package faces the front of the fixture. It has a total of 24 possible orientations.

SO_PEGBOARD_DISP_CONFIG_STG

This table contains the historical planogram product data for pegboard and freezer chest fixtures.

Table B-112 SO_PEGBOARD_DISP_CONFIG_STG

Column Name	Data Type	Comments	Nullable?
DISPLAY_STYLE_KEY	VARCHAR2(80)	External ID that identifies a display style associated to a single product.	Y
BAY_KEY	VARCHAR2(80)	Bay external ID. Bay is a direct dependent of the planogram.	Y
FIXTURE_KEY	VARCHAR2(80)	Fixture external ID. Fixture is a direct dependent of the Bay.	Y
ORIENTATION_KEY	VARCHAR2(80)	External ID that identifies orientation used.	Y
POS_X	NUMBER(18,4)	Position of the product on the X axis. Origin point: bottom, left, back.	Y
POS_Y	NUMBER(18,4)	Position of the product on the Y axis. Origin point: bottom, left, back.	Y
POS_Z	NUMBER(18,4)	Position of the product on the Z axis. Origin point: bottom, left, back.	Y
FACING_QUANTITY	NUMBER(5)	Number of facings of the product.	Y

Notes:

This table contains the list of products and distribution of them across historical planograms. It includes the position and orientation of the products within the planogram as well as the number of facings per products This data is used to estimate facing lift.

SO_POG_ASSORT_MAPPING_STG

This staging table contains the cross reference data to perform POG to assortment mapping.

Table B-113 SO_POG_ASSORT_MAPPING_STG

Column Name	Data Type	Comments	Nullable?
POG_DEPT_KEY	VARCHAR2(80)	This is the POG dept key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
POG_CATEGORY_KEY	VARCHAR2(80)	This is the POG category key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
POG_SUB_CATEGORY_KEY	VARCHAR2(80)	This is the POG subcategory key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
ASSORT_PRODUCT_LEVEL	VARCHAR2(80)	This is an identifier to the product level within the product hierarchy. This value must match the product hierarchy available within SO.	Y
ASSORT_PRODUCT_KEY	VARCHAR2(80)	This is an identifier to a node within the merchandise hierarchy. It could be a specific product or any other node not higher than the assortment product category level within the merchandise hierarchy.	Y
DEMAND_SPREAD_FACTOR	NUMBER(6,3)	This is the demand spread factor. This value is normally null, meaning a 100% demand is assigned to the POG node. In specific cases where the product is placed on multiple POG nodes, a demand spread factor can be used to split the demand across those multiple POGs.	Y

Notes:

This table contains the POG hierarchy to assortment product mapping information. This data is used to identify that POG should be used for each product within an assortment.

SO_POG_ASSORT_SEAS_MAPPING_STG

This staging table contains the cross reference data for the assortment-to-POG season mapping.

Table B-114 SO_POG_ASSORT_SEAS_MAPPING_STG

Column Name	Data Type	Comments	Nullable?
POG_DEPT_KEY	VARCHAR2(80)	This is the POG dept key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
POG_CATEGORY_KEY	VARCHAR2(80)	This is the POG category key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
POB_SUB_CATEGORY_KEY	VARCHAR2(80)	This is the POG subcategory key. This is a POG hierarchy external key known to the external source. It is a mandatory value.	Y
SEASONAL_ATTRIBUTE	VARCHAR2(30)	This field refers to a specific year independent time period (season) for a Category Management assortment and a POG set. Examples include Spring, holiday, back to school, year-round, Fall, and Winter.	Y
MIN_ASSORT_START_DB	DATE	The year component is irrelevant; it should be 0000. This is a year independent time period. The assortment start date is matched within the date range specified by the min assort start date and the max assort start date.	Y
MAX_ASSORT_START_DT	DATE	The year component is irrelevant; it should be 0000. This is a year independent time period. The assortment start date is matched within the date range specified by the min assort start date and the max assort start date.	Y

Notes:

Once the mapping from product to POG has been performed, a second pass examines the data to identify the specific POG season to use, based on the assortment start date.

SO_POG_BAY_STG

This table contains the list of bays that are used to build a planogram.

Table B-115 SO_POG_BAY_STG

Column Name	Data Type	Comments	Nullable?
BAY_KEY	VARCHAR2(80)	Bay external ID. Bay is a direct dependent of the planogram.	Y
POG_KEY	VARCHAR2(80)	External planogram identifier.	Y
BAY_SEQUENCE	NUMBER(3)	Sequence from left to right in which the bay appear within the planogram.	Y

Notes:

A bay is the level under the planogram that is used to position fixtures to build the final planogram layout. The bay is directly linked to a unique planogram; fixtures are then linked to the bay.

SO_POG_DISPLAY_STYLE_STG

This table is the cross reference between historical planograms and product display styles.

Table B-116 SO_POG_DISPLAY_STYLE_STG

Column Name	Data Type	Comments	Nullable?
POG_KEY	VARCHAR2(80)	External planogram identifier.	Y
DISPLAY_STYLE_KEY	VARCHAR2(80)	External display style identifier. This identifier links a historical planogram with a specific product.	Y

Notes:

This table contains the list of products (based on the display style) that use this historical planogram.

SO_POG_FIXT_CONFIG_ALGORITHM

This table keeps the list of available algorithms to perform the shelf fixture smart start process (create shelves for empty fixtures).

Table B-117 SO_POG_FIXT_CONFIG_ALGORITHM

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Parameter unique identifier.	N
NAME	VARCHAR2(80)	Parameter name.	N
DESCR	VARCHAR2(200)	Parameter description.	Y
DEFAULT_FLG	VARCHAR2(1)	This flag is set to 'Y' for the default algorithm. The default algorithm is used during the optimization location generation before the user has the opportunity to pick or change parameters.	N
ENABLED_FLG	VARCHAR2(1)	This flag is used to indicate if the algorithm is available or active.	N

SO_POG_FIXTCONF_ALG_PARAM

This table is used to store the list of different algorithm parameters the user can customize while running the fixture smart start process.

Table B-118 SO_POG_FIXTCONF_ALG_PARAM

Column Name	Data Type	Comments	Nullable?
ID	VARCHAR2(20)	Parameter unique identifier.	N
POG_FIXT_CONFIG_ALGORITHM_ID	NUMBER(10)	Foreign key linking the parameter to a specific algorithm.	N
NAME	VARCHAR2(80)	Parameter name.	N
DESCR	VARCHAR2(200)	Parameter description.	Y
DFLT_VALUE	NUMBER(18,4)	Default parameter value that the UI suggests to the user.	N
MIN_VALUE	NUMBER(18,4)	Minimum acceptable parameter value. This value is used to validate the user entries.	N
MAX_VALUE	NUMBER(18,4)	Maximum acceptable parameter value. This value is used to validate the user entries.	N
PARAM_SEQ	NUMBER(18,4)	Sequence in which the parameter should be presented or retrieved to the user within the UI.	N

SO_POG_FIXTURE_TYPE

This entity is used to identify distinct POG types (Partial Shelf Fixture Planogram (PSFP) or Complete Planogram (CFP)).

Table B-119 SO_POG_FIXTURE_TYPE

Column Name	Data Type	Comments	Nullable?
POG_FIXTURE_TYPE	VARCHAR2(10)	Two types: Partial Shelf Fixture Planogram (PSFP) or Complete Fixture Planogram (CFP)	N
DESCR	VARCHAR2(80)	Fixture type description.	Y
UI_DESCR	VARCHAR2(80)	Fixture type description, customized for display by the UI.	Y

SO_POG_SOURCE

This table tracks the different POG sources (for example, MSM, Promotional POG from external source, and Internal POG from ASO).

Table B-120 SO_POG_SOURCE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the planogram source. This value is static. The list of recognized values is provided by the application. More sources can be added to this table; each must have a unique identifier.	N
DESCR	VARCHAR2(80)	Planogram source description.	Y

SO_POG_STATUS

Table that contains the list of possible planogram status that can be supported by the application.

Table B-121 SO_POG_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the planogram status. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(80)	Planogram status description. Values include approved, rejected, pending, and received.	Y
POG_SET_FLG	VARCHAR2(1)	Indicates is the status applies to the POG set instead of the POG.	N

Notes:

This is a lookup table that provides planogram status supported by the application. it is referenced by other tables.

SO_POG_STG

This table contains planogram level details for the planogram header data.

Table B-122 SO_POG_STG

Column Name	Data Type	Comments	Nullable?
KEY	VARCHAR2(80)	External planogram identifier.	Y
NAME	VARCHAR2(80)	Planogram name.	Y
DESCR	VARCHAR2(80)	planogram description.	Y
SEASON_CODE	VARCHAR2(30)	Seasonal code used by the historical planogram.	Y
SEASONAL_ATTRIBUTE	VARCHAR2(30)	Seasonal attribute used for the historical planogram.	Y
EFFECTIVE_START_DT	DATE	Planogram start date.	Y
EFFECTIVE_END_DT	DATE	Planogram end date.	Y
STATUS	VARCHAR2(30)	Identifier that describes the planogram status.	Y
CATEGORY_KEY	VARCHAR2(80)	POG category key. The second lowest level of POG category hierarchy.	Y
CATEGORY_NAME	VARCHAR2(80)	POG category name.	Y
SUB_CATEGORY_KEY	VARCHAR2(80)	POG sub-category key. The lowest level of POG category hierarchy.	Y
SUB_CATEGORY_NAME	VARCHAR2(80)	POG sub-category name.	Y
DEPT_KEY	VARCHAR2(80)	POG department key.	Y
DEPT_NAME	VARCHAR2(80)	POG department name.	Y
LENGTH	NUMBER(18,4)	The total length of a planogram. It must be equal to the sum of the length for all the bays within the planogram.	Y
DEPTH	NUMBER(18,4)	The total depth of a planogram. It must be equal to the greatest depth within all the fixtures in the planogram.	Y
HEIGHT	NUMBER(18,4)	The total height of a planogram. It must be equal to the highest fixture within the planogram.	Y

Notes:

The data in this table is used internally to generate the distinct POG set. The content of this table is transformed into planograms and POG sets. The rows within this table correspond to historical planograms. The layouts are received from external sources.

SO_POG_STORE_STG

This table contains the list of stores that used the historical planogram.

Table B-123 SO_POG_STORE_STG

Column Name	Data Type	Comments	Nullable?
POG_KEY	VARCHAR2(80)	External planogram identifier.	Y
STORE_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
EFFECTIVE_START_DT	DATE	Start date for which the historical planogram is valid for the given store.	Y
EFFECTIVE_END_DT	DATE	End date for which the historical planogram is valid for the given store.	Y

Notes:

This table provides a cross reference between historical planograms and stores for which the planogram is valid (depending on dates).

SO_POG_STORE_CDA_STG

This is a staging table to load customer defined attributes for POG/store combinations. These attributes are static values that are used as informational attributes within the UI.

Table B-124 SO_POG_STORE_CDA_STG

Column Name	Data Type	Comments	Nullable?
POG_KEY	VARCHAR2(80)	External planogram identifier	Y
STORE_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
ATTR_NUM_VALUE_1	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_2	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_3	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_4	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_5	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_6	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_7	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_8	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_9	NUMBER(18,4)	Generic numeric value	Y
ATTR_NUM_VALUE_10	NUMBER(18,4)	Generic numeric value	Y
ATTR_DATE_VALUE_1	DATE	Generic date value	Y
ATTR_DATE_VALUE_2	DATE	Generic date value	Y
ATTR_DATE_VALUE_3	DATE	Generic date value	Y
ATTR_DATE_VALUE_4	DATE	Generic date value	Y
ATTR_DATE_VALUE_5	DATE	Generic date value	Y
ATTR_STRING_VALUE_1	VARCHAR2(80)	Generic string value	Y
ATTR_STRING_VALUE_2	VARCHAR2(80)	Generic string value	Y
ATTR_STRING_VALUE_3	VARCHAR2(80)	Generic string value	Y
ATTR_STRING_VALUE_4	VARCHAR2(80)	Generic string value	Y
ATTR_STRING_VALUE_5	VARCHAR2(80)	Generic string value	Y
ATTR_PCT_VALUE_1	NUMBER(5,4)	Generic percentage value	Y
ATTR_PCT_VALUE_2	NUMBER(5,4)	Generic percentage value	Y
ATTR_PCT_VALUE_3	NUMBER(5,4)	Generic percentage value	Y
ATTR_PCT_VALUE_4	NUMBER(5,4)	Generic percentage value	Y
ATTR_PCT_VALUE_5	NUMBER(5,4)	Generic percentage value	Y

SO_POGSET_ASSORT_ASSIGN_TYPE

This table contains the distinct mapping types that can be used between assortments and planograms.

Table B-125 SO_POGSET_ASSORT_ASSIGN_TYPE

Column Name	Data Type	Comments	Nullable?
POGSET_ASSORT_ASSIGN_TYPE	VARCHAR2(10)	Unique identifier for the mapping assignation type. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(200)	Mapping assignation type description.	Y

Notes:

This table contains assortment to planogram assignation types. It is referenced by other tables. Values include automatic, escalation, manual, current, and unassigned.

SO_PROD_CONSTR_RANGE_VALUES

This table contains the list of product constraint values supported by the application.

Table B-126 SO_PROD_CONSTR_RANGE_VALUES

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the constraint value. This value is static. The list of recognized values is provided by the application.	N
PRODUCT_CONSTRAINT_TYPE	VARCHAR2(10)	Foreign key from so_product_constraint_type table. It identifies the product constraint for which the value can be used.	N
VALUE	VARCHAR2(30)	The actual value to be presented by the UI.	Y
MIN_FLG	VARCHAR2(1)	Y indicates it can be used as minimum value.	Y
MAX_FLG	VARCHAR2(1)	Y indicates it can be used as maximum value.	Y
UNIT_FLG	VARCHAR2(1)	Y indicates it can be used as a Units option.	Y
UI_DFLT_FLG	VARCHAR2(1)	Y indicates this is the default UI value.	Y
DB_DFLT_FLG	VARCHAR2(1)	Y indicates this is the default value to be used by the DB processes.	Y
VALUE_ORDER	NUMBER(10)	This field is used to sort the data in the appropriate way for displaying, since strings and numbers are mixed in the same table.	N

Notes:

This table contains the range and a list of values that are supported by the application. It is referenced by other tables and is used to populate a constraint list of values and options presented to the user to configure run product constraints.

SO_PROD_DISPLAY_STYLE_STG

This table contains display style cross references.

Table B-127 SO_PROD_DISPLAY_STYLE_STG

Column Name	Data Type	Comments	Nullable?
PRODUCT_KEY	VARCHAR2(80)	This is the external ID that is known and shared across applications. This cannot be a placeholder product.	Y
DISPLAY_STYLE_KEY	VARCHAR2(80)	External ID that identifies the display style.	Y
DEFAULT_FLG	VARCHAR2(1)	Y indicates the default display style for a given product. N indicates the combination should not be considered as a default. Each product should have one default display style.	Y

Notes:

This table contains product to display style mapping. It provides a list of display styles available to choose for certain product.

SO_PROD_LOC_REPL_PARAM_STG

This table contains the replenishment data corresponding to product/store combinations.

Table B-128 SO_PROD_LOC_REPL_PARAM_STG

Column Name	Data Type	Comments	Nullable?
PRODUCT_KEY	VARCHAR2(1)	This is the external ID that is known and shared across applications. For placeholder products, this field contain the Category Management placeholder product key.	Y
LOCATION_KEY	VARCHAR2(80)	This is the external store ID, known and shared across applications.	Y
CASEPACK	VARCHAR2(80)	Product casepack for the given store.	Y
REPLENISHMENT_FREQ	NUMBER(18,4)	Replenishment frequency (RF) = number of replenishments to the shelf per week.	Y
REPLENISHMENT_TYPE	NUMBER(18,4)	Replenishment source/type has two options: 1 = from DC/vendor and 2 = from back room.	Y
TRANSIT_TIME	NUMBER(10,2)	Transit time (TT) is the number of days it takes an order to go from the source (DC or back room) to the shelf.	Y
SHELF_REPLENISHMENT_TT	NUMBER(10)	Shelf replenishment trigger type has three options: 1 = cover demand over replenishment period + transit time, 2 = replenishment when inventory gets to a target percent of capacity, and 3 = replenishment when a casepack can fit.	Y
SHELF_REPLENISHMENT_PARAM	NUMBER(18,4)	Shelf replenishment parameter (currently only applies for option 2).	Y
STDEV_BOOSTER	NUMBER(10,6)	Standard deviation booster (number greater than or equal to 0, makes sense to limit to 1).	Y
DAYS_OF_SALES_PER_WK	NUMBER(3,2)	Days of sales per week (number between 1 and 7).	Y
FACINGS_LIFT	NUMBER(5,4)	Facing lift parameter.	Y

Notes:

Replenishment parameters are not directly linked to any assortment. This is generic data; however, these parameters must exist for all the known product/store combinations provided within an assortment.

SO_PROD_STACK_HEIGHT_LIMIT_STG

This table is used to accept an optional client feed that provides product-specific stacking height limits.

Table B-129 SO_PROD_STACK_HEIGHT_LIMIT_STG

Column Name	Data Type	Comments	Nullable?
PRODUCT_KEY	VARCHAR2(80)	This is the external ID that is known and shared across applications.	N
STACK_HEIGHT_LIMIT	NUMBER(18,4)	This is the stacking height limit for the specific product. The value here must be provided using the same units of measure used for all other product dimensions.	N
ENABLED_FLG	VARCHAR2(1)	This flag indicates if the product stacking height limit should be used or not. Y means the value specified here will be used; N means the value will be ignored and the application global value will be used instead for the product.	N

Notes:

Replenishment parameters are not directly linked to any assortment. This is generic data; however, these parameters must exist for all the known product/store combinations provided within an assortment.

SO_PRODUCT_CONSTRAINT_TYPE

This table contains the list of product constraint types supported by the application.

Table B-130 SO_PRODUCT_CONSTRAINT_TYPE

Column Name	Data Type	Comments	Nullable?
PRODUCT_CONSTRAINT_TYPE	VARCHAR2(10)	Unique identifier for the product constraint type. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(50)	Product constraint type name. This value is used by the UI.	Y
PROD_GROUP_FLG	VARCHAR2(1)	A value of Y identifies the rows that are valid Product Group Constraints.	Y

Notes:

This lookup table contains product constraint types supported by the application. It is referenced by other tables.Valid product constraints include IN (Inclusion), CR (Capacity Range), CRU (Capacity Range Units), FR (Facing Range), HR (Height Range). Valid group product constraints include MF (Match facing), SS (Same Shelf), CF (Choose From), AN (All or nothing).

SO_PRODUCT_PRIORITY

This table contains the list of possible product priority values supported.

Table B-131 SO_PRODUCT_PRIORITY

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the product priority. This value is static. The list of recognized product priorities is provided by the application.	N
DESCR	VARCHAR2(80)	Product Priority description.	Y

Notes:

This table contains the assortment status. It is referenced by other tables. Values include 1=Mandatory, 2=Core, 3=Optional, -1=Dropped.

SO_REPL_PARAM_DESCRIPTION

This table keeps the list of replenishment parameters the user can change. These parameters have a defined list of valid values that are kept in this table so they can be used by the UI to present them to the user.

Table B-132 SO_REPL_PARAM_DESCRIPTION

Column Name	Data Type	Comments	Nullable?
ID	VARCHAR2(10)	Unique replenishment parameter identifier.	N
REPL_PARAMETER_NAME	VARCHAR2(30)	Replenishment parameter name. This is the higher level parameter.	N
DESCR	VARCHAR2(80)	This is the description corresponding to the specific value the user can use for the parameter.	Y
UI_DESCR	VARCHAR2(80)	This is a short description to be presented to the user, that is,. labels on a list of values.	Y
VALUE_ORDER	NUMBER95)	This is the order in which the parameter value should be presented by the UI.	Y

SO_RUN_CLUSTER_SRC

This table contains the distinct mapping run cluster sources, including whether the cluster was copied from the assortment, generated by the application, loaded, or manually created.

Table B-133 SO_RUN_CLUSTER_SRC

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run cluster source. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Run cluster source. This value must not be used for display within the UI; it is used by the backend.	Y
DESCR	VARCHAR2(200)	Run cluster source description.	Y

Notes:

This information is not relevant for the end user; it for internal use only.

SO_RUN_OBJECTIVE

This table contains the list of possible run objectives that are supported by the application.

Table B-134 SO_RUN_OBJECTIVE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run objective. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Run objective name. This value must not be used for display within the UI; it is used by the backend.	Y
DESCR	VARCHAR2(200)	Run objective description.	Y

Notes:

This table contains run objectives supported by the application.It is referenced by other tables. Values include Run for Assortment Rationalization, Run for Promo POG Opt, and Refresh AR run.

SO_RUN_OBJECTIVE_FUNC

The user has eight options for the objective function:

• Maximize sales value - un-weighted/weighted by IPI

• Maximize margin value - un-weighted/weighted by IPI

• Maximize sales units - un-weighted/weighted by IPI

• Maximize total sales value/average OH value - un-weighted/weighted by IPI

Table B-135 SO_RUN_OBJECTIVE_FUNC

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run objective function. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Run objective function name. This value must not be used for display within the UI; it is used by the backend.	Y
DESCR	VARCHAR2(200)	Run objective function description.	Y

Notes:

This table contains run objective functions that are supported by the application. It is referenced by other tables.

SO_RUN_PRODUCT_DROP_REASON

This table contains the list of possible reasons for which a product can be dropped from the optimization process.

Table B-136 SO_RUN_PRODUCT_DROP_REASON

Column Name	Data Type	Comments	Nullable?
RUN_PRODUCT_DROP_REASON	VARCHAR2(20)	Unique identifier for the drop product reason. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(50)	Description of the reason that caused the product to be dropped from optimization.	Y

Notes:

Values for the reason include NS (No Solution), SC (Solver Choice), UC (User Constraints), and MO (Manual Override).

SO_RUN_STATUS

This table contains a list of possible run status, including Not Started, Warning, Processing, and OK.

Table B-137 SO_RUN_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run status. This value is static. The list of recognized run statuses is provided by the application.	N
DESCR	VARCHAR2(80)	Run status description.	Y
UI_NAME	VARCHAR2(50)	Name used within the UI to recognize the status.	N
UI_DESCR	VARCHAR2(80)	Status description displayed by the UI.	Y

Notes:

This table contains the values for the run status that are used by the application.It is referenced by other tables. Values include Initialized, Not Started, Build Optimization Locations, Processing, Approved, and Exported.

SO_RUN_STRATEGY

This table contains the distinct list of possible optimization strategies, including No Macro Space changes and Macro Space changes.

Table B-138 SO_RUN_STRATEGY

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run strategy. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Run strategy name. This value must not be used for display within the UI; it is used by the backend.	Y
DESCR	VARCHAR2(200)	Run strategy description.	Y

Notes:

This table contains run optimization strategies that are supported by the application.

SO_SHELF_STG

This table contains the list of shelves within a historical planogram that uses shelf fixtures.

Table B-139 SO_SHELF_STG

Column Name	Data Type	Comments	Nullable?
KEY	VARCHAR2(80)	External shelf identifier.	Y
DEPTH	NUMBER(18,4)	Shelf depth.	Y
HEIGHT	NUMBER(18,4)	Shelf Height. This is the physical shelf height/thickness.	Y
WIDTH	NUMBER(18,4)	Shelf width.	Y

Notes:

This table contains the list of shelves that define a shelf fixture within the historical planogram layout. Shelf are planogram components within a Shelf fixture; each shelf fixture can contain one or more shelves.

SO_TASK

This table contains the list of run tasks.

Table B-140 SO_TASK

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the run task. This value is static. The list of recognized values is provided by the application.	N
NAME	VARCHAR2(80)	Name of the task.	Y
DESCR	VARCHAR2(200)	Run task description.	Y
TASK_SEQUENCE	NUMBER(3)	Sequence in which the task should be executed.	Y
CURRENT_FLG	VARCHAR2(1)	(Y/N) Flag that indicates if the task is current or not. If the task is not current then it should not be used. A task could become current at a later time.	Y
DELETE_FLG	VARCHAR2(1)	(Y/N) Flag that indicates the task has been deleted and should no longer be used.	Y

Notes:

This is a lookup/operations table that keeps a list of tasks that need to be performed for a run. (Not currently in use).

SO_TASK_STATUS

This table contains a list of possible task status, including Not Started, Warning, Processing, completed, and paused.

Table B-141 SO_TASK_STATUS

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	Unique identifier for the task status . This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(80)	Run task status description.	Y

Notes:

This table contains the run task status that can be supported by the application. It is referenced by other tables.

SO_UI_MODULE

This table contains the list of UI modules that make use of the metadata configuration saved within the database.

Table B-142 SO_UI_MODULE

Column Name	Data Type	Comments	Nullable?
UI_MODULE	VARCHAR2(30)	Unique identifier for the UI module. This value is static. The list of recognized values is provided by the application.	N
DESCR	VARCHAR2(50)	UI module description, usually matching the train stop name.	N

Notes:

This is a lookup/metadata table that tracks the different UI modules that require some metadata from the database. It is referenced by other tables. These table contain entries for the different train stops and UI sub-modules.

STAGE

This table defines processing stages for an application workflow.

Table B-143 STAGE

Column Name	Data Type	Comments	Nullable?
ID	NUMBER(10)	PK for this table.	N
NAME	VARCHAR2(80)	The name for this stage.	Y
DESCR	VARCHAR2(255)	More descriptive text for this stage.	Y
SEQ	NUMBER(10)	The sequence in which this stage is executed. The numbers are sequential starting at 1, with no overlap.	Y
SRVC_TYPE	VARCHAR2(30)	The name of the database service type used for any stage processes.	N
SRVC_NAME	VARCHAR2(30)	The name of the database service that runs for this stage of processing.	N
APPL_CODE	VARCHAR2(20)	The application code that uses this set of stages.	Y

Notes:

The ID in this table is a fixed ID and is referenced by application code. The NAME is also referenced by application code. Therefore, they cannot be changed.

The description column (DESCR) can be changed if desired.

The SEQ column denotes the sequence of the stages. The sequence of stages is generally not considered changeable, as the applications expect processes to run in a particular order. However, it is present to allow for the introduction of new stages between the existing stages.

The SRVC_TYPE is a fixed value to distinguish one application's stages from another application's stages. This value is fixed and is referenced by the application code and therefore cannot be changed. It can be a reference to a value in the RSE_SRVC_TYPE table.

The SRVC_NAME is a reference to the RSE_SRVC_CONFIG's NAME values. It enables system-generated code to exist, so that it is possible to dynamically invoke the appropriate database service implementation for a given stage.

The APPL_CODE is a application identifier to indicate which application the stages are used by. This value should be similar to the values used in the RSE_CONFIG's APPL_CODE column.