1. Implementation Guide
  2. Appendix: Loading Replenishment Data

C Appendix: Loading Replenishment Data

Currently, replenishment conversion is not support by Data Conversion tool. This section outlines different ways for loading replenishment data by utilizing core replenishment processing in RMFCS.

Manual Spreadsheet Upload

This functionality supports manual upload of replenishment information from a spreadsheet into REPL_ATTR_UPDATE* tables. An upload from a spreadsheet is initiated by user request through Merchandising screens. Post processing of data into replenishment tables including MASTER_REPL_ATTR table will be done through replenishment batch process. Records are picked by batch processing based on activation date in REPL_ATTR_UPDATE_HEAD table. The size for upload file is controlled by a system parameter, REPL_INDUCT_CONFIG.MAX_FILE_SIZE_FOR_UPLD. By default, it allows maximum file size of 500000 bytes, however this can be increased to support loads up to 2MB.

Bulk Upload Batch

Bulk integration capability is provided through the upload replenishment induction data batch process (replindbatch.ksh), which bulk uploads xml file data to REPL_ATTR_UPDATE* tables. Based on Activate Date, item/location becomes active for replenishment through replenishment batch process. Bulk upload is preferred over manual spreadsheet upload when file size is greater than 2MB. The XML format accepted by the batch will be the same as the deconstructed XML format used by manual spreadsheet upload.

The batch supports multiple files to be loaded at one time, then a single batch call can be scheduled using the Process Orchestration and Monitoring (POM) solution or batch scheduler to process all the files.

Replenishment Schedule ReST Service

This service creates scheduled replenishments to load input data to the staging tables and then calling the core replenishment package to validate and insert data to the REPL_ATTR_UPDATE* tables. Based on Activate Date, item/location becomes active for replenishment through replenishment batch process. You are required to build a script to call this rest service.

Custom Load Script

You may also choose to load replenishment data by means of custom scripts in the pre-production environment using the APEX Data Viewer. There are two ways to load data using this approach,

  1. Load data directly into main merchandising replenishment tables. This requires loading data into MASTER_REPL_ATTR table using the data conversion tool and then running custom scripts to load data into other replenishment tables. Or,

  2. Load data into REPL_ATTR_UPDATE* tables using custom scripts. Processing of data into replenishment tables including MASTER_REPL_ATTR table will be done through replenishment batch process.

Key Considerations

  • If you wish to just load the data into REPL_ATTR_UPDATE* tables and not make these record active during the data conversion, either populate the ACTIVATE_DATE as a future date, like cut-over or go-live date, in upload files so that it becomes active from that date. Another option is after loading the data into REPL_ATTR_UPDATE* tables, do a mass update of activate and deactivate date to a date prior to the SCHEDULED_ACTIVE_DATE. Ensure DEACTIVATE_DATE should be at least ACTIVATE_DATE +1.

  • Regardless of method used, the activate date must be set to the current date or later. Past dates are not supported.