Status

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	80100

Owner

VIDWANS-ext, Sauradh

Stakeholders

PILLAY-ext, Lawrence

Purpose

The purpose of this document is to define the conversion approach to create Facilities Transactions in S/4 HANA.

Facilities are borrowing arrangements with either one or multiple banks. If we have a long term borrowing facility with one bank its called as Bi-Lateral Facility. Under this facility you, can define the fund requirements and the Bank will ear mark these funds to be drawn at a certain interval. If this facility is with multiple banks its called as Syndicate Facility. In a Syndicate there is normally a Lead Banker who will arrange the lending commitment from other lenders and will also have a Lead Banker charges.

These instruments are created under a certain Product Type (Instrument Number) and a Transaction Type (Kind of action i.e. buying or selling) against a counterparty (BP Number) in a Company Code.

Conversion Scope

The scope of this document covers the approach for converting active Facilities from Legacy Source System (Quantum) into S/4HANA.

The relevancy criteria is not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template).

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
Quantum	Live Commercial Paper Facilities Contracts	100 <TBC>	S4HANA	100 <TBC>

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

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

Extraction of CP data Facilities data from source system i.e. Quantum is to be done manually
Cleansing by business team in the source system (Quantum) to ensure that only active and in use records for CP’s Facilities are provided in DCT
The extracted records to be converted into a DCT and stored in the Syniti for Transformation
Below Configuration Check Tables needs to be referenced in Syniti to validate the data in the DCT:

Counterparty to Business Partner - BUT100
Company Code - T001
Product Type - TZPA
Transaction Type - AT10
Trader - TZDEA
Portfolio Code - TWPOB
General Valuation Class - TRGC_COM_VALCL
Interest Calculation Method - Custom Check Table with Value Fields given in the below CNV

Amount and date format from source system to align with S4HANA
As the target structure in S4HANA involves dependency on various Configuration and BP Master Data objects (CNV 3040), all this data needs to be loaded before Transactions Data loads.

Custom Check Tables for Interest Calculation Method, Frequency and Update Rule are as under:

Interest Calculation Method:

Interest Calculation Method	Text
1	360E/360
B	360E/365
L	360/360 (German)
F	360/360 (ISDA)
H	360/365 (ISDA)
7	360/360
2	act/360
E	act/364
3	act/365
R	act/365.25
4	act/366
M	act/365P
5	act/actP (ICMA)
6	act/actY (ISDA)
G	act/actE (AFB)
Q	act/actEP (AFB)
N	act/365L
S	act/365Y
A	actW/252
D	365/360
C	365/365
I	360E/actY
8	30.42E/360
9	*365.25/360
P	01-01-2026
J	m+act/360
K	m+30/360
0	Not Specified
T	act/act[M]
U	actW/actW[M]

Update Rule:

Rule Number	Text
0	Pro Rata Temporis
1	Include Fully
2	Do Not Include

Frequency:

1	At End of Term
5	On First Day of Month
2	On Last Day of Month
3	Monthly
4	Daily
0	Manual Input

BP Number

BP Number	BP Name
0000000001	TEST

Target Design

For a Transaction Load DCT, since there are no standard LTMC objects that we can use for loading this data, we will be using BAPI’s for this purpose. In a BAPI there are multiple fields, off which all are not necessary to be utilized as part of DCT.

In this section, we will see the full list of fields that are part of the DCT. This section will also explain field by field mapping of the DCT structure and where the data will come from for each field.

The technical design of the target for this conversion approach.

Table Name	Field	Field Description	Data Type	Length	Requirement
Utility Field (VTBFHA)

BUKRSCOMPANY_CODE

ZSTDTINCL

Calculation Period: Start Inclusive vs. End Inclusive

CHAR

4

1	This is a Required Field
Utility Field (VTBFHA)

SGSARTPRODUCT_TYPECHAR3This is a Required FieldVTBFHASFHAARTTRANSACTION_TYPECHAR3This is a Required FieldVTBFHAKONTRHPARTNERCHAR10This is a Required FieldVTBFHADBLFZCONTRACT_DATEDATS8This is a Required FieldVTBFHAZURDEALERTRADERCHAR12This is Optional Field

ZCALCMETH	Calculation method for first period of condition item	NUMC	1	This is Optional Field
Utility Field (VTBFHA)	ZCALCEND	Calculation method for last period of condition item	NUMC	1	This is Optional Field
Utility Field (VTBFHA)	ZINTCALCMET	Interest Calculation Method	CHAR	1	This is Optional Field
Utility Field (VTBFHA)	ZUPDATERULE	Update for Calculation/Due Date for Interest	NUMC	2	This is Optional Field
Utility Field (VTBFHA)	ZINCLIND	Inclusive Indicator for Calculation Date	CHAR	1	This is Optional Field
Utility Field (VTBFHA)	ZMENDINDI	Month-End Indicator for Calculation Date	CHAR	1

VTBFHARPORTBPORTFOLIOCHAR10

	This is Optional Field
Utility Field (VTBFHA)

ZUONDASSIGNMENT

ZMENDINDIR

Month-End Indicator for Due Date

CHAR

18

1	This is Optional Field

VTBFHAZUNORDEXTEXTERNAL_REFERENCE

Utility Field
(VTBFHA)

ZDUEDATEINDI

Shift Due Date Back to End of Term

CHAR

16

1	This is Optional Field
VTBFHA

REFER

BUKRS

INTERNAL

COMPANY_

REFERENCE

CODE

CHAR

16

4

This is

Optional

a Required Field

VTBFHA

MERKM

RFHA

CHARACTERISTICS

TRANSACTION NUMBER

CHAR

25

13

This is

a Required

Internal Field

VTBFHA

TPM_COM_VAL_CLASSVALUATION_CLASSNUMC

SGSART

PRODUCT_TYPE

CHAR

3

4

	This is a Required Field
VTBFHA

DBLFZTerm StartDATS8

SFHAART	TRANSACTION_TYPE	CHAR	3	This is a Required Field
VTBFHA

DELFZ

KONTRH

Term End

PARTNER

DATS

CHAR

8

10	This is a Required Field

NA

VTBFHA

NA

RPORTB

PORTFOLIO

Calculation Period: Start Inclusive vs. End Inclusive

CHAR

1

10

This is

a Required

Optional Field

VTBFHA

WGSCHFT

ZUOND

Transaction Currency

ASSIGNMENT

CUKY

CHAR

5

18

This is

a Required

Optional Field

VTB_ASGN_LIMITLIMIT_DATEFTR Assignment Management: Limit DateDATS8This is a Required FieldVTB_ASGN_LIMITLIMIT_CHG_AMOUNTFTR Assignment Management: Drawing AmountCURR17

VTBFHA	REFER	INTERNAL_REFERENCE	CHAR	16	This is Optional Field
VTBFHA	MERKM	CHARACTERISTICS	CHAR	25	This is a Required Field
VTBFHA	RCOMVALCL	VALUATION_CLASS	NUMC	4	This is a Required Field

VTB_ASGN_LIMITLIMIT_CURRENCYFTR Assignment Management: Limit CurrencyCUKY

VTBFHA

DBLFZ

Term Start

DATS

8

5

This is a Required Field

VTB_ASGN_LIMITLIMIT_POS_AMOUNTFTR Assignment Management: Drawing Amount (BAPI)DEC

VTBFHA

DELFZ

Term End

DATS

8

23

This is a Required Field

VTBFINKO

VTBFHA

SRHYTHM

WGSCHFT

Frequency

Transaction Currency

NUMC

CUKY

3

5

This is

Optional

a Required Field

VTBFINKOAMMRHY OR ATTRHY
(Pick any field that has a value. If the Frequency Indicator is set to Months, then AMMRHY will have a value. If Frequency Indicator is set to Days then ATTRHY will have a value.Unit for FrequencyNUMC1This is Optional FieldVTBFHAPOPKONDPercentage rate for condition itemsDEC10This is Optional FieldNANACalculation method for first period of condition itemNUMC1This is Optional FieldNANACalculation method for last period of condition itemNUMC1This is Optional FieldNANAInterest Calculation MethodCHAR1This is Optional FieldVTBFHAPOSKALIDWTInterest CalendarCHAR2This is Optional FieldNANAUpdate for Calculation/Due Date for InterestNUMC2This is Optional FieldVTBFHAPODVALUTCalculation DateDATS8This is Optional FieldNANAInclusive Indicator for Calculation DateCHAR1This is Optional FieldNANAMonth-End Indicator for Calculation DateCHAR1This is Optional FieldVTBFINKOSVWERKWorking Day Shift for Calculation DayNUMC1This is Optional Field

Utility Field (VTB_ASGN_LIMIT)	ZBUKRS	COMPANY_CODE	CHAR	4	This is a Required Field
Utility Field (VTB_ASGN_LIMIT)	ZRFHA	TRANSACTION NUMBER	CHAR	13	This is Internal Field
VTB_ASGN_LIMIT	RELAT_OBJ	FTR Assignment Management: Assignment Object	CHAR	22	This is Internal Field
VTB_ASGN_LIMIT	RELAT_OBJ_CAT	FTR Assignment Management: Category of Assignment Object	CHAR	3	This is Internal Field
VTB_ASGN_LIMIT	LIMIT_DATE	FTR Assignment Management: Limit Date	DATS	8	This is a Required Field
VTB_ASGN_LIMIT	LIMIT_CHG_AMOUNT	FTR Assignment Management: Drawing Amount	CURR	17,2	This is a Required Field
VTB_ASGN_LIMIT	LIMIT_CURRENCY	FTR Assignment Management: Limit Currency	CUKY	5	This is a Required Field
VTB_ASGN_LIMIT	LIMIT_POS_AMOUNT	FTR Assignment Management: Drawing Amount (BAPI)	DEC	23	This is a Required Field
VTBFHAPO	BUKRS	COMPANY_CODE	CHAR	4	This is a Required Field
VTBFHAPO	RFHA	TRANSACTION NUMBER	CHAR	13	This is Internal Field
VTBFHAPO	RFHAZU	Transaction Activity	NUMC	5	This is Internal Field
VTBFHAPO	DCRDAT	ENTERED ON

VTBFINKODFAELLDue date

DATS

8

This is

Optional

Internal Field

NANAMonth-End Indicator for Due DateCHAR1This is Optional Field

VTBFHAPO	TCRTIM	ENTRY TIME	TIMS	6	This is Internal Field
VTBFHAPO	RFHAZB	TRANSACTION FLOW	NUMC	4	This is Internal Field
VTBFHAPO	PKOND	Percentage rate for condition items	DEC	10, 7

VTBFINKOSFWERKWorking Day Shift for Due DateNUMC1

This is Optional Field

NA

VTBFHAPO

NA

SKALIDWT

Interest Calendar

Shift Due Date Back to End of Term

CHAR

1

2	This is Optional Field

There are 5 main tables in consideration here.

VTBFHA
VTBFHAPO
VTBFINKO
VTB_ASGN_LIMIT
VTBFHAZU

The reference between the tables is a combination of Company Code and Transaction Number. This is the Primary Key to join these tables.

In Addition to this, the field "Characteristics" will have the Legacy Quantum Deal Number. This will form a linkage between Deals loaded in the system vs Quantum deals.

In the above table we saw fields in the DCT. Now we will check the fields in the BAPI and the data logic how it will correspond to the DCT.

Data Cleansing

For the Object 9113 – Treasury Facilities no specific data cleansing is applicable due to below reasons/assumptions:

The Source System is Quantum and therefore it will be a manual extract of relevant data in a DCT form

Data- Pre Load Validation Report

However, for the purpose of the object 9113 – Treasury Facilities, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file.

ID	Criticality	Error Message/Report Description	Rule	Output
1	High	Company Code is valid	Check if BUKRS is valid as per Company Codes created in the system in Table T001	Invalid Company Code
1	High	PRODUCT_TYPE	Check if VVSART is valid as per Product Types created in the system in Table TZPA. Value for Facility Product Type is “CPF” or "BLT". If this is not, then the validation should fail.	Invalid Product Type
1	High	TRANSACTION_TYPE	Check if SFHAART is valid as per Transaction Types created in the system in Table AT10	Invalid Transaction Type
1	High	PARTNER	Check if KUNNR is valid as per Business Partners created in the system under CNV 3040 Business Partner Counterparty	Invalid Partner
1	High	CONTRACT_DATE	Check if DVTRAB is valid in YYYYMMDD Format and is < or = Load Date	Contract Date greater than Load Date
1	High	VALUATION_CLASS	Check if TPM_COM_VAL_CLASS is valid as per Company Codes created in the system in Table TRGC_COM_VALCL	Invalid Valuation Class
1	High	TERM START	Check if DBLFZ is valid in YYYYMMDD Format and is < or = Contract Date	Term Start greater than or equal to Contract Date
1	High	TERM END	Check if DELFZ is valid in YYYYMMDD Format and is < Start Date	Term End greater than Term Start

Apart from the above, a custom report is required to be created for this. The report needs to have row reference for each Interest Rate Instrument loaded under this CNY and display the standard BAPI return messages successful as well as failed. This will make sure all the deposits successfully pass all checks. An additional check is needed if

All dates loaded are correctly transformed into the deals created
Payment Details are not going blank and if yes, the BAPI will return a warning for the same. If this warning appears, it will signify the BP Master Maintenance has been missed. Such records must fail and the maintenance needs to be done at the BP Master.


VTBFHAPO	DVALUT	Calculation Date	DATS	8	This is Optional Field
VTBFHAZU	BUKRS	COMPANY_CODE	CHAR	4	This is a Required Field
VTBFHAZU	RFHA	TRANSACTION NUMBER	CHAR	13	This is Internal Field
VTBFHAZU	RFHAZU	TRANSACTION ACTIVITY	NUMC	5	This is Internal Field
VTBFHAZU	NORDEXT	EXTERNAL_REFERENCE	CHAR	16	This is Optional Field
VTBFHAZU	DVTRAB	CONTRACT_DATE	DATS	8	This is a Required Field
VTBFINKO	BUKRS	COMPANY_CODE	CHAR	4	This is a Required Field
VTBFINKO	RFHA	TRANSACTION NUMBER	CHAR	13	This is Internal Field
VTBFINKO	RGATT	CLASS	CHAR	13	This is Internal Field
VTBFINKO	RFHAZU	Transaction Activity	NUMC	5	This is Internal Field
VTBFINKO	RKONDGR	DIRECTION OF TRANSACTION	NUMC	1	This is Internal Field
VTBFINKO	RKOND	CONDITION	NUMC	4	This is Internal Field
VTBFINKO	DGUEL_KP	CONDITION ITEM EFFECTIVE FROM	DATS	8	This is Internal Field
VTBFINKO	NSTUFE	LEVEL NUMBER OF CONDITION ITEMS FOR RECURRING PAYMENT	NUMC	2	This is Internal Field
VTBFINKO	SRHYTHM	Frequency	NUMC	3	This is Optional Field
VTBFINKO	AMMRHY	Defined Frequency in Months	NUMC	3	This is a Optional Field
VTBFINKO	ATTRHY	Defined Frequency in Days	NUMC	3	This is a Optional Field
VTBFINKO	SVWERK	Working Day Shift for Calculation Day	NUMC	1	This is Optional Field
VTBFINKO	DFAELL	Due date	DATS	8	This is Optional Field
VTBFINKO	SFWERK	Working Day Shift for Due Date	NUMC	1	This is Optional Field

There are 5 main tables in consideration here.

VTBFHA
VTBFHAPO
VTBFINKO
VTB_ASGN_LIMIT
VTBFHAZU

The reference between the tables is a combination of Company Code and Transaction Number. This is the Primary Key to join these tables.

In Addition to this, the field "Characteristics" will have the Legacy Quantum Deal Number. This will form a linkage between Deals loaded in the system vs Quantum deals.

In the above table we saw fields in the DCT. Now we will check the fields in the BAPI and the data logic how it will correspond to the DCT.

Data Cleansing

For the Object 9113 – Treasury Facilities no specific data cleansing is applicable due to below reasons/assumptions:

The Source System is Quantum and therefore it will be a manual extract of relevant data in a DCT form

Data- Pre Load Validation Report

However, for the purpose of the object 9113 – Treasury Facilities, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file.

ID	Criticality	Error Message/Report Description	Rule	Output
1	High	Company Code is valid	Check if BUKRS is valid as per Company Codes created in the system in Table T001	Invalid Company Code
1	High	PRODUCT_TYPE	Check if VVSART is valid as per Product Types created in the system in Table TZPA. Value for Facility Product Type is “CPF” or "BLT". If this is not, then the validation should fail.	Invalid Product Type
1	High	TRANSACTION_TYPE	Check if SFHAART is valid as per Transaction Types created in the system in Table AT10	Invalid Transaction Type
1	High	PARTNER	Check if KUNNR is valid as per Business Partners created in the system under CNV 3040 Business Partner Counterparty	Invalid Partner
1	High	CONTRACT_DATE	Check if DVTRAB is valid in YYYYMMDD Format and is < or = Load Date	Contract Date greater than Load Date
1	High	VALUATION_CLASS	Check if TPM_COM_VAL_CLASS is valid as per Company Codes created in the system in Table TRGC_COM_VALCL	Invalid Valuation Class
1	High	TERM START	Check if DBLFZ is valid in YYYYMMDD Format and is < or = Contract Date	Term Start greater than or equal to Contract Date
1	High	TERM END	Check if DELFZ is valid in YYYYMMDD Format and is < Start Date	Term End greater than Term Start
1	High	AMMRHY & ATTRHY	Either of the fields should have a value populated	Interest Payment Duration is Blank

Apart from the above, a custom report is required to be created for this. The report needs to have row reference for each Interest Rate Instrument loaded under this CNY and display the standard BAPI return messages successful as well as failed. This will make sure all the deposits successfully pass all checks. An additional check is needed if

All dates loaded are correctly transformed into the deals created
Payment Details are not going blank and if yes, the BAPI will return a warning for the same. If this warning appears, it will signify the BP Master Maintenance has been missed. Such records must fail and the maintenance needs to be done at the BP Master.

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 9113- Treasury Facilities DCT will be used for transformation and generation of the pre-load file.

Data Privacy and Sensitivity

Not Applicable

Extraction

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

The data exists. connects to the source and loads the data into . There are 3 methods:

Perform full data extraction from relevant tables in the source system(s).
Perform extraction through the application layer.
Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in

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 relevant tables/reports from Quantum all relevant information required to populate the DCT for Interest Rate Instruments for relevant Company Codes.

This extraction is dependent on the extraction, validation and load of Master Data Object CNV 3040 BP Master. It is also dependent on completion of configuration for items like Company Code, Product Type, Transaction Type, Portfolio Codes, General Valuation Class.

Business

Selection Screen

Not applicable as the extraction is manual activity to be performed by business in Quantum system.

Data Collection Template (DCT)

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

9113 - TRM Facilities DCT Rules

Field Name	Field Description	Data Type	Length	Rule
BUKRS	COMPANY_CODE	Same as Target Design		This is a Required field. This data will be captured by business. It is the Company Code under which a Stock is to be created. In DCT, S4HANA number to be populated based upon the list of Company Codes. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Default Value "1010"
SGSART	PRODUCT_TYPE	Same as Target Design

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 9113- Treasury Facilities DCT will be used for transformation and generation of the pre-load file.

Data Privacy and Sensitivity

Not Applicable

Extraction

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

The data exists. connects to the source and loads the data into . There are 3 methods:

Perform full data extraction from relevant tables in the source system(s).
Perform extraction through the application layer.
Only if ; 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 . This is to be conducted using DCT (Data Collection Template) in

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 DescriptionTeam Responsible

01

Extract from relevant tables/reports from Quantum all relevant information required to populate the DCT for Interest Rate Instruments for relevant Company Codes.

This extraction is dependent on the extraction, validation and load of Master Data Object CNV 3040 BP Master. It is also dependent on completion of configuration for items like Company Code, Product Type, Transaction Type, Portfolio Codes, General Valuation Class.

Business

Selection Screen

Not applicable as the extraction is manual activity to be performed by business in Quantum system.

Data Collection Template (DCT)

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

9113 - TRM Facilities DCT Rules

Field NameField DescriptionRuleBUKRSCOMPANY_CODEThis is a Required field.
This data will be captured by business. It is the Company Code under which a Stock is to be created.
In DCT, S4HANA number to be populated based upon the list of Company Codes. This list needs to be provided to the Business Team who will be downloading data from Quantum System.
Default Value "1010"SGSARTPRODUCT_TYPEThis is a Required field.
This data will be captured by business. It is the Product Type under which a Stock is to be created.
In DCT, S4HANA number is defaulted to “EAP”.
Drop Down Value "CPF" and "BLT"SFHAARTTRANSACTION_TYPEThis is a Required field.
This data will be captured by business. It is the Transaction Type under which a Stock is to be created.
In DCT, S4HANA number is defaulted to “100”.
Default Value "OBT"KONTRHPARTNERThis is a Required field.
This data will be captured by business for Counterparties. A validation is needed to check the BP number captured in the DCT is valid one and is present as per CNV 3040 - Business Partner Counterparty.
Transformation Rule is to be applied to get the BP Number from BP Text.DBLFZCONTRACT_DATEThis is a Required field.
Date format is YYYYMMDD. Contract Date will always be LESS Than the Load Date. This check needs to be implemented.
Example: 99991231RDEALERTRADERThis is a Optional field.
This data will be captured by business. It is the Trader who concludes the Stock.
In DCT, S4HANA Trader Code needs to be populated based upon the list of configured Traders. This list needs to be provided to the Business Team who will be downloading data from Quantum System.
Validation check needs to be done with check table TZDEARPORTBPORTFOLIOThis is a Optional field.
This data will be captured by business. It is the Portfolio Code to bucket all Stock under for reporting purposes.In DCT, S4HANA Portfolio Codes needs to be populated based upon the list of Portfolio's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System.
Validation check needs to be done with check table TWPOBZUONDASSIGNMENTThis is a Optional field.
This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. NORDEXTEXTERNAL_REFERENCEThis is a Optional field.
This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. REFERINTERNAL_REFERENCEThis is a Optional field.
This is a freely maintainable field to capture additional data for the deal. No validations needed for this field. MERKMCHARACTERISTICSThis is a Required field.
This field will be populated with the Legacy Quantum Deal NumberTPM_COM_VAL_CLASSVALUATION_CLASS

This is a Required field.

This data will be captured by business. It is the

Valuation Class

Product Type under which a Stock is to be

accounted for

created.

In DCT, S4HANA

GVC

number

needs to be populated based upon the list of GVC's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System.DBLFZ

is defaulted to “EAP”. Drop Down Value "CPF" and "BLT"
SFHAART	TRANSACTION_TYPE	Same as Target Design

Term Start

This is a Required

Field
Date format is YYYYMMDD. Start Term Date will always be LESS Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation.
Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record. DELFZTerm EndThis is a Required Field

field.

This data will be captured by business. It is the Transaction Type under which a Stock is to be created.

In DCT, S4HANA number is defaulted to “100”.

Default Value "OBT"

KONTRH

PARTNER

CHAR

20

This is a Required field.

This data will be captured by business for Counterparties. A validation is needed to check the BP number captured in the DCT is valid one and is present as per CNV 3040 - Business Partner Counterparty.

Drop Down Value needed as a Composite Drop Down box. Please refer to the Table BP Number in the special requirements section.

DVTRAB

CONTRACT_DATE

Same as Target Design

This is a Required field.

Date format is YYYYMMDD.

End Term

Contract Date will always be

Greater

LESS Than the Load Date. This check needs to be implemented.

Example:

If load date is 20260401 and date in DCT is 20250401, then the Validation Check should fail this record. NACalculation Period: Start Inclusive vs. End Inclusive

99991231
RPORTB	PORTFOLIO	Same as Target Design		This is a Optional

Field
This field defines if the Start Date is to be made inclusive in the calculation of InterestWGSCHFTTransaction CurrencyThis is a Required Field

field.

This data will be captured by business. It is the

Currency of the Fixed Deposit.
Currency Codes are ISO standards hence it will be same in all Treasury systems. Still a Validation check is needed in Syniti to check if a valid Currency Code is used in the DCT.
Drop Down value from table "TCURC"LIMIT_DATEFTR Assignment Management: Limit DateThis is a Required field
This field defines from when the Facility Limit is applicable from.LIMIT_CHG_AMOUNTFTR Assignment Management: Drawing AmountThis is a Required field
This field defines what is value of the facility.LIMIT_CURRENCYFTR Assignment Management: Limit CurrencyThis is a Required field
This field defines what is the currency of the facilityLIMIT_POS_AMOUNTFTR Assignment Management: Drawing Amount (BAPI)This is a Required field
This field defines what amount of the facility is available to be drawn.SRHYTHMFrequencyThis is a Optional field
This field defines the Frequency on which Interest is to be paid
There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT.
For Eg. Monthly or Quarterly.
Drop Down Value as per the "Frequency Category" table provided Above.AMMRHY OR ATTRHY
(Pick any field that has a value. If the Frequency Indicator is set to Months, then AMMRHY will have a value. If Frequency Indicator is set to Days then ATTRHY will have a value.Unit for FrequencyThis is a Optional field
This field defines the number of days or months when Interest needs to be paidPKONDPercentage rate for condition itemsThis is a Optional Field
This field defines the Interest Rate if applicable to the deal.NACalculation method for first period of condition itemThis is a Optional field
This field defines what is the calculation method of first period of Interest.
Drop Down Value from the table "Update Rule"NACalculation method for last period of condition itemThis is a Optional field
This field defines what is the calculation method of Last period of Interest.
Drop Down Value from the table "Update Rule"NAInterest Calculation MethodThis is a Optional field
This is the Interest Calculation Method for Day Counting

Portfolio Code to bucket all Stock under for reporting purposes.In DCT, S4HANA Portfolio Codes needs to be populated based upon the list of Portfolio's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System. Validation check needs to be done with check table TWPOB
ZUOND	ASSIGNMENT	Same as Target Design	This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field.
NORDEXT	EXTERNAL_REFERENCE	Same as Target Design	This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field.
REFER	INTERNAL_REFERENCE	Same as Target Design	This is a Optional field. This is a freely maintainable field to capture additional data for the deal. No validations needed for this field.
MERKM	CHARACTERISTICS	Same as Target Design	This is a Required field. This field will be populated with the Legacy Quantum Deal Number
RCOMVALCL	VALUATION_CLASS	Same as Target Design	This is a Required field. This data will be captured by business. It is the Valuation Class under which a Stock is to be accounted for. In DCT, S4HANA GVC number needs to be populated based upon the list of GVC's configured in the system. This list needs to be provided to the Business Team who will be downloading data from Quantum System.
DBLFZ	Term Start	Same as Target Design	This is a Required Field Date format is YYYYMMDD. Start Term Date will always be LESS Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation. Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record.
DELFZ	Term End	Same as Target Design	This is a Required Field Date format is YYYYMMDD. End Term will always be Greater Than the Load Date. This check needs to be implemented. Example: If load date is 20260401 and date in DCT is 20250401, then the Validation Check should fail this record.
ZSTDTINCL	Calculation Period: Start Inclusive vs. End Inclusive	Same as Target Design	This is a Optional Field This field defines if the Start Date is to be made inclusive in the calculation of Interest
WGSCHFT	Transaction Currency	Same as Target Design	This is a Required Field This data will be captured by business. It is the Currency of the Fixed Deposit. Currency Codes are ISO standards hence it will be same in all Treasury systems. Still a Validation check is needed in Syniti to check if a valid Currency Code is used in the DCT. Drop Down value from table "TCURC"
LIMIT_DATE	FTR Assignment Management: Limit Date	Same as Target Design	This is a Required field This field defines from when the Facility Limit is applicable from.
LIMIT_CHG_AMOUNT	FTR Assignment Management: Drawing Amount	Same as Target Design	This is a Required field This field defines what is value of the facility.
LIMIT_CURRENCY	FTR Assignment Management: Limit Currency	Same as Target Design	This is a Required field This field defines what is the currency of the facility
LIMIT_POS_AMOUNT	FTR Assignment Management: Drawing Amount (BAPI)	Same as Target Design	This is a Required field This field defines what amount of the facility is available to be drawn.
SRHYTHM	Frequency	Same as Target Design	This is a Optional field This field defines the Frequency on which Interest is to be paid There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT. For Eg. Monthly or Quarterly. Drop Down Value as per the "Frequency Category" table provided Above.
AMMRHY OR ATTRHY (Pick any field that has a value. If the Frequency Indicator is set to Months, then AMMRHY will have a value. If Frequency Indicator is set to Days then ATTRHY will have a value.	Unit for Frequency	Same as Target Design

of Interest and needs to be provided by business.
There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT.
For Eg. ACT/360 in SAP means 2.
Drop Down Value as per the "Interest Calculation Methods" table provided Above.SKALIDWTInterest CalendarThis is a Optional field
This defines Calendar to be considered to check if the Payment date is a holiday. Calendars are another configuration item and a list needs to be provided to business to populate the DCT.
A Pre Validation check is needed if the calendar is valid in the DCT.
Drop Down Values from table "TFACD - IDENT"NAUpdate for Calculation/Due Date for Interest

This is a Optional field

This field defines the

update rule for Calculation Date and Due Date.
Drop Down Values from table "Update Rules"DVALUT

number of days or months when Interest needs to be paid
PKOND	Percentage rate for condition items	Same as Target Design

Calculation DateNAInclusive Indicator for Calculation Date

This is a Optional Field

This field

Date format is YYYYMMDD. Calculation Date will always be GREATER Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation.
Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record.

defines the Interest Rate if applicable to the deal.
ZCALCMETH	Calculation method for first period of condition item	Same as Target Design

This is a Optional field

This field defines

if calculation period is to be shiftred to Start Inclusive or End Enclusive

what is the calculation method of first period of Interest.

Drop Down Value

is "X

from the table "Update Rule"

NAMonth-End Indicator for Calculation Date

ZCALCEND

Calculation method for last period of condition item

Same as Target Design

This is a Optional field

This field defines

if Calculation Date is to be shifted to nearest Month End

what is the calculation method of Last period of Interest.

Drop Down Value

is "X

from the table "Update Rule"

SVWERK

ZINTCALCMET

Interest Calculation Method

Same as Target Design

Working Day Shift for Calculation Day

This is a Optional field

This

field defines the how the Working Day

is the Interest Calculation Method for Day Counting of Interest and needs to be

calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date.
Default Value "1"

provided by business. There is a domain value range for this field which needs to be given to business which they extract and prepare this DCT. For Eg. ACT/360 in SAP means 2. Drop Down Value as per the "Interest Calculation Methods" table provided Above.
SKALIDWT	Interest Calendar	Same as Target Design

DFAELLDue date

This is a Optional field

This

field

defines

if calculation Date is to be shiftred to Start Inclusive or End Enclusive
Drop Down Value is "X"NAMonth-End Indicator for Due Date

Calendar to be considered to check if the Payment date is a holiday. Calendars are another configuration item and a list needs to be provided to business to populate the DCT. A Pre Validation check is needed if the calendar is valid in the DCT. Drop Down Values from table "TFACD - IDENT"
ZUPDATERULE	Update for Calculation/Due Date for Interest	Same as Target Design		This is a Optional field This field defines

if calculation period is to be shiftred to Start Inclusive or End Enclusive
Drop Down Value is "X"SFWERKWorking Day Shift for Due Date

the update rule for Calculation Date and Due Date. Drop Down Values from table "Update Rules"
DVALUT	Calculation Date	Same as Target Design		This is a Optional field

This field defines the how the Working Day needs to be calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date.
Default Value "1"

Date format is YYYYMMDD. Calculation Date will always be GREATER Than or Equal to Load Date. This check needs to be implemented as part of Preload Validation. Example: If load date is 20260401 and date in DCT is 20260501, then the Validation Check should fail this record.
ZINCLIND	Inclusive Indicator for Calculation Date	Same as Target Design	This is a Optional field This field defines if calculation period is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X"
ZMENDINDI	Month-End Indicator for Calculation Date	Same as Target Design

NAShift Due Date Back to End of Term

This is a Optional field

This field defines if

the due date

Calculation Date is to be shifted to

the end date of the deal.

nearest Month End

Drop Down Value

for this

is "X"

Extraction Dependencies

For object 9113 - TRM Facilities dependencies are applicable as under

SVWERK	Working Day Shift for Calculation Day	Same as Target Design	This is a Optional field This field defines the how the Working Day needs to be calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date. Default Value "1"
DFAELL	Due date	Same as Target Design	This is a Optional field This field defines if calculation Date is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X"
ZMENDINDIR	Month-End Indicator for Due Date	Same as Target Design	This is a Optional field This field defines if calculation period is to be shiftred to Start Inclusive or End Enclusive Drop Down Value is "X"
SFWERK	Working Day Shift for Due Date	Same as Target Design	This is a Optional field This field defines the how the Working Day needs to be calculated, for eg. If the interest payment date is a holiday then it should shift it to the Next working date. Default Value "1"
ZDUEDATEINDI	Shift Due Date Back to End of Term	Same as Target Design	This is a Optional field This field defines if the due date is to be shifted to the end date of the deal. Drop Down Value for this is "X"

Extraction Dependencies

For object 9113 - Facilities there will be no extraction dependencies since the data is captured as part of the DCT from Quantum System.

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

Perform value mapping and data transformation rules.

Legacy values are mapped to the to-be values (this could include a default value)
Values are transformed according to the rules defined in

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 CONSTRUCT 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

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

Item #Step DescriptionTeam Responsible

0001

TRM Business Partner

Data Team/Functional Treasury Team

0002

Treasury Configuration

Functional Treasury Team

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

Perform value mapping and data transformation rules.

Legacy values are mapped to the to-be values (this could include a default value)
Values are transformed according to the rules defined in

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 CONSTRUCT 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

From DCT Field SFHAART

Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	BUKRS	COMPANY_CODE	From DCT Field BUKRS
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	SGSART	PRODUCT_TYPE	From DCT Field SGSART
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	SFHAART	TRANSACTION_TYPE
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	KONTRH	ZSTDTINCL	Calculation Period: Start Inclusive vs. End InclusivePARTNER	From DCT Field KONTRH Step 1 - Concatenate BUT000 - Name_ORG1, Name_ORG2, Name_ORG3 & Name_ORG4. Step 2 - Compare the BP Name in the DCT with the concatenated filed name. Step 3 - Find the BP Number for the match BUT000 - PARTNER Step 4 - Pass the BP Number fetched in BUT000 in table BUT100 to check if Role "TR0151" Step 5 - If the condition matches, then replace the BP Number in the DCT field VTBFHA - KONTRHCalculation Period: Start Inclusive vs. End Inclusive
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	DBLFZ	ZCALCMETH	Calculation method for first period of condition itemCONTRACT_DATE	From DCT Field DBLFZCalculation method for first period of condition item
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAZU	RDEALER	Utility Table (VTBFHA)	ZCALCEND	Calculation method for last period of condition itemTRADER	From DCT Field RDEALERCalculation method for last period of condition item
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	RPORTBZINTCALCMETPORTFOLIO	Interest Calculation Method	From DCT Field RPORTBInterest Calculation Method
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	ZUOND	ZUPDATERULE	Update for Calculation/Due Date for InterestASSIGNMENT	From DCT Field ZUONDUpdate for Calculation/Due Date for Interest
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAZU	NORDEXT	Utility Table (VTBFHA)	ZINCLIND	Inclusive Indicator for Calculation DateEXTERNAL_REFERENCE	From DCT Field NORDEXTInclusive Indicator for Calculation Date
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	REFER	ZMENDINDI	Month-End Indicator for Calculation DateINTERNAL_REFERENCE	From DCT Field REFERMonth-End Indicator for Calculation Date
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA)	MERKM	ZMENDINDIR	Month-End Indicator for Due DateCHARACTERISTICS	From DCT Field MERKMMonth-End Indicator for Due Date
NA	NA	NA	CONSTRUCT	S4HANA	Utility Table (VTBFHA	TPM_COM_VAL_CLASS	)	ZDUEDATEINDI	Shift Due Date Back to End of TermVALUATION_CLASS	From DCT Field TPM_COM_VAL_CLASSShift Due Date Back to End of Term
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	DBLFZ	BUKRS	COMPANY_CODETerm Start	From DCT Field DBLFZBUKRS
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	DELFZRFHA	Term End	From DCT Field DELFZ	TRANSACTION NUMBER	Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA	NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Calculation Period: Start Inclusive vs. End Inclusive	From DCT Field Calculation Period: Start Inclusive vs. End Inclusive
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	WGSCHFT	SGSART	PRODUCT_TYPETransaction Currency	From DCT Field WGSCHFTSGSART
NA	NA	NA	CONSTRUCT	S4HANA	VTB_ASGN_LIMIT	LIMIT_DATE	FTR Assignment Management: Limit Date		VTBFHA	SFHAART	TRANSACTION_TYPE	From DCT Field SFHAARTFrom DCT Field LIMIT_DATE
NA	NA	NA	CONSTRUCT	S4HANA	VTB_ASGN_LIMIT	LIMIT_CHG_AMOUNT	FTR Assignment Management: Drawing Amount	From DCT Field LIMIT_CHG_AMOUNT
NA	NA	NA	CONSTRUCT	S4HANA	VTB_ASGN_LIMIT	LIMIT_CURRENCY	FTR Assignment Management: Limit Currency	From DCT Field LIMIT_CURRENCY
NA	NA	NA	CONSTRUCT	S4HANA	VTB_ASGN_LIMIT	LIMIT_POS_AMOUNT	FTR Assignment Management: Drawing Amount (BAPI)	From DCT Field LIMIT_POS_AMOUNT
NA	NA	NA	CONSTRUCT	S4HANA	VTBFINKO	SRHYTHM	Frequency	From DCT Field SRHYTHM
NA	NA	NA	CONSTRUCT	S4HANA	VTBFINKO	AMMRHY OR ATTRHY	Unit for Frequency	From DCT Field AMMRHY OR ATTRHY
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAPO	PKOND	Percentage rate for condition items	From DCT Field PKOND
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Calculation method for first period of condition item	From DCT Field Calculation method for first period of condition item
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Calculation method for last period of condition item	From DCT Field Calculation method for last period of condition item
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Interest Calculation Method	From DCT Field Interest Calculation Method
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAPO	SKALIDWT	Interest Calendar	From DCT Field SKALIDWT
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Update for Calculation/Due Date for Interest	From DCT Field Update for Calculation/Due Date for Interest
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAPO	DVALUT	Calculation Date	From DCT Field DVALUT
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Inclusive Indicator for Calculation Date	From DCT Field Inclusive Indicator for Calculation Date
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Month-End Indicator for Calculation Date	From DCT Field Month-End Indicator for Calculation Date
NA	NA	NA	CONSTRUCT	S4HANA	VTBFINKO	SVWERK	Working Day Shift for Calculation Day	From DCT Field SVWERK
NA	NA	NA	CONSTRUCT	S4HANA	VTBFINKO	DFAELL	Due date	From DCT Field DFAELL
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Month-End Indicator for Due Date	From DCT Field Month-End Indicator for Due Date
NA	NA	NA	CONSTRUCT	S4HANA	VTBFINKO	SFWERK	Working Day Shift for Due Date	From DCT Field SFWERK
NA	NA	NA	CONSTRUCT	S4HANA	NA	NA	Shift Due Date Back to End of Term	From DCT Field Shift Due Date Back to End of Term

Transformation Mapping

Mapping Table NameMapping Table Description

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 commenceItem #Step DescriptionTeam 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 Pre Load validations are performed by Project Team

Completeness

TaskAction

Generation of
Pre-load reports

Mandatory field check.

Company Code for which deal is created is part of the scope
The business partner is in the Counterparty role
Product Type, Transaction Type, Portfolio Code and General Valuation Class is matching the configuration check tables
The validity end date of the deal in the Pre-load file is not prior to cutover/go-live date
All other fields marked as Mandatory are not kept blank in the DCT File

Record Count

Record Count

Confirm the record counts in preload summary report

Total Records:

Valid Records:
Invalid Records

Business Confirmation

Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist

To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion

Business Representatives to validate the pre-load file

Agree with data team on the next steps for erroneous records

Accuracy

TaskAction

Mandatory field mapping and transformation

Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.

Company Code, Product Type, Transaction Type, Portfolio Code and GVC in the DCT is matching with the Check Tables provided
Custom Table checks for Interest Calculation Method and Frequency are matched

Business Value Checks

All dates, Amount and Interest Rate for the Fixed Deposits are accurately populated in the deal as per DCT.

Records in Errors

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

VTBFHA

KONTRH

PARTNER

From DCT field "KONTRH"

Step 1 - Compare the BP Number in the DCT with BP XREFF - BPEXT field

Step 2 - Find the BP Number for the match BP XREFF - PARTNER Field

Step 3 - Pass the BP Number fetched from BP XREFF in table BUT100 to check if Role "TR0151" is assigned to the BP

Step 4 - If the condition matches, then replace the BP Number in the DCT field VTBFHA - KONTRH

Business

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

Completeness

TaskAction

Check Data load register count

Business Data Owner/s to verify that the total number of relevant records to be converted as per DCT is equal to the total number of records in the Preload file.

Key Fields Check

Business to check some key fields such as validity end date, Start an End Date, Amount, Interest Rate, etc., are correctly populated against the DCT

Accuracy

TaskAction

Conversion accuracy

To check and validate the load files with all the transformation and mapping rules, to be signed off.

Load

For loading Facilities, SAP has provided a standard BAPI which will have all the necessary fields for successful creation of Facilities. The said BAPI has various Sub-Sections which will form a Load Template and a mapping rule between the DCT and BAPI load format.

BAPI Name : BAPI_FTR_FAC_DEALCREATE

BAPIFTRFAC_DEALCREATE42BAPIFTRFAC_DEALCREATEBAPIFTRFAC_CHARGE432345151617181920

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target BAPI	Target BAPI Structure	Target Field	Target Description	Transformation Logic
1	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_CREATE_FAC	START_TERM	Term Start	From DCT Field DBLFZ
2	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_CREATE_FAC	END_TERM	Term End	From DCT Field DELFZ
3	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_CREATE_FAC	START_INCLUSIVE	Calculation Period: Start Inclusive vs. End Inclusive	From DCT Field Calculation Period: Start Inclusive vs. End Inclusive
4	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_CREATE_FAC	CURRENCY	Transaction Currency	From DCT Field WGSCHFT
5	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	TABLEINDEX	Unique Identifier of a Table Row	Ignore or Keep Blank
6	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CONDITION_TYPE	Condition Type (Smallest Subdivision of Condition Records)	Ignore or Keep Blank
7	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	EFFECTIVE_FROM	Condition Item Effective From	Ignore or Keep Blank
8	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	ZERO_CONDITION	Condition is a Zero Condition	Ignore or Keep Blank
9	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	FREQUENCY	Frequency	From DCT Field SRHYTHM
10	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	FREQUENCY_UNIT	Unit for Frequency	From DCT Field AMMRHY OR ATTRHY
11	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	AMOUNT_CALC_RULE	Amount-Based Structure of a Condition	Ignore or Keep Blank
12	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	PERCENTAGE_RATE	Percentage rate for condition items	From DCT Field PKOND
13	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	AMOUNT	Condition Item Currency Amount	Ignore or Keep Blank
14	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CURRENCY	Currency of Condition Item	Ignore or Keep Blank
15	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CURRENCY_ISO	ISO currency code	Ignore or Keep Blank
16	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_1ST_PERIOD	Calculation method for first period of condition item	From DCT Field Calculation method for first period of condition item
17	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_LST_PERIOD	Calculation method for last period of condition item	From DCT Field Calculation method for last period of condition item
18	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_EXPONENTIAL	Type of Compound Interest Calculation	Ignore or Keep Blank
19	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	PAYMENT_RATE	Payment Rate	Ignore or Keep Blank
20	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_METHOD	Interest Calculation Method	From DCT Field Interest Calculation Method
21	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_CALENDAR	Interest Calendar	From DCT Field SKALIDWT
22	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	DATE_UPDATE_RULE	Update for Calculation/Due Date for Interest	From DCT Field Update for Calculation/Due Date for Interest
23	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_DATE	Calculation Date	From DCT Field DVALUT
24	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_DATE_INCLUSIVE	Inclusive Indicator for Calculation Date	From DCT Field Inclusive Indicator for Calculation Date
25	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_DATE_MONTH_END	Month-End Indicator for Calculation Date	From DCT Field Month-End Indicator for Calculation Date
26	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALC_DATE_WKDAY_SHIFT	Working Day Shift for Calculation Day	From DCT Field SVWERK
27	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	DUE_DATE	Due date	From DCT Field DFAELL
28	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	DUE_DATE_MONTH_END	Month-End Indicator for Due Date	From DCT Field Month-End Indicator for Due Date
29	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	DUE_DATE_WKDAY_SHIFT	Working Day Shift for Due Date	From DCT Field SFWERK
30	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	SHIFT_DUE_DATE_TO_END	Shift Due Date Back to End of Term	From DCT Field Shift Due Date Back to End of Term
31
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	SHIFT_DAYS	Shift Days for Relative Date Determination	VTBFHAZU	DVTRAB	CONTRACT_DATE	From DCT Field DVTRAB
Ignore or Keep Blank	32	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALENDAR1	Calendar for working day rules	Ignore or Keep Blank	VTBFHA	RPORTB	PORTFOLIO	From DCT Field RPORTB33
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALENDAR2	Calendar for working day rules	Ignore or Keep Blank	VTBFHA	ZUOND	ASSIGNMENT	From DCT Field ZUOND34
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	CALENDAR3	Calendar for working day rules		VTBFHA	REFER	INTERNAL_REFERENCE	From DCT Field REFER
Ignore or Keep Blank	35	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	ROUND_TYPE	Rounding Category	Ignore or Keep Blank	36	VTBFHA	MERKM	CHARACTERISTICS	From DCT Field MERKM
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHA	RCOMVALCL	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	ROUND_UNIT	Rounding Unit	VALUATION_CLASS	From DCT Field TPM_COM_VAL_CLASS
Ignore or Keep Blank	37	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	ROUNDUNIT_BASE	Currency Amount in BAPI Interfaces	VTBFHA	DBLFZ	Term Start	From DCT Field DBLFZ
Ignore or Keep Blank	38	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	SETTLE_FREQUENCY_EXPONENTIAL	Interest Settlement Frequency for Exponential Interest Calc.	Ignore or Keep Blank	VTBFHA	DELFZ	Term End	From DCT Field DELFZ39
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	FACILITYLINE	Line of Credit	Ignore or Keep Blank		VTBFHA	WGSCHFT	Transaction Currency	From DCT Field WGSCHFT
NA	NA	NA	CONSTRUCT	S4HANA	Utility Field (VTB_ASGN_LIMIT)	BUKRS	COMPANY_CODE	From DCT Field BUKRS40
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CHARGE	AMOUNT_EFFECTIVE_FROM	Condition Item Effective from Amount	Ignore or Keep Blank	Utility Field (VTB_ASGN_LIMIT)	RFHA	TRANSACTION NUMBER	Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA41
NA	NA	NA	CONSTRUCT	S4HANA
VTB_
ASGN_
BAPI_FTR_FAC_CHARGE	CALC_BASE_TYPE	Calculation Base Indicator	Ignore or Keep Blank
LIMIT	RELAT_OBJ	FTR Assignment Management: Assignment Object	Internal Field generated by SAP. Use Internally generated Sequential Number
NA	NA	NA	CONSTRUCT	S4HANA
VTB_
ASGN_
LIMIT
RELAT_
OBJ_
CHARGE_KEY	Key which Identifies a Condition in the BAPI	Ignore or Keep Blank
CAT	FTR Assignment Management: Category of Assignment Object	Internal Field generated by SAP. Use Internally generated Sequential Number
NA	NA	NA	CONSTRUCT	S4HANA	BAPIVTB_FTRASGN_FAC_DEALCREATELIMIT	BAPI_FTR_FAC_CREDLINE	VALID_FROM	LIMIT_DATE	FTR Assignment Management: Limit Date	From DCT Field LIMIT_DATE
44	NA	NA	NA	CONSTRUCT	S4HANA	BAPIVTB_FTR_FACASGN_DEALCREATELIMITBAPI	LIMIT_FTR_FACCHG_CREDLINEAMOUNT	FTR Assignment Management: Drawing Amount	From DCT Field LIMIT_CHG_AMOUNT	45
NA	NA	NA	CONSTRUCT	S4HANA	BAPIVTB_FTRASGN_FAC_DEALCREATE	BAPI_FTR_FAC_CREDLINE	LIMIT	LIMIT_CURRENCY	FTR Assignment Management: Limit Currency	From DCT Field LIMIT_CURRENCY46
NA	NA	NA	CONSTRUCT	S4HANA	BAPIVTB_FTRASGN_FAC_DEALCREATELIMIT	BAPI_FTR_FAC_CREDLINE	CURRENCY_ISO	ISO currency code	Ignore or Keep Blank	47	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BAPI_FTR_FAC_CREDLINE	AMOUNT_NEWLIMIT_POS_AMOUNT	FTR Assignment Management: Drawing Amount (BAPI)	From DCT Field LIMIT_POS_AMOUNT
Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
AMOUNT
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAPO	BUKRS	COMPANY_CODE	From DCT Field BUKRS
NA	NA	NA	CONSTRUCT	S4HANA	VTBFHAPO	RFHA	TRANSACTION NUMBER	Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA1
NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	BUKRS	COMPANY_CODE	From DCT field "BUKRS”
VTBFHAPO	RFHAZU	Transaction Activity	Internal Field generated by SAP. Use Internally generated Sequential Number

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	VVSART	PRODUCT_TYPE	From DCT field "SGSART"
VTBFHAPO	DCRDAT	ENTERED ON	Internal Field generated by SAP. Use System Date while you generate your report

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_SFHAART	TRANSACTION_TYPE	From DCT field "SFHAART"
VTBFHAPO	TCRTIM	ENTRY TIME	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_RFHA	EXTERNAL_TRANSACTION_NUMBER	Keep Blank or Ignore the field
VTBFHAPO	RFHAZB	TRANSACTION FLOW	Internal Field generated by SAP. Use Internally generated Sequential Number

NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_KUNNR_NEW	PARTNER	From DCT field "KONTRH"	VTBFHAPO	PKOND	Percentage rate for condition items	From DCT Field PKOND6
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_DVTRAB	CONTRACT_DATE	From DCT field "DBLFZ"	VTBFHAPO	SKALIDWT	Interest Calendar	From DCT Field SKALIDWT7
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_TVTRAB	CONTRACT_TIME	VTBFHAPO	DVALUT	Calculation Date	From DCT Field DVALUT
System Time at the time of Data Load	8	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_GSPPART	CONTACT_PERSON	Keep Blank or Ignore the field	VTBFHAZU	BUKRS	COMPANY_CODE	From DCT Field BUKRS9
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	RDEALER	TRADER	From DCT field "RDEALER"		VTBFHAZU	RFHA	TRANSACTION NUMBER	Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA10
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	RREFKONT_OBSOLETE	ACCT_ASSIGNMENT_REF	Keep Blank or Ignore the field	VTBFHAZU	RFHAZU	TRANSACTION ACTIVITY	Internal Field generated by SAP. Use Internally generated Sequential Number 11
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	RPORTB	VTBFHAZU	NORDEXT	EXTERNAL_REFERENCEPORTFOLIO	From DCT field "RPORTB"	12	Field NORDEXT
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_TFPROJ	FINANCE_PROJECT	Keep Blank or Ignore the field	VTBFINKO	BUKRS	COMPANY_CODE	From DCT Field BUKRS13
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_RGARANT_NEW	GUARANTOR	Keep Blank or Ignore the field	VTBFINKO	RFHA	TRANSACTION NUMBER	Internal Field generated by SAP. Note Copy field MERKM field in DCT to ZLEGACYRFHA14
NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_RMAID	MASTER_AGREEMENT	Keep Blank or Ignore the field
VTBFINKO	RGATT	CLASS	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_ZUOND	ASSIGNMENT	From DCT field "ZUOND"
VTBFINKO	RFHAZU	Transaction Activity	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_NORDEXT	EXTERNAL_REFERENCE	From DCT field "NORDEXT"
VTBFINKO	RKONDGR	DIRECTION OF TRANSACTION	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_REFER	INTERNAL_REFERENCE	From DCT field "REFER"
VTBFINKO	RKOND	CONDITION	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TB_MERKM	CHARACTERISTICS	From DCT field "MERKM"
VTBFINKO	DGUEL_KP	CONDITION ITEM EFFECTIVE FROM	Internal Field generated by SAP. Use System Date while you generate your report

NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TBEGRU	AUTH_GROUP	Keep Blank or Ignore the field
VTBFINKO	NSTUFE	LEVEL NUMBER OF CONDITION ITEMS FOR RECURRING PAYMENT	Internal Field generated by SAP Use System Time when you generate your report.

NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_CRUSER	CREATE_USER	Keep Blank or Ignore the field	VTBFINKO	SRHYTHM	Frequency	From DCT Field SRHYTHM21
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_DCRDAT	ENTRY_DATE	Date on which the data is getting loaded.	VTBFINKO	AMMRHY OR ATTRHY	Unit for Frequency	From DCT Field AMMRHY OR ATTRHY22
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_FACILITYNR	FACILITY	VTBFINKO	SVWERK	Working Day Shift for Calculation Day	From DCT Field SVWERK
Keep Blank or Ignore the field	23	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_FACILITYBUKRS	FACILITY_COMPANY_CODE	Keep Blank or Ignore the field	VTBFINKO	DFAELL	Due date	From DCT Field DFAELL24
NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_COM_VAL_CLASS	VALUATION_CLASS	From DCT field "TPM_COM_VAL_CLASS”
25	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	FM_FUND	FUND	Keep Blank or Ignore the field
26	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	GM_GRANT_NBR	GRANT_NBR	Keep Blank or Ignore the field
27	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_SPESEN	EXPENSE_KEY	Keep Blank or Ignore the field
28	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TB_SANST	RESERV_REASON	Keep Blank or Ignore the field
29	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_TREA_CLEARING_OPT	CLEARING_OPTION	Keep Blank or Ignore the field
30	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_TREA_CLEARING_STATUS	CLEARING_STATUS	Keep Blank or Ignore the field
31	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_TREA_CLEARING_DATE	CLEARING_DATE	Keep Blank or Ignore the field
32	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_EXT_ACCOUNT	EXT_ACCOUNT	Keep Blank or Ignore the field
33	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPM_TREA_CLEARING_DATE_ACT	CLEAR_DATE_ACT	Keep Blank or Ignore the field
	VTBFINKO	SFWERK	Working Day Shift for Due Date	From DCT Field SFWERK

Transformation Mapping

Mapping Table Name	Mapping Table Description
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 Pre Load validations are performed by Project Team

Completeness

Task

Action

Generation of
Pre-load reports

Mandatory field check.

Company Code for which deal is created is part of the scope
The business partner is in the Counterparty role
Product Type, Transaction Type, Portfolio Code and General Valuation Class is matching the configuration check tables
The validity end date of the deal in the Pre-load file is not prior to cutover/go-live date
All other fields marked as Mandatory are not kept blank in the DCT File

Record Count

Record Count

Confirm the record counts in preload summary report

Total Records:

Valid Records:
Invalid Records

Business Confirmation

Data team after the initial validation of Pre-Load validation based on the pre agreed validation checklist

To send the Pre-Load file to the Business Representatives for all plants/valuation area in scope for conversion

Business Representatives to validate the pre-load file

Agree with data team on the next steps for erroneous records

Accuracy

Task

Action

Mandatory field mapping and transformation

Obtain a list of the fields to be populated with values from mapping files and ensure all these fields contain S/4HANA values.

Company Code, Product Type, Transaction Type, Portfolio Code and GVC in the DCT is matching with the Check Tables provided
Custom Table checks for Interest Calculation Method and Frequency are matched

Business Value Checks

All dates, Amount and Interest Rate for the Fixed Deposits are accurately populated in the deal as per DCT.

Records in Errors

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

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

Completeness

Task	Action
Check Data load register count	Business Data Owner/s to verify that the total number of relevant records to be converted as per DCT is equal to the total number of records in the Preload file.
Key Fields Check	Business to check some key fields such as validity end date, Start an End Date, Amount, Interest Rate, etc., are correctly populated against the DCT

Accuracy

Task	Action
Conversion accuracy	To check and validate the load files with all the transformation and mapping rules, to be signed off.

Load

For loading Facilities, SAP has provided a standard BAPI which will have all the necessary fields for successful creation of Facilities. The said BAPI has various Sub-Sections which will form a Load Template and a mapping rule between the DCT and BAPI load format.

BAPI Name : BAPI_FTR_FAC_DEALCREATE

S4HANAS4HANAKOSTLCOSTCENTERPSPSP_PNRWBSELEMENTS4HANAS4HANATRPAINITIAL_STAGEINITCLASSIFIERS4HANAS4HANA

Target BAPI	Target Field	Target Description	Transformation Logic	34	NA	NA	NA	CONSTRUCT
BAPI_FTR_FAC_DEALCREATE
FTR_THRESHOLD_RISK_MITIGATING	RISK_MITIGATION	Keep Blank or Ignore the field
BUKRS	COMPANY_CODE	From DCT field "BUKRS”
35	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE
FTR_THRESHOLD_SCHEME	LEGAL_BASIS	Keep Blank or Ignore the field	36	NA	NA	NA	CONSTRUCT	S4HANA
VVSART	PRODUCT_TYPE	From DCT field "SGSART"
BAPI_FTR_FAC_DEALCREATE
FTR_TARO_TRADE_ID	EXTERNAL_TRADE_ID	Keep Blank or Ignore the field
TB_SFHAART	TRANSACTION_TYPE	From DCT field "SFHAART"
37	NA	NA	NA	CONSTRUCT

BAPI_FTR_FAC_DEALCREATE
PRCTR	PROFIT_CENTER	Keep Blank or Ignore the field
TB_KUNNR_NEW	PARTNER	From DCT field "KONTRH"
38	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE
TB_DVTRAB
CONTRACT_
DATE	From DCT field "DVTRAB"
Keep Blank or Ignore the field	39	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE
TB_
TVTRAB
CONTRACT_
TIME	System Time at the time of Data Load
BAPI_FTR_FAC_DEALCREATE	RPORTB	PORTFOLIO	From DCT field "RPORTB"
Keep Blank or Ignore the field	40	NA	NA	NA	CONSTRUCT

BAPI_FTR_FAC_DEALCREATE
GSBER	BUSINESS_AREA	Keep Blank or Ignore the field	41	NA	NA	NA	CONSTRUCT
TB_ZUOND	ASSIGNMENT	From DCT field "ZUOND"

BAPI_FTR_FAC_DEALCREATE
TOE_HEDGING_CLASSIFICATION_OLD	HEDGE_CLASSIFICATION	Keep Blank or Ignore the field
TB_NORDEXT	EXTERNAL_REFERENCE	From DCT field "NORDEXT"
42	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE
TB_
REFER
INTERNAL_
REFERENCE	From DCT field "REFER"
BAPI_FTR_FAC_DEALCREATE	TB_MERKM	CHARACTERISTICS	From DCT field "MERKM"
Keep Blank or Ignore the field	43	NA	NA	NA	CONSTRUCT

BAPI_FTR_FAC_DEALCREATE
LAND1	COUNTRY	Keep Blank or Ignore the field	44	NA	NA	NA	CONSTRUCT	S4HANA
TB_DCRDAT	ENTRY_DATE	Date on which the data is getting loaded.
BAPI_FTR_FAC_DEALCREATE
INTCA	COUNTRY_ISO	Keep Blank or Ignore the field
TPM_COM_VAL_CLASS	VALUATION_CLASS	From DCT field "TPM_COM_VAL_CLASS”
45	NA	NA	NA	CONSTRUCT

BAPI_FTR_FAC_DEALCREATE	FBSTART_SEGMENTTERM	SEGMENT	Keep Blank or Ignore the field	46	NA	NA	NA	CONSTRUCT	Term Start	From DCT Field DBLFZ
BAPI_FTR_FAC_DEALCREATE	END_TERM	Term End	From DCT Field DELFZS4HANA
BAPI_FTR_FAC_DEALCREATE	START_INCLUSIVE	Calculation Period: Start Inclusive vs. End Inclusive	From DCT Field Calculation Period: Start Inclusive vs. End Inclusive
BAPI_FTR_FAC_DEALCREATE	CURRENCY	Transaction Currency	From DCT Field WGSCHFT
BAPI_FTR_FAC_DEALCREATE	FREQUENCY	Frequency	From DCT Field SRHYTHM	TRBA_BEHALF_OF_COMPANY	ON_BEHALF_OF_COMPANY	Keep Blank or Ignore the field	47	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TOE_HEDGING_CLASSIFICATION	HEDGING_CLASSIFICATION	Keep Blank or Ignore the field	48	NA	NA	NA	CONSTRUCT	S4HANA	FREQUENCY_UNIT	Unit for Frequency	From DCT Field AMMRHY OR ATTRHY
BAPI_FTR_FAC_DEALCREATE	TOE_REQUEST_ID	HEDGE_REQUEST_ID	Keep Blank or Ignore the field	49	NA	NA	NA	CONSTRUCT	S4HANA		PERCENTAGE_RATE	Percentage rate for condition items	From DCT Field PKOND
BAPI_FTR_FAC_DEALCREATE	CALC_1ST_PERIOD	Calculation method for first period of condition item	From DCT Field Calculation method for first period of condition item
BAPI_FTR_FAC_DEALCREATEFTR	CALC_CFILST_CODEPERIOD	Calculation method for last period of condition item	From DCT Field Calculation method for last period of condition item
CFI_CODE	Keep Blank or Ignore the field	50	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	RANLCALC_ISINMETHOD	ISIN	Keep Blank or Ignore the field	51	NA	NA	NA	CONSTRUCT	S4HANA	Interest Calculation Method	From DCT Field Interest Calculation Method
BAPI_FTR_FAC_DEALCREATE	TBACALC_MICCALENDAR	MIC	Keep Blank or Ignore the field	52	NA	NA	NA	CONSTRUCT	S4HANA	Interest Calendar	From DCT Field SKALIDWT
BAPI_FTR_FAC_DEALCREATEFTR	DATE_CONTRACTUPDATE_TIMESTAMP_UTCRULE	Update for Calculation/Due Date for Interest	From DCT Field Update for Calculation/Due Date for Interest
CONTRACT_TIMESTAMP_UTC	Keep Blank or Ignore the field	53	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	BUPLA	BUSINESSCALC_PLACE	Keep Blank or Ignore the field	54	NA	NA	NA	CONSTRUCT	S4HANA	DATE	Calculation Date	From DCT Field DVALUT
BAPI_FTR_FAC_DEALCREATE	CALC_DATE_INCLUSIVE	Inclusive Indicator for Calculation Date	From DCT Field Inclusive Indicator for Calculation Date
BAPI_FTR_FAC_DEALCREATE	CALC_DATE_MONTH_END	Month-End Indicator for Calculation Date	From DCT Field Month-End Indicator for Calculation Date
FKBER	FUNCTIONAL_AREA	Keep Blank or Ignore the field	55	NA	NA	NA	CONSTRUCT	S4HANA	BAPI_FTR_FAC_DEALCREATE	TPMCALC_CUSTDATE_DIFF_TERM_VALUE	CUSTOM_DIFF_TERM_1	Keep Blank or Ignore the field	56	NA	NA	NA	CONSTRUCT	S4HANA	WKDAY_SHIFT	Working Day Shift for Calculation Day	From DCT Field SVWERK
BAPI_FTR_FAC_DEALCREATE	DUE_DATE	Due date	From DCT Field DFAELL
BAPI_FTR_FAC_DEALCREATE	TPMDUE_CUSTDATE_DIFFMONTH_TERM_VALUE	CUSTOM_DIFF_TERM_2	Keep Blank or Ignore the field	END	Month-End Indicator for Due Date	From DCT Field Month-End Indicator for Due Date	57	NA	NA	NA	CONSTRUCT	S4HANA
BAPI_FTR_FAC_DEALCREATE	TPMDUE_CUSTDATE_DIFFWKDAY_TERM_VALUE	CUSTOM_DIFF_TERM_3	Keep Blank or Ignore the field	58	NA	NA	NA	CONSTRUCT	S4HANA	SHIFT	Working Day Shift for Due Date	From DCT Field SFWERK
BAPI_FTR_FAC_DEALCREATE	TPMSHIFT_CUSTDUE_DIFFDATE_TERM_VALUE	CUSTOM_DIFF_TERM_4	Keep Blank or Ignore the field	59	NA	NA	NA	CONSTRUCT	TO_END	Shift Due Date Back to End of Term	From DCT Field Shift Due Date Back to End of Term
BAPI_FTR_FAC_DEALCREATE	VALID_FROM	FTR Assignment Management: Limit Date	From DCT Field LIMIT_DATES4HANA
BAPI_FTR_FAC_DEALCREATE	TPM_CUST_DIFF_TERM_VALUE	CUSTOM_DIFF_TERM_5	Keep Blank or Ignore the field	60	NA	NA	NA	CONSTRUCT	S4HANA	AMOUNT	FTR Assignment Management: Drawing Amount	From DCT Field LIMIT_CHG_AMOUNT
BAPI_FTR_FAC_DEALCREATE	CURRENCY	FTR Assignment Management: Limit Currency	From DCT Field LIMIT_CURRENCY
BAPI_FTR_FAC_DEALCREATE	TPM_CUST_DIFF_TERM_VALUE	CUSTOM_DIFF_TERM_5	AMOUNT_NEW	FTR Assignment Management: Drawing Amount (BAPI)	From DCT Field LIMIT_POS_AMOUNTKeep Blank or Ignore the field

This BAPI has a simulation run provision. As part of the Pre-Load check when all the Syniti ADMM checks are performed, before making the production run of all the Interest Rate Instruments, a simulation run should be performed and all the standard BAPI errors needs to be documented.

A custom report, if required needs to be created for this. The report needs to have row reference and display the standard BAPI return messages successful as well as failed. This will make sure all the Interest Rate Instruments successfully pass all checks.

Note: It is also assumed that the DCT will not bring in Payment Details of Interest Rate Instruments. This information will be loaded as part of CNV 3040 – Business Partner Counterparty. Under this CNV, Payment SI details are created and assigned to this instrument. If this is done, once the BAPI is executed, it will automatically get assigned to the deal as part of Standard BAPI processing. A Data Pre-Validation check has been introduced for this step.

The load process includes:

Execute the automated data load into target system using "BAPI_FTR_IRATE_CREATE" and use the DCT File vs structure section of this document to populate the BAPI details.
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation with side by side check of each fields in scope of the objects with fields to be displayed as XXXX_ECC, XXXX_S4HANA, XXXX_MATCH ( As TRUE or FALSE) with an additional column denoting fields not matching and status of loading in S/4HANA as LOADED_IN_S4HANA ( As TRUE or FALSE)

Load Run Sheet

Item #	Step Description	Team Responsible
01	Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step.	Data team
02	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	Data team
03	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
04	Validate few records loaded by accessing standard transactions from S/4HNA e.g. FTR_EDIT or check in the tables - VTBFHA, VTBFHAZU or VTBFHAPO	Data team
05	Generate post load report if step 5 is validated	Data team
06	Log errors as defects, if any and address resolutions. Close defects.	Data team
07	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
08	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
09	Repeat steps 1 to 5 if necessary.	Data team

Load Phase and Dependencies

The load phase for the object 9116-Treasury Interest Rate Instruments is Pre-Cutover Phase 3

Configuration

Item #	Configuration Item
01	Company Codes relevant for Treasury- Field BUKRS (Check Table: T001)
02	Treasury Business Partners - BUT100
03	House Bank Ids- Field HKTID (Check Table: T012K)
04	Payment Methods- Field ZLSCH (Check Table: T042Z)
05	Contract Type - Field RANTYP
06	Product Category- Field SANLF (Check Table: TZAF)
07	Product Type- Field SGSART (Check Table: TZPA)
08	Financial Transaction Types- Field SFHAART (Check Table: AT10)
09	Portfolio Code - Check Table: TWPOB
10	General Valuation Class - Check Table: TRGC_COM_VALCL

Conversion Objects

Object #	Preceding Object Conversion Approach
CNV-3007	Business Partner - General Role
CNV-1083	Bank Master
CNV-3040	Business Partner - Treasury

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
Valid Master	Business Partner is not having a valid treasury role i.e. TR0151	Ensure that Business Partner is updated with correct role
Invalid Company Code	Company Code in the DCT is invalid based on the check table T001	Ensure correct Company Code is supplied to the BAPI
Invalid Product Type	Product Type in the DCT is invalid based on the check table TZPA	Ensure correct Product Type is supplied to the BAPI
Invalid Transaction Type	Transaction Type in the DCT is invalid based on the check table AT10	Ensure correct Transaction Type is supplied to the BAPI
Invalid Trader	Trader in the DCT is invalid based on the check table TZDEA	Ensure correct Trader is supplied to the BAPI
Invalid Portfolio Code	Portfolio Code in the DCT is invalid based on the check table TWPOB	Ensure correct Portfolio Code is supplied to the BAPI
Invalid Interest Calculation Method	Interest Calculation Method is invalid as per the Custom Check Table	Ensure correct Interest Calculation method is supplied to the BAPI
Invalid Frequency Category	Frequency Category is invalid as per the Custom Check Table	Ensure correct Frequency Category is supplied to the BAPI

Post-Load Validation

Project Team

The following post load validations will be done by Project Team

Completeness

Task

Action

Reconciliation of Record Count

Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has it's own data record count)

Check for logs from Load and fix erroneous records, if any.

To check the records loaded, a variant will be created in standard SAP report "FTR_00". We can take a dump from this standard report to verify all the relevant information as part of the load.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation.

Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time.

Any mismatch will be reported under the Post Load - Error report.

Business

The following post load validations will be done by business.

Completeness

Task

Action

Record Count Check

Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations

Business may also run transaction code FTR_EDIT or FTR_00 to cross check the records created for Counterparties

Accuracy

Task

Action

Field Checks

Check key fields to ensure that Business Partner - Counterparty has been maintained with proper details such as

Right Amount is loaded in the created deal
Correct Payment Details are loaded in the deal
Ensure Correct Interest Rate is loaded in the deal
Ensure correct Start and End Date are loaded in the created deal

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
All configuration items like Company Code, Product Type, Transaction Type, etc are approved by business and pre-configured before this data can be loaded
All Bank Account information is approved by business and loaded in the system. Same are also created as SI details in BP master and assigned to the correct Product Type/Transaction Type combination in the BP master as these will be auto loaded in the deal and will not be part of the DCT.

Change log

Change History

limit	10

From Apr 23, 2026 to May 14, 2026	Actor	Type	Activity	Version
Revision in Progress	VIDWANS-ext, Sauradh	Edit	updated the page at 12:24 pm
	VIDWANS-ext, Sauradh	State	changed state to Revision in Progress at 11:43 am	v30
Approved	VIDWANS-ext, Sauradh	Edit	updated the page at 11:43 am
Apr 20, 2026
	TAN-ext, Charmaine	State	changed state to Approved at 3:14 pm (State override) [PMO Comments] Conversion Spec completed as per CS register and functional review completed	v29
Lead Approval	TAN-ext, Charmaine	State	gave Minor change approval at 3:14 pm [PMO Comments] Conversion Spec completed as per CS register and functional review completed

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 13

New Version 31

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Data- Pre Load Validation Report

Data Cleansing

Data- Pre Load Validation Report

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Transformation Mapping

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