| 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 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 and post go-live, the bank master data will be maintained by loading delta changes on a monthly basis.
Conversion Scope
We have 3 options available for creating bank master. Once the decision is finalized the CS will be updated accordingly.
1) Load from a 3rd-party file (to be done by functional, not confirmed at this point).
2) Data migration from ECC clients to S4 ( As discussed in yesterday’s team meeting, and as Lawrence suggested in team meeting on 16/09), let’s proceed with option 2. This may change later
3) Load from a 3rd-party file along with a delta file containing new entries.
SWIFTRef is a centralized global reference database provided by SWIFT that contains detailed bank information.
The data from SWIFTREF file includes:
- Bank Key
- Bank Country
- Bank Name
- Bank Address
- SWIFT/BIC Code
- Bank Number / Routing Code
Relevancy Criteria:
1) All Bank keys in BNKA table are in scope from both WP2 and PF2
2) If there are any duplicate keys in source systems, Combine both records from WP2 and PF2 and select the Max value.
3) Business is responsible for Data cleansing.
| Source | Scope | Source Approx No. of Records | Target System | Target Approx No. of Records |
|---|---|---|---|---|
| PF2 | Bank Master | 374000 | S4 | 374000 |
| WP2 | Bank Master | 292000 | S4 | 292000 |
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/Region Key | CHAR | 3 | Mandatory |
| BNKA | BANKL | BANKK | Bank Keys | CHAR | 15 | Mandatory |
| BNKA | BANKA | BANKA | Name of Financial Institution | CHAR | 60 | Mandatory |
| BNKA | PROVZ | REGIO | Region (State, Province, County) | CHAR | 3 | Optional |
| BNKA | STRAS | STRAS_GP | Street and House Number | CHAR | 35 | Optional |
| BNKA | ORT01 | 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 | BNKLZ | BANKL | Bank Number | CHAR | 15 | Mandatory |
| BNKA | PSKTO | PSKTO_CH | Post office bank current account number | CHAR | 16 | Optional |
| BNKA | ADRNR | AD_ADDRNUM | Address Number | CHAR | 10 | Optional |
| BNKA | BRNCH | BRNCH | Bank Branch | CHAR | 40 | Optional |
| BNKA | CHKME | CHECKMETH | Check Digit Calculation Method | CHAR | 4 | Optional |
| BNKA | VERS | VERS_BF | Format of File with Bank Data | CHAR | 3 | Optional |
| BNKA | IBAN_RULE | IBAN_RULE | IBAN Rule | CHAR | Optional | |
| BNKA | SDD_B2B | SDD_B2B | Support of SEPA B2B Direct Debit | CHAR | 1 | Optional |
| BNKA | SDD_COR1 | SDD_COR1 | Support of SEPA COR1 Direct Debit | CHAR | 1 | Optional |
| BNKA | SDD_RTRANS | SDD_RTRANS | Support of SEPA Returned Debits (R Transactions) | CHAR | 1 | Optional |
| BNKA | BICKY | PRQ_BICKY | Key of a BIC+ data record (Swift) | CHAR | 12 | Optional |
| BNKA | RCCODE | PRQ_RCC | Routing Control Code | CHAR | 15 | Optional |
Data Cleansing
No data cleansing is required if the Bank Master is purchased from a third party SWIFTRef however, If the data from ECC to S4 is migrated, the following cleansing criteria should be applied. This cleaning should be performed by business/Cleansing team
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 |
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 |
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 |
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 |
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 |
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 |
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:
Data Privacy and Sensitivity
Extraction
Extract data from SWIFTRef file (File will be provided by Business) and Load SWIFTRef file into Syniti Staging Database and Define Source Object in Syniti for SWIFTRef Bank Data and Run initial profiling to check data completeness (missing BIC, invalid country codes, duplicates)
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.| Field Name | Field description | Rule |
| BNKA-BANKS | Bank Country | Business will provide the content |
| BNKA-BANKL | Bank Key | Business will provide the content |
| BNKA-BANKA | Bank name | Business will provide the content |
| BNKA-SWIFT | SWIFT code | Business will provide the content |
| BNKA-PROVZ | Region | Business will provide the content |
| BNKA-STRAS | Street | Business will provide the content |
| BNKA-ORT01 | City | Business will provide the content |
| BNKA-BRNCH | Bank Branch | Business will provide the content |
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.
- 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 |
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 Field | Source Description | Target System | Target Table | Target Field | Target Description | Transformation Logic |
| 1 | ECC / SWIFTREF | BNKA | BANKS | Bank Country/Region Key | S/4 HANA | BNKA | BANKS | Bank Country/Region Key | Copy as-is from ECC |
| 2 | ECC / SWIFTREF | BNKA | BANKL | Bank Keys | S/4 HANA | BNKA | BANKL | Bank Keys | Copy as-is from ECC |
| 3 | ECC / SWIFTREF | BNKA | BANKA | Name of Financial Institution | S/4 HANA | BNKA | BANKA | Name of Financial Institution | Copy as-is from ECC |
| 4 | ECC / SWIFTREF | BNKA | PROVZ | Region (State, Province, County) | S/4 HANA | BNKA | PROVZ | Region (State, Province, County) | Copy as-is from ECC |
| 5 | 7ECC / SWIFTREF | BNKA | STRAS | Street and House Number | S/4 HANA | BNKA | STRAS | Street and House Number | Copy as-is from ECC |
| 6 | ECC / SWIFTREF | BNKA | ORT01 | City | S/4 HANA | BNKA | ORT01 | City | Copy as-is from ECC |
| 7 | ECC / SWIFTREF | BNKA | SWIFT | SWIFT-BIC for International Payments | S/4 HANA | BNKA | SWIFT | SWIFT-BIC for International Payments | Copy as-is from ECC |
| 8 | ECC / SWIFTREF | BNKA | BGRUP | Bank Group (bank network) | S/4 HANA | BNKA | BGRUP | Bank Group (bank network) | Copy as-is from ECC |
| 9 | ECC / SWIFTREF | BNKA | XPGRO | Post Office Bank Current Account Flag | S/4 HANA | BNKA | XPGRO | Post Office Bank Current Account Flag | Copy as-is from ECC |
| 10 | ECC / SWIFTREF | BNKA | LOEVM | Deletion Indicator | S/4 HANA | BNKA | LOEVM | Deletion Indicator | Copy as-is from ECC |
| 11 | ECC / SWIFTREF | BNKA | BNKLZ | Bank Number | S/4 HANA | BNKA | BNKLZ | Bank Keys | Copy as-is from ECC |
| 12 | ECC / SWIFTREF | BNKA | PSKTO | Post office bank current account number | S/4 HANA | BNKA | PSKTO | Post office bank current account number | Copy as-is from ECC |
| 13 | ECC / SWIFTREF | BNKA | ADRNR | Address Number | S/4 HANA | BNKA | ADRNR | Address Number | Copy as-is from ECC |
| 14 | ECC / SWIFTREF | BNKA | BRNCH | Bank Branch | S/4 HANA | BNKA | BRNCH | Bank Branch | Copy as-is from ECC |
| 15 | ECC / SWIFTREF | BNKA | CHKME | Check Digit Calculation Method | S/4 HANA | BNKA | CHKME | Check Digit Calculation Method | Copy as-is from ECC |
| 16 | ECC / SWIFTREF | BNKA | VERS | Format of File with Bank Data | S/4 HANA | BNKA | VERS | Format of File with Bank Data | Copy as-is from ECC |
| 17 | ECC / SWIFTREF | BNKA | IBAN_RULE | IBAN Rule | S/4 HANA | BNKA | IBAN_RULE | IBAN Rule | Copy as-is from ECC |
| 18 | ECC / SWIFTREF | BNKA | SDD_B2B | Support of SEPA B2B Direct Debit | S/4 HANA | BNKA | SDD_B2B | Support of SEPA B2B Direct Debit | Copy as-is from ECC |
| 19 | ECC / SWIFTREF | BNKA | SDD_COR1 | Support of SEPA COR1 Direct Debit | S/4 HANA | BNKA | SDD_COR1 | Support of SEPA COR1 Direct Debit | Copy as-is from ECC |
| 20 | ECC / SWIFTREF | BNKA | SDD_RTRANS | Support of SEPA Returned Debits (R Transactions) | S/4 HANA | BNKA | SDD_RTRANS | Support of SEPA Returned Debits (R Transactions) | Copy as-is from ECC |
| 21 | ECC / SWIFTREF | BNKA | BICKY | Key of a BIC+ data record (Swift) | S/4 HANA | BNKA | BICKY | Key of a BIC+ data record (Swift) | Copy as-is from ECC |
| 22 | ECC / SWIFTREF | BNKA | RCCODE | Routing Control Code | S/4 HANA | BNKA | RCCODE | Routing Control Code | Copy 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
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 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.
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||