Professional Documents
Culture Documents
Applies to:
SAP BI 7.0. For more information, visit the Business Intelligence homepage.
Summary
This document guides to establish connection between BW and R/3, so as there can two way
communications for various purposes. This can be done by simply creating source system in TCode SCC4 and later generating Partner Profile. This information is available easily on
help.sap.com and SDN (see related links), but this setting is not enough to have data transfer
between R/3 and BW. To achieve one is expected to make setting for Message types, which will
behave as a protocol for communication between the two systems. So this document takes you step
by step to create source system and which message types to use for communication.
Author:
Aadil Siddiqui
Author Bio
Aadil Siddiqui is currently working in Patni Computers Ltd. He is working on SAP BI 7.0 and is
mainly involved in Development and Enhancement work.
Table of Contents
Communication Setting between BW and R/3: ..................................................................................................3
Step 1: Define Logical System in R/3. ................................................................................................................4
Step 2: Assigning Logical System to Client. .......................................................................................................5
Step 3: Setting Up an RFC Destination. .............................................................................................................6
Step 4: Distributing Data Model:.........................................................................................................................7
Message Types Involved in Process of Data Loading:...................................................................................7
Step 5: Generating Partner Profile ...................................................................................................................11
Step 6: Maintaining Message types in T-Code WE20:.....................................................................................13
Related Content................................................................................................................................................15
Disclaimer and Liability Notice..........................................................................................................................16
Once an entry is made in above screen, one is navigated to next screen where standard settings are needed
to be maintained. Here importantly one needs to maintain the Logical system that is needed to be assigned.
Then save the
settings.
Please repeat the same step in BW also with respective client number for BW.
Next in the Logon & Security tab, fill login details for the target system (in this case BW).
Please repeat the same step in BW also but select source system as R/3 in SM59.
Once Distribution Model is created, lets add Message type using which the sender and receiver system will
communicate (in this case BW and R/3 also remember that the communication will be both ways i.e. from
R/3 to BW and from BW to R/3). To achieve this, place cursor on Model created (VCR3BW) and click on
Add Message type button on top right corner. This will open a dialog button where fill the sender system id
and receiver system id.
Message Types Involved in Process of Data Loading:
RSRQST: This message type is send by BW to R/3 while loading any data. This gives information about the
data source, selection condition and other BW settings to R/3. As and when a load is started in BW,
RSRQST message type is sent to R/3 requesting for data.
RSINFO: Once R/3 receives RSRQST message from BW, it sends an acknowledgement message type to
BW informing about the status of request. That is whether the request can be handled or not by R/3. It also
gives information about how many data packages are being send and what is the total number of records
extracted for the given data source and selection.
RSSEND: After sending a positive acknowledgement to BW, R/3 starts the extraction job and starts
collecting data in data idocs. This message type carries the actual data with it into the BW system.
For more details on this please check my earlier article.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0087780d-81b0-2a10-eb82-86e1062f1a2d
Hence we need to maintain these message types for the distribution model we created above. But make
sure that correct messages are assigned to correct system.
So Click on Add Message Type and give sender as R/3 system and receiver as BW system and message
type as RSINFO.
Having created the Distribution model, lets distribute this model. This process will replicate a similar setting
in BW side automatically.
Please note that Distribution of data model is not needed to be repeated in BW side as this step
automatically replicates settings in BW.
Go to Edit Model View Distribute.
Next, one is taken to following screen where one can define the partner system id and the user that
communicates.
After this Execute and wait for the system messages which inform whether partner profile was successfully
created or not.
Now logon on to the BW system and go to T-Code BD64 and test the partner profile settings, whether they
are correctly transmitted or not. We can execute it here (in BW) also and get our settings tested.
Depending on your client settings one can define different message types for eg:
Now test once again for Partner profile setting and we are ready to have data transfer between BW and R/3
(this can be done directly using T-Code BD82).
Related Content
http://help.sap.com/bp_biv135/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0087780d-81b0-2a10-eb8286e1062f1a2d
http://help.sap.com/printdocu/core/Print46c/EN/data/pdf/CABFAALEQS/CABFAALEQS.pdf