This section is only applicable for EICS to integration with customer have on-premise RPM, RPM pricing files are placed on EICS SFTP incoming locations, and the file import job processes each file from incoming directory when a corresponding completer file presents. The completer is a zero byte file which indicates file transfer is complete and ready for processing. The reject files will be pushed to outgoing for client review.
Note:
Pricing file import from On-premise RPM will be phased out in future releases.This batch imports the clearance price changes from flat file into item price table. Each file contains price change record for a single location. Files with location type of store (file name with suffix of "S") are relevant to EICS. The import process skips file with location type which are not store.
There are two phases involve in the batch process. The file load phase loads the file into price change worksheet table; the extract phase kicks off multiple threads to extract the approved worksheet records into item price table.
To optimize price change batch import process, admin user can change the system configuration parameter 'DAYS_TO_HOLD_PRICE_CHANGE_WORKSHEET' value
to 0, the completed staged worksheet records will be deleted after price change records are extracted into item_price table.
File Name Format: CLRPC _<date in YYYYMMDDHH24MISS format>_<loc type>
Where <loc type> can be S (store) or W (Warehouse), EICS only process files which have loc_type of S.
File Layout: See Clearance Price Change Import File Layout Specification.
ClearancePriceChange_OpsJob
<File name>
If not specified, then the data file in incoming directory are processed.
The batch job will be marked as failed if the file staging fails. The staging process is all or none transaction so if an error occurs during the batch process, none of the transactions in the file will be staged. The user will need to rerun the same file again after resolving any errors.
This batch imports the promotion price changes from flat file into item price table.
There are two phases involve in the batch process. The file load phase loads the file into price change worksheet table; the extract phase kicks off multiple threads to extract the approved worksheet records into item price table.
To optimize price change batch import process, admin user can change the system configuration parameter 'DAYS_TO_HOLD_PRICE_CHANGE_WORKSHEET' value
to 0, the completed staged worksheet records will be deleted after price change records are extracted into item_price table.
File Name format: PRMPC_<date in YYYYMMDDHH24MISS format>_<loc id>_<loc type>
Where <loc type> can be S (store) or W (Warehouse), EICS only process files which have loc_type of S.
File Layout: See Promotion Price Change Import File Layout Specification.
PromotionPriceChange_OpsJob
<File name>
If not specified, then the data file in incoming directory are processed.
The batch job will be marked as failed if the file staging fails. The staging process is all or none transaction so if an error occurs during the batch process, none of the transactions in the file will be staged. The user will need to rerun the same file again after resolving any errors.
This batch imports the regular price changes from flat file into item price table.
There are two phases involve in the batch process. The file load phase loads the file into price change worksheet table; the extract phase kicks off multiple threads to extract the approved worksheet records into item price table.
To optimize price change batch import process, admin user can change the system configuration parameter 'DAYS_TO_HOLD_PRICE_CHANGE_WORKSHEET' value
to 0, the completed staged worksheet records will be deleted after price change records are extracted into item_price table.
File Name format: REGPC_<date in YYYYMMDDHH24MISS format>_<loc id>_<loc type>
Where <loc type> can be S (store) or W (Warehouse), EICS only process files which have loc_type of S.
File Layout: See Regular Price Change Import File Layout Specification.
RegularPriceChange_OpsJob
<File name>
If not specified, then the data file in incoming directory are processed.
The batch job will be marked as failed if the file staging fails. The staging process is all or none transaction so if an error occurs during the batch process, none of the transactions in the file will be staged. The user will need to rerun the same file again after resolving any errors.