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

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:

1. Extraction of CP data Facilities data from source system i.e. Quantum is to be done manually
2. 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
3. The extracted records to be converted into a DCT and stored in the Syniti for Transformation
4. Below Configuration Check Tables needs to be referenced in Syniti to validate the data in the DCT:
1. Counterparty to Business Partner - BUT100
2. Company Code - T001
3. Product Type - TZPA
4. Transaction Type -  AT10
5. Trader - TZDEA
6. Portfolio Code - TWPOB  
7. General Valuation Class - TRGC_COM_VALCL
8. Interest Calculation Method - Custom Check Table with Value Fields given in the below CNV
5. Amount and date format from source system to align with S4HANA 
6. 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:

Update Rule:

Frequency:

BP Number 

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.

There are 5 main tables in consideration here. 

1. VTBFHA
2. VTBFHAPO
3. VTBFINKO
4. VTB_ASGN_LIMIT
5. 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:

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

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.

There are 5 main tables in consideration here. 

1. VTBFHA
2. VTBFHAPO
3. VTBFINKO
4. VTB_ASGN_LIMIT
5. 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:

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

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:

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

Data Privacy and Sensitivity

Extraction

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

1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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

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

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

Data Privacy and Sensitivity

Extraction

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

1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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

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

Extraction Dependencies

For object 9113 - TRM Facilities dependencies are applicable as under

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:

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

Transformation Rules

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:

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

Transformation Rules

Transformation Mapping

Business Partner 

Mapping Table for Quantum counterparty/partner code to S4HANA Business Partner

Transformation Dependencies

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

Completeness

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

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

Completeness

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

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

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

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:

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

Load Phase and Dependencies

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

Configuration