Mirror of Oracle documentation

Converted for search and offline reading. Authoritative source: Oracle. Diagrams and some complex tables are simplified — check the PDF when in doubt.

Applications deployed in PDS can get the same using RDX. For more details about the RAP Inbound Interfaces, see the Oracle Retail Analytics and Planning Implementation Guide . Any supplemental data that is specific to planning can be directly loaded into PDS as PDS Flat Files. This section shows the details about the interfaces used by PDS in RAP using RDX.

Following is the pre-defined grouping of interfaces available in the APCS template version within RAP integration.

Pre-defined imports from RAP integration to APCS:

  • Import Foundation and Transactional data from Retail Insights (RI)

  • Import Forecasts from AI Foundation (AIF)

  • Import DT Parameters from AI Foundation (AIF)

  • Import Location Clusters from AI Foundation (AIF)

  • Import Customer Segments from AI Foundation (AIF)

  • Import Size Profiles from AI Foundation (AIF)

Pre-defined exports to RAP integration to APCS:

  • Export Assortment Periods for Location Clusters from AI Foundation (AIF)

  • Export Active Assortments to AI Foundation (AIF)

  • Export Assortment Groups to AI Foundation (AIF)

  • Export Assortment Plans to Retail Insights (RI)

Import Foundation and Transactional Data from Retail Insights

RMFCS can send Foundation and Transactional data to RAP integration using Retail Insights (RI) and other systems within RAP. The systems can share the data, even if RMFCS is not implemented for the customer. The customer can upload the foundation and data files in the file format needed by RI in RAP integration. That way, the same data can be published to all applications within RAP. It can be done by scheduling required job flows in Retail Insights to get the foundation data from RMFCS and loading it into the staging tables present in Retail Data Exchange (RDX) from where the configured interfaces in APCS can pull the required data into Facts in Planning Data Schema (PDS) where APCS is deployed.

The customer can also load foundation data directly into RAP using the file format specified for RAP integration and using the same staging process in RI to write the data into RDX staging tables from where Planning can pull the data using standard configured interfaces. Only mapped columns specific to GA interfaces are detailed in this guide. For more details about interface file formats and the jobs flow details, see the Oracle Retail Analytics and Planning Implementation Guide . Also refer to those guides to find more information about the available columns in each interface staging tables in RDX sourced from RI so that customers using extensibility on template or using custom configuration (non-template) can pull the required data from RDX.

The following table shows the list of interfaces in RAP to get the foundation and transactional data:

InterfaceInterface and Table NameInterface Type
Product HierarchyW_PDS_PRODUCT_DHierarchy Importer
Location HierarchyW_PDS_ORGANIZATION_DHierarchy Importer
InterfaceInterface and Table NameInterface Type
Calendar HierarchyW_PDS_CALENDAR_D
(VW_CLND_HIER)
Hierarchy Importer
Cluster HierarchyVW_CLRH_HIER
(W_PDS_ORGANIZATION_D
Hierarchy Importer
Product Attribute HierarchyW_PDS_UDA_DHierarchy Importer
Sales InterfaceW_PDS_SLS_IT_LC_WK_AData Importer
Inventory InterfaceW_PDS_INV_IT_LC_WK_AData Importer
On Order InterfaceW_PDS_PO_ONORD_IT_LC_WK_AData Importer
Receipts InterfaceW_PDS_INVRC_IT_LC_WK_AData Importer
Inventory TransfersW_PDS_INVTSF_IT_LC_WK_AData Importer
Markdowns InterfaceW_PDS_MKDN_IT_LC_WK_AData Importer
Wholesale/FranchiseW_PDS_SLSWF_IT_LC_WK_AData Importer
Product AttributesW_PDS_PRODUCT_ATTR_DData Importer
Location DataVW_LOC_DATAData Importer
Product DataVW_PROD_DATAData Importer
UDA DataVW_UDA_DATAData Importer
Location Attributes HierarchyVW_SATR_HIERHierarchy Importer
Customer Segment HierarchyW_PDS_CUSTSEG_DHierarchy Importer
Location AttributesW_PDS_ORG_ATTR_STR_DData Importer
Replenishment DataW_PDS_REPL_ATTR_IT_LC_DData Importer

The following table shows the mapping of dimensions to columns for Hierarchy Importer interfaces from external interface tables:

HierarchyDimensionExternal Interface TableExternal Mapped Column
prodskuW_PDS_PRODUCT_DITEM
prodsku_labelW_PDS_PRODUCT_DITEM_DESC
prodskupW_PDS_PRODUCT_DITEM_PARENT_DIFF
prodskup_labelW_PDS_PRODUCT_DITEM_PARENT_DIFF_DESC
prodskugW_PDS_PRODUCT_DITEM_PARENT
prodskug_labelW_PDS_PRODUCT_DITEM_PARENT_DESC
prodsclsW_PDS_PRODUCT_DCLASS_ID
prodscls_labelW_PDS_PRODUCT_DDEPT
prodclssW_PDS_PRODUCT_DGROUP_NO
prodclass_labelW_PDS_PRODUCT_DDIVISION
proddeptW_PDS_PRODUCT_DCOMPANY
proddept_labelW_PDS_PRODUCT_DCO_NAME
prodpgrpW_PDS_PRODUCT_DGROUP_NO
prodpgrp_labelW_PDS_PRODUCT_DGROUP_NAME
proddvsnW_PDS_PRODUCT_DDIVISION
proddvsn_labelW_PDS_PRODUCT_DDIV_NAME
prodcmppW_PDS_PRODUCT_DCOMPANY
HierarchyDimensionExternal Interface TableExternal Mapped Column
prodcmpp_labelW_PDS_PRODUCT_DCO_NAME
prodvndrW_PDS_PRODUCT_DSUPPLIER
prodvndr_labelW_PDS_PRODUCT_DSUP_NAME
prodbrndW_PDS_PRODUCT_DBRAND_NAME
prodbrnd_labelW_PDS_PRODUCT_DBRAND_DESCRIPTION
prodsta1W_PDS_PRODUCT_DNA
prodsta1_labelW_PDS_PRODUCT_DUnassigned
locstorW_PDS_ORGANIZATION_DLOCATION
locstor_labelW_PDS_ORGANIZATION_DLOC_NAME
locdstrW_PDS_ORGANIZATION_DDISTRICT
locdstr_labelW_PDS_ORGANIZATION_DDISTRICT_NAME
locregnW_PDS_ORGANIZATION_DREGION
locregn_labelW_PDS_ORGANIZATION_DREGION_NAME
locchnlW_PDS_ORGANIZATION_DAREA
locchnl_labelW_PDS_ORGANIZATION_DAREA_NAME
locchanW_PDS_ORGANIZATION_DCHAIN
locchan_labelW_PDS_ORGANIZATION_DCHAIN_NAME
loccompW_PDS_ORGANIZATION_DCOMPANY
loccomp_labelW_PDS_ORGANIZATION_DCO_NAME
locphwhW_PDS_ORGANIZATION_DPHYSICAL_WH
locphwh_labelW_PDS_ORGANIZATION_DPHYSICAL_WH_NAME
locloctW_PDS_ORGANIZATION_DLOC_TYPE
locloct_labelW_PDS_ORGANIZATION_DLOC_TYPE_NAME
locstrcW_PDS_ORGANIZATION_DLOCATION
locstrc_labelW_PDS_ORGANIZATION_DLOCATION_NAME
locchncW_PDS_ORGANIZATION_DPLANNING_CHANNEL_ID
locchnc_labelW_PDS_ORGANIZATION_DPLANNING_CHANNEL_NAME
loccctyW_PDS_ORGANIZATION_DPLANNING_COUNTRY_ID
locccty_labelW_PDS_ORGANIZATION_DPLANNING_COUNTRY_NAME
clnddayW_PDS_CALENDAR_DDAY
clndday_labelW_PDS_CALENDAR_DDAY_LABEL
clndweekW_PDS_CALENDAR_DWEEK
clndweek_labelW_PDS_CALENDAR_DWEEK_LABEL
clndmnthW_PDS_CALENDAR_DMNTH
clndmnth_labelW_PDS_CALENDAR_DMNTH_LABEL
clndqrtrW_PDS_CALENDAR_DQRTR
clndqrtr_labelW_PDS_CALENDAR_DQRTR_LABEL
clndhalfW_PDS_CALENDAR_DHALF
clndhalf_labelW_PDS_CALENDAR_DHALF_LABEL
clndyearW_PDS_CALENDAR_DYEAR

Import Foundation and Transactional Data from Retail Insights

HierarchyDimensionExternal Interface TableExternal Mapped Column
clndyear_labelW_PDS_CALENDAR_DYEAR_LABEL
clndwoyrW_PDS_CALENDAR_DWOYR
clndwoyr_labelW_PDS_CALENDAR_DWOYR_LABEL
clndstdbW_PDS_CALENDAR_DSTDB
clndstdb_labelW_PDS_CALENDAR_DSTDB_LABEL
clndhldyW_PDS_CALENDAR_DNA
clndhldy_labelW_PDS_CALENDAR_DUnassigned
clndevntW_PDS_CALENDAR_DNA
clndevnt_labelW_PDS_CALENDAR_DUnassigned
clndbypdW_PDS_CALENDAR_DNA
clndbypd_labelW_PDS_CALENDAR_DUnassigned
clrhclusVW_CLRH_HIERCLUS_ID
clrhclus_labelVW_CLRH_HIERCLUS_DESC
patrpatvW_PDS_UDA_D
(VW_PATR_HIER)
PROD_ATTR_VALUE
patrpatv_labelW_PDS_UDA_D
(VW_PATR_HIER)
PROD_ATTR_VALUE_DESC
patrpattW_PDS_UDA_D
(VW_PATR_HIER)
PROD_ATTR
patrpatt_labelW_PDS_UDA_D
(VW_PATR_HIER)
PROD_ATTR_DESC
satrsattVW_SATR_HIERATTR_ID
satrsatt_labelVW_SATR_HIERATTR_DESC
satrsatvVW_SATR_HIERATTR_VALUE
satrsatv_labelVW_SATR_HIERATTR_VALUE_DESC
csghcsvdW_PDS_CUSTSEG_DCUSTSEG_ID
csghcsvd_labelW_PDS_CUSTSEG_DCUSTSEG_NAME
csghcsgdW_PDS_CUSTSEG_DCUSTSEG_ID
csghcsgd_labelW_PDS_CUSTSEG_DCUSTSEG_NAME

Note: For Calendar Hierarchy (clnd), RMFCS is not sending the labels. Internally, VW_CLND_HIER is defined in PDS against the interface W_PDS_CALENDAR_D table to derive the labels and also default the calendar import to PDS to have two past years, one current year, and two future years based on the current business date. The Administrator can update the same using the Online Administration Tool Tasks under System Admin Tasks List/Set/Unset PDS Integration variables and can update the CLND_PAST_YEARS and CLND_FUTURE_YEARS variables. By default, both are set to 2. The customer can also update the start fiscal month by setting the CLND_START_MONTH variable. By default, it is set to 2 to have the fiscal start month label be generated as February. CLND_TYPE can be set to ‘F’ (Fiscal) or ‘G’ (Gregorian) or ‘B’ (Both) based on the type of calendar the customer wants to use for the calendar date range in PDS. It is defaulted to Both, in order to include the calendar range of both Fiscal and Gregorian Calendar start and end dates by default.

Note: For Cluster Hierarchy (clrh), there is no direct interface table. Internally, VW_CLRH_HIER is defined in PDS against the interface W_PDS_ORGANIZATION_D table to get the locations as cluster ids.

Note: The VW_PATR_HIER view is an internal view in PDS against the base RDX tables W_PDS_UDA_D, W_PDS_DIFF_D, W_PDS_SUPPLIER_D, and W_PDS_BRAND_D by concatenating all of them as product attributes. It also concatenates the product attribute name with the product attribute values using ‘_’ to make the product attribute values unique. The Product Attribute name for Supplier (W_PDS_SUPPLIER_D) is used as ‘supp’ and Brand (W_PDS_BRAND_D) is used as ‘brnd’. Only Product attributes with UDA_TYPE_CODE as ‘LV’ from W_PDS_UDA_D are included in the view. PDS Integration variables PATR_BRAND, PATR_SUPP are defaulted with values ‘brnd’ and ‘supp’, but those can be changed if the customer wants to use different attribute names. PDS Integration variable ‘PATR_OTHER’ can be enabled to ‘Y’ (default is set ‘N’) to include the ‘Z_Other’ attribute value for all the attributes that are used by AP GA.

Note: For the Location Attribute Hierarchy (SATR), there is no direct interface table. Internally, VW_SATR_HIER is defined in PDS against the interface W_PDS_ORG_ATTR_STR_D table to get the distinct location attributes. PDS Integration variable ‘SATR_GROUP’ can be enabled to ‘Y’ (default is set to ‘N’) to include the Sales Performance Group and Space Group Location Attributes used by AP GA.

Note: For all APCS hierarchies that are not integrated using RAP integration, the customer needs to explicitly provide those files.

The following table shows the mapping of fact names/measures names to columns for the Data Importer interfaces from the external interface tables in RDX:

Fact NameExternal Interface TableExternal Mapped ColumnExternal Mapping
Condition
drtyeop1cW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_COSTCLEAR_IND = ‘N’
drtyeop1rW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_RETAILCLEAR_IND = ‘N’
drtyeop1uW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_UNITSCLEAR_IND = ‘N’
drtyeop2cW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_COSTCLEAR_IND = ‘Y’
drtyeop2rW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_RETAILCLEAR_IND = ‘Y’
drtyeop2uW_PDS_INV_IT_LC_WK_AREGULAR_INVENTORY_UNITSCLEAR_IND = ‘Y’
drtynslsclrcW_PDS_SLS_IT_LC_WK_ANET_SALES_CLR_COST
drtynslsclrrW_PDS_SLS_IT_LC_WK_ANET_SALES_CLR_RETAIL
drtynslsclruW_PDS_SLS_IT_LC_WK_ANET_SALES_CLR_UNITS
drtynslsprocW_PDS_SLS_IT_LC_WK_ANET_SALES_PRO_COST
drtynslsprorW_PDS_SLS_IT_LC_WK_ANET_SALES_PRO_RETAIL
drtynslsprouW_PDS_SLS_IT_LC_WK_ANET_SALES_PRO_UNITS
drtynslsregcW_PDS_SLS_IT_LC_WK_ANET_SALES_REG_COST
drtynslsregrW_PDS_SLS_IT_LC_WK_ANET_SALES_REG_RETAIL
drtynslsreguW_PDS_SLS_IT_LC_WK_ANET_SALES_REG_UNITS
drtyrtnclrcW_PDS_SLS_IT_LC_WK_ARETURNS_CLR_COST
drtyrtnclrrW_PDS_SLS_IT_LC_WK_ARETURNS_CLR_RETAIL
drtyrtnclruW_PDS_SLS_IT_LC_WK_ARETURNS_CLR_UNITS
drtyrtnprocW_PDS_SLS_IT_LC_WK_ARETURNS_PRO_COST
drtyrtnprorW_PDS_SLS_IT_LC_WK_ARETURNS_PRO_RETAIL
drtyrtnprouW_PDS_SLS_IT_LC_WK_ARETURNS_PRO_UNITS
drtyrtnregcW_PDS_SLS_IT_LC_WK_ARETURNS_REG_COST
drtyrtnregrW_PDS_SLS_IT_LC_WK_ARETURNS_REG_RETAIL
Fact NameExternal Interface TableExternal Mapped ColumnExternal Mapping
Condition
drtyrtnreguW_PDS_SLS_IT_LC_WK_ARETURNS_REG_UNITS
drtyoocW_PDS_PO_ONORD_IT_LC_WK_AON_ORDER_COST
drtyoorW_PDS_PO_ONORD_IT_LC_WK_AON_ORDER_RETAIL
drtyoouW_PDS_PO_ONORD_IT_LC_WK_AON_ORDER_UNITS
drtyporcptcW_PDS_INVRC_IT_LC_WK_APO_RECEIPT_COST
drtyporcptrW_PDS_INVRC_IT_LC_WK_APO_RECEIPT_RETAIL
drtyporcptuW_PDS_INVRC_IT_LC_WK_APO_RECEIPT_UNITS
drtytraninbcW_PDS_INVTSF_IT_LC_WK_ATSF_IN_COSTTSF_TYPE = ‘B’
drtytraninbrW_PDS_INVTSF_IT_LC_WK_ATSF_IN_RETAILTSF_TYPE = ‘B’
drtytraninbuW_PDS_INVTSF_IT_LC_WK_ATSF_IN_UNITSTSF_TYPE = ‘B’
drtytraninicW_PDS_INVTSF_IT_LC_WK_ATSF_IN_COSTTSF_TYPE = ‘I’
drtytraninirW_PDS_INVTSF_IT_LC_WK_ATSF_IN_RETAILTSF_TYPE = ‘I’
drtytraniniuW_PDS_INVTSF_IT_LC_WK_ATSF_IN_UNITSTSF_TYPE = ‘I’
drtytraninrW_PDS_INVTSF_IT_LC_WK_ATSF_IN_RETAILTSF_TYPE = ‘N’
drtytranincW_PDS_INVTSF_IT_LC_WK_ATSF_IN_COSTTSF_TYPE = ‘N’
drtytraninuW_PDS_INVTSF_IT_LC_WK_ATSF_IN_UNITSTSF_TYPE = ‘N’
drtytranoutbcW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_COSTTSF_TYPE = ‘B’
drtytranoutbrW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_RETAILTSF_TYPE = ‘B’
drtytranoutbuW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_UNITSTSF_TYPE = ‘B’
drtytranouticW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_COSTTSF_TYPE = ‘I’
drtytranoutirW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_RETAILTSF_TYPE = ‘I’
drtytranoutiuW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_UNITSTSF_TYPE = ‘I’
drtytranoutrW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_RETAILTSF_TYPE = ‘N’
drtytranoutuW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_UNITSTSF_TYPE = ‘N’
drtytranoutcW_PDS_INVTSF_IT_LC_WK_ATSF_OUT_COSTTSF_TYPE = ‘N’
drtyicmkurW_PDS_MKDN_IT_LC_WK_AINTERCOMPANY_MARKUP
drtyicmkdrW_PDS_MKDN_IT_LC_WK_AINTERCOMPANY_MARKDOWN
drtywfslsuW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_SALES_UNITS
drtywfslscW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_SALES_COST
drtywfslsrW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_SALES_RETAIL
drtywfrtnuW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_RETURNS_UNITS
drtywfrtnrW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_RETURNS_COST
drtywfrtncW_PDS_SLSWF_IT_LC_WK_AFRANCHISE_RETURNS_RETAIL
addvlocopndVW_LOC_DATASTORE_OPEN_DATE
addvlocenddVW_LOC_DATASTORE_CLOSE_DATE
addvlocrefdVW_LOC_DATAREMODEL_DATE
drdvprdattW_PDS_PRODUCT_ATTR_D
(VW_PATV_DATA)
PROD_ATTR_VALUE
drdvppatvtVW_PATV_DATAPATV_VALUE
drtyudabVW_UDS_DATATrue for PROD_ATTR
Fact NameExternal Interface TableExternal Mapped ColumnExternal Mapping
Condition
drtypclsstVW_PROD_DATACLASS_DISPLAY_ID
drtypsclstVW_PROD_DATASUBCLASS_DISPLAY_ID
drdvskuimgtVW_PROD_DATAPRODUCT_IMAGE_NAME
drdvskuimglVW_PROD_DATAPRODUCT_IMAGE_ADDR
drdvslsprcrVW_PROD_DATAINITIAL_ITEM_RETAIL
drdvslsprccVW_PROD_DATAINITIAL_ITEM_COST
addvlocattW_PDS_ORG_ATTR_STR_DATTR_VALUE
drtyreplbW_PDS_REPL_ATTR_IT_LC_DREPL_ACTIVE_FLAG
drtyrcptdW_PDS_INV_IT_LC_WK_AFIRST_INVRC_DT
drtyslsprcW_PDS_INV_IT_LC_WK_AUNIT_COST
drtyslsprrW_PDS_INV_IT_LC_WK_AUNIT_RETAIL

Note: For Location specific data, the same W_PDS_ORGANIZATION_D hierarchy table used for the location hierarchy is used. The view VW_LOC_DATA is defined in PDS to point to the same set of data and used as data importer interface. Similarly, VW_PROD_DATA is defined against W_PDS_PRODUCT_D to load any required data as measures such as Image details, RMF CS Unique Class, and Sub-Class Ids.

VW_PATR_DATA is defined against W_PDS_PRODUCT_ATTR_D for UDA_TYPE in ‘LV’ and also gets attribute values for the DIFF*, SUPPLIER, AND BRAND_NAME from the W_PDS_PRODUCT_D table at the item level. It also concatenates the product attribute values with product attribute names using ‘_’ and uses ‘supp’ and ‘brnd’ as product attribute names for Supplier and Brand.

The VW_PATV_DATA internal view defined against the Product Attribute Hierarchy table contains product attribute values without concatenation of product attribute names and it uses similar tables as in VW_PATR_HIER. The VW_UDA_DATA is defined against W_PDS_UDA_D to only contain distinct UDA to uniquely identify the UDAs defined in RMFCS.

Note: If the customer wants to use position filtering to filter a few products only in APCS in a multi-app environment, they can use the extensibility in GA, to set the Position Filter Measure property for product in Hierarchies to the measure DRDVAPFltSkuB and then can use any flex field for the product in W_PDS_PRODUCT_D to mark those items as ‘Y’ and interface that data to APCS_DRDVAPFltSkuB by changing the interface.cfg mapping for VW_PROD_DATA using extensibility guidelines.

Note: Pack Items are filtered by default for AP during the product hierarchy import from RAP using the Pack Item Filter Value measure set to N. This shared filter measure, PCKFLGVAL, can be managed in the Planning Admin workbook. In a multi-app scenario, if other applications need to bring in pack items, this can be changed to % to bring in both pack and non-pack items.

Import Forecasts from AI Foundation

Forecasts can be generated from AI Foundation (AIF) and imported to APCS using RAP integration. AI Foundation can generate different levels of forecasts as needed by different levels of plans. It generates both Pre-Season forecasts (using the Auto-ES Forecast method) and In-Season Forecasts (using the Bayesian Forecast Method). AI Foundation directly gets the actuals through RAP integration. Job flows in AI Foundation need to be scheduled to

generate the forecast and import the same to APCS. For more details, see the Oracle Retail Analytics and Planning Integration Implementation Guide .

In order to get forecasts 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 .

Note

The AI Foundation default Location Hierarchy does not contain the Planning Channel. Customers need to use the Alternate Hierarchy setup which uses the Planning Channel as an alternate hierarchy and create forecasts at the Planning Channel level as needed by MFP GA. For more details about creating forecasts at the Planning Channel level, see the AI Foundation documentation set.

The following table shows the interface table column details from AI Foundation in RDX used for the interface.

Interface Name: RSE_FCST_DEMAND_EXP

Table ColumnData TypeComments
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
CAL_HIER_LEVELVarchar2(30)The calendar level data is for Fiscal Year, Fiscal
Quarter, Fiscal Period, Fiscal Week, and Fiscal Day.
LOC_HIER_LEVELVarchar2(30)The location hierarchy level data is for COMPANY,
CHAIN, AREA, REGION, DISTRICT, LOCATION,
and CHANNEL.
PROD_HIER_LEVELVarchar2(30)The product hierarchy level the data is for CMP, DIV,
GRP, DEPT, CLS, SBC, STYLE, STYLE_COLOR,
and ITEM.
FCST_DATE_FROMDateThe start date which the forecast is for.
LOC_EXT_KEYVarchar2(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).
PROD_EXT_KEYVarchar2(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
CLS123456~789).
CUSTSEG_EXT_KEYVarchar2(80)The external id of the customer segment. It will be
NULL if not applicable.
FCST_TYPEVarchar2(20)The type of forecast. PI, NPI (PI=Plan Influenced, PI
= Non Plan Influenced)
REG_SLS_QTYNumber(38,20)Regular Sales Units
REG_SLS_AMTNumber(38,20)Regular Sales Amount
PR_SLS_QTYNumber(38,20)Promo Sales Units
PR_SLS_AMTNumber(38,20)Promo Sales Amount
CLR_SLS_QTYNumber(38,20)Clearance Sales Units
CLR_SLS_AMTNumber(38,20)Clearance Sales Amount
REG_PR_SLS_QTYNumber(38,20)Regular and Promo Sales Units
Table ColumnData TypeComments
REG_PR_SLS_AMTNumber(38,20)Regular and Promo Sales Amount
SLS_QTYNumber(38,20)Total Sales Units
SLS_AMTNumber(38,20)Total Sales Amount
RET_QTYNumber(38,20)Return Units
RET_AMTNumber(38,20)Return Amount

The same Interface table contains the forecast data for different levels of plans differentiated by _LEVEL columns within the interface. The single interface run pulls data for different levels of forecasts which are pre-configured. Customers using non-template versions, if using different levels of plans, can use the supported levels in AI Foundation to generate forecasts. The following sections provide the default levels of forecasts exported for the APCS template version and their mappings.

Item Level Forecasts Mapping

The following table shows the mapping for pre-season and in-season Item Level Forecasts.

Table ColumnMapping for Pre-Season (MPP)Mapping for In-Season (MPI)
CAL_HIER_LEVELFiscal WeekFiscal Week
LOC_HIER_LEVELLOCATIONLOCATION
PROD_HIER_LEVELITEMITEM
FCST_DATE_FROMWEEKWEEK
LOC_EXT_KEYSTORSTOR
PROD_EXT_KEYSKUSKU
CUSTSEG_EXT_KEYNULLNULL
FCST_TYPENPIPI
REG_PR_SLS_QTYFCTYFCPMUFCTYFCIMU
REG_PR_SLS_AMTFCTYFCPMRFCTYFCIMR

Sub-Class Level Forecasts Mapping

The following table shows the mapping for pre-season Sub-Class Level Forecasts.

Table ColumnMapping for Pre-Season (MTP)
CAL_HIER_LEVELFiscal Week
LOC_HIER_LEVELLOCATION
PROD_HIER_LEVELSBC
FCST_DATE_FROMWEEK
LOC_EXT_KEYSTOR
PROD_EXT_KEYSCLS
CUSTSEG_EXT_KEYNULL
FCST_TYPENPI
REG_PR_SLS_QTYFCDVSlS1U
REG_PR_SLS_AMTFCDVSLS1R

Import DT Parameters from AI Foundation

The previous version of APCS used Demand Transference (DT) from AI Foundation to suggest and optimize the assortments. DT is based on Item attributes, Attribute Weights, Functional Fit for Attributes, Assortment Elasticity, and Rate of Sale of Items. Item Attributes and Rate of Sale of item are available from RI interfaces. Other DT parameters such as Attribute Weights, Functional Fit for Attributes, and Assortment Elasticity are interfaced from AI Foundation through RAP integration. The APCS template version gets the DT parameters from RAP at the Sub-Class/Channel level, so it needs to be defined in AI Foundation at that level.

In order to get DT parameters from AI Foundation, during implementation, some initial setups need to be done in the AI Foundation platform. AI Foundation needs a customer segment to be defined for DT interfaces. AI Foundation can use multiple customer segments, so those customer segments need to be loaded as the CSGH hierarchy, in order for AP to interface DT parameters. AP is not directly using customer segments in planning workbooks, but the user can choose the Customer Segment to use for a Sub-Class in the Planning Admin workbook. Only those selected Customer Segments DT Parameters for the Sub-Class will be used in the AP workbooks. 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 DT Integration is set to true, then this interface will run as part of the weekly batch.

The current version of AP is not using the below interface but still kept the details for nontemplate customers to customize and use the same if they are still using this integration.

Interface Name: RSE_ASSORT_ELASTICITY_EXP

Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
LOC_HIER_LEVELVarchar2(30)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, LOCATION, and
CHANNEL_COUNTRY.
CHANNEL_COUNTRY
PROD_HIER_LEV
EL
Varchar2(30)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, STYLE_COLOR, and ITEM.
SBC
LOC_EXT_KEYVarchar2(80)The external id of the location. It will
use the integration ids as provided to
RI.
CHNC
PROD_EXT_KEYVarchar2(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
CLS123456~789).
SCLS
CUSTSEG_EXT_K
EY
Varchar2(80)The external id of the customer
segment.
CSGD
ASSORT_ELASTIC
ITY
Number(38,20)The assortment elasticity which DT has
calculated.
DRTYASSRTELASV

Table Column Data Type Comments Dimension / Measure / Value Mapping EFFECTIVE_DT_F Date The date when this data was activated. ROM

Interface Name: RSE_ASSORT_ATTR_WGT_EXP

Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
LOC_HIER_LEVELVarchar2(30)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, LOCATION, and
CHANNEL_COUNTRY.
CHANNEL_COUNTRY
PROD_HIER_LEV
EL
Varchar2(30)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, STYLE_COLOR, and SKU.
SBC
LOC_EXT_KEYVarchar2(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).
CHNL
PROD_EXT_KEYVarchar2(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
CLS123456~789).
SCLS
CUSTSEG_EXT_K
EY
Varchar2(80)The external id of the customer
segment. It will be NULL if not
applicable.
CSGD
PROD_ATTR_GRP
_EXT_KEY
Varchar2(80)The external ID for the product
attribute.
PATT
ATTR_WGTNumber(38,20)The attribute weight.DRTYATTRWGTV
FUNC_ATTR_FLGVarchar2(1)Y/N Flag indicating this is a functional
attribute. A functional attribute is one
which fits a specific purpose and
cannot be substituted by other products
with other values for this attribute.
DRTYFUNCFITB

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 ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
LOC_HIER_LEVELVarchar2(30)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, and LOCATION.
LOCATION
PROD_HIER_LEV
EL
Varchar2(30)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, STYLE_COLOR, and ITEM.
DEPT
LOC_EXT_KEYVarchar2(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_KEYVarchar2(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
CLS123456~789).
DEPT
EFF_START_DTDateThe starting date which the cluster is
effective.
WEEK, DRDVSRTD
EFF_END_DTDateThe ending date for which the cluster is
effective.
DRDVENDD
CLUSTER_IDNumber(10)The identifier for the cluster.DRDVSTRCLUST
CLUSTER_LABELVarchar2(50)A descriptive name/label for the cluster.DRDVSTRCLUSL

Import Size Profiles from AI Foundation

Size Profiles can be defined in AI Foundation and can be interfaced to APCS. The previous version of the APCS template version used Size Profiles defined from AIF or the size profiles set at the Admin level within the application. The APCS template version imports size profiles from AIF at the sub-class level. It is used to define Buy Quantity by Size and Receipts by Sizes while planning them.

In order to get Size Profiles 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. For complete details of all available columns, see the Oracle Retail Analytics and Planning Integration Implementation Guide . If RAP integration is enabled and Enable RSE Size Profile Integration is set to true, then this interface will run as part of the weekly batch. If integration is enabled, it will use the same interface table data to also load the Size Hierarchy file (SIZH) using the internal view VW_SIZH_HIER and then also load the Size Profile.

The current version of AP is not using the below interface but still kept the details for nontemplate customers to customize and use the same if they are still using this integration.

Interface Name: RSE_SIZE_PROFILE_EXP

Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
LOC_LEVEL_NAM
E
Varchar2(255)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, and LOCATION.
LOCATION
PROD_LEVEL_NA
ME
Varchar2(255)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, and STYLE_COLOR.
SBC
LOC_EXT_KEYVarchar2(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_KEYVarchar2(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
CLS123456~789).
SCLS
SIZE_EXT_IDNumber(10)Size External IdentifierSIZD
SIZE_PCT_UNITSNumber(10,5)Size Profile PercentageDRDVSIZE
USED_BY_AIPVarchar2(1)Flag to indicate that record is for AIP YPRFP
SIZE_LABELVarchar2(255)Size LabelSIZD_LABEL
SIZE_GROUP_IDVarchar2(255)Size Group IdentifierSRNG
SIZE_GROUP_LA
BEL
Varchar2(255)Size Group LabelSRNG_LABEL

Note

For Size Hierarchy (sizh), the internal view (VW_SIZE_HIER) is defined against the AIF RSE_SIZE_PROFILE_EXP table to get the unique sizes (SIZE_EXT_ID, SIZE_LABEL) and size ranges (SIZE_GROUP_ID and SIZE_GROUP_LABEL) which are marked to be used AP (USED_BY_AIP flag as ‘Y’).

SIZE_EXT_LABEL, also available as part of this view, can be used instead of SIZE_LABEL to get extended labels for sizes from AIF.

Export Assortment Periods for Location Clustering to AI Foundation

In the APCS template version, the customer can define the Assortment periods at pre-defined product levels (DEPT). Assortment Periods are date ranges to plan the assortments; it can vary for different product levels. The customer can export the defined Assortment Periods by enabling the Boolean measure Export Period for Clustering at the Assortment Period level.

In order to import and use this data 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 tables and column details from APCS 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: AP_ASSORT_PERIOD_EXP

Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
PROD_LEVELVarchar2(80)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, STYLE_COLOR, and SKU.
DEPT
PROD_KEYVarchar2(80)Product IdentifierDEPT
LOC_LEVELVarchar2(80)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, and LOCATION.
COMPANY
LOC_KEYVarchar2(80)Location IdentifierCOMP
ASSORT_PERIOD
_KEY
Varchar2(80)Assortment Period KeyBPER
ASSORT_PERIOD
_START_DATE
DateAssortment Period Start DateBCDVSRTD
ASSORT_PERIOD
_END_DATE
DateAssortment Period End DateBCDVENDD
EXT_NAMEVarchar2(80)External Cluster NameBCDVCLUSTERT
CLUSTER_DESCRVarchar2(255)Cluster DescriptionBCDVPRDL

Export Active Assortments to AI Foundation

In the APCS template version, the customer can plan active assortments for an assortment period and those details can be exported to AI Foundation at the Item/Store level.

In order to import and use this data 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 tables and column details from APCS 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, then this interface will run as part of the weekly batch.

Interface Name: AP_ACTIVE_ASSORT_EXP

Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
RUN_IDNumber(10)The export Run ID as obtained from the
RAP_INTF_UTIL.
Table ColumnData TypeCommentsDimension / Measure /
Value Mapping
PROD_KEYVarchar2(80)Product IdentifierSKU
LOC_KEYVarchar2(80)Location IdentifierSTOR
PROD_LEVELVarchar2(80)The product hierarchy level the data is
for CMP, DIV, GRP, DEPT, CLS, SBC,
STYLE, STYLE_COLOR, and SKU.
ITEM
LOC_LEVELVarchar2(80)The location hierarchy level data is for
COMPANY, CHAIN, AREA, REGION,
DISTRICT, and LOCATION.
LOCATION
ACTIVE_START_D
ATE
DateActive Assortment Start DateBPDBSRTD
ACTIVE_END_DAT
E
DateActive Assortment End DateBPDBENDD

Export Assortment Groups to AI Foundation

In the APCS template version, the customer can define the Assortment Groups at pre-defined product levels (DEPT). Assortment Groups are a unique combination of Assortment Period and Associated Location Clusters defined in the Assortment Period Setup workbook. That is used by AI Foundation in order to Optimize Sales data and calculate Option Counts and Sales Potential data that is later used by the AP solution custom menu’s using web service calls.

To import and use this data 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 tables and column details from APCS 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, then this interface will run as part of the daily/weekly batch.

Interface Name: AP_ASSORT_GROUP_EXP

Table ColumnData TypeCommentsDimension/
Measure/Value
Mapping
RUN_IDNumber(10)The export Run ID as obtained from the RAP_
INTF_UTIL.
LOC_HIER_LEVELVarchar2(30)The location hierarchy level data is for COMPANY,
CHAIN, AREA, REGION, DISTRICT, and LOCATION.
LOCATION
PROD_HIER_LEVELVarchar2(30)The product hierarchy level the data is for CMP, DIV,
GRP, DEPT, CLS, and SBC.
DEPT
LOC_EXT_KEYVarchar2(80)The external id of the location.STOR
PROD_EXT_KEYVarchar2(80)The external id of the product hierarchy.DEPT
EFF_START_DATEDateThe starting date which the cluster is effective.APCS_BGDVSRTD
EFF_END_DATEDateThe ending date for which the cluster is effective.APCS_BGDVENDD
ASSORT_PERIOD_I
D
Varchar2(80)Assort Period Id used in AP.BPER
Table ColumnData TypeCommentsDimension/
Measure/Value
Mapping
ASSORT_PERIOD_L
ABEL
Varchar2(255)Assort Period User Label.APCS_BGDVPRDL
ASSORT_GROUP_I
D
Varchar2(80)Unique Id to group Product/Assort Period/Cluster
Grouping based on Approval Date.
APCS_BGDVPRDT
ASSORT_PROD_LE
VEL
Varchar2(80)The product hierarchy level for Assortment Strategy.SBC
CLUSTER_IDVarchar2(80)Unique identifier for the cluster.APCS_BGDVSTRCL
UST
CLUSTER_LABELVarchar2(255)A descriptive name/label for the cluster used in AP.APCS_BGDVSTRCL
USL

Export Assortment Plans to Retail Insights

Approved plans from APCS can be exported to Retail Insights within RAP integration. The APCS template version allows creating and exporting plans at the week/store/style-color level for both different versions. Plans for different versions can be exported to Retail Insights on a weekly basis. It exports all the approved plans for the unelapsed periods. With the AP nontemplate version, customers can create a different level of plans and they can also configure various metrics. The interface staging table in Retail Sights contains more metrics columns and various flex columns. The customer can update and configure the interface.cfg mappings to export additional columns that can be used by Retail Insights.

For more details about the list of columns available in the Retail Insights Interface Staging table if the customer plans to use extensibility or use the non-template version to send additional data, see the Oracle Retail Insights Implementation Guide . This guide contains only the mapped columns for the APCS template version.

This plan is one table for one level and uses the VERSION_NUM to differentiate different versions for the same level of data, such as WP and CP versions, for exporting both the OP and CP versions of the approved Assortment Plan.

Only AP_PLAN2_EXP is used by the AP template version to export plans at the Style-Color/ Store/Week level. The AP_PLAN1_EXP table and interface is still available for non-template version customers if they want to customize and do exports at the Item/Store/Week level.

Interface Name: AP_PLAN2_EXP

  • Plan Level: Style-Color/Store/Week

  • Plan Version: AF CP

  • Plan Version Number: 2

  • Export Filter: APCS_APCPEXPORTB

Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
RUN_IDInterface Run IdentifierNumber(10)NThe export Run
ID as obtained
from the
RAP_INTF_UTI
L
Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
PROD_KEYProduct DimensionVARCHAR2(80)NDimension
STYL from
PROD
APCS_APHDP
SKUGT
LOC_KEYLocation DimensionVARCHAR2(80)NDimension
STOR from
LOC
CLND_KEYCalendar DimensionVARCHAR2(80)NDimension
WEEK from
CLND
PROD_DH_ATTRAttribute Dimension for
RI
VARCHAR2(80)NColor AttributeAPCS_APHDP
COLORT
SUPPLIER_NUMSupplier Dimension for
RI
VARCHAR2(80)NDefaulted to -1
CAL_DATELast Day of WeekDateNLast Date of
CLND_KEY as
Date
APCS_APHDP
WKED
VERSION_NUMVersion NumberNumber(10)NDefaulted to 2
PROD_LEVELProduct LevelVARCHAR2(80)Defaulted to
COLOR
LOC_LEVELLocation LevelVARCHAR2(80)Defaulted to
LOCATION
FLEX1_CHAR_VALUEStyle-Color IdVARCHAR2(80)Dimension
SKUP from
PROD
SLS_QTYAF Cp Sales UNUMBER(20,4)APCS_APCPS
LSU
SLS_RTL_AMTAF Cp Sales RNUMBER(20,4)APCS_APCPS
LSR
SLS_COST_AMTAF Cp Sales CNUMBER(20,4)APCS_APCPS
LSC
ASRT_INTENTAF Cp Item IntentVARCHAR2(80)APCS_APCPIN
TENTT
ASRT_STATUSAF Cp Item StatusVARCHAR2(80)APCS_APCPS
TATUST
ASRT_FLAGAF Cp Option AssortedVARCHAR2(80)APCS_APCPA
SRTSKUPB
ASRT_COUNTAF Cp Option Assorted
Count
NUMBER(18,4)APCS_APCPA
SRTSKUPCT
PLAN_START_DATEAF Cp Week StartDATEAPCS_APCPS
RTD
PLAN_END_DATEAF Cp Week EndDATEAPCS_APCPE
NDD

Plan Level: Style-Color
Plan Version: AF WP
/Store/Week
  • Plan Version Number: 3

  • Export Filter: APCS_APWPEXPORTB

Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
RUN_IDInterface Run IdentifierNumber(10)NThe export Run
ID as obtained
from the
RAP_INTF_UTI
L
PROD_KEYProduct DimensionVARCHAR2(80)NDimension
STYL from
PROD
APCS_APHDP
SKUGT
LOC_KEYLocation DimensionVARCHAR2(80)NDimension
STOR from
LOC
CLND_KEYCalendar DimensionVARCHAR2(80)NDimension
WEEK from
CLND
PROD_DH_ATTRAttribute Dimension for
RI
VARCHAR2(80)NColor AttributeAPCS_APHDP
COLORT
SUPPLIER_NUMSupplier Dimension for
RI
VARCHAR2(80)NDefaulted to -1
CAL_DATELast Day of WeekDateNLast Date of
CLND_KEY as
Date
APCS_APHDP
WKED
VERSION_NUMVersion NumberNumber(10)NDefaulted to 3
PROD_LEVELProduct LevelVARCHAR2(80)Defaulted to
COLOR
LOC_LEVELLocation LevelVARCHAR2(80)Defaulted to
LOCATION
FLEX1_CHAR_VALUEStyle-Color IdVARCHAR2(80)Dimension
SKUP from
PROD
SLS_QTYAF Wp Sales UNUMBER(20,4)APCS_APWPS
LSU
SLS_RTL_AMTAF Wp Sales RNUMBER(20,4)APCS_APWPS
LSR
SLS_COST_AMTAF Wp Sales CNUMBER(20,4)APCS_APWPS
LSC
ASRT_INTENTAF Wp Item IntentVARCHAR2(80)APCS_APWPI
NTENTT
ASRT_STATUSAF Wp Item StatusVARCHAR2(80)APCS_APWPS
TATUST
ASRT_FLAGAF Wp Option
Assorted
VARCHAR2(80)APCS_APWPA
SRTSKUPB
ASRT_COUNTAF Wp Option
Assorted Count
NUMBER(18,4)APCS_APWPA
SRTSKUPCT
PLAN_START_DATEAF Wp Week StartDATEAPCS_APWPS
RTD
PLAN_END_DATEAF Wp Week EndDATEAPCS_APWPE
NDD
  • Plan Level: Style-Color/Store/Week

  • Plan Version: IF CP

  • Plan Version Number: 4

  • Export Filter: APCS_ISCPEXPORTB

Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
RUN_IDInterface Run IdentifierNumber(10)NThe export Run
ID as obtained
from the
RAP_INTF_UTI
L
PROD_KEYProduct DimensionVARCHAR2(80)NDimension
STYL from
PROD
APCS_APHDP
SKUGT
LOC_KEYLocation DimensionVARCHAR2(80)NDimension
STOR from
LOC
CLND_KEYCalendar DimensionVARCHAR2(80)NDimension
WEEK from
CLND
PROD_DH_ATTRAttribute Dimension for
RI
VARCHAR2(80)NColor AttributeAPCS_APHDP
COLORT
SUPPLIER_NUMSupplier Dimension for
RI
VARCHAR2(80)NDefaulted to -1
CAL_DATELast Day of WeekDateNLast Date of
CLND_KEY as
Date
APCS_APHDP
WKED
VERSION_NUMVersion NumberNumber(10)NDefaulted to 4
PROD_LEVELProduct LevelVARCHAR2(80)Defaulted to
COLOR
LOC_LEVELLocation LevelVARCHAR2(80)Defaulted to
LOCATION
FLEX1_CHAR_VALUEStyle-Color IdVARCHAR2(80)Dimension
SKUP from
PROD
SLS_QTYIF Cp Sales UNUMBER(20,4)APCS_ISCPSL
S1U
SLS_RTL_AMTIF Cp Sales RNUMBER(20,4)APCS_ISCPSL
S1R
SLS_COST_AMTIF Cp Sales CNUMBER(20,4)APCS_ISCPSL
S1C
EOH_COST_AMTIF Cp EOP CNUMBER(20,4)APCS_ISCPEO
PC
EOH_RTL_AMTIF Cp EOP RNUMBER(20,4)APCS_ISCPEO
PR
EOH_QTYIF Cp EOP UNUMBER(20,4)APCS_ISCPEO
PU
INVRC_COST_AMTIF Cp Rcpt CNUMBER(20,4)APCS_ISCPRC
PTC
INVRC_RTL_AMTIF Cp Rcpt RNUMBER(20,4)APCS_ISCPRC
PTR
INVRC_QTYIF Cp Rcpt UNUMBER(20,4)APCS_ISCPRC
PTU
PLAN_START_DATEIF Cp Week StartDATEAPCS_ISCPSR
TD
PLAN_END_DATEIF Cp Week EndDATEAPCS_ISCPEN
DD
  • Plan Level: Style-Color/Store/Week

  • Plan Version: IF WP

  • • Plan Version Number: 5

  • Export Filter: APCS_ISWPEXPORTB

Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
RUN_IDInterface Run IdentifierNumber(10)NThe export Run
ID as obtained
from the
RAP_INTF_UTI
L
PROD_KEYProduct DimensionVARCHAR2(80)NDimension
STYL from
PROD
APCS_APHDP
SKUGT
LOC_KEYLocation DimensionVARCHAR2(80)NDimension
STOR from
LOC
CLND_KEYCalendar DimensionVARCHAR2(80)NDimension
WEEK from
CLND
PROD_DH_ATTRAttribute Dimension for
RI
VARCHAR2(80)NColor AttributeAPCS_APHDP
COLORT
SUPPLIER_NUMSupplier Dimension for
RI
VARCHAR2(80)NDefaulted to -1
CAL_DATELast Day of WeekDateNLast Date of
CLND_KEY as
Date
APCS_APHDP
WKED
VERSION_NUMVersion NumberNumber(10)NDefaulted to 4
PROD_LEVELProduct LevelVARCHAR2(80)Defaulted to
COLOR
LOC_LEVELLocation LevelVARCHAR2(80)Defaulted to
LOCATION
FLEX1_CHAR_VALUEStyle-Color IdVARCHAR2(80)Dimension
SKUP from
PROD
SLS_QTYIF Wp Sales UNUMBER(20,4)APCS_ISWPSL
S1U
SLS_RTL_AMTIF Wp Sales RNUMBER(20,4)APCS_ISWPSL
S1R
SLS_COST_AMTIF Wp Sales CNUMBER(20,4)APCS_ISWPSL
S1C
EOH_COST_AMTIF Wp EOP CNUMBER(20,4)APCS_ISWPE
OPC
EOH_RTL_AMTIF Wp EOP RNUMBER(20,4)APCS_ISWPE
OPR
EOH_QTYIF Wp EOP UNUMBER(20,4)APCS_ISWPE
OPU
INVRC_COST_AMTIF Wp Rcpt CNUMBER(20,4)APCS_ISWPR
CPTC
INVRC_RTL_AMTIF Wp Rcpt RNUMBER(20,4)APCS_ISWPR
CPTR
Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
INVRC_QTYIF Wp Rcpt UNUMBER(20,4)APCS_ISWPR
CPTU
PLAN_START_DATEIF Wp Week StartDATEAPCS_ISWPS
RTD
PLAN_END_DATEIF Wp Week EndDATEAPCS_ISWPE
NDD
  • Plan Level: Style-Color/Store/Week

  • Plan Version: Rec Opt

  • Plan Version Number: 6

  • Export Filter: APCS_ARDBEXPORTB

Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
RUN_IDInterface Run IdentifierNumber(10)NThe export Run
ID as obtained
from the
RAP_INTF_UTI
L
PROD_KEYProduct DimensionVARCHAR2(80)NDimension
STYL from
PROD
APCS_APHDP
SKUGT
LOC_KEYLocation DimensionVARCHAR2(80)NDimension
STOR from
LOC
CLND_KEYCalendar DimensionVARCHAR2(80)NDimension
WEEK from
CLND
PROD_DH_ATTRAttribute Dimension for
RI
VARCHAR2(80)NColor AttributeAPCS_APHDP
COLORT
SUPPLIER_NUMSupplier Dimension for
RI
VARCHAR2(80)NDefaulted to -1
CAL_DATELast Day of WeekDateNLast Date of
CLND_KEY as
Date
APCS_APHDP
WKED
VERSION_NUMVersion NumberNumber(10)NDefaulted to 5
PROD_LEVELProduct LevelVARCHAR2(80)Defaulted to
COLOR
LOC_LEVELLocation LevelVARCHAR2(80)Defaulted to
LOCATION
FLEX1_CHAR_VALUEStyle-Color IdVARCHAR2(80)Dimension
SKUP from
PROD
SLS_QTYRec Sales Potential UNUMBER(20,4)APCS_ARDBS
LSPOTU
SLS_RTL_AMTRec Sales Potential RNUMBER(20,4)APCS_ARDBS
LSPOTR
SLS_COST_AMTRec Sales Potential CNUMBER(20,4)APCS_ARDBS
LSPOTC
Table ColumnTable ColumnData TypeNullableCommentsAP Fact
Mapping
ASRT_FLAGRec Option AssortedVARCHAR2(80)APCS_ARDBA
SRTSK

AIF Integration using a Web Service

Customers can use AIF to calculate the Optimized History, Option Counts and Sales Potential that are used by AP during the Assortment Fit Process. The Optimized History/Option Count and Sale Potential can be interfaced to AP.

Before using the web service calls in AP, AP needs to export the Assortment Group that is the combination of unique Assortment Periods and Location Clusters. It runs as part of the daily batch and AIF also needs additional setups during implementation to run those Option Forecasts in the nightly batch. For more details, see the Oracle Retail Analytics and Planning Integration Implementation Guide .

Generated Option Forecasts/Optimized Sales/Sales Potential from AIF can be interfaced using the custom menu planning actions, directly into relevant workspaces that are pre-configured to get the data through internal web service calls using the standard RPAS web service framework.

The RPAS web service framework uses the configured serviceConfig.json file, which can be used to map the RPAS dimensions/measures that are used in workbook templates against the keys present in web service requests and responses for web services created within RAP; the same web service can be triggered using the custom menu from those templates. For more details about the mapping of serviceConfig.json, see the Service Config Definitions section in the Deployment Tool chapter in the Oracle Retail Predictive Application Server Cloud Edition Configuration Tools User Guide .

On successful connection using a web service call, an Admin task with the name <service_name> from workbook <workbook_name> will be available in OAT. It shows the calls triggered from the template with the details of contents in the web service request and response in JSON format. Sample request and response triggered from the custom menu are provided in the examples below. The same OAT log can be used to debug any issues during the transfer of data using web service calls if the response has any errors due to any issues.

Following are the details of the two configured web services with AIF for the AP GA configuration.

WebService for Optimized History/Option Count

AIF Service Name: /app/rgbuaifpyapwebservice/optioncountinference

AP Service Name: AIFService1

Service Version: dis

The following tables shows the key fields present in the web service request and response, and the corresponding mapped measures in AP GA.

Web Service Request Input Key Mappings

Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
asrtReqIdVARCHAR2(250)Dept/Assort PeriodAssortmentaft1asrtidt
Request Id
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
asrtLabel
asrtProdId
VARCHAR2(250)
VARCHAR2(80)
Dept/Assort Period
Dept/Assort Period
Assortment Label
Assortment Parent
Product
Dimension.
Department
Position Id will be
used in AP.
aft1asrtidl
aft1prodkeyt
asrtPeriodVARCHAR2(80)Dept/Assort PeriodAssort Period
Dimension Id used
in AP
aft1asrtlblt
asrtGroupIdVARCHAR2(80)Dept/Assort PeriodAssortment Group
Id
aft1prdt
attrTypeIdListVARCHAR2(80)Dept/Assort PeriodList of Eligible
Product Attribute
Type Id’s
aft1prdattt
prodListDept/Assort PeriodCollection for List
of Product/Store
Cluster
aft1clusidb
prodIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Product Idbwdbprodkeyt
storClusIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Store Cluster Idbwdbclusidt
keyStorIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
One Sample Key
Store Id with in
Store Cluster
against which to
receive the data.
afdbclusidt
tgtSlsNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Target Sales Unitsafdbtgtslsu
fcstSlsNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Forecasted Sales
Units
afdbfcstslsu
histSlsNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Historical Sales
Units
afdbhistslsu
attrSlsThrNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Optional Historic
Sales Threshold %
for Attributes
Values to
Recommend.
afdbattrslsthrp

Web Service Response Output Key Mappings

Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
asrtStgyRecOptHeaderDept/Assort PeriodCollection for the
Main Request
Response Header
responseCodeVARCHAR2(80)Dept/Assort PeriodEx:
200 - For
Successful
Processing of
Data
aft1respcodet
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
responseCodeMessageVARCHAR2(255)Dept/Assort PeriodDetailed
Response
Message for
Request
aft1respcodel
asrtStgyRecOptDetailDept/Assort PeriodCollection for the
Main Request
Response Details
asrtReqIdVARCHAR2(80)Dept/Assort PeriodSame asrtReqId
provided in the
input request
aft2asrtidt
asrtProdIdVARCHAR2(80)Dept/Assort PeriodSame asrtProdId
provided in the
input request
dept
asrtPeriodVARCHAR2(80)Dept/Assort PeriodSame asrtPeriod
provided in the
input request
bper
asrtGroupIdVARCHAR2(80)Dept/Assort PeriodAssortment Group
Unique Id to link
Prod/Assort
Period/Store
Clusters
aft2prdt
prodCntNUMBER(10,0)Dept/Assort PeriodNumber of
SubClass/Store
Clusters in the
request for the
Dept.
afdvprdct
prodListSubclass/Assort Period/
Store Cluster
Collection for List
of Products/Store
Cluster
prodIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Same product Id
provided in the
input request
scls
storClusIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Same Store
Cluster Id provided
in the input
request
bwdbclusidt
storIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
One Store Id with
in the Store
Cluster
stor
optTtlSlsNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Optimized Total
Sales
aft1optslsu
optTtlCntNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Optimized Sales
Option Count
aft1recoptnct
tgtTtlCntNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Target Sales
Option Count
aft1tgtttlct
histTtlCntNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Actual Sales
Option Count
aft1histttlct
fcstTtlCntNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Forecast Sales
Option Count
aft1fcstttlct
statusCodeVARCHAR2(255)Subclass/Assort Period/
Store Cluster
Status Code to
capture any errors
at detail level.
aft1statcodet
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
statusMessageVARCHAR2(255)Subclass/Assort Period/
Store Cluster
Status Message to
capture any errors
at detail level.
aft1statcodel
attrTypeListSubclass/Assort Period/
Store Cluster
attrTypeIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster/Attribute
Type
Collection for
Attribute Types
patt
attrTypeWgtNUMBER(20,4)Subclass/Assort Period/
Store Cluster/Attribute
Type
Attribute Type
Weight calculated
in Science for
Recommending
this Attribute
aft1attrtypev
attrListSubclass/Assort Period/
Store Cluster/Attribute
Type
Collection for
Attribute Value List
attrValueVARCHAR2(80)Subclass/Assort Period/
Store Cluster/Attribute
Value
Attribute Value
Name
aft1attridl
attrIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster/Attribute
Value
Attribute Name
and ”_” and
Attribute Value
Name. Unique Id
used in Planning
for Attribute
Values.
patv
optAttrSlsNUMBER(20,4)Subclass/Assort Period/
Store Cluster/Attribute
Value
Optimized
Attribute Value
Sales Units
aft1optattrslsu
optAttrMixNUMBER(20,4)Subclass/Assort Period/
Store Cluster/Attribute
Value
Recommended
Attribute Value Mix
Percentage
aft1optattrmixv

Sample Web Service Request Call

{
    "asrtStgyRecOptHeader": {
        "requestID": "103_ap03_20230507192443",
        "rspVersion": "v1",
        "timeout": 4.0
    },
    "asrtReqId": "103_ap03_20230507192443",
    "asrtLabel": "SPRING SUMMER 2023",
    "asrtProdId": "103",
    "asrtPeriod": "ap03",
    "asrtGroupId": "103_ap03_20230507",
    "attrTypeIdList": [
        "brnd",
        "color",
        "fabric"
     ],
    "prodList": [
        {
            "prodId": "1030101",
            "storClusId": "us_1_52058",
            "keyStorId": "1175",
            "tgtSls": 0,
            "fcstSls": 33592,
            "histSls": 76028,
            "attrSlsThr": 0.0
        },
        {
            "prodId": "1030202",
            "storClusId": "us_1_52058",
            "keyStorId": "1175",
            "tgtSls": 0,
            "fcstSls": 14977,
            "histSls": 29254,
            "attrSlsThr": 0.0
        }
    ]
}

Sample Web Service Response Call

{
    "AsrtStgyRecOptDetail": {
        "asrtGroupId": "103_ap03_20230507",
        "asrtPeriod": "ap03",
        "asrtProdId": "103",
        "asrtReqId": "103_ap03_20230507192443",
        "prodCnt": 2,
        "prodList": [
            {
                "attrTypeList": [
                    {
                        "attrList": [
                            {
                                "attrId": "color_pink",
                                "attrValue": "pink",
                                "optAttrMix": 0.1364,
                                "optAttrSls": 212637.0
                            },
                            {
                                "attrId": "color_purple",
                                "attrValue": "purple",
                                "optAttrMix": 0.0909,
                                "optAttrSls": 7542.0
                            },
                            {
                                "attrId": "color_off_white",
                                "attrValue": "off_white",
                                "optAttrMix": 0.0227,
                                "optAttrSls": 30006.0
                            }
                        ],
                        "attrTypeId": "color",
                        "attrTypeWgt": 0.0168
                    },
                    {
                        "attrList": [
                            {
                                "attrId": "fabric_wool",
                                "attrValue": "wool",
                                "optAttrMix": 0.1364,
                                "optAttrSls": 74618.0
                            },
                            {
                                "attrId": "fabric_polyester",
                                "attrValue": "polyester",
                                "optAttrMix": 0.0682,
                                "optAttrSls": 113571.0
                            },
                            {
                                "attrId": "fabric_organiccotton",
                                "attrValue": "organiccotton",
                                "optAttrMix": 0.2045,
                                "optAttrSls": 334509.0
                            }
                        ],
                        "attrTypeId": "fabric",
                        "attrTypeWgt": 0.126
                    }
                ],
                "fcstTtlCnt": 0.6572,
                "histTtlCnt": 1.4874,
                "keyStorId": "1175",
                "optTtlCnt": 21.9848,
                "optTtlSls": 1123705,
                "prodId": "1030101",
                "statusCode": "",
                "statusMessage": "",
                "storClusId": "us_1_52058",
                "tgtTtlCnt": 0.0
            },
            {
                "attrTypeList": [
                    {
                        "attrList": [
                            {
                                "attrId": "color_white",
                                "attrValue": "white",
                                "optAttrMix": 0.075,
                                "optAttrSls": 4875.0
                            },
                            {
                                "attrId": "color_blue",
                                "attrValue": "blue",
                                "optAttrMix": 0.075,
                                "optAttrSls": 39521.0
                            },
                            {
                                "attrId": "color_maroon",
                                "attrValue": "maroon",
                                "optAttrMix": 0.025,
                                "optAttrSls": 15163.0
                            }
                        ],
                        "attrTypeId": "color",
                        "attrTypeWgt": 0.0338
                    },
                    {
                        "attrList": [
                            {
                                "attrId": "fabric_woolsilk",
                                "attrValue": "woolsilk",
                                "optAttrMix": 0.025,
                                "optAttrSls": 15163.0
                            },
                            {
                                "attrId": "fabric_polyester",
                                "attrValue": "polyester",
                                "optAttrMix": 0.025,
                                "optAttrSls": 16810.0
                            },
                            {
                                "attrId": "fabric_merinowool",
                                "attrValue": "merinowool",
                                "optAttrMix": 0.125,
                                "optAttrSls": 46314.0
                            }
                        ],
                        "attrTypeId": "fabric",
                        "attrTypeWgt": 0.0196
                    }
                ],
                "fcstTtlCnt": 1.4811,
                "histTtlCnt": 2.8931,
                "keyStorId": "1175",
                "optTtlCnt": 39.6602,
                "optTtlSls": 401023,
                "prodId": "1030202",
                "statusCode": "",
                "statusMessage": "",
                "storClusId": "us_1_52058",
                "tgtTtlCnt": 0.0
            }
        ]
    },
    "asrtStgyRecOptHeader": {
        "responseCode": "200",
        "responseCodeMessage": "Assortment Strategy - Key Attributes data returned
Successfully"
    }

Web Service for Sales Potential

AIF Service Name: /app/rgbuaifpyapwebservice/salespotential

AP Service Name: AIFService2

Service Version: dis

The following tables shows the key fields present in the web service request and response, and the corresponding mapped measures in AP GA.

Web Service Request Input Key Mappings

Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
asrtReqIdVARCHAR2(80)Dept/Assort PeriodAssortment
Request Id
aft1asrtidt
asrtProdIdVARCHAR2(80)Dept/Assort PeriodAssortment Parent
Product
Dimension.
Department
Position Id will be
used in AP.
aft1prodkeyt
asrtPeriodVARCHAR2(80)Dept/Assort PeriodAssort Period
Dimension Id used
in AP
aft1asrtlblt
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
asrtGroupIdVARCHAR2(80)Dept/Assort PeriodAssortment Group
Id
aft1prdt
itemLevelVARCHAR2(80)Dept/Assort PeriodItem Level used in
Input - STYL
(Style), COLOR
(Style-Color) or
ITEM (SKU). AP
GA will use
COLOR for Style-
Color
aft1asrtitemt
attrTypeIdListVARCHAR2(80)Dept/Assort PeriodList of Eligible
Product Attribute
Type Id’s
aft1prdattt
storClusCntNUMBER(10,0)Dept/Assort PeriodCount of Store-
Clusters with in
product for this
request.
aft1clusidi
storClusListVARCHAR2(80)Dept/Assort PeriodCollection for
Store Cluster
afdbclusidb
storClusIdVARCHAR2(80)Dept/Assort Period/Store
Cluster
Store Cluster Idbwt2clusidt
keyStorIdVARCHAR2(80)Dept/Assort Period/Store
Cluster
One Sample Key
Store Id with in
Store Cluster
against which to
receive the data.
aft2clusidt
itemCntNUMBER(10,0)Dept/Assort PeriodCount of Items
(Style-Color) with
in the product for
this request.
afdbstatusct
itemListDept/Assort Periodafdbstatusb
itemIdVARCHAR2(80)Style-Color/Assort PeriodItem Identifierbwdvitemidt
prodIdVARCHAR2(80)Style-Color/Assort PeriodProduct Idafdvprodkeyt
NewItemVARCHAR2(80)Style-Color/Assort PeriodY/N. Flag to tell if
item if item is new
item. For New
Items it’s Y else N.
afdvphitmt
attrListVARCHAR2(80)Style-Color/Assort PeriodAttribute List at
Style-Color level
afdbprdattrb
attrTypeIdVARCHAR2(80)Style-Color/Assort
Period/Attribute Value
Attribute Type
Identifier
afdvprdattl
attrValueIdVARCHAR2(80)Style-Color/Assort
Period/Attribute Value
Attribute Value
Identifier
afdvprdattt
Web Service Request Output Key Mappings
Key/ParameterData TypeGA IntersectionDescription
Mapped Measure
asrtFitSlsPHeaderDept/Assort PeriodCollection for the
Main Request
Response Header
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
responseCodeVARCHAR2(80)Dept/Assort PeriodEx:
200 - For
Successful
Processing of
Data
aft2respcodet
responseCodeMessageVARCHAR2(255)Dept/Assort PeriodDetailed
Response
Message for
Request
aft2respcodel
asrtFitSlsPDetailDept/Assort PeriodCollection for the
Main Request
Response Details
asrtReqIdVARCHAR2(80)Dept/Assort PeriodSame asrtReqId
provided in the
input request
aft2asrtidt
asrtProdIdVARCHAR2(80)Dept/Assort PeriodSame asrtProdId
provided in the
input request
dept
asrtPeriodVARCHAR2(80)Dept/Assort PeriodSame asrtPeriod
provided in the
input request
bper
asrtGroupIdVARCHAR2(80)Dept/Assort PeriodAssortment Group
Unique Id to link
Prod/Assort
Period/Store
Clusters
aft2prdt
prodListDept/Assort PeriodCollection for List
of Products/Store
Cluster
prodIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Same product Id
provided in the
input request
scls
storClusIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Same Store
Cluster Id provided
in the input
request
bwdbclusidt
keyStorIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster
One Store Id from
the Store Cluster
stor
avgROSNUMBER(20,4)Subclass/Assort Period/
Store Cluster
Average Rate of
Sales
aft2rosv
statusCodeVARCHAR2(80)Subclass/Assort Period/
Store Cluster
Status Codeaft3statcodet
statusMessageVARCHAR2(255)Subclass/Assort Period/
Store Cluster
Status Messageaft3statcodel
itemListStyle-Color/Assort
Period/Store Cluster
Collection for Item
List
itemIdVARCHAR2(80)Subclass/Assort Period/
Store Cluster/Attribute
Value
Same Item/Style-
Color Id passed in
Input
skup
itemASlsPNUMBER(20,4)StyleColor/Assort Period/
Store Cluster
Average Sales
Potential
calculated at Item/
Style-Color Level
aft2itemaslspu
Key/ParameterData TypeGA IntersectionDescriptionMapped Measure
itemMSlsPNUMBER(20,4)StyleColor/Assort Period/
Store Cluster
Maximum Sales
Potential
calculated at Item/
Style-Color Level
aft2itemmslspu
statusCodeVARCHAR2(80)StyleColor/Assort Period/
Store Cluster
Status Codeaft2statcodet
statusMessageVARCHAR2(255)StyleColor/Assort Period/
Store Cluster
Status Messageaft2statcodel

Sample Web Service Request Call

{
    "asrtStgyRecOptHeader": {
        "requestID": "103_ap03_20230507025519",
        "rspVersion": "v1",
        "timeout": 4.0
    },
    "asrtReqId": "103_ap03_20230507025519",
    "asrtProdId": "103",
    "asrtPeriod": "ap03",
    "asrtGroupId": "103_ap03_20230507",
    "itemLevel": "COLOR",
    "attrTypeIdList": [
        "brnd",
        "color",
        "fabric"
    ],
    "storClusCnt": 2,
    "itemCnt": 2,
    "storClusList": [
        {
            "storClusId": "us_1_52056",
            "keyStorId": "1117"
        },
        {
            "storClusId": "us_1_52058",
            "keyStorId": "1175"
        }
    ],
    "itemList": [
        {
            "itemId": "1101279",
            "prodId": "1030201",
            "NewItem": "N",
            "attrList": [
                {
                    "attrTypeId": "brnd",
                    "attrValueId": "PrivateLabel"
                },
                {
                    "attrTypeId": "color",
                    "attrValueId": "red"
                },
                {
                    "attrTypeId": "fabric",
                    "attrValueId": "wool"
                }
            ]
        },
        {
            "itemId": "1101282",
            "prodId": "1030201",
            "NewItem": "N",
            "attrList": [
                {
                    "attrTypeId": "brnd",
                    "attrValueId": "PrivateLabel"
                },
                {
                    "attrTypeId": "color",
                    "attrValueId": "green"
                },
                {
                    "attrTypeId": "fabric",
                    "attrValueId": "cotton"
                }
            ]
        }
    ]
}

Sample Web Service Response Call

                        "itemASlsP": 400,
                        "itemMSlsP": 500,
                        “statusCode”: Null,
                        “statusMessage”: Null
                    },
                    {
                       "itemId": "1101282",
                       "itemASlsP": 500,
                       "itemMSlsP": 600,
                       “statusCode”: Null,
                       “statusMessage”: Null
                    }
                ],
                "keyStorId": "1117",
                "prodId": "1030201",
                “statusCode”: Null,
                “statusMessage”: Null,
                "storClusId": "us_1_52056"
            },
            {
                "avgROS": 14000,
                "itemList": [
                    {
                        "itemId": "1101279",
                        "itemASlsP": 500,
                        "itemMSlsP": 600,
                        “statusCode”: Null,
                        “statusMessage”: Null
                    },
                    {
                        "itemId": "1101282",
                        "itemASlsP": 600,
                        "itemMSlsP": 700,
                        “statusCode”: Null,
                        “statusMessage”: Null
                    }
                ],
                "keyStorId": "1175",
                "prodId": "1030201",
                “statusCode”: Null,
                “statusMessage”: Null,
                "storClusId": "us_1_52058"
            }
        ]
    },
    "AsrtFitSlsPHeader": {
        "responseCode": 200,
        "responseCodeMessage": "Assortment Fit - Sales Potential data returned
Successfully"
    }
}

Implementation Steps with RAP Integration

If RAP integration is enabled in the environment (that is, if the customer is going to get data from RMFCS using RDX integration), follow these steps for implementation. The steps assume that RPAS, RASL, UI, and RDX are already deployed:

1. Run the Batch Process in RAP in Retail Insights (RI) to load the required initial data into the RDX staging tables.

2. Upload any application-specific hierarchy files and data files that are not coming from RDX into Object Storage.

3. Once the AP Cloud Service environment is provisioned, use the bootstrap Build Application task to build the application and use the batch task as set_rdx to just set the Enable RDX Boolean before the initial batch, or run post_hier to enable the RDX Boolean and load/import only the hierarchy files, or run postbuild_rdx to enable the RDX and to load/import initial hierarchy and data files and also run the initial batch. Batch step post_hier can also be run from OAT, to enable the RDX and load the available hierarchy files after building the domain. Use postbuild only if planning to load and use only the GA data set.

4. Schedule the regular weekly flow in the RI, AIF, and Planning applications in JOS/POM to interface the initial data into the application to get data from both RDX and Object Storage.

Note

At least post_hier or postbuild_rdx should be run once with at least the calendar hierarchy file before trying to run the weekly batch using JOS/POM.


In this guide

  • 3 RAP IntegrationMerchandise Financial Planning Cloud Service Implementation Guide · shares AREA_NAME, ATTR_DESC, ATTR_ID, ATTR_VALUE
  • 1 MFP Batch Task AdministrationMerchandise Financial Planning Cloud Service Administration Guide · shares VW_LOC_DATA, VW_SATR_HIER, W_PDS_CALENDAR_D, W_PDS_INVRC_IT_LC_WK_A
  • 1 APCS Batch Task AdministrationAssortment Planning Cloud Service Administration Guide · shares VW_CLRH_HIER, VW_SATR_HIER, W_PDS_CALENDAR_D, W_PDS_ORGANIZATION_D
  • 5 RAP IntegrationIPOCS-Demand Forecasting and IPOCS-LAR Implementation Guide · shares AREA_NAME, ATTR_WGT, BRAND_NAME, CHAIN_NAME
  • 12 Pre-Pack OptimizationAI Foundation Implementation Guide · shares CAL_DATE, EOH_COST_AMT, EOH_QTY, EOH_RTL_AMT
  • 2 AI Foundation Data Standalone ProcessesAI Foundation Operations Guide · shares AP_ASSORT_GROUP_EXP, AP_PLAN1_EXP, W_PDS_CALENDAR_D, W_PDS_CUSTSEG_D