Purpose

The purpose of this document is to define the conversion approach to create Object 1204 - Treasury Business Partner - IHB Account Holder - IHB100 in S/4 HANA.

The Business Partner role IHB100 is a specific SAP role for an "Inhouse Bank Account Holder" used in in-house banking scenarios to manage a business partner entity as Internal bank account which processes intercompany payment, cash pooling, and related transactions. It also helps in the Payments on Behalf Of (POBO) scenarios, if applicable.

The below table explains the Role Matrix, applicable S4HANA tables and related Conversion Objects.

Note: Role IHB200 (IHB Authorised Drawer) is paired with Role IHB200. This is being covered in the CNV-1205

 The key fields for the above mentioned S4HANA tables pertaining to CNV-1203 Treasury Business Partner Depository Bank are explained below:

• Table BUT100 - Role assignment:
• PARTNER - Business Partner Number - unique identifier of the Business partner which can be internally assigned by SAP or externally assigned by user. For Intercompany Business Partner, it will be externally assigned. Others will be internally assigned following the number ranges by the groups as specified in the CNV-3007
• RLTYP - Business Partner Role - This field is to select the Partner Role. For IHB Account Holder, the role to be used is IHB100
• VALID_FROM - Validity Start of a BP Role 
• VALID_TO - Validity End of a BP Role

The treasury function in legacy is carried out in the Quantum system and therefore for the data related to IHB Account Holder will be provided by business in a Data Collection Template (DCT). which will be transformed in Syniti to generate a preload file as the per the to-be S4HANA design. The load will be part of the Business Partner Load (Object 3007) for the General Data and IHB Account Holder (Role IHB100) data using the LTMC <TBC as the available LTMC for Business Partner- Treasury is only Direct Transfer>. The function module is CNV_OT_APPL_FI_TRM_BP_ROLE and the BAPI/API is FTB_BUPA_DARK_MAINTAIN_INTERN

Conversion Scope

The scope of this document covers the approach for converting active Depository Bank from Legacy Source Systems into S/4HANA following the MDS for Object-1204 - DD-FUN-050 Master Data Standard-3XXX-Consolidated Business Partner.

The relevancy criteria are not applicable for this object as the relevant data will be provided by business in a DCT (Data Collection Template), however as the general data of IHB Account Holder will be part of the object 3007, it needs to be ensured from deduplication perspective.

 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 IHB Account Holder data from source system i.e. Quantum is to be done manually or to be constructed manually by the business in DCT
2. Cleansing by business team in the source system (Quantum) to ensure that only active and in use records for IHB Account Holder are provided in DCT
3. Separate DCTs to be provided i.e. for General Role and IHB Account Holder Role  
4. The extracted/constructed records to be converted into a DCT and stored in the Syniti for Transformation
5. Amount and date format from source system to align with S4HANA 
6. As the target structure in S4HANA involves dependency on the Object 3007 (Business Partner- General Data), and all other Roles (see dependencies section) should have been loaded before IHB100 - IHB Account Holder Role

Target Design

The technical design of the target for this conversion approach for Object 1204- IHB Account Holder - IHB100 is as below, following the MDS Object-1204 - DD-FUN-050 Master Data Standard-3XXX-Consolidated Business Partner

The technical design of the target for this conversion approach.

Data Cleansing

For the Object 1204- IHB Account Holder, 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
2. The General Data View of IHB Account Holder will be handled together with the Object 3007 (Business Partner- General) and Object - 3040 (Counterparty) and therefore same de-duplication/cleansing rules will be followed

Data- Pre Load Validation Report

However, for the purpose of the Object 1204- TIHB Account Holder, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file. 

The above report (ID-01) is similar to CNV-3040, CNV-1202 and CNV 1203

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 1204- IHB Account Holder IHB100 Master Data - 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. 

Data Privacy and Sensitivity

Extraction

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

1. 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 1204- IHB Account Holder IHB100 Master Data , the data is to be provided in a DCT by the business, therefore extraction related activity is not carried out via Syniti

Selection Screen

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

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