Versions Compared

Old Version 7

changes.mady.by.user NAIDU-ext, Prasad

Saved on

compared with

New Version Current

changes.mady.by.user NAIDU-ext, Prasad

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Status

Page Status

OwnerPrasad Naidu
Stakeholders

NG-ext, Bernard PILLAY-ext, Lawrence 

Purposeurpose

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 external Banks (from tables like BNKA): Used for storing details of banks globally (e.g., SWIFT, bank address, bank key).

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

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.

The data from legacy system includes:

  1. Bank Key
  2. Bank Country
  3. Bank Name
  4. Bank Address
  5. SWIFT/BIC Code
  6. Bank Number / Routing Code

The data from legacy system excludes:

  1. Bank configuration for treasury or cash management tools not in active use
  2. Bank Communication Management (BCM) configurations unless separately scoped

 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.


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

PF2
PI2Bank Master
WP2
~374000
Bank Master
S4~374000
PI2Bank Master

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements




Target Design

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement
BNKA
MANDTBNKABANKSBANKS
BANKS
MANDTClientCLNT3Mandatory
BANKS
Bank Country/Region KeyCHAR3Mandatory
BNKA
BANKK
BANKLBANKKBank KeysCHAR15
OptionalBNKAERDAT_BF
ERDAT_BFRecord Created OnDATS8
Mandatory
BNKA
ERNAM_BF
BANKABANKA
ERNAM_BF
Name of
person who created the object
Financial InstitutionCHAR
12
60Mandatory
BNKA
BANKA
PROVZ
BANKAName of Financial InstitutionCHAR60OptionalBNKAREGIOREGIO
REGIORegion (State, Province, County)CHAR3Optional
BNKASTRAS
_GP
STRAS_GPStreet and House NumberCHAR35Optional
BNKAORT01
_GP
ORT01_GPCityCHAR35Optional
BNKASWIFTSWIFTSWIFT-BIC for International PaymentsCHAR11Optional
BNKABGRUPBGRUPBank Group (bank network)CHAR2Optional
BNKAXPGROXPGROPost Office Bank Current Account FlagCHAR1Optional
BNKALOEVMLOEVMDeletion IndicatorCHAR1Optional
BNKA
BANKL
BNKLZBANKLBank
Keys
NumberCHAR15
OptionalBNKAAD_ADDRNUM
Mandatory
BNKA
PSKTO_CHPSKTO_CHPost office bank current account numberCHAR16Optional
ADRNRAD_ADDRNUMAddress NumberCHAR10Optional
BNKABRNCHBRNCHBank BranchCHAR40Optional
BNKA
CHECKMETH
CHKMECHECKMETHCheck Digit Calculation MethodCHAR4Optional
BNKAVERS
_BF
VERS_BFFormat of File with Bank DataCHAR3Optional
BNKA
BNKA_SEPA
BICKY
BNKA
PRQ_
SEPASEPA-relevant Local Bank Name
BICKYKey of a BIC+ data record (Swift)CHAR
60
12Optional
BNKAIBAN_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 attributesCHAROptionalBNKAPRQ_BICKYPRQ_BICKYKey of a BIC+ data record (Swift)CHAR12OptionalBNKAPRQ_RCCPRQ_RCCRouting Control CodeCHAR15Optional

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

Cleansing is not applicable if the bank master file is procured from the third-party SWIFTREF and no legacy bank master needs to be migrated.

Conversion Process

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

Image Removed

Data Privacy and Sensitivity

Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 ; 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 . 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 DescriptionTeam Responsible

Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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


Data Cleansing

NA

Conversion Process

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

Image Added

Data Privacy and Sensitivity


Extraction

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

  1. The data exists. connects to the source and loads the data into . 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 ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.

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

NA










Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set





















Data Collection Template (DCT)

No DCT for this object


Extraction Dependencies

Item #Step DescriptionTeam 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:

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


Transformation Rules


Rule#Source
System		Source
Table		Source FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ECCBNKABANKSBank Country/Region KeyS/4 HANABNKABANKSBank Country/Region KeyCopy as-is from ECC
2ECCBNKABANKLBank KeysS/4 HANABNKABANKLBank KeysCopy as-is from ECC
3ECCBNKABANKAName of Financial InstitutionS/4 HANABNKABANKAName of Financial InstitutionCopy as-is from ECC
4ECCBNKAPROVZRegion (State, Province, County)S/4 HANABNKAPROVZRegion (State, Province, County)Copy as-is from ECC
5ECCBNKASTRASStreet and House NumberS/4 HANABNKASTRASStreet and House NumberCopy as-is from ECC
6ECCBNKAORT01CityS/4 HANABNKAORT01CityCopy as-is from ECC
7ECCBNKASWIFTSWIFT-BIC for International PaymentsS/4 HANABNKASWIFTSWIFT-BIC for International PaymentsCopy as-is from ECC
8ECCBNKABGRUPBank Group (bank network)S/4 HANABNKABGRUPBank Group (bank network)Copy as-is from ECC
9ECCBNKAXPGROPost Office Bank Current Account FlagS/4 HANABNKAXPGROPost Office Bank Current Account FlagCopy as-is from ECC
10ECCBNKALOEVMDeletion IndicatorS/4 HANABNKALOEVMDeletion IndicatorCopy as-is from ECC
11ECCBNKABNKLZBank NumberS/4 HANABNKABNKLZBank KeysCopy as-is from ECC
12ECCBNKAADRNRAddress NumberS/4 HANABNKAADRNRAddress NumberCopy as-is from ECC
13ECCBNKABRNCHBank BranchS/4 HANABNKABRNCHBank BranchCopy as-is from ECC
14ECCBNKACHKMECheck Digit Calculation MethodS/4 HANABNKACHKMECheck Digit Calculation MethodCopy as-is from ECC
15ECCBNKAVERSFormat of File with Bank DataS/4 HANABNKAVERSFormat of File with Bank DataCopy as-is from ECC
16ECCBNKA

Extraction Dependencies

Item #Step DescriptionTeam Responsible

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:

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

Data team

2.      

In tool, select the Object Cost Centre

Data team

3.      

Go to Process Area Launch and Process the Object - Cost Centre - Cost Centre

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

Transformation Rules

Rule#Source
System		Source
Table		Source FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1ECCBNKAMANDTClientS/4 HANABNKAMANDTClientCopy as-is
2ECCBNKABANKSBank Country/Region KeyS/4 HANABNKABANKSBank Country/Region KeyCopy as-is
3ECCBNKABANKKBank KeysS/4 HANABNKABANKKBank KeysCopy as-is
4ECCBNKAERDAT_BFRecord Created OnS/4 HANABNKAERDAT_BFRecord Created OnCopy as-is
5ECCBNKAERNAM_BFName of person who created the objectS/4 HANABNKAERNAM_BFName of person who created the objectCopy as-is
6ECCBNKABANKAName of Financial InstitutionS/4 HANABNKABANKAName of Financial InstitutionCopy as-is
7ECCBNKAREGIORegion (State, Province, County)S/4 HANABNKAREGIORegion (State, Province, County)Copy as-is
8ECCBNKASTRAS_GPStreet and House NumberS/4 HANABNKASTRAS_GPStreet and House NumberCopy as-is
9ECCBNKAORT01_GPCityS/4 HANABNKAORT01_GPCityCopy as-is
10ECCBNKASWIFTSWIFT-BIC for International PaymentsS/4 HANABNKASWIFTSWIFT-BIC for International PaymentsCopy as-is
11ECCBNKABGRUPBank Group (bank network)S/4 HANABNKABGRUPBank Group (bank network)Copy as-is
12ECCBNKAXPGROPost Office Bank Current Account FlagS/4 HANABNKAXPGROPost Office Bank Current Account FlagCopy as-is
13ECCBNKALOEVMDeletion IndicatorS/4 HANABNKALOEVMDeletion IndicatorCopy as-is
14ECCBNKABANKLBank KeysS/4 HANABNKABANKLBank KeysCopy as-is
15ECCBNKAPSKTO_CHPost office bank current account numberS/4 HANABNKAPSKTO_CHPost office bank current account numberCopy as-is
16ECCBNKAAD_ADDRNUMAddress NumberS/4 HANABNKAAD_ADDRNUMAddress NumberCopy as-is
17ECCBNKABRNCHBank BranchS/4 HANABNKABRNCHBank BranchCopy as-is
18ECCBNKACHECKMETHCheck Digit Calculation MethodS/4 HANABNKACHECKMETHCheck Digit Calculation MethodCopy as-is
19ECCBNKAVERS_BFFormat of File with Bank DataS/4 HANABNKAVERS_BFFormat of File with Bank DataCopy as-is
20ECCBNKABNKA_SEPASEPA-relevant Local Bank NameS/4 HANABNKABNKA_SEPASEPA-relevant Local Bank NameCopy as-is
21ECCBNKAIBAN_RULEIBAN RuleS/4 HANABNKAIBAN_RULEIBAN RuleCopy as-is
22ECCBNKASDD_B2BSupport of SEPA B2B Direct DebitS/4 HANABNKASDD_B2BSupport of SEPA B2B Direct DebitCopy as-is
23ECCBNKASDD_COR1Support of SEPA COR1 Direct DebitS/4 HANABNKASDD_COR1Support of SEPA COR1 Direct DebitCopy as-is
24ECCBNKASDD_RTRANSSupport of SEPA Returned Debits
(R Transactions)		S/4 HANABNKASDD_RTRANSSupport of SEPA Returned Debits (R Transactions)Copy as-is
25ECCBNKABNKAAPPBank Application – Unique key for application-specific
 bank attributes		S/4 HANABNKABNKAAPPBank Application – Unique key for application-specific
 bank attributes		Copy as-is
26ECCBNKAPRQ_BICKYKey of a BIC+ data record (Swift)S/4 HANABNKAPRQ_BICKYKey of a BIC+ data record (Swift)Copy as-is27ECCBNKAPRQ_RCCRouting Control CodeS/4 HANABNKAPRQ_RCCRouting Control CodeCopy as-is from ECC


Transformation Mapping

Mapping Table NameMapping Table Description








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

Completeness

TaskAction
Generation of
Pre-load reports
Reconciliation of total

Record Count

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

Accuracy

TaskAction

set.




Accuracy

TaskAction
Mandatory field mapping and transformationObtain 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

TaskAction
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

TaskAction





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

View file
nameSource data for Bank.xml
height250

Load Run Sheet

Item

Step 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


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 TypeError DescriptionAction Taken










Post-Load Validation

Project Team

Completeness

TaskAction
Reconciliation of Record CountConfirm all the  Bank Master records listed in the Construction file (DCT )/ from the third party SWIFTREF file are loaded





Accuracy

TaskAction
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

TaskAction
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

TaskAction
Complete CheckPost-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.


See also

Change log

Change History
limit10

Workflow history

Workflow Report
parent@self
hideheadertrue
typeapprovals