Scribd
Upload
1K views18 pages

Exchange Rate Sync Using IDoc

This document provides steps to sync exchange rates between SAP systems using IDocs. It describes setting up a distribution model in the source system using transaction code BD64 to call the BAPI_EXCHANGERATE_SAVEREPLICA interface and send the exchange rate data as an IDoc. It also describes configuring the destination system using transaction codes WE57, BD51 and WE20 to process the incoming IDoc and update the exchange rates in the target system. The process is tested by making a change to exchange rates in the source system and running program RFALEX00 to transfer the changes to the destination system via IDoc.

Uploaded by

toralber
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views18 pages

Exchange Rate Sync Using IDoc

This document provides steps to sync exchange rates between SAP systems using IDocs. It describes setting up a distribution model in the source system using transaction code BD64 to call the BAPI_EXCHANGERATE_SAVEREPLICA interface and send the exchange rate data as an IDoc. It also describes configuring the destination system using transaction codes WE57, BD51 and WE20 to process the incoming IDoc and update the exchange rates in the target system. The process is tested by making a change to exchange rates in the source system and running program RFALEX00 to transfer the changes to the destination system via IDoc.

Uploaded by

toralber
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Exchange Rate Sync using IDoc

January 7, 2018 | 656 Views |

Former Member


SAP HANA remote data sync
ABAP DevelopmentMigrate DataNW ABAP Integration Technology (ALE)SAP Data IntegratorSAP
Revenue Accounting and Reporting

In the source system: in my case it was ECC – D01 800


Tcode: BD64 – Distribution Model

Click on Edit, Select the node and click on Add BAPI


Add the Obj Name/Interface: ExchangeRate and Method: SaveReplica
Go to Environment -> Change Partner Profile
This takes us to tcode WE20 for partner profile maintenance
For partner type LS (Logical System), choose the destination system (D09CLNT100 in this case)
Add a new parameter in the Outbound Parameters section
Message Type: EXCHANGE_RATE; Basic Type: EXCHANGE_RATE01
Once saved, go back to the Distribution Model tcode BD64. Select the model view -> Edit -> Model View ->
Distribute. Select the receiver of the model view from the list
Log is displayed
In the destination system (in my case it is RAR D09 100)

Go to tcode WE57 – Idoc assignment of FM to Log. Message and Idoc Type (Cross Client Settings). Create the
following assignment:

Go to tcode BD51 – Characteristics of Inbound Functional Modules. Add entry for FM


BAPI_EXCHANGERATE_SAVEREPLICA (Cross Client Settings)
Go to tcode WE20 to maintain partner profiles for Partner Type LS and Partner No. = <Source Partner System>
(D01 800 in this case)
Add a new inbound parameter
New parameter details: Message Type – EXCHANGE_RATE; Process Code – BAPI
Once the Idoc is setup, in the source system make a change in the forex using tcode OB08
Current setup in destination system:

Run program RFALEX00 in the source system to transfer the changes through Idoc.
Log is displayed
In the target system check that the update has happened as expected

Idocs can be viewed in tcode BD87/WE02

You might also like