mdp_matrix : A series that consists of time-independent data for each item-locat

ion combination. This

data is stored in mdp_matrix.
MSC_ST_PLANNERS : Data integrity errors detected during the load are stored in t
he ERROR_TEXT field in the
appropriate staging table, for example, MSC_ST_PLANNERS.
MSC_ST_PRICE_LIST : the price list data resides in the MSC_ST_PRICE_LIST staging
table.
T_SRC_ITEM_TMPL Demantra Staging Table
Data for additional levels in the item hierarchy can be stored i
n the T_SRC_ITEM_TMPL Demantra staging table.
T_SRC_ITEM_TMPL has several placeholder columns such as E1_ITEM_CATEGORY_1 to
E_ITEM_CATEGORY_23. These columns can be used to load data for n
ew item hierarchy levels.
In the shipped settings, seven columns are mapped to placeholder levels such as
Item Category
Code 1 and Item Category Code 2. If you need to use more than seven levels, upda
te the data
model to map the columns in T_SRC_ITEM_TMPL to new levels.
T_SRC_LOC_TMPL Demantra Staging Table
Data for additional levels in the organization hierarchy can be stored in the T_
SRC_LOC_TMPL
Demantra staging table.
T_SRC_LOC_TMPL has several placeholder columns such as E1_BRANCH_CATEGORY_1 to
E1_BRANCH_CATEGORY_30. These columns can be used to load data for new organizati
on
hierarchy levels.
In the shipped settings, five columns are mapped to placeholder levels such as B
ranch Category
Code 1 and Branch Category Code 2. If you need to use more than five levels, upd
ate the data
model to map the columns in T_SRC_LOC_TMPL to new levels.
The data for the additional levels in the organization hierarchy can be stored i
n the Demantra
staging table T_SRC_LOC_TMPL. The data for the additional levels in the customer
site
hierarchy can be stored in T_SRC_LOC_TMPL.