1 MFP Batch Task Administration

The Merchandising Financial Planning (MFP) Cloud Service batch task is a powerful tool provided to the Administrator to manage periodic load/export of Data/Hierarchy from the front end, eliminating the cumbersome effort of scheduling and running the batch from the back end domain server.

MFP Cloud Service uses the Oracle Retail Predictive Application Server Cloud Edition (RPASCE) Online Administration Tools to schedule RPASCE services to run batch on the Cloud. Administrative users can view the results of the scheduled services in the log on a dashboard through the RPASCE front end.

RPASCE Online Administration Tools support the scheduling of standard RPAS utilities and, in addition, scheduling application-specific services. For a detailed understanding of the Online Administration Tools, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide.

The following sections explain the application-specific administration tasks that are pre-configured for MFP Cloud Service. These tasks are only applicable for non-Enterprise Edition implementations.

With Enterprise Edition implementations, the Configured Batch Tasks can be fully configured by making changes to the batch control files. For information about changing the batch control files and how to upload them, see the Oracle Retail Predictive Application Server Cloud Edition Implementation Guide.

Non-Enterprise Edition retailers can also customize the tasks by changing the control files as part of the Extensibility framework. For allowed changes, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Application-Specific Batch Tasks

The application-specific batch tasks are a set of tasks that help the Administrator to load/export a predefined set of data and hierarchies. These tasks are found in the Online Administration Tools as Configured Batch Tasks.

Each task in turn calls predefined batch services to do the required tasks. MFP Cloud Service uses the Enterprise Edition batch framework to define the batch process.

Some tasks require input data files or hierarchy files as input. These files must be uploaded before the tasks are scheduled. Some tasks export files out of the application. Those files are copied to the SFTP export location, and Administrators can download these exported files.

The SFTP file location is a space provided to the Administrator to load import files and access exported batch files. For more information, see "Batch File Uploads/Downloads."

Administrators can set up some additional batch specific measures, such as Enable RMF CS Integration, that control the batch process in the client UI in MFP Setup -> Manage Batch -> Manage Batch.

If Bulk Data Integration (BDI) is enabled during implementation, the Batch Uses BDI flag should be enabled in the Manage Batch task. If Planning Data Storage (PDS) is enabled during implementation, the Batch Uses PDS flag is set. Based on those flags, additional steps will get executed during the batch.

The following list shows the application-specific administration tasks that are pre-configured for MFP Cloud Service under Configured Batch Tasks:

Run Batch Measure Load Group
Run Batch Measure Export Group
Run Batch Calc Group
Run Batch Task Group

These batch tasks are explained in detail in subsequent sections. There are some additional tasks available under Configured Batch Tasks which are generic RPAS-specific tasks. Details about the RPAS-specific tasks can be found in the Batch Administration section in the Oracle Retail Predictive Application Server Cloud Edition Administration Guide.

Run Batch Measure Load Group

This task is used to load a predefined set of measures grouped as a measure set in the batch control file batch_loadmeas_list.txt. These set of measures can be loaded together. Actuals Data is a named set of load measures in the batch control file. If the Administrator decides to load the measure set for Actuals Data, the Administrator needs to load data for measures which includes measures such as Ty Sales Clr R and TY Sales Clr U. All required data files must be uploaded to the SFTP location before scheduling this task. For more information, see "Batch File Uploads/Downloads." If there is no file present to load a particular measure in that measure set, it will be logged as not found and skipped.

This process will only load the data into those measures and will not run any subsequent calculations. The Administrator may need to schedule the necessary Run Batch Calc Group task after scheduling this task in order to process the loaded data.

The Predefined Measure Load Options in MFP are listed below:

Actuals Data (load_act) - To load all the measures containing actual data as needed such as Sales, Inventory, Receipt, Shrink, and so on.
On Order Data (load_oo) - To load only On Order data files.
Admin Data (load_adm) - To load planning administration level data such as VAT %, Currency Conversion Rates, Week Mapping, and so on.
RMS Forecast (load_rms) - To load transformed RMF CS interface data files.
Translation Files (load_tran) - To load all the translation files.

For details about the list of measure files that are loaded for different measure sets and information on the data file formats, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Run Batch Measure Export Group

This task exports a predefined set of measure data into flat files. The predefined set of measures to be exported are defined in the batch control file batch_exportmeas_list.txt. This set of exported data can be used for integration with other applications. Typically, the data exported can be interfaced to an external database that can be used to create reports or queries by users who need Planning data. The Administrator needs to schedule the Set Export Flags under the Run Batch Calc Group task to set the required export flags before scheduling this task. Exported files for this task are put into the SFTP Export location; the Administrator can download the files from this location. For more information, see "Batch File Uploads/Downloads."

The standard exports from MFP are available to the retailer to use by any downstream applications which needs MFP plan data. Default approved plan standard exports are included as part of the daily and weekly batch.

The predefined options for these tasks are listed below:

Merch Plan - Current Plan (mpcp)
Merch Plan - Original Plan (mpop)
Merch Plan - Submitted Plan (mpwa)
Merch Plan - Working Plan (mpwp)
Merch Target - Target Plan (mttg)
Merch Target - Working Plan (mtwp)
Location Plan - Current Plan (lpcp)
Location Plan - Original Plan (lpop)
Location Plan - Working Plan (lpwp)
Location Target - Target Plan (lttg)
Location Target - Working Plan (ltwp)

For details about the different versions for export, the list of measures exported in each file, and the file name and format details, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Run Batch Calc Group

This task is used to run a predefined set of all batch rules (as batch calc sets) against the domain to do the necessary data aggregation that is defined in the batch control file batch_calc_list.txt.

The following predefined batch calculation sets are available in MFP:

Weekly Batch Calc (batch_week)
Generate Forecast (batch_fcst)
Set Export Flags (exp_set)

Weekly Batch Calc (batch_week)

This batch calc set is used to run all required batch process calculations to do the necessary data aggregation and inventory roll operations after the weekly data load. It internally runs the batch rule groups Batch_GB, Batch_AggW and Batch_InvRoll.

This allows the users to see actualized data for the current elapsed week such as sales, markdowns, and receipts as well as inventory for both current and recalculated for future periods. This also allows users to see a sales forecast based on actuals that have been loaded and apply the trend to go forward weeks.

This process runs as part of a Weekly Batch. This task may be also scheduled if a retailer has data issues and needs to reload corrected actual data files in the middle of week and reprocess the week batch calculation.

Batch_GB sets the elapsed measures and runs domain calcs for the Location Target measures. Batch_AggW copies all loaded actuals into the WP and CP versions for the elapsed periods. Batch_InvRoll rolls forward the new EOP of the elapsed periods to the future BOP and EOP for both the WP and CP versions.

Generate Forecast (batch_fcst)

This batch calc set is used to generate forecast data used by MFP Cloud Service. It uses the embedded RDF forecast procedures by calling the internal configuration rule groups Batch_Fcst_G and Batch_Fcst_L. These rule groups call the embedded RDF forecast procedure to calculate the forecast for future periods of all versions using loaded actual and approved plan data. It calculates both the in-season forecast and pre-season forecast for all versions. Only one version of the forecast is shown in the workbook, based on the workbook build for in-season or pre-season. It uses the Auto-ES forecast method for Pre-Season forecasts and the Bayesian forecasting method for In-Season forecasts for all levels of plans. The customer can modify this to supported forecast methods at the department/channel level in the MFP Maintenance -> MFP Setup -> Forecast Setup view.

This process also runs as part of the regular weekly batch, but if the retailer wants to regenerate the forecast after loading corrected actuals in the middle of the week, then they can run this task.

Following is the list of forecast measures that are calculated by this process:

Wp Fcst In Reg+Promo R
Wp Fcst In Clr R
Wp Fcst In Reg+Promo U
Wp Fcst In Clr U
Wp Fcst Pre Reg+Promo R
Wp Fcst Pre Clr R
Wp Fcst Pre Reg+Promo U
Wp Fcst Pre Clr U

Set Export Flags (exp_set)

This batch calc set is used to set the necessary export flags for all standard exports used by MFP Cloud Service. The user can control the position exported for all versions by setting the administration measure addvexportb Export Mask in the Manage Export view. If the Export Elapsed Periods flag is set to false (the default), it will not export elapsed period data. This task sets export flags for each version of exports based on the Export Mask. For approved and submitted plans, the export flag is set based on the Export Mask and Approved or Submitted Info measure. For working plans, it is set based on the Export Mask and Seeded Info measures.

By default, daily and weekly batch runs these calculations before running an export. It can be turned off during the daily or weekly batch by turning off the Boolean admin measures Enable Daily Exports and Enable Weekly Exports in the Manage Batch view. The Administrator needs to run this task only if they have changed the export settings and wants to create an on-demand plan data export.

Run Batch Task Group

This task is used to schedule a predefined set of batch tasks such as load measure, batch calc, and batch exports in a sequential order. The batch control file
batch_exec_list.txt defines the steps in the specific order that will be executed during batch task execution. This task is used to schedule a typical daily or weekly MFP Cloud Service batch. If any task aborts, a log is created and the process terminates. This task has the option to restart from the last failed service rather than running all the completed services again.

Note:

Typically, the Administrator must schedule this task within a time frame after a domain backup and when no users are logged into the domain because this task runs in domain exclusive mode. The Administrator must work with Oracle to find out the time of backups and any other jobs.

The following predefined batch sets are available:

Daily Batch (batch_daily)
Weekly Batch (batch_weekly)
Transform RMS Files (batch_rms_xform)
Transform RMS Warehouse Data (batch_rms_wh)
Load Hierarchies (load_hier)
Export All Approved Plans (export_all)
Export All Working Plans (export_wp)
Exports to Retail Insights (export_ri)
Exports to Shared Services (export_ss)
Post Build Batch (postbuild)

Daily Batch (batch_daily)

This task is used to schedule a daily plan data export and load on-order files. A retailer may need on-order on a daily basis during an open-to-buy for example.

If a daily load or export is not needed, this step can be skipped as they are scheduled in the weekly load/export process. Steps in this process are also part of the Weekly Batch, so they do not have to schedule this during weekly batch.

Also, if the retailer does not need exports on a daily basis, they can skip scheduling this process.

This task runs the following set of activities in this order:

Run Batch Calc: Set Batch Specific Flags
If Enable Daily Exports is set to true: Set Export Flags and Export All Plan Versions
Measure Load: Load On Order and Process On Order
Rebuild Dashboard

Weekly Batch (batch_weekly)

This task is used to schedule a typical weekly MFP batch, which includes loading all hierarchy files and actual data and running all batch aggregations tasks needed for inventory roll. This task is the main task that needs to be scheduled to run on a weekly basis so the Administrator can see the most up-to-date location and product structures and information. Before scheduling this task, all necessary hierarchy and data files need to be uploaded to the SFTP server. This task runs the conditional execution of different tasks based on the various batch control flags set in the application.

This task runs the following activities in this order:

Run Batch Calc: Set Batch Specific Flags
If Enable Weekly Exports is set to true: Set Export Flags and Export all Plan Versions
If Enable RMF CS Integration is set to true:
- If no PDS and no BDI (Flat file integration): Transform RMS Files
- If PDS and no BDI: Load Dimension Data into PDS
- Load Hierarchies
- If no PDS and no BDI (Flat file integration): Load RMF CS Interface Files
- If PDS and no BDI: Load Fact Data into PDS
- Load non-RMF CS Interface Files
- Run Batch Calc: Batch Agg for RMF CS data
- Run Batch Calc: Transform RMF Warehouse Data
If Enable RMF CS Integration is set to false:
- If PDS is not enabled: Load Dimension Data
- Load Hierarchies
- If PDS is enabled: Load Actuals
- If PDS is enabled: Load non-RMF CS Interface Files
- If PDS is enabled: Batch Agg for PDS Loaded Data
Run Batch Calc: Weekly Batch Calc
Run Batch Calc: Generate Forecast
Refresh All Workbooks
Rebuild Dashboard

Transform RMS Files (batch_rms_xform)

This task is used to transform all hierarchy and data files from RMF CS to the MFP required format. This task transforms the RMF CS hierarchy and data files and also creates rms_hier.zip and rms_data.zip and copies them to the SFTP outgoing path. This task is mainly for creating the initial set of transformed RMF CS hierarchy files to build a new domain with the RMF CS hierarchy files using Self Service. The user does not need to use this task if there is no RMF CS integration.

This task runs the following activities in this order:

Transform RMF CS Calendar Hierarchy File
Transform RMF CS Product Hierarchy File
Transform RMF CS Location Hierarchy File
Transform RMF CS Currency Hierarchy File
Transform RMF CS Inventory File
Transform RMF CS On Order File
Transform RMF CS Tran Data File
Transform RMF CS Currency Conversion Rate File
Transform RMF CS Location File

Transform RMS Warehouse Data (batch_rms_wh)

This task is used to transform the loaded RMF CS warehouse inventory, receipts, and on-order data to the mapped MFP Channels. It also spreads those warehouse metrics to stores within those channels, to be used in the Location Plan. It actually creates an internal export of loaded warehouse inventory, receipts, and on-order data, transforms warehouse to channels and reloads, and then runs the batch aggregates. This task runs as part of the regular Weekly Batch with RMF CS Integration enabled. The user needs to schedule this only if the user changes the Warehouse-Channel Mapping in the middle of week and would like to reallocate the Warehouse Inventory to the newly mapped Channels for all history in the middle of the week. The user does not need to use this task if there is no RMF CS integration.

This task runs the following activities in this order:

Run Batch Calc - Initialize RMF CS Warehouse Data for Export
Exports RMF CS Warehouse Inventory Data
Transform RMF CS Warehouse Inventory with MFP Channel
Exports RMF CS Warehouse On Order Data
Transform RMF CS Warehouse On Order with MFP Channel
Exports RMF CS Warehouse Receipt Data
Transform RMF CS Warehouse Receipt with MFP Channel
Load RMF CS Warehouse data to MFP Channel
Run Batch Calc - Weekly Batch Calc

Export All Approved Plans (export_all)

This task is used to export all submitted and approved plan versions (all non-working plan versions). This task first runs the export set flag task and then exports all the plan versions. This task also runs as part of the daily or weekly batch, so the user needs to run this task only if they need to re-export all plan data on an on-need basis. The exported data is used in reports, customer's data marts, and query programs.

Following is the list of export plan versions that are exported for both MFP Retail Cloud Service and MFP Cost Cloud Service:

Merch Plan - Current Plan
Merch Plan - Original Plan
Merch Plan - Submitted Plan
Merch Target - Target Plan
Location Plan - Current Plan
Location Plan - Original Plan
Location Target - Target Plan

For details on the versions for export, the list of measures exported in each file, and the file name and format details, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Export All Working Plans (export_wp)

This task is used to export all the working plan versions. This task first runs the export set flags task and then exports all working plan versions. This task only needs to be run if the user wants an export of all working plan versions for any reporting needs.

Following is the list of export plan versions that are exported for both MFP Retail Cloud Service and MFP Cost Cloud Service:

Merch Plan - Working Plan
Merch Target - Working Plan
Location Plan - Working Plan
Location Target - Working Plan

Exports to Retail Insights (export_ri)

This task is used to export all approved Merch Plans for the planned periods to Oracle Retail Insights (RI) Cloud Service Suite. This can only be scheduled if the retailer has Oracle Retail Insights (RI).

Following is the list of export plan versions that are exported for both MFP Retail Cloud Service and MFP Cost Cloud Service:

Merch Plan - Current Plan
Merch Plan - Original Plan

For details about integration with RI, the list of measures exported in each file, and the file name and format details, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Exports to Shared Services (export_ss)

This export set is used to export all approved Merch Plans and Location Plans for the planned periods to Assortment & Item Planning Cloud Service. It exports the required measures and copies the file to the common cloud service application share location RGBU_CLOUD_DATA. Assortment & Item Planning Cloud Service can access the file from that location.

Post Build Batch (postbuild)

This task is available as an option to be called as part of the initial domain build, to load and process all loaded initial data after the initial domain build. If not called during the domain build time, this task can be run after the domain build using this OAT task.

Scheduling Configured Batch Administration Tasks

This section walks through an example of the process for scheduling and monitoring the Configured Batch Administration task named Run Batch Measure Export Group. The steps for scheduling all other tasks are similar, and most of the tasks do not have additional input parameters specific to that task. For more details about scheduling and monitoring online administration tasks, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide.

To schedule and monitor a Configured Batch Administration task:

Log in to the MFP Retail Cloud Service (mfprcs) or MFP Cost Cloud Service (mfpccs) application as an Administration user.
In the Tasks list, select Admin Tasks for MFP CS Retail/Cost Customer Domain and then select Online Admin Tools. Click Submit a New Admin Task.

Figure 1-1 Administration Tasks
Select the Configured Batch Tasks for Task Group and click Next.

Figure 1-2 Select Task Group Window
In the task list, select Run Measure Export Group and click Next.

Figure 1-3 Select Task Workbook Wizard Window
Enter the Task Label. This task has an additional parameter to choose the export measure group. In following figure, as an example, Merch Plan - Current Plan is selected. Click Next.

Figure 1-4 Select Export Measure Group
To schedule the task to run immediately, select Run ASAP and click Next. To run on a particular date and time, set that information, select Run on a Schedule (One time / Hourly /Daily/ Weekly/ Monthly). Provide the Server Start / Stop Date/Time and click Next.

Figure 1-5 Schedule Task Workbook Wizard Window
In the Confirm Action window, review the task scheduling details. To confirm the scheduling and submit the task, click Finish.

Figure 1-6 Confirm Action Window

The task submitted confirmation message appears.

Figure 1-7 Task Submitted Confirmation Message

To check the status of all submitted tasks in the Dashboard, click Dashboard and select Administration from the list of Dashboard Profiles in the dropdown.

Figure 1-8 Location of Administration Dashboard Selection

At the bottom of the dashboard, it contains the lists of tasks submitted and their status.

Figure 1-9 List of Submitted Tasks

The Status column shows whether a job has completed successfully, failed, or is pending (Scheduled). For any completed (Success/Failed) tasks, click the job name to view the subtask details if any for that job. To view the log, select the task and click Download Log. For failed tasks, the logs show the error details.

Following is an example of a log showing an error:

Surrounding text describes oat-log-example1.png.

Following is an example of a log showing the cause of an error:

Surrounding text describes oat-log-example2.png.

Note:

The detailed log file can be found in the SFTP sever. The log file names are first appended with the text success/failure (with error code) along with the process name and control file entry set names and the time stamp for easy identification. For example:

success.eebatch_calc.exp_set.20190614124917.tar.gz

failure.13.eebatch_exec.setup.20190614043009.tar.gz

Modify Configured Batch Tasks

Due to a business requirement, the Administrator may need to modify a scheduled batch task. The Modify an Admin task capability of RPAS provides the Administrator the tool to handle this kind of situation.

For example, an Online Administration Tool task is currently scheduled for weekly once on Sunday, but due to a business constraint, the Administrator needs to run the specific task on Saturday instead of Sunday for a week. The Administrator can achieve the goal using the Modify an Admin task.

The alternate way of handling with any change in a scheduled task is by copying the scheduled task, changing the start date, and then deleting the original scheduled task.

The Administrator submits any configured Batch Task scheduled weekly on Sunday. The following steps walk you through the process of changing the schedule of any scheduled batch using Online Administration Tools:

Set up the Run Batch Task Group.

Figure 1-10 Schedule Task Window
Review the selected setup.

Figure 1-11 Confirm Action Window
View the submitted task on the dashboard.

Figure 1-12 View of Submitted Task
Modify the task to run on Saturday rather than Sunday.

Figure 1-13 Admin Tasks
Select the task to modify.

Figure 1-14 Modify an Admin Task
Verify the details. Enter the new parameters for modification.

Figure 1-15 Modify an Admin Task
Submit the modified task.

Figure 1-16 Confirm Action Window

Dashboard

The Dashboard provides pre-configured dashboard profiles to the user once logged into the application. There are six profiles pre-configured for MFP CS:

Administration - task status
MFP: In-Season
MFP: Pre-Season
MT: Exceptions
MP: Exceptions
LP: Exceptions

For more information about the usage of Dashboards in MFP CS, see the Oracle Retail Merchandise Financial Planning Cost Cloud Service User Guide and Oracle Retail Merchandise Financial Planning Retail Cloud Service User Guide.

The dashboard pulls the data from an admin workbook built from the Online Administration Tool. In order to view the dashboard, an Administrator must schedule the dashboard builds from the System Admin Tasks.

Figure 1-17 Schedule Dashboard Build Task

Surrounding text describes Figure 1-17 .

Figure 1-18 Specify Arguments for Schedule Dashboard Build Task

Surrounding text describes Figure 1-18 .

Task Label - Enter the name of the build task to review the status of build.
Select Override RPAS_TODAY - Check box and then select a date, if you need to build the dashboard as of a day other than the current date.
Range dimension - Calendar dimension against which the dashboard will be pre-ranged.
Pre-Season Range - Number of periods of the Range dimension that need to be included before the Current period Range. Current Period Range will be always included.
Post-Season Range - Number of periods of the Range dimension that need to be included after RPAS_TODAY.
Select Delete and Recreate Dashboard Segment check box, only if there are any changes to the dashboard template selection after patching.
Users - Select All Users, Group, or Users that can access that dashboard.

Note:

For the pre-configured GA dashboard profiles, the preferred selections for Range dimension: Half, Pre-Season Range: 1, and Post-Season Range: 1.

Retail Home

If Retail Home is configured, it provides a dashboard view of key configured metrics as tiles across multiple applications in the enterprise. MFP CS has the following tile views configured for Retail Home. The metrics are configured in the same dashboard templates, so the regular dashboard segment first should be built first, in order to see the tiles from Retail Home. Retail Home uses a different set of JSON files to get the data from the dashboard segments into these tiles. In this release, it is only available for non-Enterprise Edition implementations.

Figure 1-19 MFP CS Tile View for Retail Home

Surrounding text describes Figure 1-19 .

Metrics shown in the above figure:

Month-to-Date Sales (MTD)
MTD Sales to Plan (OP)
MTD Sales variance to LY
MTD Margin %
MTD Margin variance to Plan (OP)
MTD Margin variance to LY
Open to Buy bullet chart: total is Open to Buy + Net On Order

Figure 1-20 MFP CS Tile View for Retail Home

Surrounding text describes Figure 1-20 .

Metrics shown in the above figure:

Year-to-Date Sales (YTD)
YTD Margin %
YTD Sales variance to Plan (OP)
YTD Returns
Line Chart: YTD Sales variance to Plan with X-axis as Month

Batch File Uploads/Downloads

The following sections describe the file upload/download process. For the batches that load data, the Administrator needs to upload the relevant files which load the data to the SFTP server before running the batch. After running any export task, the exported files can be found in the export location of the SFTP server.

For details regarding file contents and formatting of the upload and download files, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

Adding Authorized Keys

This section describes the process to generate a 2048 bit RSA key and add the same to the SFTP server. This is done with the help of the WinSCP tool on Windows. However, the same can be done using ssh-keygen on Linux as well.

Prerequisites:

The WinSCP tool must be installed before performing the following process.
The Private/Public keys must be generated and the Public key must be associated with your SFTP Account for the file upload/Download.

Launch WinSCP and select Tools > Run PuttyGen.
Select SSH-2 RSA for the type of key to generate and enter 2048 for the number of bits in a generated key field. Click Generate.

Figure 1-21 Key Generator
Move the mouse over the blank space in the window until the key is generated. Moving the mouse over the blank space creates a random pattern which is used for key generation.

Figure 1-22 Key Generator Progress
Once the key is generated, click Save public key to save the public key to a file.
Click Save private key to save the private key to a file. Confirm to save it with or without a passphrase.
Open an SR with Oracle Support, to associate the public key with your SFTP account (attach the key with the SR).

Logging In to WinSCP

The upload steps use the private key generated in the Adding Authorized Keys section.

Launch WinSCP and connect to <SFTP Server> using port 22.
Enter the user name and click Advanced.
Click Authentication.
In the Private Key File field, click Browse and select the private key created in the Adding Authorized Keys section.

Figure 1-23 Advanced Site Settings Dialog
After loading the private key file, click OK.

Figure 1-24 Private Key File Loaded
Click Login. The window does not prompt for a password and logs in to the SFTP server. Provide a passphrase if one has been set up.

Uploading the Batch File

The following diagram provides an overview of the FTP/internal holding area/domain and how the files move.

Figure 1-25 File Movement Between Internal Holding Area and Domain

Surrounding text describes Figure 1-25 .

The following steps walk you through the process to upload batch (data/Hierarchy) file. For information about the administration tasks that require uploading batch files, see "Application-Specific Batch Tasks."

For information about the file contents of various exports and formatting, see the information on data load in the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

To upload the batch file:

Log in to WinSCP. Follow the steps in "Logging In to WinSCP."
Transfer all the data files to the directory /<SFTP User>.
Create a directory named COMMAND under /<SFTP User> if it does not already exist.
Change to the /<SFTP User>/COMMAND directory.
Transfer an empty file named COMPLETE.
Run the required batch/task from the Online Administration Tools.

File Downloads

The following steps walk you through the process of accessing download files. For information about the administration tasks that create different exports from the applications, see "Application-Specific Batch Tasks."

For information about the file contents of various exports and formatting, see the information on exports in the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

To download files:

Log in to WinSCP. Follow the steps in "Logging In to WinSCP."
Change the directory to /<SFTP User>/EXPORT or /<SFTP User>/Export/logs (for log files).
Create a directory named COMMAND under /<SFTP User>/EXPORT if it does not already exist.
Change to the /<SFTP User>/EXPORT/COMMAND directory.
Transfer an empty file named COMPLETE.
Run the required batch/task from the Online Administration Tools.

Download all the data files. The log files are in tar.gz format.

Note:

The log file names are appended with the success/failure text in it along with the time stamp for easy identification.

For example:
success.<process_name>.<set_name>.<timestamp>.tar.gz and failure.<error_code>.<process_name>.<set_name>.<timestamp>.
tar.gz