Merchandising Foundation Cloud Service Data Mapping
After Golden Gate makes the copy of all data residing in the source Merchandising Foundation Cloud Service (MFCS) environment, there is a mapping layer that connects the replicated database schema to Retail Data Extractor (RDE) programs. This mapping layer consists of two parts:
-
The replicated schema contains wrapper view (WV) objects on top of the cloned tables to provide a layer of abstraction between the source and destination. If the underlying table changes in the source it does not necessarily have to impact the target systems, since the view could remain unchanged. For example, the source table
ITEM_MASTER
has a wrapper viewRDS_WV_ITEM_MASTER
on top of it. -
Within the target RAP database, synonyms are created to map each wrapper view back to its source system name. The synonyms are what are granted to RDE and Innovation Workbench. For example, there is a synonym named
ITEM_MASTER
which is used by RDE to extract data from theRDS_WV_ITEM_MASTER
view. TheITEM_MASTER
synonym can also be directly queried from Innovation Workbench instead of trying to query the original wrapper view object. The synonyms reside in theRABE01USER
user in the database.
This architecture is used for almost all objects from MFCS, with the following exceptions:
-
The synonym for
ITEM_LOC_SOH
points to the MFCS tableITEM_LOC_SOH_EOD
, which is the end-of-day inventory snapshot. This is required for RAP to ensure it receives the same end-of-day inventory positions that MFCS and other applications will show. TheITEM_LOC_SOH
table itself is not used in RAP integrations at this time due to the constantly changing data from 24/7 inventory program activity. -
The synonym for
MV_CURRENCY_CONVERSION_RATES
refers toV_CURRENCY_CONVERSION_RATES
. This is becauseMV_CURRENCY_CONVERSION_RATES
cannot be replicated to a Golden Gate schema, so MFCS created theV_CURRENCY_CONVERSION_RATES
view as a replacement. -
RAP uses the
RMS_CALENDAR
synonym to refer to theCALENDAR
table. This is because RI also has aCALENDAR
table in its schema and the object names would have conflicted within RDE.