Import Location Clusters from AI Foundation
Location Clusters can be defined in AI Foundation and can be interfaced to APCS. The APCS template version also supports defining Location Clusters within the application. AI Foundation allows defining clusters at different levels across the product hierarchy but the APCS template version allows interfacing clusters defined at the department level. Location Clusters are defined for a date range and those date ranges can be defined as Assortment Periods in APCS and the same can be exported to AI Foundation to define the Location Clusters. For more details, see Export Assortment Periods for Location Clustering to AI Foundation.
In order to get location clusters from AI Foundation, during implementation, some initial setups need to be done in the AI Foundation platform. For more details, see the Oracle Retail Analytics and Planning Integration Implementation Guide.
The following table shows the interface table column details from AI Foundation in RDX used for the interface and the corresponding mapping of columns in APCS. Only mapped columns are used by the APCS template version. If RAP integration is enabled and if Enable RSE Cluster Integration is set to true, then this interface will run as part of the weekly batch.
Interface Name: RSE_LOC_CLUSTER_EXP
| Table Column | Data Type | Comments | Dimension / Measure / Value Mapping |
|---|---|---|---|
|
RUN_ID |
Number(10) |
The export Run ID as obtained from the RAP_INTF_UTIL. |
|
|
LOC_HIER_LEVEL |
Varchar2(30) |
The location hierarchy level data is for COMPANY, CHAIN, AREA, REGION, DISTRICT, and LOCATION. |
LOCATION |
|
PROD_HIER_LEVEL |
Varchar2(30) |
The product hierarchy level the data is for CMP, DIV, GRP, DEPT, CLS, SBC, STYLE, STYLE_COLOR, and ITEM. |
DEPT |
|
LOC_EXT_KEY |
Varchar2(80) |
The external id of the location. It will use the integration ids as provided to RI (preferably the RMS id, and not an integration id such as AREA~123). |
STOR |
|
PROD_EXT_KEY |
Varchar2(80) |
The external id of the product hierarchy. It will use the integration ids as provided to RI (preferably the RMS id, and not an integration id such as CLS~123~456~789). |
DEPT |
|
EFF_START_DT |
Date |
The starting date which the cluster is effective. |
WEEK, DRDVSRTD |
|
EFF_END_DT |
Date |
The ending date for which the cluster is effective. |
DRDVENDD |
|
CLUSTER_ID |
Number(10) |
The identifier for the cluster. |
DRDVSTRCLUST |
|
CLUSTER_LABEL |
Varchar2(50) |
A descriptive name/label for the cluster. |
DRDVSTRCLUSL |