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.

In this step, you 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) and give System No. and IP Address 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.

These steps will ensure that the BW and other source systems are in sync and will
communicate as expected.