7.2 List of Values (LOV) Mapping

List of Values (LoV) mappings are used when a value for a business term in the source needs to be mapped to a different value in the target. Since, LoVs are well-defined for source and target business terms, DFCS allows a mapping of LoVs to be maintained between source and target business terms. Thus, it ensures that the data conforms to the specific set of allowed values in the target system. For PBSMCS, there are ~20 LoV mappings.

The first kind of LoV mapping between DFCS and PBSMCS is that is pre-defined (seeded) within DFCS. An LOV from a business term in DFCS is automatically mapped to a business term in PBSMCS. The user does not need to take any action.

Table 7-2 Type 1 – Pre-defined Mapping between Source Data and PBSMCS

Source Business Term Code	Source Business Term Name	PBSMCS Business Term Code	PBSMCS Business Term Name
Day Count Indicator	Day Count Indicator Name	Accrual Basis Code	Accrual Basis Name
Interest Rate Type	Interest Rate Type Name	Adjustable Type Code	Adjustable Type Name
Amortization Type	Amortization Type Name	Amortization Type Code	Amortization Type Name
Behavior Type	Behavior Type Name	Behavior Type Code	Behavior Type Name
Scenario Code	Scenario Name	Consolidation Code	Consolidation Name
Credit Status Code	Credit Status Name	Credit Status Code	Credit Status Name
Income Documentation Program Code	Income Documentation Program Name	Documentation Code	Documentation Name
Lien Position Code	Lien Position Name	Lien Position Code	Lien Position Name
Mortgage Occupancy Code	Mortgage Occupancy Name	Occupancy Code	Occupancy Name
Option Type	Option Type Description	Option Type Code	Option Type Name
Payment Type Code	Payment Type Name	Payment Type Code	Payment Type Name
Dimension Code	Dimension Name	Dimension Numeric Identifier	Dimension Name

Table 7-3 Example of Type 1 LoV Mapping:

Source - Interest Rate Type	Source - Interest Rate Type Name	PBSMCS - Adjustable Type Code	PBSMCS- Adjustable Type Name
Source - Interest Rate Type	Source - Interest Rate Type Name	PBSMCS - Adjustable Type Code	PBSMCS- Adjustable Type Name
Fixed Rate	Fixed Rate	FIX	Fixed Rate
Floating Rate	Floating Rate	FLOAT	Floating Rate
Other Adjustable	Other Adjustable	OTH_ADJ	Other Adjustable
Repricing Pattern	Repricing Pattern	REP_PAT	Repricing Pattern
Tier Rate	Tier Rate	TIER_RATE	Tiered Balance Interest Rate

User Specified Mapping between Source Data and PBSMCS

This is performed through a mapping table that refers to e.g. Account Status Code as Application Service Status Code. In Glossary Mapping and Connector Mapping for ADS, you will see mapping between Account Status Code (PBSMCS) to Application Service Account Status Code (DFCS).

Table 7-4 Type 2 – User Specified Mapping between Source Data and PBSMCS

Source Business Term Code	Source Business Term Name	PBSMCS Business Term Code	PBSMCS Business Term Code	Mapper Name
Account Status Code	Application Service Account Status Name	Account Status Code	Account Status Name	Mapper Base for Account Status Code in Profitability and Balance Sheet Planning
Party Type	Application Service Party Type Name	Customer Type Code	Customer Type Name	Mapper Base for Customer Type Code in Profitability and Balance Sheet Planning
Account Purpose Code	Application Service Account Purpose Name	Purpose Code	Purpose Name	Mapper Base for Purpose Code in Profitability and Balance Sheet Planning
Product Code	Application Service Product Name	Instrument Type Code	Instrument Type Name	Mapper Base for Instrument Type Code in Profitability and Balance Sheet Planning

Table 7-5 Example of Type 2 LoV Mapping:

DFCS – Behavior Sub Type	DFCS – Behavior Sub Type	PBSMCS – Behavior Type Code	PBSMCS- Behavior Type Code
D1	Doubtful 1	NP	Non-Performing
D2	Doubtful 2	NP	Non-Performing
D3	Doubtful 3	NP	Non-Performing
DBTFL	Doubtful	NP	Non-Performing
DR	Devolvement and Recovery	DR	Devolvement and Recovery
LOSS	Loss	NP	Non-Performing
NM	Non-Maturity	NM	Non-Maturity
S	Standard	NP	Non-Performing
SPECMEN	Special Mention	NP	Non-Performing
SUBSTRD	Substandard	NP	Non-Performing

In the above example the LOV mapping will be executed via a mapper.

The user provides mapping for 4 dimension-related business terms. The user runs SCD as part Dim population Pipeline to ensure history is captured.

The below example is for Account Status Code (PBSMCS) to Account Status Code (DFCS) mapping which the user must upload.