| Oracle® Retail Advanced Inventory Planning Operations Guide Release 14.1.1 |
|
 Previous |
Functionally the AIP RPAS Intra-day batch scripts are broadly classified in Table 12-1. Each of the scripts listed next to its descriptive step name exists to perform that batch step.
Table 12-1 AIP Intra-day Batch Scripts by Class
| AIP Intra-day Batch Class | Step Description | Batch Script |
|---|---|---|
|
Intra-day External Integration Inventory Data Processing and Load into AIP RPAS |
Verify and Process Inventory Data from External System |
check_process_intraday_inventory_data.sh |
|
Load Intra-day Inventory Data |
load_intraday_inventory_data.sh |
|
|
Run Intra-day Replenishment Process for Global Domain |
Run Intra-day Replenishment for Global Domain |
run_intraday_scrp_global.sh |
|
Prepare Intra-day Local Domain List |
Prepare Intra-day Local Domain List |
prepare_intraday_localdomain_list.sh |
|
Calculate and Export the Intra-day Replenishment Plans for Local Domains |
Calculate Intra-day Replenishment Plans for Local Domains |
run_intraday_scrp_local.sh |
|
Export Intra-day Replenishment Data for Local Domains |
export_intraday_data_local.sh |
|
|
Send Intra-day Replenishment Data from AIP RPAS to AIP Oracle |
Send Intra-day Replenishment Data to OM |
send_intraday_data_to_om.sh |
|
Update Intra-day Alert Indicator |
Calculate Intra-day Alert Indicator |
update_intraday_alerts.sh |
|
Build Intra-day Workbooks after Intra-day Batch Run |
Auto Build Intra-day Global Workbooks |
build_intraday_workbooks_global.sh |
|
Auto Build Intra-day Local Workbooks |
build_intraday_workbooks_local.sh |
These sections describe the steps needed for this process:
Step Name
prep_intraday_inventory_data
The Intra-day data from RMS and/or non-RMS external system is processed as a set of flat files that follow an agreed AIP file format. AIP validates all of the files to ensure that the required data is present, and massages the files to produce the input required for subsequent steps of the AIP RPAS Intra-day batch.
The dynamic Intra-day measure data are listed in Table 12-2. They are also listed in the $AIPDOMAIN/interface/config/intraday/intraday_inventory_data.config. For AIP RPAS Intra-day batch to properly process external system data, all of the flat files must follow a particular format, which is explained in the Oracle Retail Advanced Inventory Planning Implementation Guide. The flat files must have a *.txt extension.
Table 12-2 Dynamic Measure Data
| File Name | Description |
|---|---|
|
idstrcurinvi.txt |
Intra-day Loaded Store Current Inventory |
|
idstriti.txt |
Intra-day Store In Transits |
|
idstrooi.txt |
Intra-day Store On Orders |
|
idwhcurinvi.txt |
Intra-day Loaded Warehouse Current Inventory |
|
idwhiti.txt |
Intra-day Warehouse In Transits |
|
idwhooi.txt |
Intra-day Warehouse On Orders |
|
idaiwi.txt |
Intra-day WH Allocations in the Well |
|
idtiwi.txt |
Intra-day WH Transfers in the Well |
|
iddayslsi.txt |
Intra-day Loaded Daily Sales |
Wave on Wave Processing
The following steps describe Wave on Wave processing,
Verify that all previous required files have been downloaded. Failure to download any of the required files results in an error and termination of the batch.
Prefix all the measure data listed in Table 12-2 except iddayslsi with the stocking point prefixes, using construct_ntier_measuredata.ksh:
idstrcurinvi.txt
idstriti.txt
idstrooi.txt
idwhcurinvi.txt
idwhiti.txt
idwhooi.txt
idaiwi.txt
idtiwi.txt
Using interutil binary, convert from RMS SKU to AIP SKU all RMS-sourced inventory measure data except iddayslsi. See the earlier script and the Oracle Retail Advanced Inventory Planning Implementation Guide for details on this configuring.
If the inventory tracking level is set to True, all like keys needs to be summed for all files except iddayslsi.
|
Note: The reason daily sales is excluded from prefixing is that the prefixing is done insideaipt_sr0_dayslsld_rms<x>.ksh. The reason daily sales is excluded from interutil mapping is that it does not need RMS SKU/Order Mutliple -> SKPS mapping (it is at SKU). The reason it should be excluded from like-key summing is that this is unnecessary for those data feeds not run through interutil. |
This Script Calls These Scripts:
_check_for_required_files (defined in bsa_check_for_required_files.sh)
process_intraday_inventory_data.sh
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
All data files from Table 12-2 should be copied by the client's batch scheduler into the $AIPDOMAIN/interface/rms directory.
Refer to the $AIPDOMAIN/interface/config/intraday/intraday_inventory_data.config for requirements.
Restart/Recovery
If the process_intraday_inventory_data.sh script failed, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Re-copy or re-FTP all required files listed in $AIPDOMAIN/interface/config/intraday/intraday_inventory_data.config into the $AIPDOMAIN/interface/rms directory.
The new copies should overwrite the existing files in this directory.
Restart the batch.
Step Name
load_intraday_inventory_data
Script Call
run_ride.sh load_intraday_inventory_data.sh
Parameters
None.
Functional Overview
This script preprocesses and loads into the AIP RPAS domain all store and warehouse replenishment measure data that come from RMS or other external inventory system.
Technical Details
This script will loop over all measures in the intraday_inventory_data.config and move them to the AIP domain input directory and then load them into the domain. It will load all files as .ovr.
Wave on Wave Processing
Call loadmeasure.sh (a script wrapper for loadmeasure RPAS binary) on the measure data files corresponding to the Intra-day measure data received from the inventory system (example, RMS). The measures loaded are listed in the following configuration files:
$AIPDOMAIN/interface/config/intraday/intraday_inventory_data.config
|
Note: All measures are loaded as overlay (.ovr). |
|
Note: For run_ride.sh:This is a wrapper script for the RPAS ride utility which is introduced for Intra-day. The run_ride.sh, when being run against a global domain, will lock all domains; however, when the script is run against local domains, it will only lock those local domains maintained in a cached local domain list. The usage for run_ride.sh is: run_ride.sh [-local] script If the flag -local is used, the script will lock only local domains listed in the cached list; otherwise, it will lock all domains. |
This Script Calls This Script:
loadmeasure.sh
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
check_process_intraday_inventory_data.sh
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Ensure that the *.txt files are transferred through FTP by client scheduled process from RMS to the correct location.
Ensure all RMS file are present.
Ensure all files are formatted correctly.
Restart the batch.
This section describes the steps needed for this process:
Step Name
run_intraday_replenishment_global
Script Call
run_ride.sh run_intraday_scrp_global.sh ${waveNumber}
Parameters
Wave Number
Functional Overview
The current wave measure which is a scalar is populated with the desired wave number before it can be used in the subsequent Intra-day batch steps.
Technical Details
This step initiates the current wave measure IdCurWavI based on the provided parameter.
Wave on Wave Processing
Populate the current wave measure to be used by subsequent Intra-day batch steps.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
None.
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
This section describes the steps needed for this process:
Step Name
prepare_intraday_local_domain_list
Script Call
run_ride.sh prepare_intraday_localdomain_list.sh
Parameters
None.
Functional Overview
A list of local domains that need to be locked by run_ride.sh is prepared during this step for subsequent Intra-day batch calls which are run against local domains.
Technical Details
This step prepares a list of local domains to be used in subsequent, applicable Intra-day batch steps. This script first runs rule group id_preLocDomList, then exports measure IdLocDomListO to a temporary file, then generates the position list file and local domain list file.
Table 12-3 Rule Groups Used for Preparing Intra-day Local Domain List
| Rule Group | Description |
|---|---|
|
id_preLocDomList |
Prepare a list of local domains to be used in subsequent Intra-day batch steps. |
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
run_ride.sh run_intraday_scrp_global.sh ${waveNumber}
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
These sections describe the steps needed for this process:
Step Name
run_intraday_replenishment_local
Script Call
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p run_intraday_scrp_local.sh [DOMAIN]
Parameters
Path to Local Domain
Functional Overview
Intra-day Replenishment and Reconciliation is part of the AIP batch run which generates an Intra-day Receipt Plan from Warehouses or Supplier to Stores across the length of the horizon. The final output from this Intra-day batch process is:
Intra-day Constrained Receipt Plan for Stores across the Fixed Period.
Unconstrained Intra-day Receipt Plan for Stores across the post Fixed Period up to the end of the horizon.
Technical Details
run_intraday_scrp_local.sh on all local domains. The local scripts internally invoke a set of rule groups according to the sequence described in Table 12-4. Each rule group is responsible for performing a specific step in the supply chain replenishment planning process.
Table 12-4 lists rule groups involved in the AIP local Intra-day replenishment and reconciliation batch process.
Table 12-4 Rule Groups for AIP Local Intra-day Batch Process
| Rule Group | Description |
|---|---|
|
Local Rule Groups |
The following rule groups are called by run_intraday_scrp_local.sh script. |
|
id_setup |
Run all Intra-day setup steps for AIP. |
|
id_preReplenish |
Runs all Intra-day pre replenishment steps for AIP. |
|
id_replenish |
Runs Intra-day replenishment batch run and generates an unconstrained receipt plan. |
|
id_preReconcile |
Runs Intra-day pre reconciliation steps for AIP. |
|
id_reconcile |
Runs Intra-day reconciliation and generates an Intra-day constrained receipt plan. |
|
id_pushToStore |
Runs Intra-day stockless reconciliation at store destinations for stockless items and pushes the excess quantity to the stores. |
|
id_replPstFxd |
Runs Intra-day replenishment batch run post fixed period and generates an Intra-day unconstrained receipt plan for post fixed period. |
|
id_post |
Runs Intra-day post replenishment process. |
Wave on Wave Processing
The run_intraday_scrp_local.sh will call rule groups according to the previous orders against the local domains produced by the previous step.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
run_ride.sh run_intraday_scrp_global.sh ${waveNumber}
run_ride.sh prepare_intraday_localdomain_list.sh
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
Step Name
export_intraday_replenishment_data
Script Call
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p export_intraday_data_local.sh [DOMAIN]
Parameters
Path to Local Domain
Functional Overview
The replenishment plan's planned orders from suppliers and transfers from warehouses must be exported from populated measures into files suitable for interfacing with AIP Oracle. In this batch step, the exports are performed independently in each local domain, resulting in each having its own copy of the export files placed in the local domain output directory, as shown in Table 12-5.
Table 12-5 Export Files
| File Name | Description |
|---|---|
|
strsplrord.dat |
Supplier to store orders for release today through the planning horizon. |
|
strwhord.dat |
Warehouse to store transfers for release today. |
Technical Details
This step's command line script call is a composite of two scripts, for_each_local_domain.sh and export_intraday_data_local.sh, which together cause the exporting of order and transfer data to be performed in parallel across all local domains. At the local domain level, the process is driven by the aipcmd binary, which processes the XML resource command files to produce the parenthesized output files:
exportPlanStrSplrIdOrd.xml (strsplrord.dat)
exportPlanStrWhIdOrd.xml (strwhord.dat)
These XML resource files all make use of the ExportPlan command to perform the specialized data exports.
Wave on Wave Processing
Script for_each_local_domain.sh performs the following steps:
Determine the list of local domains under $AIPDOMAIN.
For each local domain, call in parallel the script export_intraday_data_local.sh and pass it the local domain path. That path is substituted automatically for the DOMAIN] token by for_each_local_domain.sh.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p run_intraday_scrp_local.sh [DOMAIN]
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
This section describes the steps needed for this process:
Step Name
send_intraday_replenishment_data_to_om
Script Call
send_intraday_data_to_om.sh
Parameters
None.
Functional Overview
Planned orders and transfers, exported separately per local domain in the Export Replenishment Data step, are combined, tarred, and compressed for interfacing with AIP Online.
Technical Details
In this batch step, the filenames listed in the global domain's $AIPDOMAIN/interface/config/intraday/intraday_scrp_export_to_om.config are located in each local domain's output directory and concatenated into like-named files in the global domain's $AIPDOMAIN/interface/export directory.
Wave on Wave Processing
Verify the existence and writeability of the global domain's interface/export directory, the destination of the concatenated export files.
For each of the files listed in the global domain's $AIPDOMAIN/interface/config/intraday/intraday_scrp_export_to_om.config file, delete any existing instance in the global domain's $AIPDOMAIN/interface/export directory, then iterate over the list of local domains, concatenating each instance of the file found in the local domain's output directory into the global interface file of the same name in global domain's $AIPDOMAIN/interface/export directory.
Compress each global domain export file, package them all into a single tar file, then compress the tar file into a single file:
$AIPDOMAIN/interface/export/srp.tar.Z.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p export_intraday_data_local.sh [DOMAIN]
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
This section describes the steps needed for this process:
Step Name
run_intraday_alerts
Script Call
for_each_local_domain.sh -p update_intraday_alerts.sh [DOMAIN]
Parameters
Path to Local Domain
Functional Overview
This step calculates the Intra-day Out of Stock Indicator which then be used by the next overnight batch for calculating the SRP Alerts.
Technical Details
This step updates the Intra-day Out of Stock Indicator after the Intra-day batch jobs have finished.
Wave on Wave Processing
Execute id_srpAlerts rule group to update the Intra-day Out of Stock Indicator (IdOosI) for later overnight batch use.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until successful completion of the following:
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p run_intraday_scrp_local.sh [DOMAIN]
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
These sections describe the steps needed for this process:
This section describes the steps needed for this process:
Step Name
auto_build_intraday_workbooks_global
Script Call
run_ride.sh build_intraday_workbooks_global.sh ${waveNumber}
Parameters
Wave Number
Functional Overview
Many of the Intra-day workbooks can be configured by the system administrator to be automatically built during the day as part of the AIP RPAS Intra-day batch run. This allows you to enter the worksheets directly without going through the workbook creation wizard. All Intra-day workbooks configured for commit at global domain level are committed in this step. This script may also be run from the command line ad hoc throughout the day by administrators or users.
|
Note: Only a workbook that is in the Intra-day category can be built during the Intra-day batch run. None of the workbooks other than Intra-day workbooks will change during the day. |
Technical Details
This step uses the RPAS utility wbbatch to automatically build Intra-day workbooks. In order to successfully auto-build workbooks, they must be configured through the RPAS client. Refer to the Oracle Retail Predictive Application Server Administration Guide for information on automatically building workbooks.
Wave on Wave Processing
Call wbbatch to build all workbooks on the $AIPDOMAIN global domain build queue.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until the following steps (scripts) are successfully completed.
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p run_intraday_scrp_local.sh [DOMAIN]
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
This section describes the steps needed for this process:
Step Name
auto_build_intraday_workbooks_local
Script Call
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p build_intraday_workbooks_local.sh [DOMAIN] ${waveNumber}
Parameters
Path to Local Domain and Wave Number
Functional Overview
Many of the Intra-day workbooks can be configured by the system administrator to be automatically built during the day as part of the AIP RPAS Intra-day batch run. This allows you to enter the worksheets directly without going through the workbook creation wizard. All Intra-day workbooks configured for commit at local domain level are committed in this step. This script may also be run from the command line ad hoc throughout the day by administrators or users.
Technical Details
This step uses the RPAS utility wbbatch to automatically build Intra-day workbooks. In order to successfully auto-build workbooks, they must be configured through the RPAS client. Refer to the Oracle Retail Predictive Application Server Administration Guide for information on automatically building workbooks.
|
Note: Only workbook that is in the Intra-day category can be built during the Intra-day batch run. None of the workbooks other than Intra-day workbook will change during the day. |
Wave on Wave Processing
For each local domain, call wbbatch to build all Intra-day workbooks on each local domain build queue.
Appropriate Batch Run
Intra-day Wave.
Prerequisites
This step must not be initiated until the following steps (scripts) are successfully completed.
run_ride.sh -local for_each_local_domain.sh -l $INTRADAY_LOCAL_DOMAIN_LIST -p run_intraday_scrp_local.sh [DOMAIN]
Restart/Recovery
If this script fails, perform the following steps:
Examine the log files to determine the cause of the failure.
Correct any identified setup or environment issues.
Restart the batch.
