Communication Setting between BW and ECC
Communication Setting between BW and R/3
Step 1: Define Logical System in R/3
Step 2: Assigning Logical System to Client
Step 3: Setting Up an RFC Destination
Step 4: Distributing Data Model
Message Types Involved in Process of Data Loading
Step 5: Generating Partner Profile
Step 6: Maintaining Message types in T-Code WE20
Creating Source System (SALE): This step creates source systems which are to be connected.
- 1. Assigning Source System to Client (SALE): This step gives a logical name to a SAP Client from which the communication is to be established.
- 2. Setting up RFC Destination (SM59): This step is required to establish remote connection to the partner with which Source system is trying to communicate. Here one has to maintain the logon and IP details of the target system.
- 3. Distributing Data Model (BD64): A distribution model is used to model a distributed environment in which you specify messages exchanged between sending and receiving systems. Here one has to define the message protocols with which the two systems will communicate.
- 4. Generating Partner Profile (BD82): This process generates a partner profile for each system with which your system communicates. Outbound records are created in the partner profile for each outgoing message, and inbound records are created for each incoming message.
Note: If one distributes Data Model before generating partner profile then one has to redefine partner profile in other system also (repeat step in both system). In this document we are generating partner profile after Distribution of data model so as to demonstrate how to maintain inbound and outbound message types in WE20.
- 5.Maintaining Message Types (WE20): This process is optional. Generally while generating partner profiles we automatically get the respective Outbound and Inbound messages, which can be checked in T-Code WE20. If the message types are not defined then one can manually do it by following this process.
Step 1: Define Logical System in R/3.
- Log into R/3 and then go to transaction SALE. Here under IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Define logical system. Here one can define the source systems one wants to connect. Make entries for both R/3 and BW system.
Defining the Logical Systems
Repeat the same steps in BW
Create ALEREMOTE User in both the clients with following profiles
The ALEREMOTE user needs the following authorization profiles:
* In the Business Information Warehouse:
S_BI-WHM_RFC (Business Information Warehouse: RFC users in the Warehouse)
* In the source system:
S_BI-WX_RFC (Business Information Warehouse: RFC users in extraction)
Define the RFC connections in SM59.Test the connections on the same..make sure you are connecting as the background user you created.
General checks in trouble shooting…
check table RSBASIDOC in SE16…on both the sides (R/3 and BW)
to mirror each other..and the entries are active in both the sides.
Step 3: Setting Up an RFC Destination.
create an RFC destination on the local system for each remote SAP system with which you want to communicate. In the RFC destination, you specify all the information necessary to log on to the remote system to execute functions remotely, including the host name, the user ID, the password, the client, the system number, and additional communication settings.
So after creating a new entry of type ABAP Connection (The ALE process uses type R/ 3 connections to communicate with a remote SAP system, and the EDI process uses type TCP/IP connections to communicate with the EDI subsystem), one is expected to fill in details in Technical tab. Fill the Target Host Id (this should be same as defined in SALE) andgive System No. and IP Address of the target system or the Alias for the system as shown below:
Please repeat the same step in BI also but select source system as R/3 in SM59.
Step 4: Distributing Data Model:
You begin by clicking the Create Model View button on the main screen of transaction BD64.
Then add Message type
Having created the Distribution model, let’s 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.
Hence the partner profile was successfully generated…
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.
Step 6: Maintaining Message types in T-Code WE20:
Again we need to follow this activity both in BW and R/3. When in R/3 systems WE20, then click on BW system id, and check whether Outbound and Inbound parameters are correctly filled if not then fill it manually as below
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).
Now go to RSA1 in BI System
- Click On Replicate As Well –à here BI will fetch the data from R3 and it takes 10 to 15 min time.