Status

Page Status

Owner

Prasad Naidu

Stakeholders

NG-ext, Bernard PILLAY-ext, Lawrence

Purpose

The purpose of this document is to define the approach, scope, and rules for the conversion of Bank Master Data from legacy systems into SAP S/4HANA. The Bank Master includes information about House Banks and Bank Directory (External Banks) required for processing payment transactions such as vendor payments, customer refunds, and bank reconciliations.

This conversion ensures that all bank-related master data is available and consistent in the S/4HANA system to support business-critical financial operations post go-live. The data migration encompasses both:· External external Banks (from tables like BNKA): Used for storing details of banks globally (e.g., SWIFT, bank address, bank key).

· House Banks: Internal company banks used for executing payments and receiving cash (e.g., bank account number, account ID, GL account linkage).

The migration process includes the cleansing, transformation, mapping, and loading of this data in alignment with SAP's Business Partner and Financial Supply Chain Management framework, while adhering to data quality and audit requirements.

Conversion Scope

The scope of this conversion covers the migration of all relevant Bank Master Data from the legacy SAP ECC system to the SAP S/4HANA system. This includes both External Bank Directory data and House Bank configurations, ensuring continuity in banking operations such as payments, collections, and bank reconciliations.

In Syensqo, the bank master data will be loaded and post go-live, the bank master data will be maintained by loading delta changes on a monthly basis.

Conversion Scope

Bank master Data will be migrated from PI2 client to S4

Relevancy Criteria:

1) All Bank keys in BNKA table are in scope from PI2

2) If there are any duplicate keys in source systems

a) Read all the records from table BNKA

b) Eliminate Duplicates - Select max( BANKS, BANKL) , All the other fields from the step b by grouping on the fields BANKS, BANKL

3) Business is responsible for Data cleansing.

The data from legacy system includes:

Bank Key
Bank Country
Bank Name
Bank Address
SWIFT/BIC Code
Bank Number / Routing Code

The data from legacy system excludes:

Bank configuration for treasury or cash management tools not in active use

Bank Communication Management (BCM) configurations unless separately scoped

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records

PF2

PI2	Bank Master

WP2

~374000

Bank Master

S4

PI2

~374000

Bank Master

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

BNKA

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
BNKA

MANDTMANDTClientCLNT3Mandatory

BANKS	BANKS	Bank Country/Region Key	CHAR	3	Mandatory
BNKA

BANKK

BANKL

BANKK

Bank Keys

CHAR

15

OptionalBNKAERDAT_BFERDAT_BFRecord Created OnDATS8MandatoryBNKAERNAM_BFERNAM_BFName of person who created the objectCHAR12

	Mandatory
BNKA	BANKA	BANKA	Name of Financial Institution	CHAR	60

Optional

Mandatory

BNKA

REGIO

PROVZ	REGIO	Region (State, Province, County)	CHAR	3	Optional
BNKA	STRAS

_GP

	STRAS_GP	Street and House Number	CHAR	35	Optional
BNKA	ORT01

_GP

	ORT01_GP	City	CHAR	35	Optional
BNKA	SWIFT	SWIFT	SWIFT-BIC for International Payments	CHAR	11	Optional
BNKA	BGRUP	BGRUP	Bank Group (bank network)	CHAR	2	Optional
BNKA	XPGRO	XPGRO	Post Office Bank Current Account Flag	CHAR	1	Optional
BNKA	LOEVM	LOEVM	Deletion Indicator	CHAR	1	Optional
BNKA

BANKL

BNKLZ

BANKL

Bank

Keys

Number

CHAR

15

OptionalBNKAAD_ADDRNUM

Mandatory

BNKA

PSKTO_CHPSKTO_CHPost office bank current account numberCHAR16Optional

ADRNR

AD_ADDRNUM	Address Number	CHAR	10	Optional
BNKA	BRNCH	BRNCH	Bank Branch	CHAR	40	Optional
BNKA

CHECKMETH

CHKME	CHECKMETH	Check Digit Calculation Method	CHAR	4	Optional
BNKA	VERS

_BF

VERS_BF

Format of File with Bank Data

CHAR

3

OptionalBNKABNKA_SEPABNKA_SEPASEPA-relevant Local Bank NameCHAR60OptionalBNKAIBAN_RULEIBAN_RULEIBAN RuleCHAROptionalBNKASDD_B2BSDD_B2BSupport of SEPA B2B Direct DebitCHAR1OptionalBNKASDD_COR1SDD_COR1Support of SEPA COR1 Direct DebitCHAR1OptionalBNKASDD_RTRANSSDD_RTRANSSupport of SEPA Returned Debits (R Transactions)CHAR1OptionalBNKABNKAAPPBNKAAPPBank Application – Unique key for application-specific bank attributesCHAR

	Optional
BNKA

PRQ_

BICKY

PRQ_BICKY

Key of a BIC+ data record (Swift)

CHAR

12

Optional

BNKA

PRQ_RCCPRQ_RCCRouting Control CodeCHAR15Optional

Data Cleansing

NA

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1	High	Bank key not unique within country	BANKS + BANKL must be unique	Flag as duplicate; reject or merge records	PF2,WP2,PI2
2	High	Missing or invalid SWIFT/BIC code	SWIFT field must be 8 or 11 alphanumeric characters	Flag and request update from valid bank directory	PF2,WP2,PI2
3	Medium	Bank name contains special characters or inconsistent casing	BANKA field should follow naming conventions and avoid special characters	Normalize or correct bank name formatting	PF2,WP2,PI2
4	High	Obsolete bank record not linked to any business partner	Check if BANKL is not referenced in any related table (e.g., LFBK, KNBK)	Mark for archival or deletion after verification	PF2,WP2,PI2
7	High	Duplicate bank key entries detected	BANKL must be unique per BANKS; fuzzy match for duplicates	Flag duplicates; consolidate or clean up	PF2,WP2,PI2
10	High	Bank key format invalid per country-specific rules	BANKL format must match country-specific structure rules (e.g., DE = 8 digits)	Flag and correct according to rulebook or SAP note	PF2,WP2,PI2

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

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

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
	NA

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field NameField DescriptionRuleBNKA-BANKSBank Country/Region KeyThe country in which the bank is located.
ISO Country code
e.g. AE for United Arab EmiratesBANKA-BANKKBank KeysA Bank Key in SAP uniquely identifies a particular Bank in particular country.
Bank Keys are created automatically in SAP using the following logic:
If Bank Number is available, then Bank Number is equal to Bank Key.
If Bank Number is unavailable, then SWIFT/BIC code is equal to Bank Key.
Different length by country, for AE is 3 digits length
e.g. for AE is 027 - SAP provides a guidance listBNKA-BANKLBank NumberA Bank Number is a SAP terminology for identifying Bank Code, Sort Code, BSB Number
etc.
Different length by country, for AE is 3 digits length
e.g. for AE is 027 - SAP provides a guidance listBNKA-ERNAM_BFName of person who created the objectThe user who created it - OptionalBNKA-BANKAName of Financial InstitutionName of the Bank - Optional
e.g. FIRST ABU DHABI BANK PJSCBNKA-REGIORegion (State, Province, County)Bank Region - OptionalBNKA-STRAS_GPStreet and House NumberBank address - OptionalBNKA-ORT01_GPCityCity - OptionalBNKA-SWIFTSWIFT/BIC for International Payments8 digits to max 11 digits- OptionalBNKA-BGRUPBank group (bank network)Bank group (bank network)- OptionalBNKA-XPGROPost Office Bank Current AccountPost Office Bank Current Account- Optional

No DCT for this object

Extraction Dependencies

Item #	Step Description	Team Responsible
	NA

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 to make the data Target ready:

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

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 toolMigrate.	Data team
2.	In tool, select the Object Bank Master	Data team
3.	Go to Process Area Launch and Process the Object - Bank Master	Data team
4.	Launch the Objects to execute transformation.	Data team
5.	Monitor the transformation progress and ensure performance and completion is within allowed timeframe	Data team
6.	Generate Pre-Load reports .	Data team
7.	Generate data load count.	Data team
8.	Log errors as defects, if any and address resolutions. Close defects.	Data team
9.	Re-transform and re-validate the Pre-load reports if necessary.	Data team
10.	Validate the transformed file as part of pre-load validation, raise data defects or provide the pre-load sign-off.	Business
11.	Analyse and resolve any pre-load defects logged by business.	Data team
12.	Repeat steps 6 to 11 if necessary	Data team
13.	Proceed to pre-load validations	Data team

Team Responsible

Transformation Rules

Rule#	Source System	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1

ECCBNKAMANDTClientS/4 HANABNKAMANDTClientCopy as-is2

ECC

BNKA

BANKS

Bank Country/Region Key

S/4 HANA

BNKA

BANKS

Bank Country/Region Key

Copy as-is from ECC

3

2

ECC

BNKA

BANKK

BANKL

Bank Keys

S/4 HANA

BNKA

BANKK

BANKL

Bank Keys

Copy as-is

45ECCBNKAERNAM_BFName of person who created the objectS/4 HANABNKAERNAM_BFName of person who created the objectCopy as-is6

from ECC

BNKAERDAT_BFRecord Created OnS/4 HANABNKAERDAT_BFRecord Created OnCopy as-is

3

ECC

BNKA

BANKA

Name of Financial Institution

S/4 HANA

BNKA

BANKA

Name of Financial Institution

Copy as-is from ECC

7

4

ECC

BNKA

REGIO

PROVZ

Region (State, Province, County)

S/4 HANA

BNKA

REGIO

PROVZ

Region (State, Province, County)

Copy as-is from ECC

8

5

ECC

BNKA

STRAS

_GP

Street and House Number

S/4 HANA

BNKA

STRAS

_GP

Street and House Number

Copy as-is from ECC

9

6

ECC

BNKA

ORT01

_GP

City

S/4 HANA

BNKA

ORT01

_GP

City

Copy as-is from ECC

10

7

ECC

BNKA

SWIFT

SWIFT-BIC for International Payments

S/4 HANA

BNKA

SWIFT

SWIFT-BIC for International Payments

Copy as-is from ECC

11

8

ECC

BNKA

BGRUP

Bank Group (bank network)

S/4 HANA

BNKA

BGRUP

Bank Group (bank network)

Copy as-is from ECC

12

9

ECC

BNKA

XPGRO

Post Office Bank Current Account Flag

S/4 HANA

BNKA

XPGRO

Post Office Bank Current Account Flag

Copy as-is from ECC

13

10

ECC

BNKA

LOEVM

Deletion Indicator

S/4 HANA

BNKA

LOEVM

Deletion Indicator

Copy as-is from ECC

14

11

ECC

BNKA

BANKL

BNKLZ

Bank

Keys

Number

S/4 HANA

BNKA

BANKL

BNKLZ

Bank Keys

Copy as-is

15ECCBNKAPSKTO_CHPost office bank current account numberS/4 HANABNKAPSKTO_CHPost office bank current account numberCopy as-is16

from ECC
12	ECC	BNKA

AD_ADDRNUM

ADRNR

Address Number

S/4 HANA

BNKA

AD_ADDRNUM

ADRNR

Address Number

Copy as-is from ECC

17

13

ECC

BNKA

BRNCH

Bank Branch

S/4 HANA

BNKA

BRNCH

Bank Branch

Copy as-is from ECC

18

14

ECC

BNKA

CHECKMETH

CHKME

Check Digit Calculation Method

S/4 HANA

BNKA

CHECKMETH

CHKME

Check Digit Calculation Method

Copy as-is from ECC

19

15

ECC

BNKA

VERS

_BF

Format of File with Bank Data

S/4 HANA

BNKA

VERS

_BF

Format of File with Bank Data

Copy as-is

20ECCBNKABNKA_SEPASEPA-relevant Local Bank NameS/4 HANABNKABNKA_SEPASEPA-relevant Local Bank NameCopy as-is21ECCBNKAIBAN_RULEIBAN RuleS/4 HANABNKAIBAN_RULEIBAN RuleCopy as-is22ECCBNKASDD_B2BSupport of SEPA B2B Direct DebitS/4 HANABNKASDD_B2BSupport of SEPA B2B Direct DebitCopy as-is23ECCBNKASDD_COR1Support of SEPA COR1 Direct DebitS/4 HANABNKASDD_COR1Support of SEPA COR1 Direct DebitCopy as-is24ECCBNKASDD_RTRANSSupport of SEPA Returned Debits
(R Transactions)S/4 HANABNKASDD_RTRANSSupport of SEPA Returned Debits (R Transactions)Copy as-is25ECCBNKABNKAAPPBank Application – Unique key for application-specific
bank attributesS/4 HANABNKABNKAAPPBank Application – Unique key for application-specific
bank attributesCopy as-is26

from ECC
16	ECC	BNKA

PRQ_

BICKY

Key of a BIC+ data record (Swift)

S/4 HANA

BNKA

PRQ_

BICKY

Key of a BIC+ data record (Swift)

Copy as-is

27ECCBNKAPRQ_RCCRouting Control CodeS/4 HANABNKAPRQ_RCCRouting Control CodeCopy as-is

from ECC

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

Pre-Load Validation

Project Team

Completeness

Task

Action

Generation of
Pre-load reports

Reconciliation of total

Record Count

Summary of Record Counts from Constructed dataset, Valid and Invalid record set.

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. Review the data report to ensure mapping value is not missing in tool. Capture errors in the Data Error report.

Business

Completeness

Task	Action
Verify record count in Pre-load reports	Ensure third party file SWIFTREF used for Bank master is up to date and it is the latest version file.

Accuracy

Task	Action

Load

The load process includes:

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

View file

name	Source data for Bank.xml
height	250

Load Run Sheet

Item

#

	Step

Description

description	Team responsible
1	Ensure the load tools are transported into the correct tool instance.	Data team
2	Ensure DCTs and all required mappings are submitted and complete	Data team
3	Ensure Pre-load sign-offs are obtained.	Data team
4	Execute tool Trial Balance Upload	Data team
5	Generate the post load reports in tool.	Data team
6	Log errors as defects, if any and address resolutions. Close defects.	Data team
7	Resolve defects by reupload and re-generate post load reports if necessary.	Data team
8	Business to validate the post load files as part of post-load validation, raise data defects or provide the post-load sign-off.	Business
9	Repeat steps 5 to 7 if necessary.	Data team

Team Responsible

Load Phase and Dependencies

Configuration

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action
Reconciliation of Record Count	Confirm all the Bank Master records listed in the Construction file (DCT )/ from the third party SWIFTREF file are loaded

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.

Any mismatch will be reported under the Post Load - Error report.

Each Column will have Source field, target field and Matching Status. ( XXXX_ECC, XXXX_S4HANA, XXXX_MATCH). A loading status field to show the record is loaded in S/4HANA. Also, a field to unmatched fields in the Post-Load file.

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 will check BNKA table using tcode SE16N.

Accuracy

Task	Action
Complete Check	Post-Load File contains matching status of each field.
Spot check

Key Assumptions

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

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Mar 24, 2026	Actor	Type	Activity	Version
Approved	GONCHIGARU-ext, Ashok	State	changed state to Approved at 1:56 pm	v33
Revision under Review	GONCHIGARU-ext, Ashok	State	gave Minor change approval at 1:56 pm Approved
Revision under Review	GONCHIGARU-ext, Ashok	State	changed state to Revision under Review at 1:55 pm	v33
Mar 18, 2026
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:44 pm	v33
From Dec 03, 2025 to Mar 03, 2026
Edited following Approval	NAIDU-ext, Prasad	Edit	updated the page at 4:08 pm
	NAIDU-ext, Prasad	Comment	commented 3:35 pm Updated

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 5

New Version Current

Key

Conversion Scope

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history