| Oracle Retail AI Foundation Cloud Services Implementation Guide Release 22.2.401.0 F72321-01 |
|
 Previous |
 Next |
| Oracle Retail AI Foundation Cloud Services Implementation Guide Release 22.2.401.0 F72321-01 |
|
Previous |
Next |
This chapter describes the Control and Tactical Center, where an administrative user can access and manage configurations for different applications.
Under the Control and Tactical Center, a user can access Strategy and Policy Management, which is the central place for managing the configurations of different applications and for setting up and configuring the demand forecasting runs. In addition, the modules for managing product attributes (Attribute Extraction and Attribute Binning) as well as the link for managing web service-related credentials can be also found under the Control and Tactical Center.
Depending on the role, a user will see one or multiple of the following links, as shown in Figure 13-1. Typically, the administrative user has access to all of the following.
Strategy and Policy Management
Manage Credential Stores
Attribute Extraction
Attribute Binning
In Strategy and Policy Management, a user can edit the configurations of different applications using the Manage System Configurations screen. Only the tables that are editable can be accessed in this screen. Within each table, one or multiple columns are editable and a user can override the values in those columns.
Manage Forecast Configurations can be used to set up, manage, and configure the demand forecasting runs for different applications such as Offer Optimization (OO), Inventory Optimization (OO), Retail Demand Forecasting (RDF), and Merchandise Financial Planning (MFP).
To configure the forecast process for MFP, complete the following two steps:
Use the Manage System Configurations screen to review and modify the global configurations in RSE_CONFIG. For further details, see "Configuration Updates". The relevant configurations in RSE_CONFIG that must be reviewed and edited as required are listed in Table 13-1.
Table 13-1 Configurations
| APPL CODE | PARAM NAME | PARAM VALUE | DESCR |
|---|---|---|---|
|
RSE |
EXTENDED_HIERARCHY_SRC |
Default value is NON-RMS. |
Data source providing extended hierarchy data RMS/NON-RMS. |
|
RSE |
LOAD_EXTENDED_PROD_HIER |
Default value is Y. If the product hierarchy data had nine levels, keep this value as Y. If it has seven levels, change this value to N. |
Y/N Value. This parameter is used by the product hierarchy ETL to determine if the extended product hierarchy is required. |
|
PMO |
PMO_PROD_HIER_TYPE |
Default value is 3. If the product hierarchy data has nine levels (i.e., it has an extended hierarchy), keep this value as 3. If it has seven levels, change this value to 1. |
The hierarchy ID to use for the product (installation configuration). |
|
RSE |
PROD_HIER_SLSTXN_HIER_LEVEL_ID |
Default value is 9. |
This parameter identifies the hierarchy level at which sales transactions are provided (7-Style, 8-Style/color, or 9 Style/color/Size). It must match the extended hierarchy leaf level. |
|
PMO |
PMO_AGGR_INVENTORY_DATA_FLG |
Default value is Y. |
Specifies if inventory data is present and if it must be used when aggregating activities data. Set this value to N if inventory data is not loaded. (Inventory data is not required for MFP forecasting but it is required for other applications such as Offer Optimization, Inventory Optimization and Retail Demand Forecasting.) |
Use the Manage Forecast Configurations screen to set up the forecast runs for MFP, as follows.
In Manage Forecast Configurations, start by setting up a run type in the Setup train stop. Click the + icon above the table and fill in the fields in the pop-up. For MFP forecasting, the forecast method must be selected as Automatic Exponential Smoothing. You must create a run type for each forecast measure/forecast intersection combination that is required for MFP.
Once you are done with setting up the run types, click Start Data Aggregation in the Setup train stop. Select all the run types that were created and click Submit. When the aggregation is complete, the aggregation status will change to Complete. At this point, ad-hoc test runs and batch runs can be created and executed to generate a forecast.
Once you have finished setting up the run types, click Start Data Aggregation in the Setup train stop. Select all the run types that were created and click Submit. When the aggregation is complete, the aggregation status will change to Complete. At this point, ad-hoc test runs and batch runs can be created and executed to generate a forecast.
To create an ad-hoc run, go to the Test train stop. First, click a run type in the top table and then click the + icon in the bottom table to create a run. In the Create Run pop-up, you can change the configurations parameters related to estimation process and forecast process in their respective tabs. For example, if you want to test a run using the Bayesian method, edit the Estimation Method parameter in the Estimation tab using the Edit icon above the table. After modifying and reviewing the configuration parameters, click Submit to start the run. Once the run is complete, the status will change to Forecast Generation Complete.
Doing test runs is an optional step. In addition to that, you must modify and review the configurations of the run type, activate the run type, enable auto-approve, and map the run type to the downstream application (in this case to MFP). In the Manage train stop, select a row, click Edit Configurations Parameters, and edit the estimation and forecast parameters as necessary. Once you are done, go to Review tab and click Validate and then close tab.
|
Note: If the run type is active, you will only be able to view the parameters. In order to edit the parameters, the run type must be inactive. |
To activate the run type and enable the auto-approve, select a run type in the table and click the corresponding buttons above the table. Lastly, to map the run type to MFP, go to Map train stop and click the + icon to create a new mapping.
To set up GA runs, create one run type for each forecast intersection/measure combination. Table 13-2 shows the configurations for each run type.
Table 13-2 Run Type Configurations
| Forecast Level (Merchandise/Location/Calendar) | Forecast Measure | Forecast Method | Data Source | |
|---|---|---|---|---|
|
Location Plan |
Department/Location/Week |
Total Gross Sales Units |
Automatic Exponential Smoothing for all run types |
Store Sales for all run types |
|
Total Gross Sales Amount |
||||
|
Total Returns Units |
||||
|
Total Returns Amount |
||||
|
Location Target |
Company/Location/Week |
Total Gross Sales Units |
||
|
Total Gross Sales Amount |
||||
|
Total Returns Units |
||||
|
Total Returns Amount |
||||
|
Merchandise Plan |
Subclass/Area/Week |
Clearance Gross Sales Units |
||
|
Clearance Gross Sales Amount |
||||
|
Regular and Promotion Gross Sales Units |
||||
|
Regular and Promotion Gross Sales Amount |
||||
|
Total Returns Units |
||||
|
Total Returns Amount |
||||
|
Merchandise Target |
Department/Area/Week |
Clearance Gross Sales Units |
||
|
Clearance Gross Sales Amount |
||||
|
Regular and Promotion Gross Sales Units |
||||
|
Regular and Promotion Gross Sales Amount |
||||
|
Total Returns Units |
||||
|
Total Returns Amount |
|
Note: For all batch runs, in addition to the pre-season forecast, the Bayesian forecast is also generated by default. In the Manage train stop, you must only set the method for the pre-season forecast (either as Automatic Exponential Smoothing or Seasonal Exponential Smoothing). |
The Batch and Ad-Hoc jobs listed in Table 13-3 are used for loading foundation data (product hierarchy, location hierarchy, calendar, product attributes, and so on).
Table 13-3 Batch and Ad-Hoc Jobs for MFP Forecasting
| JobName | Description | RmsBatch |
|---|---|---|
|
ORASE_START_BATCH_JOB |
ORASE_START_BATCH_JOB |
rse_process_state_update.ksh |
|
ORASE_START_BATCH_SET_ACTIVE_JOB |
ORASE_START_BATCH_SET_ACTIVE_JOB |
rse_batch_type_active.ksh |
|
ORASE_START_BATCH_REFRESH_RESTR_JOB |
ORASE_START_BATCH_REFRESH_RESTR_JOB |
rse_batch_freq_restriction.ksh |
|
ORASE_START_BATCH_END_JOB |
ORASE_START_BATCH_END_JOB |
rse_process_state_update.ksh |
|
RSE_WEEKLY_INPUT_FILES_START_JOB |
RSE_WEEKLY_INPUT_FILES_START_JOB |
rse_process_state_update.ksh |
|
RSE_WEEKLY_INPUT_FILES_END_JOB |
RSE_WEEKLY_INPUT_FILES_END_JOB |
rse_process_state_update.ksh |
|
RSE_PROD_HIER_ETL_START_JOB |
RSE_PROD_HIER_ETL_START_JOB |
rse_process_state_update.ksh |
|
RSE_PROD_SRC_XREF_LOAD_JOB |
RSE_PROD_SRC_XREF_LOAD_JOB |
rse_prod_src_xref_load.ksh |
|
RSE_PROD_HIER_LOAD_JOB |
RSE_PROD_HIER_LOAD_JOB |
rse_prod_hier_load.ksh |
|
RSE_PROD_TC_LOAD_JOB |
RSE_PROD_TC_LOAD_JOB |
rse_prod_tc_load.ksh |
|
RSE_PROD_DH_LOAD_JOB |
RSE_PROD_DH_LOAD_JOB |
rse_prod_dh_load.ksh |
|
RSE_PROD_GROUP_LOAD_JOB |
RSE_PROD_GROUP_LOAD_JOB |
rse_load_prod_group.ksh |
|
RSE_PROD_HIER_ETL_END_JOB |
RSE_PROD_HIER_ETL_END_JOB |
rse_process_state_update.ksh |
|
RSE_LOC_HIER_ETL_START_JOB |
RSE_LOC_HIER_ETL_START_JOB |
rse_process_state_update.ksh |
|
RSE_LOC_SRC_XREF_LOAD_JOB |
RSE_LOC_SRC_XREF_LOAD_JOB |
rse_loc_src_xref_load.ksh |
|
RSE_LOC_HIER_LOAD_JOB |
RSE_LOC_HIER_LOAD_JOB |
rse_loc_hier_load.ksh |
|
RSE_LOC_HIER_TC_LOAD_JOB |
RSE_LOC_HIER_TC_LOAD_JOB |
rse_loc_hier_tc_load.ksh |
|
RSE_LOC_HIER_DH_LOAD_JOB |
RSE_LOC_HIER_DH_LOAD_JOB |
rse_loc_hier_dh_load.ksh |
|
RSE_LOC_HIER_ETL_END_JOB |
RSE_LOC_HIER_ETL_END_JOB |
rse_process_state_update.ksh |
|
RSE_PROD_ATTR_LOAD_START_JOB |
RSE_PROD_ATTR_LOAD_START_JOB |
rse_process_state_update.ksh |
|
RSE_PROD_ATTR_LOAD_END_JOB |
RSE_PROD_ATTR_LOAD_END_JOB |
rse_process_state_update.ksh |
|
RSE_CM_GRP_HIER_LOAD_START_JOB |
RSE_CM_GRP_HIER_LOAD_START_JOB |
rse_process_state_update.ksh |
|
RSE_CM_GRP_HIER_LOAD_END_JOB |
RSE_CM_GRP_HIER_LOAD_END_JOB |
rse_process_state_update.ksh |
|
RSE_TRADE_AREA_HIER_LOAD_START_JOB |
RSE_TRADE_AREA_HIER_LOAD_START_JOB |
rse_process_state_update.ksh |
|
RSE_TRADE_AREA_SRC_XREF_LOAD_JOB |
RSE_TRADE_AREA_SRC_XREF_LOAD_JOB |
rse_trade_area_src_xref_load.ksh |
|
RSE_TRADE_AREA_HIER_LOAD_JOB |
RSE_TRADE_AREA_HIER_LOAD_JOB |
rse_trade_area_hier_load.ksh |
|
RSE_TRADE_AREA_TC_LOAD_JOB |
RSE_TRADE_AREA_TC_LOAD_JOB |
rse_trade_area_tc_load.ksh |
|
RSE_TRADE_AREA_DH_LOAD_JOB |
RSE_TRADE_AREA_DH_LOAD_JOB |
rse_trade_area_dh_load.ksh |
|
RSE_TRADE_AREA_HIER_LOAD_END_JOB |
RSE_TRADE_AREA_HIER_LOAD_END_JOB |
rse_process_state_update.ksh |
|
RSE_CAL_HIER_ETL_START_JOB |
RSE_CAL_HIER_ETL_START_JOB |
rse_process_state_update.ksh |
|
RSE_REGULAR_MAIN_LOAD_JOB |
RSE_REGULAR_MAIN_LOAD_JOB |
rse_regular_main_load.ksh |
|
RSE_FISCAL_MAIN_LOAD_JOB |
RSE_FISCAL_MAIN_LOAD_JOB |
rse_fiscal_main_load.ksh |
|
RSE_CAL_HIER_ETL_END_JOB |
RSE_CAL_HIER_ETL_END_JOB |
rse_process_state_update.ksh |
|
RSE_DIMENSION_LOAD_END_START_JOB |
RSE_DIMENSION_LOAD_END_START_JOB |
rse_process_state_update.ksh |
|
RSE_DIMENSION_LOAD_END_END_JOB |
RSE_DIMENSION_LOAD_END_END_JOB |
rse_process_state_update.ksh |
|
RSE_DIMENSION_LOAD_START_START_JOB |
RSE_DIMENSION_LOAD_START_START_JOB |
rse_process_state_update.ksh |
|
RSE_DIMENSION_LOAD_START_END_JOB |
RSE_DIMENSION_LOAD_START_END_JOB |
rse_process_state_update.ksh |
|
RSE_SLS_START_START_JOB |
RSE_SLS_START_START_JOB |
rse_process_state_update.ksh |
|
RSE_SLS_START_END_JOB |
RSE_SLS_START_END_JOB |
rse_process_state_update.ksh |
|
RSE_SLS_END_START_JOB |
RSE_SLS_END_START_JOB |
rse_process_state_update.ksh |
|
RSE_SLS_END_END_JOB |
RSE_SLS_END_END_JOB |
rse_process_state_update.ksh |
|
ORASE_END_START_JOB |
ORASE_END_START_JOB |
rse_process_state_update.ksh |
|
ORASE_END_RUN_DATE_UPDT_JOB |
ORASE_END_RUN_DATE_UPDT_JOB |
rse_batch_run_date_update.ksh |
|
ORASE_END_END_JOB |
ORASE_END_END_JOB |
rse_process_state_update.ksh |
|
RSE_BATCH_ENABLE_ADHOC_JOB |
Enable the running of AdHoc batches while disabling Scheduled batches |
rse_batch_enable_adhoc.ksh |
|
RSE_BATCH_DISABLE_ADHOC_JOB |
Disable the running of AdHoc batches while enabling Scheduled batches |
rse_batch_enable_scheduled.ksh |
|
RSE_FCST_SALES_PLAN_START_JOB (needed for Bayesian method) |
Start job for sales plan data load |
rse_process_state_update.ksh |
|
RSE_FCST_SALES_PLAN_LOAD_JOB (needed for Bayesian method) |
Load job for sales plan data |
rse_fcst_sales_plan_load.ksh |
|
RSE_FCST_SALES_PLAN_END_JOB(needed for Bayesian method) |
End job for sales plan data load |
rse_process_state_update.ksh |
|
RSE_MASTER_ADHOC_JOB |
Run RSE master script |
rse_master.ksh |
The jobs listed in Table 13-4are used to prepare weekly data and to run weekly batches for MFP.
Table 13-4 Weekly Data and Weekly Batches
| JobName | Dexcription | RmsBatch |
|---|---|---|
|
PMO_ACTIVITY_LOAD_START_JOB |
PMO Activity load start job |
rse_process_state_update.ksh |
|
PMO_ACTIVITY_STG_JOB |
PMO Activity data staging |
pmo_activity_load_setup.ksh |
|
PMO_ACTIVITY_LOAD_JOB |
PMO Activity load job |
pmo_activity_load_process.ksh |
|
PMO_ACTIVITY_LOAD_END_JOB |
PMO Activity load end job |
rse_process_state_update.ksh |
|
RSE_MFP_FCST_BATCH_RUN_START_JOB |
Start job for executing MFP forecast batch runs |
rse_process_state_update.ksh |
|
RSE_CREATE_MFP_BATCH_RUN_PROC_JOB |
Create MFP batch runs |
rse_create_mfp_batch_run_procksh |
|
RSE_MFP_FCST_BATCH_PROCESS_JOB |
Execute MFP forecast batch |
rse_fcst_mfp_batch_process.ksh |
|
RSE_MFP_FCST_BATCH_RUN_END_JOB |
End job for executing MFP forecast batch runs |
rse_process_state_update.ksh |
|
RSE_CREATE_MFP_BATCH_RUN_PROC_ADHOC_JOB |
Ad hoc job to create MFP batch runs |
rse_create_mfp_batch_run_procksh |
|
RSE_MFP_FCST_BATCH_PROCESS_ADHOC_JOB |
Ad hoc job to execute MFO forecast batch |
rse_fcst_mfp_batch_process.ksh |
The forecast values generated by runs that are associated with active run types are exported to the RDX schema. The jobs for exporting the outputs to the RDX schema are listed in Table 13-5.
To configure forecast process for RDF, complete following steps.
Use the Manage System Configurations screen to review and modify the global configurations in RSE_CONFIG. For further details, see "Configuration Updates". The relevant configurations in RSE_CONFIG that must be reviewed and edited as required are listed in Table 13–1.
Table 13-6 RSE Configurations
| APPL_CODE | PARAM_NAME | PARAM_VALUE | DESCR |
|---|---|---|---|
|
RSE |
EXTENDED_HIERARCHY_SRC |
Default value is NON-RMS. |
Data source providing extended hierarchy data RMS/NON-RMS. |
|
RSE |
LOAD_EXTENDED_PROD_HIER |
Default value is Y. If the product hierarchy data had 9 levels, keep this value as Y. If it has 7 levels, change this value to N. |
Y/N Value. This parameter is used by the product hierarchy ETL to know if the extended product hierarchy is needed. |
|
PMO |
PMO_PROD_HIER_TYPE |
Default value is 3. If the product hierarchy data has 9 levels (i.e. it has extended hierarchy), keep this value as 3. If it has 7 levels, change this value to 1. |
The hierarchy id to use for the product (Installation configuration). |
|
RSE |
PROD_HIER_SLSTXN_HIER_LEVEL_ID |
Default value is 9. |
This parameter identifies the hierarchy level at which sales transactions are provided (7-Style, 8-Style/color or 9 Style/color/Size). It MUST match the extended hierarchy leaf level |
|
PMO |
PMO_AGGR_INVENTORY_DATA_FLG |
Default value is Y. |
Specifies if inventory data is present and if it should be used when aggregating activities data. Set this value to N if inventory data is not loaded (inventory data is not required for MFP forecasting but it is required for other applications like Offer Optimization, Inventory Optimization and Retail Demand Forecasting). |
|
RSE |
SLS_TXN_EXCLUDE_LIABILITY_SLS |
Default value is N. |
/N flag indicating if liability sales columns should be excluded when retrieving sales transaction data. |
|
RSE |
RSE_LOC_HIER_EXCL_FRANCHISE |
Default value is N. |
Y/N flag indicating if franchise locations should be excluded from the location hierarchy. |
Use the Manage Forecast Configurations screen to set up the forecast runs, as follows.
In Manage Forecast Configurations, start by setting up a run type in the Setup train stop. Click the + icon above the table and fill in the fields in the pop-up. If the customer has both Short Life Cycle and Long Life Cycle items, you must create one run type for each. You must create a run type for each forecast intersection combination that is required.
Once you are done with setting up the run types, click Start Data Aggregation in Setup train stop. Select all the run types that were created and click Submit. When the aggregation is complete, the aggregation status will change to Complete. At this point, ad-hoc test runs and batch runs can be created and executed to generate a forecast.
Once you have finished setting up the run types, click Start Data Aggregation in the Setup train stop. Select all the run types that were created and click Submit. When the aggregation is complete, the aggregation status will change to Complete. At this point, ad-hoc test runs and batch runs can be created and executed to generate a forecast.
To create an ad-hoc run, go to the Test train stop. First, click a run type in the top table and then click the + icon in the bottom table to create a run. In the Create Run pop-up, you can change the configurations parameters related to estimation process and forecast process in their respective tabs. After modifying and reviewing the configuration parameters, click Submit to start the run. Upon submit, a validation process runs to validate the value of configuration parameters. If there is any error, correct the corresponding parameter and submit again. Once the run is complete, the status will change to Forecast Generation Complete.
Once you are done with testing, you must modify and review the configurations of the run type, activate the run type, enable auto-approve, and map the run type to the downstream application (for example, RDF). In the Manage train stop, select a row, click Edit Configurations Parameters, and edit the estimation and forecast parameters as necessary. Once you are done, go to Review tab and click Validate and then close tab.
|
Note: If the run type is active, you will only be able to view the parameters. In order to edit the parameters, the run type must be inactive. |
To activate the run type and enable the auto-approve, select a run type in the table and click the corresponding buttons above the table. Lastly, to map the run type to MFP, go to Map train stop and click the + icon to create a new mapping.
|
Note: For RDF, you will be able to map one or multiple run types to the same "external app" run type. The run types that are being mapped to the same external app run type must have same forecast intersection, same price zone and customer segment flag, and same data source. |
The Batch and Ad-Hoc jobs listed in Table 13-7 are used for preparing weekly data and running weekly batches for RDF.
Table 13-7 Batch and Ad Hoc Jobs for RDF Forecasting
| JobName | Description | RmsBatch |
|---|---|---|
|
PMO_ACTIVITY_LOAD_START_JOB |
PMO Activity load start job |
rse_process_state_update.ksh |
|
PMO_ACTIVITY_STG_JOB |
PMO Activity data staging |
pmo_activity_load_setup.ksh |
|
PMO_ACTIVITY_LOAD_JOB |
PMO Activity load job |
pmo_activity_load_process.ksh |
|
PMO_ACTIVITY_LOAD_END_JOB |
PMO Activity load end job |
rse_process_state_update.ksh |
|
PMO_CREATE_BATCH_RUN_JOB |
Create batch run for PMO execution |
rse_create_pmo_batch_run_proc.ksh |
|
PMO_RUN_EXEC_SETUP_JOB |
Setup job for PMO run execution |
pmo_run_exec_setup.ksh |
|
PMO_RUN_EXEC_START_JOB |
Start job for PMO run execution |
rse_process_state_update.ksh |
|
PMO_RUN_EXEC_PROCESS_JOB |
Process job for PMO run execution |
pmo_run_exec_process.ksh |
|
PMO_RUN_EXEC_END_JOB |
End job for PMO run execution |
rse_process_state_update.ksh |
|
RSE_CREATE_FCST_BATCH_RUN_JOB |
Create forecast batch run |
rse_create_fcst_batch_run_proc.ksh |
|
RSE_FCST_BATCH_PROCESS_JOB |
Execute Base Demand and Demand Forecast for forecast run |
rse_fcst_batch_process.ksh |
|
RSE_FCST_BATCH_RUN_END_JOB |
End job for creating forecast batch run |
rse_process_state_update.ksh |
|
RSE_CREATE_FCST_BATCH_RUN_ADHOC_JOB |
Adhoc job to create forecast batch run |
rse_create_fcst_batch_run_proc.ksh |
|
RSE_FCST_BATCH_PROCESS_ADHOC_JOB |
Execute Base Demand and Demand Forecast for forecast run |
rse_fcst_batch_process.ksh |
The forecast values generated by runs that are associated with active run types and mapped to RDF are exported to RDX schema.
Table 13-8 Jobs for Exporting Outputs to RDX
| JobName | Description | RMSBatch |
|---|---|---|
|
RSE_RDF_FCST_EXPORT_JOB |
Export RDF forecast |
rse_rdf_export.ksh |
|
RSE_RDF_FCST_EXPORT_ADHOC_JOB |
Ad hoc job to export RDF forecast |
rse_rdf_export.ksh |
Table 13-9 list the additional jobs for exporting different data like flexible groups, promotions, and so on.
Table 13-9 Additional Jobs for Exporting Data
| JobName | Description | RmsBatch |
|---|---|---|
|
RSE_FLEX_GROUP_EXPORT_SETUP_JOB |
Setup job for exporting flexible groups |
rse_flex_group_exp_setup.ksh |
|
RSE_FLEX_GROUP_EXPORT_PROCESS_JOB |
Process job for exporting flexible groups |
rse_flex_group_exp_process.ksh |
|
RSE_PROMO_OFFER_EXPORT_JOB |
Export promotion offers |
rse_rdf_offers_hier_exp.ksh |
|
RSE_PROMO_OFFER_SALES_EXPORT_JOB |
Export promotion offer sales figures |
rse_rdf_offer_sales_exp.ksh |
|
RSE_PROMO_OFFER_EXPORT_ADHOC_JOB |
Ad hoc job to export promotion offers |
rse_rdf_offers_hier_exp.ksh |
|
RSE_PROMO_OFFER_SALES_EXPORT_ADHOC_JOB |
Ad hoc job to export promotion offer sales figures |
rse_rdf_offer_sales_exp.ksh |
|
RSE_FCST_ESC_LVL_EXPORT_SETUP_JOB |
Setup job for exporting escalation levels |
rse_fcst_esc_lvl_exp_setup.ksh |
|
RSE_FCST_ESC_LVL_EXPORT_PROCESS_JOB |
Process job for exporting escalation levels |
rse_fcst_esc_lvl_exp_process.ksh |
|
RSE_FCST_RUN_TYPE_CONF_EXPORT_SETUP_JOB |
Setup job for exporting runtype config |
rse_fcst_run_type_conf_exp_setup.ksh |
|
RSE_FCST_RUN_TYPE_CONF_EXPORT_PROCESS_JOB |
Process job for exporting runtype con |
rse_fcst_run_type_conf_exp_process.ksh |
The jobs for exporting forecast parameters from RDX schema are listed in Table 13-10:
Table 13-10 Forecast Parameters for Export Jobs
| JobName | Description | RMSBatch |
|---|---|---|
|
RSE_RDX_FCST_PARAM_SETUP_JOB |
Setup job for importing forecast parameters |
rse_rdx_fcst_param_setup.ksh |
|
RSE_RDX_FCST_PARAM_PROCESS_JOB |
Process job for importing forecast parameters |
rse_rdx_fcst_param_process.ksh |
The approved forecast is exported to RMS. The jobs are listed in Table 13-11.
