Status
Owner	BAJAJ-ext, Manoj
Stakeholders	PILLAY-ext, Lawrence

Purpose

The purpose of this document is to define the conversion approach to create conversion for Object 1183 - Limits Master Data for Treasury related transactions
in S/4 HANA.

The limits act as an amount against which checks are made to determine whether the limit has been exceeded. Each limit has a validity period. A Limit is maintained for a limit type which may include combinations of Company Code, Product Group, Business Partner, Currency, Trader or Country.

The document details out the field list, extraction criteria, scoping, mapping, transformation logic, generation of the pre-load file and loading of the same with respect to the object 1183- Limits Master, to be used in treasury module of S4HANA.

Key tables and fields:

There are two tables involved in S4 with respect to the maintenance of the Limit Masters Data and these are:

VTBLS - Limits - This is used for Mapping Logical - Physical Keys of Limit to a Business Partner, Company Code, Product Group
VTBLV - Limits - This is used for maintaining the limit amounts in relevant currency

Table: VTBLS is the central table for defining Limit Structures in SAP S/4HANA Treasury and Risk Management (TRM). It maps logical limit definitions to physical keys and characteristics. The key fields of VTBLS are:

SLA – Defines the type of limit (e.g., counterparty, product group).
RLV – Limit Record Number: Unique identifier for each limit record. This is also the field which links table VTBLS to table VTBLV
BUKRS – Company Code: Organizational unit for financial accounting.
PARTNR – Business Partner: The entity to which the limit applies.
SLPG – Limit Product Group: Groups products under a common limit, example - Banks, Bonds, Derivatives, Foreign Exchange etc.
RPORTB – Portfolio: A portfolio is an organizational element to group together various treasury transactions for reporting purposes.
RDEALER – Trader: Trader ID of the in-house trader responsible for the transaction.
WAERS – Currency: Currency in which the limit is defined.
COUNTRY – Country:

Table: VTBLV is the table in SAP S/4HANA TRM that stores the actual limit values tied to each limit structure defined in VTBLS. It includes validity periods, amounts, currencies, and control parameters.

The key fields of VTBLV are:

SLA – Limit Type: Matches the type defined in VTBLS.
RLV – Limit Record Number: Unique identifier for each limit record. Links to the corresponding record in VTBLS.
DLVB – Valid From: Date from which the limit is effective.
DLVE - Valid To: Date on which validity of a limit ends.
BLIMIT– Internal Limit Amount: Internal threshold for exposure
ELIMIT – External Limit Amount: External threshold for exposure
WLIMIT – Currency: Currency in which the limit is maintained
PROZLIMIT – Critical Limit Utilization- The threshold limit maintained as % for trigger of warnings
COMPERD – Max. Risk Commit Per.Mth: The maximum risk commitment period specifies the maximum risk commitment period in which a transaction is attributed to the limit.
INFINITE – Do not check limit:If this indicator is set to "do not check", the limit is not checked against existing utilizations. A key consequence is that the system does not display amounts exceeding the limit in reports or in the results for the single transaction
EDLVE – Ext.Valid-To Date: External Validity End Date of Limit

The treasury function in legacy is carried out in the Quantum system and therefore for the conversion of this object, the data/details need to be sourced from Quantum and transformed as applicable for S4HANA in Syniti and load using LTMC for Limits in S4HANA

Conversion Scope

The scope of this document covers the approach for converting active Treasury - Limits Master from Legacy Source Systems (Quantum) into S/4HANA following the Master Data Design Standard - DD-FUN-050 Master Data Standard_1183 - Limits Master Data

The data from legacy system includes:

Active records for Limits which are still in use/valid and have validity date is > cutover date
Limit records pertain to active counterparties which will also be created as business partners with Treasury roles such as Counterparty, Issuer or Depository Bank in S4HANA

The data from legacy system excludes:

All limits records which have a validity date in the past and are not in use in any exposure

List of source systems and approximate number of records <number of company codes to be confirmed>

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
Quantum	Active and in use Limit Records	300	S4HANA	300

Additional Information

Multi-language Requirement

None

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

As the conversion involves a source system which is non-SAP, the below area needs special handling:

Extraction of Limits record from source system i.e. Quantum is to be done manually.
Cleansing by business team to mark the limit records as blocked or completed, where applicable
The extracted records to be converted into a DCT and stored in the Syniti for Transformation
Below Value mapping tables to be created in Syniti:
1. Counterparty to Business Partner
2. Source and target company code
Amount and date format from source system to align with S4HANA
As the target structure in S4HANA involves two tables- VTBLS and VTBLV, therefore the load will be a two-step process

Target Design

The Target design of the object 1183 - Limits Master Data based on the MDS - DD-FUN-050 Master Data Standard_1183 - Limits Master Data is as below

The technical design of the target for this conversion approach.

Table - VTBLV: Limits - Mapping/Logical Fields

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
VTBLS	SLA	TB_SLA	Limit Type	CHAR	3	Mandatory
VTBLS	RLV	TB_RLV	Limit Record	NUMC	20	System Generated
VTBLS	BUKRS	BUKRS	Company Code	CHAR	4	Mandatory
VTBLS	PARTNR	BP_PARTNR_NEW	Business Partner	CHAR	10	Conditional
VTBLS	SLPG	TB_SLPG	Limit Product Group	CHAR	3	Conditional
VTBLS	RPORTB	RPORTB	Portfolio	CHAR	10	Conditional
VTBLS	RDEALER	RDEALER	Trader	CHAR	12	Conditional
VTBLS	WAERS	TB_WCHAR	Currency	CUKY	5	Conditional
VTBLS	COUNTRY	LAND1_GP	COUNTRY	CHAR	3	Conditional

Note: The fields marked as conditional are based on the field VTBLS=SLA (Limit Type) and accordingly can be either required or optional

Table - VTBLS: Limits

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
VTBLV	SLA	TB_SLA	Limit Type	CHAR	3	Mandatory
VTBLV	RLV	TB_RLV	Limit Record	NUMC	20	Mandatory
VTBLV	DLVB	TB_DLVB	Valid From	DATS	8	Mandatory
VTBLV	DLVE	TB_DLVE	Valid to	DATS	8	Mandatory
VTBLV	BLIMIT	TB_BLIMIT	Internal Limit Amount	CURR	17 2 decimals	Mandatory
VTBLV	ELIMIT	TB_ELIMIT	External Limit Amount	CURR	17 2 decimals	Mandatory
VTBLV	PROZLIMIT	TB_PROZLIMIT	Critical Limit Utilization	DEC	5 2 decimals	Mandatory
VTBLV	COMPERD	TB_COMPERD	Max. Risk Commit Per.Mth	NUMC	4	Mandatory
VTBLV	INFINITE	TB_LIMIT_INFINITE	Do not check limit	CHAR	1	Conditional
VTBLV	EDLVE	TB_EDLVE	Ext.Valid-To Date	DATS	8	Mandatory

Note: The fields marked as conditional are based on the field VTBLS=SLA (Limit Type) and accordingly can be either required or optional. The fields SLV and RLV are the link to table VTBLS.

Data Cleansing

For the purpose of the Object 1183- Limit Master Data, the data cleansing should happen in the source systems i.e. Quantum as per below cleansing activity. The business cleansing is expected to be done by the business.

Identify all in active records for Limits which are not valid and have validity date in the past
Identify all records which may still be having a validity date in the future but are against the counterparties which are nor relevant for migration

Exclude such records from the extraction from the Quantum and populate in the DCT

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	High	Validity date of the Limit	Check the valid to date is not lower than the cutover date	Show records in error	DCT
2	Medium	Business Partner not found	Check the Business Partner of source counterparty to the target BP (value mapping)	Show records in error	DCT

Conversion Process

The generic high-level process steps for the conversion are as below:

Extraction:

Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
DCT: The DCT to be prepared if the data to be transformed and is part of the load file is not available in the Source system

Transform

Transform fields by applying the fields and value mapping in the Syniti
Generate and validate Pre-load files

Load

Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable.

However, with respect to object 1183- Limit Master Data - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business based on the source data from Quantum system. This DCT will be used for transformation and generation of the pre-load file.

The load will be done via LTMS using the "Limit Product" template

Data Privacy and Sensitivity

None

Extraction

Extract data from a source into Syniti. There are 2 possibilities:

The data exists. Syniti connects to the source and loads the data into Syniti. There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if Syniti; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti. This is to be conducted using DCT (Data Collection Template) in Syniti.

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
01	Extract from table Quantum all valid and in use Limit Records and place them into a DCT format	Business

Selection Screen

Not applicable:

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for1183- Limit Master Data with exception of some fields which require transformation as mentioned in the transformation rule.

1183 - Limit Mater Data DCT Rules

Field Name	Field Description	Rule
VTBLS-SLA	Limit Type	The limit type from allowed values as per configuration
VTBLS-RLV	Limit Record	Existing Limit number. in S4 the limit number will be auto generated by the system
VTBLS-BUKRS	Company Code	The company code/entity of the source. The value mapping of the source and target Company codes to be maintained separately
VTBLS-PARTNR	Business Partner	The counterparty number/code of the source. The value mapping of the source and target partners to be maintained separately
VTBLS-SLPG	Limit Product Group	Limit Product Group as per below configuration values: BA - Banks BND - Bond DE - Derivatives FX - Foreign Exchange MM - Money market MMF - Mutual Money Market Fund SH - Shareholding ST - Stock TF - Trade Finance
VTBLS-RPORTB	Portfolio	Portfolio as per the configuration list
VTBLS-RDEALER	Trader	Trader as per available value
VTBLS-WAERS	Currency	Currency key - 3 char ISO code
VTBLS-COUNTRY	Country	Country key - 2 char ISO Code
VTBLV-DLVB	Valid From	The valid from Date - Original date as per source
VTBLV-DLVE	Valid To	The valid to Date - Original date as per source
VTBLV-BLIMIT	Internal Limit Amount	Amount
VTBLV-ELIMIT	External Limit Amount	Amount
VTBLV-WLIMIT	Limit Currency	Amount
VTBLV-PROZLIMIT	Critical Limit Utilization	Percentage utilized as per source. If this is not available, then business to provide
VTBLV-COMPERD	Max. Risk Commit Per.Mth	The maximum risk commitment period specifies the maximum risk commitment period in which a transaction is attributed to the limit.
VTBLV-INFINITE	Do not check limit	If this indicator is set to "do not check", the limit is not checked against existing utilizations. A key consequence is that the system does not display amounts exceeding the limit in reports or in the results for the single transaction check. keep blank
VTBLV-EDLVE	Ext.Valid-To Date	Date

Extraction Dependencies

Item #	Step Description	Team Responsible
01	Any period / year end close activities have been fully completed	Business
02	Active limit records have been identified, and business cleansing has happened in Quantum	Business

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in Syniti
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings as maintained in the Syniti	Data team
4	Ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Execute transformation for the object	Syniti team
6	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Syniti/Data team
7.	Generate Pre-Load reports.	Syniti team
8.	Generate data load count.	Syniti team
9.	Log errors as defects, if any and address resolutions. Close defects.	Syniti/Data team
10.	Re-transform and re-validate the Pre-load reports if necessary.	Syniti/Data team
11.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
12.	Analyse and resolve any pre-load defects logged by business.	Syniti/Data team
13.	Repeat steps 5 to 11 if necessary	Syniti/Data team
14.	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
01	NA	NA	NA	DCT	S4HANA	VTBLS	SLA	Limit Type	As per DCT
02	NA	NA	NA	DCT	S4HANA	VTBLS	RLV	Limit Record	System generated
03	NA	NA	NA	DCT	S4HANA	VTBLS	BUKRS	Company Code	From value mapping
04	NA	NA	NA	DCT	S4HANA	VTBLS	PARTNR	Business Partner	From value mapping
05	NA	NA	NA	DCT	S4HANA	VTBLS	SLPG	Limit Product Group	As per DCT
06	NA	NA	NA	DCT	S4HANA	VTBLS	RPORTB	Portfolio	As per DCT
07	NA	NA	NA	DCT	S4HANA	VTBLS	RDEALER	Trader	As per DCT
08	NA	NA	NA	DCT	S4HANA	VTBLS	WAERS	Currency	As per DCT
09	NA	NA	NA	DCT	S4HANA	VTBLS	COUNTRY	Country	As per DCT
10	NA	NA	NA	DCT	S4HANA	VTBLV	DLVB	Valid From	As per DCT
11	NA	NA	NA	DCT	S4HANA	VTBLV	DLVE	Valid to	As per DCT
12	NA	NA	NA	DCT	S4HANA	VTBLV	BLIMIT	Internal Limit Amount	As per DCT
13	NA	NA	NA	DCT	S4HANA	VTBLV	ELIMIT	External Limit Amount	As per DCT
14	NA	NA	NA	DCT	S4HANA	VTBLV	PROZLIMIT	Critical Limit Utilization	As per DCT
15	NA	NA	NA	DCT	S4HANA	VTBLV	COMPERD	Max. Risk Commit Per.Mth	As per DCT
16	NA	NA	NA	DCT	S4HANA	VTBLV	INFINITE	Do not check limit	leave blank
17	NA	NA	NA	DCT	S4HANA	VTBLV	EDLVE	Ext.Valid-To Date	As per DCT

Transformation Mapping

Below value mapping tables should be constructed in Syniti

Mapping Table Name	Mapping Table Description
Company Code	Mapping Table for Quantum company/entity code to S4HANA entity code
Business Partner	Mapping Table for Quantum counterparty/partner code to S4HANA Business Partner

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure all the fields that require value mapping, as stipulated Mapping tables, have the latest signed-off mapping files imported into Syniti	Data team
2	Ensure that signed off value mappings have been maintained in the Syniti	Syniti team
3	Confirm the value mappings as maintained in the Syniti	Data team
4	Ensure that Signed off DCT from business has been received and maintained in Syniti	Syniti/Data team
5	Confirm on the extracted values	Syniti, Data and business

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
Data Object is in scope based on data design and any exception requested by business.

Any additional key assumptions.

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Special Requirements

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log