Status
Owner	BAJAJ-ext, Manoj
Stakeholders	PILLAY-ext, Lawrence

Purpose

The purpose of this document is to define the conversion approach to create Object 3042 - Business Partner - Business Partner Bank -with role type TR0703 in S/4 HANA.

Business Partner Roles for Organization - Bank (TR0703): is created be assigned to Bank Keys. This establishes a linkage between the Bank and the Business Partner to facilitate the Bank Account Management.

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

Role	Description	Table	Conversion Object
000000	General Role Business Partner - General view (including name and address standards, languages, emails, formats, identifications, bank details of the business partner, etc.)	BUT000	CNV-3007
TR0703	Business Partner Bank - TR0703	BUT100	CNV-3042

 
The Business Partner created under MDS.3007 can be extended to Bank Role (TR0703).  Bank Role is required for assigning the to the Bank as risk business partner for creating the Bank Hierarchy. It is also required for using Banks in Credit Limit as Limit attribute This role includes only general data which is same as data maintained in general role.

The key fields for the above mentioned S4HANA tables pertaining to CNV-3042 IHB Account Holder - IHB100 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 Business Partner Bank Role, the role to be used is TR0703
• VALID_FROM - Validity Start of the role
• VALID_TO - Validity End of the role

The Bank Account Management function is new in S4HANA, therefore for the data related to Bank Role 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 migrating/creating the Business Partner with Bank Role TR0703 following the Master Data Standard- DD-FUN-050 Master Data Standard_3042 - Business Partner Bank - TR0703

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 Business Partner with Bank Role, will be part of the object 3007, it needs to be ensured from deduplication perspective.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
CONSTRUCT	Active and relevant Partners requiring a Bank Role	NA	S4HANA	100

Additional Information

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. Business Partner requiring a Bank Role (TR0703) to be constructed manually by the business in DCT
2. The DCT as provided by the business will be used for the transformation and generation of load files for the extension of the role TR0703 to Business Partner
3. Amount and date format from source system to align with S4HANA 
4. 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 the load of this object

Target Design

The technical design of the target for this conversion approach for Object 3042 - Business Partner - Business Partner Bank -with role type TR0703 in S/4 HANA, following the MDS DD-FUN-050 Master Data Standard_3042 - Business Partner Bank - TR0703 is as below.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
BUT100	PARTNER	BU_PARTNER	Business Partner Number	CHAR	10	Mandatory
BUT100	RLTYP	BU_PARTNERROLE	BP Role	CHAR	6	Mandatory
BUT100	VALID_FROM	BU_ROLE_VALID_FROM	Validity Start of a BP Role	DEC	15	Mandatory
BUT100	VALID_TO	BU_ROLE_VALID_TO	Validity End of a BP Role	DEC	15	Mandatory

Data Cleansing

For the Object 3042- Business Partner Bank Role, no specific data cleansing is applicable due to below reasons/assumptions:

1. Data will be provided by Business in a DCT form
2. The General Data View of Business Partner requiring Bank Role will be handled with the Object 3007 (Business Partner- General) and therefore same de-duplication/cleansing rules will be followed

Data- Pre Load Validation Report

However, for the purpose of the Object 3042- Business Partner Bank - TR0703, below validations reports should be available in Syniti so that the data as provided in DCT is validated before generating the pre-load file. 

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
01	High	Validity end date is in the Past	Check if Business Partner RLTYP Not Equal to Blank, then the validity end date (VALID_TO) in the table BUT100 is not in the past <Cutover date	Records showing validity end date in the past	Not applicable. Check against S4 Configuration/Master Data
02	Medium	Validity start date is greater than Validity End date	Check if Business Partner RLTYP Not Equal to Blank, then the validity end date (VALID_TO) in the table BUT100 is not < than the Validity Start (VALID_FROM) date	Records showing errors	Not applicable. Check against S4 Configuration/Master Data

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

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 3042- Business Partner Bank - TR0703 - the conversion process will depend upon the DCT (Data Collection Template) which will be provided by the business. This DCT will be used for transformation and generation of the pre-load file. 

Data Privacy and Sensitivity

Not applicable.

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 3042- Business Partner Bank - TR0703, 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 source is DCT.

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Object 3042- Business Partner Bank - TR0703 Master Data with exception of some fields which require transformation as mentioned in the transformation rule.

This DCT is to be prepared in addition to the DCT containing the General Data such as Name, Address, Contact Details, Payment Information, Identification Numbers etc., which will be provided against the object 3007 - Business Partners - General (Role 000000)

Object 3042- Business Partner Bank - TR0703- DCT Rules

Field Name	Field Description	Rule
BUT100-PARTNER	Business Partner Number	This is a required field.  This data will be captured by business in DCT for Partners needing a Bank Role (TR0703). A validation is needed to check the BP number captured in the DCT is valid one against the table BUT100 Note: Though the target design of this field is 10 CHARS in length, for the DCT purpose, the length to be kept at 20 CHARS.
BUT100-RLTYP	Business Partner Role	This is a required field.  Business Partner that needs to be created as IHB Account Holder should be assigned to role TR0703 (Default to TR0703)
BUT100-VALID_FROM	Validity Start of a BP Role	This is a required field.  Though the date format is YYYYMMDDHHMMSS, in the DCT provide YYYYMMDD as real value and HHMMSS can be left blank Example: 20250101
BUT100-VALID_TO	Validity End of a BP Role	This is a required field.  Though the date format is YYYYMMDDHHMMSS, in the DCT provide YYYYMMDD as real value and HHMMSS can be left blank. If the actual end date is not known, then a generic end date of year 9999 can be provided. Example: 99991231 Note: The end date should not be prior to the cutover/go live date.

Extraction Dependencies

For Object 3042- Business Partner Bank - TR0703 no extraction dependencies are applicable as the source is via DCT and this is Master Data object 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

Item #	Step Description	Team Responsible
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 CONSTRUCT from business has been received and maintained in Syniti	Syniti/Data team
5	Execute transformation for the object	Syniti team
6	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Syniti/Data team
7.	Generate Pre-Load reports.	Syniti team
8.	Generate data load count.	Syniti team
9.	Log errors as defects, if any and address resolutions. Close defects.	Syniti/Data team
10.	Re-transform and re-validate the Pre-load reports if necessary.	Syniti/Data team
11.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
12.	Analyse and resolve any pre-load defects logged by business.	Syniti/Data team
13.	Repeat steps 5 to 11 if necessary	Syniti/Data team
14.	Proceed to pre-load validations	Data team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
01	NA	NA	NA	CONSTRUCT	S4HANA	BUT100	PARTNER	Business Partner Number	Step 1 - Compare the BP Number in the DCT with BP XREFF - BPEXT field Step 2 - Find the BP Number for the match BP XREFF - PARTNER Field Step 3 - Pass the BP Number fetched from BP XREFF in table BUT100 to check if Role "TR0703" is assigned to the BP Step 4 - If the condition matches, then replace the BP Number in the DCT field
02	NA	NA	NA	CONSTRUCT	S4HANA	BUT100	RLTYP	BP Role	Default to "TR0703"
03	NA	NA	NA	CONSTRUCT	S4HANA	BUT100	VALID_FROM	Validity Start of a BP Role	As per DCT Check the Validity Start date is not greater than Validity End Date
04	NA	NA	NA	CONSTRUCT	S4HANA	BUT100	VALID_TO	Validity End of a BP Role	As per DCT Check the Validity End date is not < Cutover date

Transformation Mapping

 

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
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

The Pre Load validations are performed by Project Team

Completeness

Task	Action
Generation of Pre-load reports	Mandatory field check. The business partner being created as IHB Account Holder-IHB100 role is available in the General Role (000000) The Role assigned in the Pre-Load validation file against a record is TR0703 The validity end date of the role for a record in the Pre-load file is not prior to cutover/go-live date The validity start date is not > the validity end date
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 record

Accuracy

Task	Action
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.  Business Partner to be created with Bank role TR0703 is correctly picked up based on XREF from the role 000000 (General Data)
Business Value Checks	The fields value as per the DCT, and pre-load fields are matching for the key fields.
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

The following pre-load validations will be performed by business

Completeness

Task	Action
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 is correctly picked up as per DCT

Accuracy

Task	Action
Conversion accuracy	To check and validate the load files with all the transformation and mapping rules, to be signed off.

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 LTMC - It is assumed that even though the LTMC - S4_FI_TRM_BP_ROLES is relevant for Direct Transfer only, it can be used for staging. If the same is not feasible <TBC by Syniti team> then function module CNV_OT_APPL_FI_TRM_BP_ROLE using a wrapper custom load program can be used as alternative
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

Item #	Step Description	Team Responsible
01	Go to load file and pick 5 data records, load manually without any tool. See what happens. If all okay, proceed with the next step.	Data team
02	Go to load file and pick 10 records and load them with the tool. No action if the previous step has fallen. If not, then continue to load 10 records with the tool. Check if everything went okay.	Data team
03	Proceed with the full load if steps one and two were succeed else fix the issue with records	Data team
04	Validate few records loaded by accessing standard transaction code "BP" from S/4HANA	Data team
05	Generate post load report if step 5 is validated	Data team
06	Log errors as defects, if any and address resolutions. Close defects.	Data team
07	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
08	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
09	Repeat steps 1 to 5 if necessary.	Data team

Load Phase and Dependencies

The load phase for the object 3042-Business Partner Bank - TR0703 is Pre-Cutover Phase.

Configuration

 No specific configurations except the role as mentioned in this CS is needed.

Conversion Objects

Object #	Preceding Object Conversion Approach
CNV-3007	Business Partner - General Role
CNV-3040	Business Partner Counterparty (TR0151)
CNV-3017	Business Partners - FI Customer (FLCU00)
CNV-3018	Business Partners - FI Vendor (FLVN00)

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. 

Error Type	Error Description	Action Taken
Valid Master	Business Partner is not having a valid role i.e. TR0703	Ensure that Business Partner is updated with correct role

Post-Load Validation

Project Team

The following post load validations will be done by Project Team

Completeness

Task	Action
Reconciliation of Record Count	Record Count - Count and check how many records were loaded vs. Records in the load file (Each mock has its own data record count) Check for logs from Load and fix erroneous records, if any.

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation. Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time. Any mismatch will be reported under the Post Load - Error report.

Business

The following post load validations will be done by business

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations Business may also run transaction code BP to cross check the records created for Issuers

Accuracy

Task	Action
Field Checks	Check key fields to ensure that Business Partner - Issuer has been maintained with proper details

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Object 3042 - Business Partner Bank - TR0703 is in scope based on data design and any exception requested by business.
• Object -3007 - BP General- Data for all applicable fields of General Role have been collected in DCT and has been loaded correctly following the specs of the CNV-3007

 

See also

CNV-3007: Business Partner General - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base

CNV- 3040 - Business Partner Counterparty - CNV-3040 Business Partner Counterparty

Change log