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

Summarize Multi-language Requirement/s, if any

Document Management

Summarize Document Management requirement, if any

Legal Requirement

Summarize Legal Requirement/s, if any

Special Requirements

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

1. Extraction of CP 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 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:

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.

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 Syniti Migrate. There are 2 possibilities:

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

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

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

<Object> DCT Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

Transformation

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

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

Transformation Run Sheet

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

The load process includes:

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

Load Run Sheet

Load Phase and Dependencies

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

Configuration

List the Configurations required before loading can commence

Conversion Objects

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

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

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

Any additional key assumptions.

See also

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

Change log