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.
10 Size Profiles
This chapter describes the Size Profiles (SP) Cloud Service module.
Overview
Size Profiles (SP) is a module under AIF Profile Sciences and is used to estimate the distribution of demand across different sizes (size profile) for different merchandise and location levels.
Size profile is estimated at different levels of merchandise and location. The lowest level of estimation is style-color (for merchandise) and store/warehouse (for location). Size profiles may also be estimated at higher levels of aggregation on both the merchandise and location dimensions (for example, at subclass-store or style/color-region), depending on the retailer’s requirements.
Data Requirements
This section provides information about setting up the data that the SP application uses, including guidelines regarding the expectations for the data element requested and where it is used. Information about these files can be found in Oracle Retail Insights Cloud Service Suite/ Oracle Retail Analytics and Planning Cloud Services Data Interface.
Most of the AI Foundation Cloud Services (AIF) data is pushed in two-step process.
1. First, data is loaded, using CSV and W_ interfaces and jobs in the AIF DATA standalone schedule in POM. Then, RADM_REFRESH_JOB must be run to refresh the table statistics before any AIF Apps job is run (though REFRESH_RADM_JOB is automatically executed as part of most ad hoc processes in AIF Data).
2. Second, appropriate AIF Apps jobs are used to push data into AIF applications. At the time of implementation, the user will only use ADHOC jobs, not any batch jobs. Batch jobs (described in “POM Jobs”) are necessary to put the system on a batch schedule.
Note that some of the jobs require relevant configuration parameters to be specified with clientspecific values. If incorrect configuration values are used, a job may run without errors, but will not produce the desired data in the target tables. If the client or implementation team wants to view the progress of the job or any errors in order to file an SR, then AIF provides database logging in a table called RSE_LOG_MSG.In addition, analytic logs generated by the programs that run optimization can be found in RSE_ANALYTIC_LOG_MSG. More details are provided in the Troubleshooting section in this chapter.
Hierarchy Data
The three types of hierarchies are Location Hierarchy, Merchandise Hierarchy, and Calendar Hierarchy.
- Location Hierarchy (ORGANIZATION.csv). An example of location hierarchy is: CHAIN ’ COUNTRY ’ REGION ’ DISTRICT ’ STORE.
Note that the E-com channel can be defined as part of the location hierarchy. Relevant interfaces are: W_INT_ORG_ATTR_DS, W_INT_ORG_DHS, W_INT_ORG_DS. These are all loaded using the ORGANIZATION.csv file.
- Merchandise Hierarchy (PRODUCT.csv). An example of merchandise hierarchy is as follows: CHAIN ’ COMPANY/BANNER ‘DIVISION ’ DEPARTMENT ‘CLASS ’ SUBCLASS ’ STYLE ’ COLOR ’ SIZE (SKU). The Size Profiles application is used for fashion apparel. Therefore, it is expected that the extended merchandise hierarchy is provided, that is, Style and Color are provided through the relevant interfaces.
The STYLE, COLOR and SIZE SKUs are expected to be provided in the W_PRODUCT_DS interface, while the levels between CHAIN and Subclass are provided via W_PROD_CAT_DHS interface. In addition, there must be consistency between the levels provided when using an extended hierarchy. W_PRODUCT_ATTR_DS is used to indicate the relationship between Style, Style/Color, and Style/Color/Size for an extended hierarchy. All of these tables will be populated when providing a PRODUCT.csv file as a foundation file input.
Here are the specific fields:
PRODUCT_ATTR13_NAME = PROD_NUM for the Style (for example, 0000190086820900)
PRODUCT_ATTR14_NAME = PROD_NUM for the Style/Color (for example, 190086834203)
PRODUCT_ATTR15_NAME = PROD_NUM for the Style/Color/Size (for example, 1975699).
The value of PROD_NUMs is the same as the value in the W_PRODUCT_DS.PROD_NUM interface.
Here is what this looks like:
Table 10-1 Hierarchy Data
PROD_NUM PRODUCT_ATTR13_N PRODUCT_ATTR14_N PRODUCT_ATTR15_N AME AME AME STYLE_PROD_NU STYLE_PROD_NUM M STY/ STYLE_PROD_NUM STY/COL_PROD_NUM COL_PROD_NUM STY/ STYLE_PROD_NUM STY/COL_PROD_NUM STY/ COL_SIZ_PROD_N COL_SIZ_PROD_NUM UM
Note
For Size Profiles Cloud Services, the Extended Product Hierarchy must be loaded. . Prior to loading data into AIF tables, make sure that the configuration LOAD_EXTENDED_PROD_HIER is set to “Y”. This can be done using Manage System Configurations (as described in Control and Tactical Center) and then selecting RSE_CONFIG from the drop-down list.
Note
The mapping of columns and the example mentioned above for product hierarchy can be different, depending on the source of the data. For example, if the data is loaded from RMS Cloud, the mapping will be as follows:
-
PRODUCT_ATTRPRODUCT_ATTR14_NAME = sku ID (a.k.a. style/color/ size)13_NAME = sku parent ID (a.k.a.style)
- PRODUCT_ATTR14_NAME = sku ID (a.k.a. style/color/size)
-
PRODUCT_ATTR16_NAME = differentiator ID (for example color, or any differentiator that is used in-between style and sku).
-
Prior to loading data into AIF tables, make sure that the configuration EXTENDED_HIERARCHY_SRC is set properly according to the source of data which can be RMS or non-RMS.
-
Calendar Hierarchy. This is one of the core hierarchies. The retailer can specify the calendar depending on their business requirements (for example, fiscal calendar). The relevant interface for this is W_MCAL_PERIOD_D, loaded using CALENDAR.csv file.
Sales Data
Historical sales data is required at the sku-store-week level and must be provided through SALES.csv file (W_RTL_SLS_TRX_IT_LC_DY_FS staging table). If the sales transaction data is provided, it will be aggregated by the application to the sku-store-level. It is necessary that the sales transaction data be provided at the lowest level of product hierarchy (that is, the level in RSE_HIER_LEVEL that has LEAF_NODE_FLG = ‘Y’ for HIER_TYPE_ID = 3).
When the system is in production, the latest incremental sales data is obtained as part of the batch process.
Inventory Data
Two methods are available for generating size profiles. For the Optimization method, historical inventory must be provided at the sku-store-week level. To generate profiles using the Normalize method, inventory data is not required. The Normalized method will not perform most of the data pre-processing stages and will not use a statistical method for estimating profiles. Therefore, the normalized profiles will not be as accurate as optimized profiles specially for categories with many stock-out weeks. Historical weekly inventory data can be specified through INVENTORY.csv
Product Attributes
Product attributes are optional. If provided, they can be used in the escalation of the profiles (which is a means of clustering style-colors and data pooling to achieve more robust size profiles). The SP supports selecting up to three product attribute for the escalation. Product attributes must use W_RTL_ITEM_GRP1_DS since it can support any number of attributes.
Product Images Data
Product images that are available on a customer-hosted web server can be viewed in the Size Profiles UI. The W_RTL_PRODUCT_IMAGE_DS.dat interface contains a column called
PRODUCT_IMAGE_ADDR, which can contain the full URL to an image of the product. This URL must be in the following format:
http[s]://servername[:port]/location/filename.extension
For example:
PRODUCT_IMAGE_NAME = imagename.png
PRODUCT_IMAGE_ADDR = http://hostname/url/imagename.png
PRODUCT_IMAGE_DESC= Short description of the image
The Size Profiles application running in the cloud does not directly access these images, so there is no need to expose these images outside of the customer’s firewall. As long as the user of the SP application has access to the URL while running the SP application, then the user’s web browser will be able to resolve the URL and retrieve the images for display when the user chooses this option. The images must be in a file format that the web browser can display. Since the images shown in the UI are small, these images do not need to be high quality images. The size of the image files will affect the time it takes to render them.
Season
The selected season for the run is used in two ways:The historical data period is set based on the start/end date of the selected season, one year ago. In addition, size profiles are generated for products that are selected for the run and are mapped to the selected season.
The season definition and the item-season mapping are required if the user wants to filter the historical data based on a specific historical season. Alternatively, user can select “no season” when setting up the run. In that case, they will be able to specify any start/end date for the historical period and all items will be considered in the data processing as long as they had any sales within those periods.
The season definition can be loaded through SEASON.csv (staging files: W_RTL_SEASON_DS and W_RTL_PHASE_DS). In addition, the W_DOMAIN_MEMBER_LKP_TL should have data for DOMAIN_CODE of SEASON and PHASE. The mapping between items and season is also required and can be loaded through PROD_SEASON.csv (staging file W_RTL_SEASON_PHASE_IT_DS).
Size and Size Range Data
The mapping between SKUs and sizes, as well as the mapping between sizes and size ranges, are both required. This data can be provided through DIFF_GROUP.csv (staging files W_RTL_ITEM_GRP1_DS, W_RTL_DIFF_GRP_DS, and W_RTL_DIFF_GRP_D_TL). It is also necessary to set the value of SPO_DIFF_TYPE in RSE_CONFIG to be the same as the diff_type that is in W_RTL_DIFF_GRP_D for size attribute.
In addition to these two interfaces, it is expected that the column prod_attr_grp_id will be populated in W_RTL_ITEM_GRP1_D for the PROD_GRP_ TYPE that is associated with Size.
For the jobs that must be run to load data to above tables, see “Batch and Ad-Hoc Jobs”.
Note
It is necessary that all attributes, including the Size attribute, are provided at the lowest level of product hierarchy (that is, the level in RSE_ HIER_LEVEL that has LEAF_NODE_FLG = Y).
Configurations
Table 11-2 shows the configurations that must be provided at the time of implementation. These configurations can be viewed and modified using Strategy & Policy Management under Control & Tactical Center. In this dashboard, you navigate to Manage System Configurations , select ALL for application, RSE_CONFIG for table, and filter the table by APPL_CODE=SPO.
Table 10-2 Configurations
| PARAM_NAME | PARAM_VALU E | DESCR |
|---|---|---|
| DEFAULT_APPL_USER | SPO_BATCH_U SR | User identifier to be used for batch activities that require user tracking. |
| RECENT_RUNS_DAYS_BACK | 30 | Number of days following creation after which successful runs do not appear in corresponding left-hand-side UI panel. |
| SPO_DIFF_TYPE | S | Diff Type value to be used for SIZE diff |
| SPO_DIFF_TYPE_COLOR | C | Diff Type value to be used for COLOR diff |
| SPO_EXPORT_FETCH_SIZE | 1000 | Fetch Size for exporting records using SPO User Interface Export To Excel. |
| SPO_LOC_HIER_PROCESSING_ LVL | 6 | Level Identifier for the level of the Location Hierarchy at which we process Size Profile. Default 6 is to process at STORE Level. |
| SPO_LOC_HIER_TYPE | 2 | Hierarchy Type Identifier for the Location Hierarchy Type. |
| SPO_PROD_HIER_PARENT_LVL | 8 | Level Identifier for the level of the Product Hierarchy of the SKU-Parent. Default 8 is the STYLE-COLOR Level. |
| SPO_PROD_HIER_PROCESSING _LVL | 9 | Level Identifier for the level of the Product Hierarchy at which we process Size Profile. Default 9 is to process at SKU Level. |
| SPO_PROD_HIER_TYPE | 3 | Hierarchy Type Identifier for the Product/ Merchandise Hierarchy Type. |
| SPO_PROF_EXP_LOC_LVL | 4 | Mark USER_BY_AIP=Y Where active Season Size Profiles created at Store level in Export DB view |
| SPO_PURGE_ALL_RUNS | N | Indicates to clean up all run data. |
| SPO_PURGE_RETENTION_DAYS | 30 | Number of days to wait before permanently deleting run data. |
| SPO_NO_SEASON_START_DATE | Override the start date of historical data when No Season option is selected. If this value is provided, the start date for the No Season record in SPO_SEASON is set to this value. If this is NULL, the start date is driven based on the earliest week available in RSE_CAL_HIER. Default is NULL but if provided, date format should be YYYYMMDD. |
Table 10-2 (Cont.) Configurations
| PARAM_NAME | PARAM_VALU E | DESCR |
|---|---|---|
| SPO_NO_SEASON_END_DATE | Override the end date of historical data when No Season option is selected. If this value is provided, the end date for the No Season record in SPO_SEASON is set to this value. If this is NULL, the end date is driven based on the latest week available in RSE_CAL_HIER. Default is NULL but if provided, date format should be YYYYMMDD. | |
| MIN_SLS_PROF_OVER_CORR_A LERT | 0.001 | Exclude sizes with low sales contribution from over-correction alert: A value greater than 0 and less than or equal to 1. This is the minimum value of escalation level sales profile that a size should have to be considered in the over correction alert check. |
| SPO_SALES_TYPE | RPC | Indicates the type of historical sales that goes into all stages of size profile generation. Valid values are RPC (regular+promo+clearance), RP (regular+promo) and R (regular). |
| SPO_GEN_WH_PROF_FLG | N | A Y/N Flag indicating whether size profiles should be generated for virtual Warehouses. |
The configurations that are used by the Size Profiles science algorithm are set when creating a run in the UI. Each configuration has a default value that is defined in
SPO_DFLT_PARAMETER. The default values can be viewed and modified using the Manage System Configuration screen. Apart from the algorithm parameters that are visible in the UI and can be set when creating a run, there are few high-level configurations that can be managed only in the Manage System Configuration screen. The following table shows these configurations.
Configurations of the Export File
In addition to the global configurations mentioned above, the merchandise and location levels for export ed profiles must be configured in SPO_EXPORT_CONFIG table. You can modify the configurations in this table using Manage System Configurations (as described in Control and Tactical Center). By default, this table will contain the values shown in the following table. The export file (spo_size_profile.csv) contains approved profiles for all intersections that have current_flg = Y. To disable a certain intersection, you can set the current_flg to N. The export file also has few indicator columns (USED_BY_ALLOCATION, USED_BY_PLM, USED_BY_AIP) that can be used by a downstream application to filter data when reading from the file. To configure an intersection for export without mapping it to any application, you can enter the app_name column as NONE.
Logic of Profiles Spread Down in the Export File
If the configured export level is SKU-parent/location (i.e. style-color/location), no spread down will be applied. The export file will contain style-color/location profiles only if there is a size profile run at the same level and profiles from that run are approved.
If the configured export level is anything other than SKU-parent/location (i.e. style-color/ location), approved profiles that are at the configured level, will be exported as-is. If there is no
approved profile that match the configured level,, the export process will find the profile at levels above the configured level and will obtain the profile from closest merchandise and location level.
To generate size profiles for warehouse locations, users should select that option when setting up the run in the UI. When the option is selected for a run, profiles will be generated for all virtual warehouse locations. The input data to the profile estimation for warehouses is the sum of outbound transfer and allocations at style-color/warehouse/week level.
Note
For AIP applications, profiles that are at the configured intersection and for the current active season will have USED_BY_AIP as Y.
| Prod Level Name | Loc Level Name | App Name | Current Flg |
|---|---|---|---|
| SBC | LOCATION | AIP | Y |
| COLOR | LOCATION | ALLOCATION | Y |
| SBC | LOCATION | ALLOCATION | Y |
| CLS | LOCATION | ALLOCATION | Y |
| DEPT | LOCATION | ALLOCATION | Y |
| COLOR | REGION | PLM | Y |
Size Profiles for Warehouse Locations
To generate size profiles for warehouse locations, users should select that option when setting up the run in the UI. When the option is selected for a run, profiles will be generated for all virtual warehouse locations. The input data to the profile estimation for warehouses is the sum of outbound transfer and allocations at style-color/warehouse/week level.
Note
Before creating a run with the option of warehouse profiles for the first time, the job for size range mapping must run so that the mapping for warehouse locations is generated. After the job runs once, the size range mapping for warehouse locations will be available and will just be updated in the subsequent execution of that job. If the daily batch jobs are enabled, the job will run automatically. Alternatively, you can run SPO_MASTER_ADHOC_JOB wit parameter -l.
Merchandise and Location Scope of the Size Profile Runs
When creating the optimization runs in the UI, user will have to specify the merchandise and location nodes for the run. The selection is made in a hierarchical way where for example user will select first the department(s), then class(es), and so on. For higher levels like department, user can select multiple values. For lower levels like style, selecting multiple values is not allowed and only possible value to select is “All”. There are few configurations that control the levels that are shown in the UI and the lowest level that multi-select is allowed. These configurations which are listed below should not be changed frequently. If there is a need to change any of these configurations, it is strongly recommended to change them only once (ideally during implementation).
-
MERCH_FILTER_START_LEVEL_ID: First merchandise level in the merchandise filter drop-down list.
-
MERCH_FILTER_END_LEVEL_ID: Last merchandise level in the merchandise filter dropdown list.
-
LOC_FILTER_START_LEVEL_ID: First location level in the location filter drop-down list.
-
• LOC_FILTER_END_LEVEL_ID: Last location level in the location filter drop-down list.
-
MERCH_FILTER_MULTISEL_ALL_LEVEL_ID: First merchandise level that selecting multiple nodes is not allowed. Only the “All” value can be selected.
-
LOC_FILTER_MULTISEL_ALL_LEVEL_ID: First location level that selecting multiple nodes is not allowed. Only the “All” value can be selected.
Data Output
The following exports are available under ORASE_WEEKLY_EXTRACT.ZIP. The content of the export files will depend on the source of data (whether it’s according to the data format in RMS or not).
Table 10-3 Data Output Exports
| Export File Name | Value of EXTENDED_HIERARC HY_SRC in RSE_CONFIG | View Name | Content |
|---|---|---|---|
| spo_size_profile.csv | NON-RMS | SPO_SZ_PROF_EXPO RT_VW | Approved Profiles at lowest level (style-color/ location) and higher level(s). |
| spo_custom_export.csv | NON-RMS | SPO_EXPORT_DATA_V W | Size profiles at product group level as defined in rse_prod_attr_group. |
Batch and Ad-Hoc Jobs
The following batch and ad-hoc jobs are responsible for loading the size, size range, and season data into SPO.
Table 10-4 Data-Loading Batch and Ad-Hoc Jobs
| JobName | Description | RmsBatch | ParameterValue | Modules |
|---|---|---|---|---|
| SPO_MASTER_AD HOC_JOB | Description Run SPO master script | spo_master.ksh | SPO_Interfaces | |
| SPO_SIZE_ETL_S TART_JOB | Start job for size related ETLs | rse_process_state_ update.ksh | SPO_SIZE_ETL_P ROCESS Start | SPO_Batch |
| SPO_SIZE_ETL_S ETUP_JOB | Setup job for size ETL | spo_size_setup.ksh | SPO_Interfaces |
Table 10-4 (Cont.) Data-Loading Batch and Ad-Hoc Jobs
| JobName | Description | RmsBatch | ParameterValue | Modules |
|---|---|---|---|---|
| SPO_SIZE_ETL_P ROCESS_JOB | Process job for size ETL | spo_size_process.k sh | SPO_Interfaces | |
| SPO_SIZE_ETL_E ND_JOB | End job for size related | rse_process_state_ update.ksh | SPO_SIZE_ETL_P ROCESS End | SPO_Batch |
| SPO_PROD_LOC_ SIZE_ETL_START _JOB | Start job for product/location/ size ETLs | rse_process_state_ update.ksh | SPO_PROD_LOC_ SIZE_ETL_PROCE SS Start | SPO_Batch |
| SPO_SIZE_RANG E_ETL_SETUP_JO B | Setup job for size range ETL | spo_size_range_se tup.ksh | SPO_Interfaces | |
| SPO_SIZE_RANG E_ETL_PROCESS _JOB | Process job for size range ETL | spo_size_range_pr ocess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_ETL_SETU P_JOB | sub size range ETL | spo_sub_size_rang e_setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_ETL_PROC ESS_JOB | Process job for sub size range ETL | spo_sub_size_rang e_process.ksh | SPO_Interfaces | |
| SPO_SIZE_MAP_ ETL_SETUP_JOB | Setup job for size map ETL | spo_size_map_set up.ksh | SPO_Interfaces | |
| SPO_SIZE_MAP_ ETL_PROCESS_J OB | Process job for size map ETL | spo_size_map_pro cess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_ MAP_ETL_SETUP _JOB | sub size map ETL | spo_sub_size_map _setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_ MAP_ETL_PROCE SS_JOB | Process job for sub size map ETL | spo_sub_size_map _process.ksh | SPO_Interfaces | |
| SPO_PROD_SIZE _ETL_SETUP_JOB | Setup job for product/size ETL | spo_prod_size_set up.ksh | SPO_Interfaces | |
| SPO_PROD_SIZE ETL_PROCESS JOB | Process job for product/size ETL | spo_prod_size_pro cess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_PROD_LO C_ETL_SETUP_J OB | Setup job for sub size/range/product/ location ETL | spo_sub_sz_range _pr_lc_setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_PROD_LO C_ETL_PROCESS _JOB | Process job for sub size/range/product/ location ETL | spo_sub_sz_range _pr_lc_process.ksh | SPO_Interfaces | |
| SPO_PROD_LOC_ SIZE_ETL_END_J OB | End job for product/ location/size ETLs | rse_process_state_ update.ksh | SPO_PROD_LOC_ SIZE_ETL_PROCE SS End | SPO_Batch |
| SPO_SIZE_ETL_S ETUP_ADHOC_JO B | Ad hoc setup job for size ETL | spo_size_setup.ksh | SPO_Interfaces |
Table 10-4 (Cont.) Data-Loading Batch and Ad-Hoc Jobs
| JobName | Description | RmsBatch | ParameterValue | Modules |
|---|---|---|---|---|
| SPO_SIZE_ETL_P ROCESS_ADHOC _JOB | Ad hoc process job for size ETL | spo_size_process.k sh | SPO_Interfaces | |
| SPO_SIZE_RANG E_ETL_SETUP_A DHOC_JOB | Ad hoc setup job for size range ETL | spo_size_range_se tup.ksh | SPO_Interfaces | |
| SPO_SIZE_RANG E_ETL_PROCESS _ADHOC_JOB | Ad hoc process job for size range ETL | spo_size_range_pr ocess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_ETL_SETU P_ADHOC_JOB | Ad hoc setup job for sub size range ETL | spo_sub_size_rang e_setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_ETL_PROC ESS_ADHOC_JOB | Ad hoc process job for sub size range ETL | spo_sub_size_rang e_process.ksh | SPO_Interfaces | |
| SPO_SIZE_MAP_ ETL_SETUP_ADH OC_JOB | Ad hoc setup job for size map ETL | spo_size_map_set up.ksh | SPO_Interfaces | |
| SPO_SIZE_MAP_ ETL_PROCESS_A DHOC_JOB | Ad hoc process job for size map ETL | spo_size_map_pro cess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_ MAP_ETL_SETUP _ADHOC_JOB | Ad hoc setup job for sub size map ETL | spo_sub_size_map _setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_ MAP_ETL_PROCE SS_ADHOC_JOB | Ad hoc process job for sub size map ETL | spo_sub_size_map _process.ksh | SPO_Interfaces | |
| SPO_PROD_SIZE _ETL_SETUP_AD | Ad hoc setup job for product/size | spo_prod_size_set up.ksh | SPO_Interfaces | |
| HOC_JOB | ETL | NE | ||
| SPO_PROD_SIZE ETL_PROCESS ADHOC_JOB | Ad hoc process job for product/size ETL | spo_prod_size_pro cess.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_PROD_LO C_ETL_SETUP_A DHOC_JOB | Ad hoc setup job for sub size/range/ product/location ETL | spo_sub_sz_range _pr_lc_setup.ksh | SPO_Interfaces | |
| SPO_SUB_SIZE_R ANGE_PROD_LO C_ETL_PROCESS _ADHOC_JOB | Ad hoc process job for sub size/range/ product/location ETL | spo_sub_sz_range _pr_lc_process.ksh | SPO_Interfaces | |
| RSE_SEASON_PH ASE_ITEM_ETL_S TART_JOB | Start job for season/phase/item ETL | rse_process_state_ update.ksh | RSE_SEASON_PH ASE_ITEM_ETL_P ROCESS Start | SPO_Batch |
| RSE_SEASON_PH ASE_ITEM_ETL_L OAD_JOB | Load job for season/phase/item ETL | rse_season_phase _item_load.ksh | SPO_Interfaces | |
| RSE_SEASON_PH ASE_ITEM_ETL_E ND_JOB | End job for season/ phase/item ETL | rse_process_state_ update.ksh | RSE_SEASON_PH ASE_ITEM_ETL_P ROCESS End | SPO_Batch |
Table 10-4 (Cont.) Data-Loading Batch and Ad-Hoc Jobs
JobName Description RmsBatch ParameterValue Modules SPO_SEASON_LO SPO_SEASON_LO rse_process_state_ SPO_SEASON_LO SPO_Batch AD_START_JOB AD_START_JOB update.ksh AD_PROCESS Start SPO_SEASON_LO SPO_SEASON_LO spo_season_load.k SPO_Interfaces|| AD_JOB AD_JOB sh SPO_Interfaces_C NE SPO_SEASON_LO SPO_SEASON_LO rse_process_state_ SPO_SEASON_LO SPO_Batch AD_END_JOB AD_END_JOB update.ksh AD_PROCESS End
The following jobs are for exporting the outputs.
Table 10-5 Output Exporting Batch and Ad-Hoc Jobs
JobName Description RmsBatch ParameterValue Modules SPO_EXPORT_ST SPO_EXPORT_ST rse_process_state_ SPO_PROD_SIZE SPO_Batch ART_JOB ART_JOB update.ksh LOAD_PROCESS Start SPO_EXPORT_PR SPO_EXPORT_PR spo_export_prep.ks SPO_Export EP_JOB EP_JOB h SPO_SZ_PROF_E SPO_SZ_PROF_E spo_sz_prof_expor #SysSPO_Export XPORT_JOB XPORT_JOB t.ksh Opt.SPO_HOME/ data/outfile/ spo_sz_prof_expor t.csv SPO_SZ_PROF_E SPO_SZ_PROF_E spo_sz_prof_expor #SysSPO_Export XPORT_ADHOC_J XPORT_ADHOC_J t.ksh Opt.SPO_HOME/ OB OB data/outfile/ spo_sz_prof_expor t.csv SPO_EXPORT_EN SPO_EXPORT_EN rse_process_state SPO_PROD_SIZE SPO_Batch D_JOB D_JOB update.ksh _LOAD_PROCESS End SPO_EXPORT_PR SPO_EXPORT_PR spo_export_prep.ks SPO_Export EP_ADHOC_JOB EP_ADHOC_JOB h SPO_CUSTOM_E Extract customized spo_custom_export SPO_Export XPORT_JOB export data .ksh SPO_CUSTOM_E Ad hoc job to spo_custom_export SPO_Export XPORT_ADHOC_J extract customized .ksh OB export data
The following jobs can be used to purge runs. The parameters that control this purge process are SPO_PURGE_RETENTION_DAYS and SPO_PURGE_ALL_RUNS in the RSE_CONFIG table. The ad hoc job can take an input that acts as an override to the
SPO_PURGE_RETENTION_DAYS value. When SPO_PURGE_ALL_RUNS = Y, then both the batch and ad hoc jobs delete data for all size profile runs, irrespective of the SPO_PURGE_RETENTION_DAYS value.
Table 10-6 Purge Run Jobs
| JobName | Description | RMSBatch | ParameterValue | Modules |
|---|---|---|---|---|
| SPO_PURGE_RU N_START_JOB | Start job for purging SPO run data | rse_process_state_ update.ksh | SPO_PURGE_RU N_PROCESS Start | SPO_Batch |
| SPO_PURGE_RU N_JOB | Purge job for SPO run data | spo_purge_run_dat a.ksh | SPO_Interfaces | |
| SPO_PURGE_RU N_END_JOB | SPO run data | rse_process_state_ update.ksh | SPO_PURGE_RU N_PROCESS End | SPO_Batch |
| SPO_PURGE_RU N_ADHOC_JOB | Ad hoc purge job for SPO run data | spo_purge_run_dat a.ksh | SPO_Interfaces |
In this guide
- Guide: AI Foundation Implementation Guide
- Previous: 1 Introduction
- Next: 11 Portfolio Optimization
Related chapters
- 15 Inventory Planning Optimization — AI Foundation Implementation Guide · shares
DHOC_JOB,EXTENDED_HIERARCHY_SRC,LOAD_EXTENDED_PROD_HIER,PRODUCT_ATTR13_NAME - 8 Size Profiles — AI Foundation User Guide · shares
RSE_CAL_HIER,SPO_DFLT_PARAMETER,SPO_NO_SEASON_END_DATE,SPO_NO_SEASON_START_DATE - 12 Pre-Pack Optimization — AI Foundation Implementation Guide · shares
APPL_CODE,DIFF_GROUP,EXTENDED_HIERARCHY_SRC,HIER_LEVEL - 5 AI Foundation Data Standalone Process Flows — AI Foundation Operations Guide · shares
DIFF_GROUP,PROD_SEASON,W_DOMAIN_MEMBER_LKP_TL,W_INT_ORG_ATTR_DS - 2 AI Foundation Data Standalone Processes — AI Foundation Operations Guide · shares
DIFF_GROUP,PROD_SEASON,W_DOMAIN_MEMBER_LKP_TL,W_INT_ORG_ATTR_DS - 3 AI Foundation Data Batch Architecture — AI Foundation Operations Guide · shares
REFRESH_RADM_JOB,W_PRODUCT_DS,W_PROD_CAT_DHS,W_RTL_ITEM_GRP1_D