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:

1. Active records for Limits which are still in use/valid and have validity date is > cutover date
2. 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:

1. 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:

1. Extraction of Limits record from source system i.e. Quantum is to be done manually.
2. Cleansing by business team to mark the limit records as blocked or completed, where applicable
3. The extracted records to be converted into a DCT and stored in the Syniti for Transformation
4. Below Value mapping tables to be created in Syniti:
   1. Counterparty to Business Partner 
   2. Risk Object types to Limit Product Groups 
5. Amount and date format from source system to align with S4HANA 
6. 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.

1. Identify all in active records for Limits which are not valid and have validity date in the past
2. 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
3	Medium	Product Group not found	Check the risk product group of source data to the target Limit product group (value mapping)	Show records in error	DCT

Conversion Process

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

1. Extraction:
1. Extract from the source systems: Apply the selection parameters and data relevancy as mentioned in this specification, from the relevant tables
2. 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
2. Transform 
1. Transform fields by applying the fields and value mapping in the Syniti 
2. Generate and validate Pre-load files
3. Load
1. Load the validated Pre-load file using SAP's LTMC or the custom upload program as applicable. 

However, with respect to object 2012- Material Master - Accounting View 1, the conversion process will depend upon the overall cutover/migration strategy <To be finalised by Functional team>, in view of the mandatory Material Ledger activation in S4HANA. The common practice/approach and steps followed are as below:

Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any

Extraction

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

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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 Migrate to make the data Target ready:

1. 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 Migrate
2. 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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

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:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log