Additional Source for Foundation Data
Some foundation data interfaces support merging two sources of information together into the same target table. One of
the sources must be MFCS while the other may be an external source that generates a CSV file for the nightly batch. This is
currently supported for Promotions, Shipments, Sales, and Inventory. These jobs should not be enabled in POM unless you are
planning to load data from an additional source, because they will conflict with the normal version of these interfaces (which
follows a truncate and load process instead of a merge). When the MERGE jobs are turned on, it is expected that all other SI_*
type jobs (like SI_W_RTL_SHIP_DETAILS_DS_JOB
) will be manually disabled, because the core
foundation dataset is coming directly from MFCS and not from these jobs.
Secondary Data Source | AIF DATA Jobs to Enable | AIF DATA Jobs to Disable |
---|---|---|
PROMO_DETAIL.csv |
SI_W_RTL_PROMO_IT_LC_DS_MERGE_JOB COPY_SI_PROMO_DETAIL_JOB STG_SI_PROMO_DETAIL_JOB |
SI_W_RTL_PROMO_IT_LC_DS_JOB |
SHIPMENT_HEAD.csv |
SI_W_RTL_SHIP_DETAILS_DS_MERGE_JOB COPY_SI_SHIPMENT_HEAD_JOB STG_SI_SHIPMENT_HEAD_JOB |
SI_W_RTL_SHIP_DETAILS_DS_JOB |
SHIPMENT_DETAIL.csv |
SI_W_RTL_SHIP_IT_LC_DY_FS_MERGE_JOB COPY_SI_SHIPMENT_DETAIL_JOB STG_SI_SHIPMENT_DETAIL_JOB |
SI_W_RTL_SHIP_IT_LC_DY_FS_JOB |
SALES.csv |
SI_W_RTL_SLS_TRX_IT_LC_DY_FS_MERGE_JOB COPY_SI_SALES_JOB STG_SI_SALES_JOB |
SI_W_RTL_SLS_TRX_IT_LC_DY_FS_ JOB |
SALES_PACK.csv |
SI_W_RTL_SLSPK_IT_LC_DY_FS_MERGE_JOB COPY_SI_SALES_PACK_JOB STG_SI_SALES_PACK_JOB |
SI_W_RTL_SLSPK_IT_LC_DY_FS_JOB |
INVENTORY.csv |
SI_W_RTL_INV_IT_LC_DY_FS_MERGE_JOB COPY_SI_INVENTORY_JOB STG_SI_INVENTORY_JOB |
SI_W_RTL_INV_IT_LC_DY_FS_JOB |
The way the data is merged depends on the interface. For PROMO_DETAIL.csv
, the Pricing CS data always
takes priority, and the CSV file data is inserted where it does not match an existing record. This is because the promotion
header interface (W_RTL_PROMO_DS
/ D
tables and PROMOTION.csv
file) from
Pricing CS already follows that logic and this detail-level table needs to match it. You should aim to ensure that there is
no overlap between the Pricing CS data and the external CSV file data.
Fact data uses configurable merge logic. For shipment data, it is a configuration option whether you want MFCS data or
the CSV files to get first priority when merging. Update the C_ODI_PARAM_VW
table from the Control Center
for parameter SHIP_SI_MERGE_PRIORITY
. When set to MFCS, the CSV file data will only be inserted if there
is no matching record. When set to EXT
(or any other value), the external file data will overwrite any matching
records from MFCS and insert for all other records. Sales and inventory use the same logic based on the value in parameters SALES_SI_MERGE_PRIORITY
and INV_SI_MERGE_PRIORITY
.