Richard Matti, Director of Program Management EMEA at OpenText, took a few minutes during the SAP Conference for Utilities in Copenhagen to describe how OpenText -- with more than 20 years of experience as an SAP partner -- is bringing value to SAP customers. .

To see this product in action, you can find a video of this product.

After a terrific 9th International SAP Conference for Utilites, Dr. Stefan Engelhardt (Head of IBU Utilities) wants to say thank you to all attendees making this event a great success.

Take the chance and listen to his thank you words.

Looking forward to seeing you in two years latest.

Denis Maia, CEO of Choice Energy Intelligence, an SAP partner, describes their offering focused on analytics offerings coupled with SAP HANA to address big data. As is the first SAP utilities partner certified for SAP HANA, Choice, is bringing new benefits to customers. The product is called "Revenue Intelligence Portolio 1.O Energy-Theft Detection Solution. Read more.

Choice was named a finalist in 2013 SAP Pinacle award in the Database and Technology / SAP HANA Application Innovator of the Year category. Read more.

International SAP Conference for Utilities 2013 in Copenhagen, Denmark

Our 9th International SAP Conference for Utilities took place on April 17-19 in the Bella Center in Copenhagen, Denmark.

More than 800 attendees represented over 200 different utilities from over 50 countries. 200 partners attended the conference and 25 of them ran an exhibition.

Our fully-packed agenda offered opportunities to everyone to deep dive in their topic of interest. The conference consisted of 14 pre-conference workshops, 7 keynotes, 28 sessions, 2 panel discussions and 9 roundtable discussions, as well as partner and SAP demo pods.

Here are some videos, recorded at the venue. More will follow soon:

• Choice: Firster partner who got the certification for HANA in Utilities
• SAP Document Presentment by OpenText
• Explore our new SAP Utilities Customer Energy Engagement App
• Basis Technologies talks about predictive analytics

Please have also a look at Stefan Engelhardt´s thank you video:

Thanks to all who joined us in Copenhagen!

2013-04-25

In this short video, recorded at the 9th International SAP Conference for Utilities in Copenhagen, Zarko Sumic from Gartner, discusses some of the common business and IT challenges utilities companies face today.

He talks about the role information technology plays in enabling business transformation and how important it is to select the right partners.

Learning from the other´s mistakes and also from their success is very helpful in these economical challenging times.

In this video Axel Memminger, Solution Manager for the Industry Business Solution Utilities, explains the advantages and capabilities of SAP HANA for Utilities and what this means for our customers.

He talks about the capability to run processes, transactions and analytics in almost real-time. Learn how a financial department can save costs and time if they run their ERP system on SAP HANA.

For more information on SAP HANA, see www.saphana.com.

Jürgen Kuhmann from the SAP Utilities Solution Management Team explains what our customers can do with the new "SAP Utlities Customer Energy Engagement" app and why utilities should take a look at it. The app, which he demonstrates using his smartphone, manages all aspects of the customer´s utility account.

Please have also a look at this great demo video or get more info at www.sap.com.

Read the latest press release here.

At the 9th International SAP Conference in Copenhagen, SAP announced the "Utility of Tomorrow" contest.

The goal of the contest is to promote, accelerate and share transformative and innovative ideas with utility companies. The contest is focused on creating a connected, interactive and engaging customer experience.

It aims at enabling university students from around the world to engage directly with leading utility companies to transform the utility customer experience.

Winners will participate in a workshop to further develop their ideas, to be held in Silicon Valley with experts from participating utilities and SAP. Finalists will also have the opportunity to present their ideas at SAP TechEd Las Vegas, being held October 21–25, 2013.

Read more about the contest >>LINK to SAP Newsroom

For more information, see press release >>metering.com

Rob Schilling, CEO of Space-Time Insight, a Real-Time Visual Analytics company and SAP partner that's expanding into Europe talks about how his company brings mutiple data sets together in real-time or near real-time. They make sense of that data and bring insight on top of big data. 

For more information, see >>www.saphana.com

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.

Situation

Managing/Transferring the Bank Master Data across SAP systems

Assumptions

     (a) The Source and target SAP systems have already been created.

     (b) The Bank Masters in Source and Target Systems are not in Sync.

Pre-requisites

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-

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-

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.

  (a) Bank.Create

  (b) Bank.Change

  (c) AddessOrg.Savereplica

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-

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-

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.

Execution-FI08

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.

Related Contents

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

Hello,

I would like to share this information.

How to attach a file in a device.

There are below ways for the same:-

Process A)

1) Open IQ02

2) Goto System tab in header--> Services for Object--> select the "Device " object type--> then see the first "CREATE Button" click the small Icon beside the BLANK page icon in this button--> and select "Create Attachment". You can directly browse to the file and complete the attachment.

The attached file can be seen after attachment steps are done with the button " Attachment List" which appears besides the create attachment button.

Process B)

1) Goto IQ02- change device mode

2) Below Serial Number there is one field called " Description", click "Intern Note" button.

3) Here you can directly type the details, Or can Copy/Paste

4) Or go to Tab TEXT--> Upload

5) Or try tab INSERT--> Text/ Clipborad/ Graphics.

6) Uploading scanned document/Image-->In INSERT--> Graphics, select--> option " Stored on document server", select image type as black/white OR Color bitmap. Browse for the file stored on your server, and complete the upload process.

Option 6- for Image upload.

Hope this is helpful for friends; who might need this in future.

Regards

Sachin

Solution Manager Axel Memminger discusses the market opportunity for customers using SAP analytics capabilities.

In this video you can learn how you can get value out of speed by reducing the time for transactions from several hours to minutes. With SAP HANA you wil be capable to send out collection letters, bills and financial statements much quicker. And there are many other areas e.g. the auditing area where saving time means saving money.

For more information, see >>www.saphana.com

In this short video interview, recorded at the 9th International SAP Conference for Utilities, Craig Oliver, SAP Partner from Basis Technologies, discusses what his company is doing to help provide utiltiies customers with predictive analytics, and the benefits they can gain.

After a terrific 9th International SAP Conference for Utilites, Dr. Stefan Engelhardt (Head of IBU Utilities) wants to say thank you to all attendees making this event a great success.

Take the chance and listen to his thank you words.

Looking forward to seeing you in two years latest.

At the 9th International SAP Conference for Utilities, Frank Erhoff demonstrates system integration and the value delivered to waste utilities. With processes integrated, as this demo shows, a truck's contents can be quickly weighed and processed to speed things up.

For more information, see www.sap.com and Waste2Energy inside the SAP Solution Explorer.

Walter Zimmermann from the development team at SAP explains the SAP Smart Energy Data Foundation and speaks about the features and functionalities of SAP Customer Energy Management to facilitate communication between utilities and customers.

For more information about SAP Smart Meter Analytics see www.sap.com

For more infromation about SAP Customer Energy Management 1.0 powered by HANA see http://help.sap.com/cem10

Note: Prior to maintaining the settings for the process chains in the job commander transaction, check table TFK090A and find the job type (JTYPE) for the desired mass activities.  Analyze the determined job type to see if it used in multiple mass activities.  If so, for example A1 is used with both BILL and EMTB.  If this is true for any of the desired mass activities, the n you will need to implement logic in event 1906 so that the right mass activity can be determined.

Start:

Execute transaction FKJOXTR or follow menu path Utilities Industry -> Tools -> Administration of Mass Processing -> Background Processing Control

Right-click on the Container Sample and choose Create Job Container.

At the pop-up window, enter the details about one of the jobs to be scheduled.

The copy template data is necessary to enable the job processor to determine/copy the specifics of the mass activity, e.g. posting date or company code.   Here the template to be copied is defined for Jan 1, 2013 ID MASS.

Period data indicates the frequency and periodicity for the job.  You are also able to define how to handle non-workdays for any of the dates in the newly created job.

The type-specific settings indicate the job(s) that will be included in this container.  Only jobs of the same category can be included in one container.

After the first container is created, then create the next one.  In this example, I create the invoicing job to follow billing:

I have made similar settings as for the previous container, using the new job category A2 which refers to invoicing.

Having created two containers, I can create a chain to hold both of them.

Right-click on Process Chain Sample and choose Create Process chain template.

Click on Add to add containers to the chain.  Note: Only inactive containers will be shown here.  Do not activate your container.  It will be activated when you activate the chain.

Choose the billing job container to add it.

Repeat the process for the invoicing job container.

The details for the chain are saved.  Activate the chain.

After activation, generate the job containers.

Click on the Process Chain Overview button.

Double-click on the newly-defined process chain.

Choose the start date/time for the chain.

Look at the job log to find the scheduled chain.

After the job chain is executed, the SM37 log shows all of the executed processes.

Results: Here are the mass activities run and scheduled via the Job Commander settings.

The billing job which was scheduled and run via the job commander parameters:

The invoicing run which was scheduled and run via the parameters:

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.

Situation

Managing/Transferring the Bank Master Data across SAP systems

Assumptions

     (a) The Source and target SAP systems have already been created.

     (b) The Bank Masters in Source and Target Systems are not in Sync.

Pre-requisites

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-

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-

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.

  (a) Bank.Create

  (b) Bank.Change

  (c) AddessOrg.Savereplica

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-

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-

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.

Execution-FI08

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.

Related Contents

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

Wanted: Sponsors for "Utility of Tomorrow" Innovation Contest

At the 9th International SAP Conference in Copenhagen, SAP announced the "Utility of Tomorrow" contest.

The goal of the contest is to promote, accelerate and share transformative and innovative ideas with utility companies. The contest is focused on creating a connected, interactive and engaging customer experience.

It aims at enabling university students from around the world to engage directly with leading utility companies to transform the utility customer experience. For students the contest begins in September, and the deadline for submissions is in October.

Now we are looking for sponsors, especially in APJ! More information how you can benefit as a sponsor read this >>blog or visit our webpage >>Utility of Tomorrow Contest