| Status | Approved |
|---|---|
| Owner | Prasad Naidu |
| Stakeholders |
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 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.
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
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Bank Master | |||
| WP2 | Bank Master | |||
| PI2 | 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.
Table | Field | Data Element | Field Description | Data Type | Length | Requirement |
BNKA | BANKS | BANKS | Bank Country Key | CHAR | 3 | Required |
BNKA | BANKL | BANKL | Bank Key | CHAR | 15 | Required |
BNKA | BANKA | BANKA | Bank Name | CHAR | 60 | Optional |
BNKA | BANKN | BANKN | Bank Account Number | CHAR | 35 | Optional |
BNKA | BANKL_OLD | BANKL_OLD | Old Bank Key | CHAR | 15 | Optional |
BNKA | BRNCH | BRNCH | Branch Number | CHAR | 15 | Optional |
BNKA | SWIFT | SWIFT | SWIFT Code | CHAR | 11 | Optional |
BNKA | CITY | ORT01 | Bank City | CHAR | 35 | Optional |
BNKA | STREET | STRAS | Street | CHAR | 60 | Optional |
BNKA | COUNTRY | LAND1 | Country | CHAR | 3 | Optional |
BNKA | REGIO | REGIO | Region (State, Province, County) | CHAR | 3 | Optional |
BNKA | BANKT | BANKT | Bank Type | CHAR | 1 | Optional |
BNKA | MCOD1 | MCOD1 | Search Term | CHAR | 25 | Optional |
BNKA | DATLZ | DATLZ | Date of Last Change | DATS | 8 | Optional |
BNKA | TIMEZ | TIMEZ | Time of Last Change | TIMS | 6 | Optional |
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,PI11 |
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:
- Perform full data extraction from relevant tables in the source system(s).
- Perform extraction through the application layer.
- 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). 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 Description | Team Responsible |
|---|---|---|
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 Name | Field Description | Rule |
|---|---|---|
Extraction Dependencies
| Item # | Step Description | Team 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:
- Perform value mapping and data transformation rules.
- Legacy values are mapped to the to-be values (this could include a default value)
- 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 | Team Responsible |
|---|---|---|
Transformation Rules
| Rule# | Source System | Source Table | Source Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
| 1 | ECC | BNKA | BANKS | Bank Country Key | S/4 HANA | BNKA | BANKS | Bank Country Key | Copy as-is |
| 2 | ECC | BNKA | BANKL | Bank Key | S/4 HANA | BNKA | BANKL | Bank Key | Copy as-is |
| 3 | ECC | BNKA | BANKA | Bank Name | S/4 HANA | BNKA | BANKA | Bank Name | Copy as-is |
| 4 | ECC | BNKA | BANKN | Bank Account Number | S/4 HANA | BNKA | BANKN | Bank Account Number | Copy as-is |
| 5 | ECC | BNKA | BANKL_OLD | Old Bank Key | S/4 HANA | BNKA | BANKL_OLD | Old Bank Key | Copy as-is |
| 6 | ECC | BNKA | BRNCH | Branch Number | S/4 HANA | BNKA | BRNCH | Branch Number | Copy as-is |
| 7 | ECC | BNKA | SWIFT | SWIFT Code | S/4 HANA | BNKA | SWIFT | SWIFT Code | Copy as-is |
| 8 | ECC | BNKA | CITY | Bank City | S/4 HANA | BNKA | CITY | Bank City | Copy as-is |
| 9 | ECC | BNKA | STREET | Street | S/4 HANA | BNKA | STREET | Street | Copy as-is |
| 10 | ECC | BNKA | COUNTRY | Country | S/4 HANA | BNKA | COUNTRY | Country | Copy as-is |
| 11 | ECC | BNKA | REGIO | Region (State, Province, County) | S/4 HANA | BNKA | REGIO | Region (State, Province, County) | Copy as-is |
| 12 | ECC | BNKA | BANKT | Bank Type | S/4 HANA | BNKA | BANKT | Bank Type | Copy as-is |
| 13 | ECC | BNKA | MCOD1 | Search Term | S/4 HANA | BNKA | MCOD1 | Search Term | Copy as-is |
| 14 | ECC | BNKA | DATLZ | Date of Last Change | S/4 HANA | BNKA | DATLZ | Date of Last Change | Copy as-is |
| 15 | ECC | BNKA | TIMEZ | Time of Last Change | S/4 HANA | BNKA | TIMEZ | Time of Last Change | Copy as-is |
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 |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
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
Load Run Sheet
| Item # | Step Description | 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 |
|---|---|
Accuracy
| Task | Action |
|---|---|
Business
Completeness
| Task | Action |
|---|---|
Accuracy
| Task | Action |
|---|---|
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
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||