Purpose

The purpose of this document is to define the conversion approach to create the Object 9111 - TRM - Bank guarantee in S4HANA.

A Bank Guarantee is an assurance on the part of a bank to make good an organisation's debt in the event of non-payment. Therefore, Bank Guarantee is essentially an agreement to stand as a cosigner on a transaction. In the event that the original party cannot follow through, the bank can be called upon to provide the payment. Till such time a Bank Guarantee is not revoked, it works as a contingent instrument. 

In S4HANA, Bank Guarantee in Treasury module is created as an instrument under the relevant Product Type, Transaction Type (Bank Guarantee received or issued), with Treasury Business Partner and the transaction code used to create such instrument is FTR_CREATE.

For the purpose of migrating active Bank Guarantees, issued or received by Syensqo, a custom program using the BAPI "BAPI_FTR_BG_DEALCREATE" will be used as the standard LTMC (Data Migration Cockpit) only supports the direct transfer i.e. if the source system is ECC.

Conversion Scope

The scope of this document covers the approach for converting active Bank Guarantees, received or issued with information sourced manually from business as the same is not used in source Treasury system (Quantum).

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

Multi-language Requirement
None

Document Management

None

Legal Requirement

None

Special Requirements

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

1. Data relevant for Bank Guarantee migration to sourced manually from Business in a Data Collection Template (DCT) 
2. Business team to ensure that only active and in use records for Bank Guarantees are provided in DCT
3. The data as collected via DCT will be 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 to check if the BP is assigned with Role "TR0151"
2. Company Code - T001
3. Product Type - TZPA
4. Transaction Type - AT10
5. Portfolio Code - TWPOB  
6. General Valuation Class - TRGC_COM_VALCL
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.

Target Design

For the purpose of migrating active Bank Guarantees as collected in the DCT, issued or received by Syensqo, a custom program using the BAPI "BAPI_FTR_BG_DEALCREATE" will be used as the standard LTMC (Data Migration Cockpit) only supports the direct transfer i.e. if the source system is ECC.

This section covers the list of fields that are part of the BAPI and DCT. This section will also explain field by field mapping of the BAPI structure and where the data will come from for each field for the BAPI.

The technical design of the target for this conversion approach.

There are 3 main tables involved as below

1. VTBFHA
2. VTBFHAZU
3. VTBFHAPO

However, unlike other TRM Instruments, Bank Guarantee does not have a direct corelation of BAPI structure to Transparent Tables such as VTBFHA, VTBFHAZU, VTBFHAPO.

The table below serves as the Header (General Data) for table VTBFHA and includes Bank Guarantee data, which updates both VTBFHAZU and VTBHAPO together upon load via BAPI.

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

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