Purpose

The purpose of this document is to define the conversion approach to create BIC Assignment to Business Partner (object 1198) in S/4 HANA.

BIC Assignment to Business Partner is a master data in Treasury and Risk Management module of S4HANA. This assignment is important to ensure that the financial transactions are processed accurately and efficiently. The BIC assignment facilitates international transfers, ensure compliance with regulations, enhances security, streamlines communications, which helps reduce errors and manual intervention. In S4HANA, the transaction code to assign BIC to business partner is FTR_BP_BIC.

The document details out the field list, extraction criteria, scoping, mapping, transformation logic, generation of the pre-load file and loading of the same with respect to the object 1198- Assign BIC to business partner, to be used in treasury module of S4HANA.

Key tables and fields: 

The following table is involved in S4HANA with respect to the assignment of BIC to BP.

Table TCORT_BP_BIC (Treasury: BIC Codes / Account Numbers for Business Partners) holds the BIC information.  The key fields of this table are:

• PARTNER – Business Partner Number – This field provides the unique identification number of the business partner.
• VALID FROM – Valid From – Date of exposure – This field determines the validity start date of a raw exposure and any related exposure position flows created when releasing the raw exposure. This field determines the validity start date of the assignment of the BIC
• RECIPIENT TYPE – Recipient / Sender Type – This field captures the partner or acting party information, who can receive/send correspondence. The correspondence recipient type is mainly used to differentiate between internal and external recipients/senders. It is also a control parameter used in the creation of outgoing/incoming messages. E.g. “Controller Email”.
• FUNCTION – Correspondence Class – This field helps identify the type of TRM correspondence between the organisation and the partner. The correspondence class is related to the business transactions of the available message formats, such as SWIFT messages. Correspondence classes are used as configuration terms that control the channel, format, and other attributes of TRM correspondence communication. E.g. “SE Order – Order to buy or sell securities”.
• BIC - SWIFT/BIC for International Payments – The BIC (Bank identifier code) also known as SWIFT code, uniquely identifies a bank throughout the world. SWIFT stands for Society for Worldwide Interbank Financial Telecommunication. This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions. It can be 8 or 11 digits.

The treasury function in legacy is carried out in the Quantum system and therefore for the conversion of this object i.e. BIC assignment to BP, the data/details need to be sourced from Quantum and transformed as applicable for S4HANA in Syniti and load using a custom program as the LTMC for this object is not available in the Data Migration Cockpit.

Conversion Scope

The scope of this document covers the approach for converting active Treasury – BIC assignments to BP from Legacy Source Systems (Quantum) into S/4HANA following the Master Data Design Standard - DD-FUN-050 Master Data Standard_1198 – Assign BIC to Business Partner.

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

Not applicable

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

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

1. Extraction of BIC Assignment to BP from source system i.e. Quantum is to be done manually.
2. Cleansing by business team to identify valid records in the source system i.e. to ensure that only active records are provided in DCT.
3. The extracted records to be converted into a DCT and stored in the Syniti for transformation
4. Below Value mapping tables to be created in Syniti:
1. Source and target company code
2. Customer / Vendor (BP) mappings i.e. source to target
5. Amount and date format from source system to align with S4HANA 

Target Design

The Target design of the object 1198 – Assign BIC to Business Partner on the MDS - DD-FUN-050 Master Data Standard_1198 – Assign BIC to Business Partner is as below

The technical design of the target for this conversion approach. 

Table TCORT_BP_BIC - Treasury: BIC Codes / Account Numbers for Business Partners

Data Cleansing

For the purpose of the Object 1201- BP Group Assignment for Inbound Correspondence, the data cleansing is not applicable. It is expected that relevant records will be provided in DCT by business.

However, for the purpose of the checking the DCT, below preload validation reports are applicable:

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 1198- Assign BIC to Business Partner - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business based on the source data from Quantum system. This DCT will be used for transformation and generation of the pre-load file. 

The load will be done via a custom program <to be confirmed>, as LTMC for this object is not available as of now.

Data Privacy and Sensitivity

None

Extraction

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

1. The data exists. Syniti connects to the source and loads the data into Syniti. 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; 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. This is to be conducted using DCT (Data Collection Template) in Syniti.

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

In case of the object 1198-Assign BIC to Business Partner the data is to be provided in a DCT by the business, therefore extraction related activity is outside Syniti. 

Extraction Run Sheet

Selection Screen

Not applicable

Data Collection Template (DCT)
Target Ready Data Collection Template will be created for Object 1198- Assign BIC to Business Partner with exception of some fields which require transformation as mentioned in the transformation rule.

1198 – Assign BIC to Business Partner DCT Rules

Note:

• Only the fields which are marked as Required or Conditional in the MDS for this object have been considered below
• Business Users to provide the values in the DCT.
• DCT checks only the field length and field behaviour (mandatory/optional etc.) checks, therefore Users must provide valid Configuration values where applicable 

Extraction Dependencies

For object 1198- Assign BIC to Business Partner, no extraction dependencies is applicable as this is DCT and a Master Data by nature.

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

List the steps that need to occur before transformation can commence

Pre-Load Validation

Project Team

The Pre Load validations are performed by Project Team

Completeness

Accuracy

Business

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

Completeness

Accuracy

Load

The load process includes:

1. Execute the automated data load into target system using load tool or produce the load file if the loading of records to be done via a custom program <TBC>, as LTMC for this object is not available as of now. 
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 1198-Assign BIC to Business Partner

Configuration

Below configurations should exist 

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

The following post load validations will be done by Project Team

Completeness

Accuracy

Business

The following post load validations will be done by business.

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Object 1198 is in scope based on data design and any exception requested by business.
• Only the relevant records for BIC Accounts to BP will be provided by business (sourced from Quantum) in the DCT 
• The load will be done via a custom program <TBC> for this object is not available as of now. 

See also

Change log