6 Script Integration

This chapter describes the Item Planning data flow and the script integration of the Fashion Planning Bundle applications.

For information about ODI enabled integration for the Fashion Planning Bundle, see Chapter 5.

Integration Scripts

These scripts can be used for moving data between applications. The following rules apply to integration scripts:

• The exportMeasure utility is used to export data in CSV (comma-separated values) format. This maintains the consistency of start and width attributes across different applications.

• Data exported from the source application is placed in the destination domain input directory.

• Export scripts must run before load scripts. They should be run in the batch window.

• Measure names should not be hard-coded. The names are included in a text file named <source application>_<destination application>_transferList.txt. For example, AP_IP_transferList.txt includes the measure names exported from AP to IP.

  Each transfer file includes two columns that correspond to the following data:

  • Measure name

  • File name

  When the transfer file is used for a load script, it contains the name of the measure to be loaded and the name of the file that contains the data.

  For an export script, the transfer file contains the name of the measure in the source application and the name of the ovr file that will be created in the input directory of the destination application. The file names correspond to the measure names in the destination application.

• The scripts have a command line argument to set the maximum number of processes that need to be run in parallel. Setting this argument can help speed up the performance of independent tasks on local domains. The default is 1.

• Do not hard-code domain paths. The paths are entered as command line arguments.

Table 6-1 lists the integration scripts for Item Planning. These scripts are located in
$IP_HOME/bin.

Table 6-1 Integration Scripts

Application	Script Name	Arguments
AP	loadActuals.ksh	measurelist
MFP	exportToMFP.ksh	maxprocesses, destination­, measurelist

Batch Designs

This section contains detailed information on the following integration scripts:

• Load Actuals Data

• Export to MFP

Load Actuals Data

Script
loadActuals.ksh

Usage
loadActuals.ksh <measurelist>

Table 6-2 Load Actuals Data Usage

Argument	Description	Notes
measurelist	Sets the location of the file which contains the list of measures to be exported.	By default, these files are provided with the package in the $IP_HOME/bin directory. The file name should follow the convention of AP_IP_transferList.txt.

Example
loadActuals.ksh $IP_HOME/bin/AP_IP_transferList.txt

Error Information

Table 6-3 Load Actuals Data Error Information

Task Name	Error Code	Abort Required?	Description of Error
loadactuals	40	yes	Argument 'measurelist' is missing.
loadactuals	41	yes	Domain does not exist.
loadactuals	42	no	Data file does not exist.
loadactuals	43	yes	All measure input files are empty or missing.
loadactuals	45	yes	Errors occurred during the load of one or more measures.

Notes:

• This script uses the RPAS loadmeasure utility. See the Oracle Retail Predictive Application Server Administration Guide for details on this utility.

• The script ignores any missing or empty measure load files.

• All measure files are placed into the domain's input folder.

• If there were no errors during the loading of all measures, the input file is archived into the domain's input/processed directory. A date stamp is appended to the end of the measure file name.

• The script does not produce an error when records are rejected from the loaded files. These rejected records are logged in the log output of the load process.

Export to MFP

Script
exportToMFP.ksh

Usage
exportToMFP.ksh <maxprocesses> <destination> <measurelist>

Table 6-4 Export to MFP Usage

Argument	Description	Notes
maxprocesses	Sets the maximum number of export processes to run in parallel.	The default is 1.
destination	Sets the path to the input folder of the destination domain where the exported files are placed.	The export script creates the file containing the exported measures in the input folder of the destination domain.
measurelist	Sets the location of the file which contains the list of measures to be exported.	By default, these files are provided with the package in the $IP_HOME/bin directory. The file name should follow the convention of IP_MFP_transferList.txt.

Example
exportToMFP.ksh 1 $MFP_HOME/domain/mfpcst $IP_HOME/bin/IP_MFP_transferList.txt

Error Information

Table 6-5 Export to MFP Error Information

Task Name	Error Code	Abort Required?	Description of Error
export	130	yes	Argument missing.
export	131	yes	Domain does not exist.
export	132	yes	Missing $EXPORTLISTFILE.
export	135	no	Errors found in the export log file.

Notes

• This optional script is used only if exports to MFP are required.

• The script uses the RPAS exportData utility to export measure data from the domain. See the Oracle Retail Predictive Application Server Administration Guide for details on this utility.