1. Implementation Guide
  2. Integration with Merchandising
  3. Batch Job Setup (Gen 2 Architecture)

Batch Job Setup (Gen 2 Architecture)

The way you configure the integration with RMFCS varies depending on where your Merchandising applications reside. In this scenario, you have both RMFCS and CE in our 2nd generation architecture and the version number is 22.1 or greater.

If you followed the Retail Home setup steps prior to this section, then most of the jobs listed below should already be configured to your specifications. However, it is still good to validate the necessary jobs are enabled/disabled per the requirements before attempting any batch run. Take the following steps to review/configure the RDE portion of the AIF DATA batch schedule:

  • Enable the jobs RDE_SETUP_INCRMNTL_RESA_JOB, RDE_SETUP_INCRMNTL_DEALACT_JOB, RDE_SETUP_INCRMNTL_JOB, and RDE_INCRMNTL_AUDIT_PRG_JOB which are mandatory for sales integration with Sales Audit and Deals integration with MFCS.

  • Disable the batch schedule link between BATCH_INITIAL_START_PROCESS / GENERIC_BATCH_MILE_MARKER_JOB and RDE schedule’s RDE_BATCHFINAL_PROCESS / RDE_BATCHFINAL_EXTLOAD_SUCCESS_JOB (if one is visible). This batch link should be disabled now because RDE is a part of AIF DATA’s schedule and is on the same POM and batch pod, which was not true in prior architectures.

  • If the client opts not to integrate the ORCE customer data, the ORCE jobs can be disabled (those with RDE_EXTRACT_CE_*). These jobs are under the following modules:

    • RDE_CE

    • RDE_CE_BATCH

    • RDE_CE_REQUIRED

    • RDE_CE_OPTIONAL

    • RDE_CE_CUSTOMER

    • RDE_CE_CUSTSEG

    • RDE_CE_LOYALTY

  • If the client opts to integrate the ORCE customer data (which means that the ORCE jobs are enabled - those with RDE_EXTRACT_CE_*), the following AIF DATA jobs should be disabled as the customer data will directly be populated without an input file:

    • W_RTL_CUST_DEDUP_DS_COPY_JOB

    • W_RTL_CUST_DEDUP_DS_STG_JOB

    • W_RTL_CUST_LYL_AWD_TRX_DY_FS_COPY_JOB

    • W_RTL_CUST_LYL_AWD_TRX_DY_FS_STG_JOB

    • W_RTL_CUST_LYL_TRX_LC_DY_FS_STG_JOB

    • W_RTL_CUST_LYL_TRX_LC_DY_FS_COPY_JOB

    • W_RTL_CUST_LYL_ACCT_DS_COPY_JOB

    • W_RTL_CUST_LYL_PROG_DS_COPY_JOB

    • W_RTL_CUSTSEG_DS_COPY_JOB

    • W_RTL_CUSTSEG_DS_STG_JOB

    • W_RTL_CUSTSEG_DS_ORASE_JOB

    • W_RTL_CUST_CUSTSEG_DS_COPY_JOB

    • W_RTL_CUST_CUSTSEG_DS_STG_JOB

    • W_RTL_CUST_CUSTSEG_DS_ORASE_JOB

    • W_RTL_CUSTSEG_ATTR_DS_COPY_JOB

    • W_RTL_CUSTSEG_ATTR_DS_STG_JOB

    • W_RTL_CUST_HOUSEHOLD_DS_COPY_JOB

    • W_RTL_CUST_HOUSEHOLD_DS_STG_JOB

    • W_RTL_CUST_ADDRESS_DS_COPY_JOB

    • W_RTL_CUST_ADDRESS_DS_STG_JOB

    • W_PARTY_PER_DS_COPY_JOB

    • W_PARTY_PER_DS_STG_JOB

    • W_RTL_PARTY_PER_ATTR_DS_COPY_JOB

    • W_RTL_PARTY_PER_ATTR_DS_STG_JOB

    • W_HOUSEHOLD_DS_COPY_JOB

    • W_HOUSEHOLD_DS_STG_JOB

  • Disable most of the AIF DATA copy jobs (those with *_COPY_JOB) except ones needed for non-RMFCS sources. These jobs should be disabled because these jobs will copy files and upload them from object storage. This is not needed because data is loaded directly into the staging tables and flat files are not expected to arrive for processing. Most of these jobs are under the following modules:

    • RI_DAT_STAGE

    • RSP_DAT_STAGE

  • Disable most of the AIF DATA stage jobs (those with *_STG_JOB) ) except ones needed for non-RMFCS sources. These jobs should be disabled as these jobs read from a flat file which are not available if using this integration. Most of these jobs are under the following modules:

    • RI_DAT_STAGE

    • RSP_DAT_STAGE

  • Disable the RAP Simplified Interface jobs (those with SI_*, COPY_SI_*, and STG_SI_* at the start of the name) as RMFCS will be the source of data to feed RI. Most of these jobs are under the modules with the patterns below:

    • RI_SI*

    • RSP_SI*

  • Disable the AIF DATA program W_PROD_CAT_DH_CLOSE_JOB, which is used to close unused hierarchy levels when non-Merchandising incremental hierarchy loads are used in RAP. It must not run with Merchandising, because the product hierarchy data is already being managed by RDE extracts.

  • Disable the AIF DATA programs ETL_REFRESH_JOB and BATCH_START_NOTIFICATION_JOB (specifically the versions belonging to process SIL_INITIAL_PROCESS) because these are redundant with jobs included in the RDE schedule.

  • If you are not providing any flat file uploads and using only RMFCS data, you may disable the jobs in CONTROL_FILE_VALIDATION_PROCESS, which will prevent any data files from being processed (and potentially overwriting the RMFCS data).

  • Disable the job named TRUNCATE_STAGE_TABLES_JOB, which is used only for data file loads and cannot be run when RDE jobs are used for direct integration. A similar job named RDE_TRUNCATE_STAGE_TABLES_JOB should remain enabled as this does apply to RDE job execution.