In a SAP implementation, there can be scores of Bank Master data which needs to be created in SAP from the existing legacy system. Moreover, going forward, Bank Master will get created on an ad-hoc basis depending on the creation of new bank entities in the specific geography.
The transaction code for creating a Bank Master in SAP is ‘FI01’(individually) and ‘BAUP’(mass).
The most common approach followed for the creation of Bank Master in SAP during implementation phase is through the use of a data migration tool, ‘LSMW’ (Legacy System Migration Workbench), wherein based on the recording of the transaction ‘FI01’ for a single record, a file containing the full list of Bank Masters along with the relevant fields is uploaded into SAP system, which in turn reads the file and creates the Bank Masters in the system, or using the transaction ‘BAUP’ where in bank masters can be uploaded in to SAP from a flat file depending on the file format assigned against the Business Transaction event for bank data transfer.
However, there are risks associated with these process as the file containing the list of bank master may get corrupted and the system is unable to read the file.
A more sophisticated and clean approach would be to use the ‘IDOCs’ functionality to transfer the Bank Masters from one SAP system to another. The major advantage of following this process is that it reduces the uncertainty around the creation of bank masters in SAP to a great extent. Once the connection is set up between two systems, the transferring can be done as much number of times.
SAP transaction ‘FI08’ is used for the transmission of bank master data in the form of IDOCs from a source SAP System to a given receiver SAP system, provided a RFC connection is set up within the two systems along with some basic ALE configuration
Advantages of FI08
(a) Management of the Bank Master will be user-independent and will be controlled by SAP.
(b) Transferring the Bank Master through IDOCs across SAP system is a much more secure way than uploading the same through a flat file or creating it individually.
(c) Once the connection is set up, the Bank master are transferred automatically to the receiver SAP system once they are created in the source SAP system either individually or in mass.
Step by Step Procedure for using FI08
There are certain pre-requisites which needs to be completed, before executing the transaction ‘FI08’. These pre-requisites are explained in detail as steps in the pages to follow.
Managing/Transferring the Bank Master Data across SAP systems
(a) The Source and target SAP systems have already been created.
(b) The Bank Masters in Source and Target Systems are not in Sync.
The country specific checks under the following configuration node in the Source System and the Target System should be in sync.
SAP Customizing Implementation Guide —-> SAP Net Weaver —-> General Settings —-> Set Countries —-> Set Country-Specific Checks
Source System-‘ID2’ Client 100
Target System-‘IST’ Client 100
Here, the value of the bank key for the specific country across SAP system should be same.
In brief, the steps are as follows-
||Description||SAP Transaction Code|
|1||Configuration and Checking of RFC Connections||SM59|
|2||Configuration of t-RFC port||WE21|
|3||Creation of Source & Target System as Logical Systems||BD54|
|4||Configuration of Distribution Model||BD64|
|5||Generate Partner Profiles in Source Systems||BD82|
|6||Configuration of Partner Profile in Source & Target Systems||WE20|
|7||Define Consolidation System for Bank Data Distribution||SPRO|
Step-1- Configurations and checking of RFC Connection
Source System-‘ID2’ Client 100
Target System-‘IST’ Client 100
Log in to the Source System (ID2) and go to Transaction Code ‘SM59’
Select the “ABAP Connections” and click on “Create” Icon.
The following values needs to be filled in-
|RFC Destination||IST100||Target System|
|Description 1||RFC Destination for IST 100||—-|
|Target Host||AB14.abcloud14.int||Target System Server Details|
|System Number||14||Target System’s Number|
Note-The values used are specific to the Target system used in here.It will be different for different for different systems.
Once the values are filled in, click on the ‘Logon &Security’ tab to set up the ‘User’ and ‘Password’ for the same.The ‘User’ should be a ‘Communication user’ and should exists in the Target System as well.
Once the details are entered, press “Save” so that the RFC destination is saved.
Now ,click on the “Connection Test” button to test the connection from ID2 to IST. For successful connection between the two systems, the following screen should appear.
If the above screen is not coming, then some error has happened in the configuration and it is better to contact the SAP BASIS team for the rectification of the same.
Step-2- Configurations of t-RFC port
In the Source System (ID2), go to Transaction Code ‘WE21’. Select the ‘Transactional RFC’ folder and Click on the Create Icon.
On clicking the create icon, a Pop-up comes asking for a port name
Select the ‘Own Port Name’ option and give name as ‘IST-100’ and press enter.
Choose ‘RFC destination’ as ‘IST-100’ from the drop down and ‘Version’ as ‘IDoc record Types SAP Release 4.x’.
Press “Save” to save the port details.
Step-3- Creation of Source & Target Systems as Logical Systems
For configuring the Partner Profile in the Source System, the ‘Target System’ has to be defined as a logical system.
In the Source System (ID2-100), go to Transaction Code ‘BD54’ and click on New Entries .
Maintain the Target System (IST-100) and press “Save” to save the details.
For configuring the Partner Profile in the Target System, the ‘Source System’ has to be defined as a logical system.
In the Target System (IST-100), go to Transaction Code ‘BD54’ and click on New Entries.
Maintain the Target System (ID2-100) and press “Save” to save the details.
Step-4- Configuration of Distribution Model
In the Source System (ID2-100) go to Transaction Code ‘BD64’. Click on Change icon to go to the ‘Change Distribution Model’ view and click on the ‘Create Model View’ icon.
A new screen pops-up and the following details are to be entered as shown in the figure
After the ‘Distribution Model’ is created, the message type needs to be added to the same.
Click on the ‘Add BAPI’ icon.
A new screen pops-up, and the following values needs to be filled in for each of the object one after another by clicking on the ‘Add BAPI’ icon.
For Bank Master Creation
For Changing Bank Master
For Address Org
Press enter and the following distribution model appears.
Step-5- Generate Partner Profiles in Source System
In the Source System (ID2-100), go to transaction Code ‘BD82’ and give the following parameters and execute.
Model View-Created in Step 3 (in this scenario, BNKA)
Partner System-Target System (In this Scenario, IST-100)
Authorized User-Type-US and ID-SAP User ID
On execution, the following log should appear as a confirmation that the Partner profile has been successfully generated in the Source System.
Step-6- Configurations of Partner Profiles in Source & Target Systems
For Configuring the partner profile in Source System, go to Transaction Code ‘WE20’ in the Source System (ID2).
Select the ‘Partner Type LS’ folder and select the Target System.
The message type related to the Bank master Save Replica, i.e-‘BANK_SAVEREPLICA’ needs to be maintained in the ‘Outbound Parameters’ Section, as the Bank Master created in the Source System will be moving automatically to the Target Systems.
Click on the “Add” icon for adding the ‘Outbound parameter’. A new screen opens up and following values needs to be feed in the screen-
|Output Mode||Transfer IDOC Immediately|
|IDOC Type (Basic Type)||BANK_SAVEREPLICA01|
Press to save the ‘Outbound parameters’ and the Partner profile.
For Configuring the partner profile in Target System, go to Transaction Code ‘WE20’ in the Target System (IST-100).
Select the ‘Partner Type LS’ folder and and select the Source System
The message type related to the Bank master Save Replica, i.e-‘BANK_SAVEREPLICA’ needs to be maintained in the ‘Inbound Parameters’ Section., as the Bank Master created in the Source System will be moving automatically to the Target Systems.
Click on the “Add” icon for adding the ‘Inbound parameters’.A new screen opens up and following values needs to be feed in the screen-
|Processing by Function Module||Trigger Immediately|
Press “Save” to save the ‘Inbound parameters’ and the Partner profile.
Step-7- Define Consolidation System for Bank Data Distribution
The significance of the Consolidation System is that if you do not enter a consolidation system, or you enter more than one, the banks are not distributed, they are only saved locally.
Go to the following configuration node in the Source System.
SAP Customizing Implementation Guide —-> Cross-Application Components—–> Bank Directory—-> Distribution of Banks—->Make Settings for Distributing Bank Master Data.
Select “Define Consolidation System for Bank Data Distribution” and maintain the Target System as the Consolidation System and press “Save” to save.
On execution, the transaction ‘FI08’ works in the following manner-
(a) If the Bank master does not yet exist in the target system but exists in the source System, it is newly created in the Target System.
(b) If the Bank master exists both in the Source as well as in the target system, then only the changed data (if any) is updated in the Target System.
(c) If the Bank master exists only in the target system and not in the source system, then it remains unchanged.
Go to Transaction code ‘FI08’ in Source System (ID2-100) and enter the following details as given-
Bank Country-Select the Country for which you want to perform the transfer.
Bank Key-Here you can give the specific bank key(s), or you can give *. This means all the Bank Keys under the specific country will be selected for transfer.
Receiving System– Target System
If you execute the transaction, with the“Test run” field as ticked, then it will not transfer the Bank master, but will only display a list of bank masters which would possibly get transferred.
On executing the transaction with un-ticking the ‘Test Run’, the transfer of Bank Master takes place from the Source System to the Target System and list gets displayed of the Bank masters that were sent.
Status Check of IDOCS
To check the status of the IDOCs, go to transaction code “BD87” in the Source System and enter the following details as shown and click on “Execute“
The IDOCs Status ‘03’ indicates that the IDOCs has been processed successfully and is sent to the Target System
To check the status of the IDOCS in the Target System (IST-100), Go to Transaction Code ‘BD87’ and the enter the following details as shown and click on ‘Execute’
The IDOC Status ‘53’, indicates that the IDOC has been received successfully in the Target System and the Bank Master has been created in IST-100 system.
Note- Step 1 to Step 7 mentioned above needs to be done only once for a given Source System and given Receiver System.
Transaction FI08 bridges the gap between the bank master data across SAP systems which were created in the Source System only and does not exists in Target System.
However, after the configuration step(s) that have been mentioned above are executed successfully, you don’t have to run FI08 for managing the Bank master. It would automatically get created in the Target System, once you create the same in the Source System
List of Transactions for transferring other SAP Business Objects
Apart from the Bank master, there are other SAP objects which can be transferred using the IDOC functionality from the Source system to a receiver system.The only difference would be in the IDOC message types for each of these SAP objects.
Here is a consolidated list of the transaction codes which can be used along with their purposes.
|BD16||Send Cost Center|
|BD18||Send G/L Accounts|
|BD24||Send Cost Elements|
|BD25||Send Activity Type|
|BD27||Send Cost Center activity Prices|
|BD28||Send Obj\Cost Element Control data|
- SAP Community Network Wiki – Code Gallery – T-codes for Data Distribution across clients
- FI08 : Distribution of bank master data
- ALE – tcode to transfer BANK KEY from source to target system.