ALE Setting for typical Business scenarios

Business Scenario:

Exchange data object such as material master between two systems to its full
extent.

Requirement:
As soon as material data get changed on SAP04 server, it should get updated to SAP02 system.
Material with material group = ‘ABC’ should get transfer to SAP02 system.

Specification for ALE interface :

Source System
Application Server name : SAP04
Description : Development Server
IP Address :172.18.26.41
Location : Satyam, Chennai centre
Development Login client for ALE setting : 555
Development Login user : develop
Logical System Name (Sending System) : SAP04_555
Client from which data to be transferred : 555
RFC destination name : SAP02_800
Target host for RFC destination : SAP02, System number : 01
TRFC port name : ZSAP02

Target System
Application Server name : SAP02
Description : IDES server
IP Address : 172.18.24.25
Location : Satyam, Chennai centre
Development Login client for ALE setting : 800
Development Login user : develop
Logical System Name (Receiving System) : SAP02_800
Client in which data to be transferred : 800

General Information
Message Type : MATMAS
IDOC record type version : SAP release 4.x

Ref : 711181685.doc Created by Vitthal Shelar Page 1 of 5

 ALE Setting for typical Business scenarios

Prerequisites
Authorization for following tcodes
SM59
SALE
WE46
WE21

Ref : 711181685.doc Created by Vitthal Shelar Page 2 of 5

 ALE Setting for typical Business scenarios

Solution :

Step1 : Basic Setting on Source system (SAP04)

1) Specify IDOC Administrator . Workflow uses EDIADMIN parameter when technical error
occurs in the ALE interface layer.
Tcode : WE46

Step2 : Basic Setting on Target system (SAP02)

1) Specify IDOC Administrator . Workflow uses EDIADMIN parameter when technical error
occurs in the ALE interface layer.
Tcode : WE46

Step 3: Communication Setting on source System (SAP04 server)

1) Create logical System on SAP04 server
Tcode : SALESending/receiving system
Logical system Name : SAP04_555

2) Allocate client to the sending logical system on source system, SAP04 server
Tcode : SALESending/receiving system allocate client
Logical system Name : SAP04_555
Client from which data to be transferred : 555

Create logical System on target system SAP02 server

Tcode : SALESending/receiving system
Logical system Name : SAP02_800
Client in which data to be transferred : 800

3) Allocate client to the receiving system on target system, SAP02 server

Tcode : SALESending/receiving system allocate client
Logical system Name : SAP02_800
Client in which data to be transferred : 800

4) Create & Test RFC connection on Source system to connect to target system
Tcode : SM59, RFC destinations  R/3 Connections

Ref : 711181685.doc Created by Vitthal Shelar Page 3 of 5

 ALE Setting for typical Business scenarios

5) Create tRFC port on source system

Tcode : WE21

1) Maintain outbound parameters for the partner profile generated in earlier step on
source system for message type MATMAS.
Tcode ; WE20

Partner type : LS , Logical System

Partner number : SAP02_800

Partner function : blank

Message type : MATMAS
Message Code : MATM
Basic IDOC type : MATMAS01

2) Maintain outbound parameters for the partner profile generated in earlier step on
source system for another message type SYNCH.
Tcode ; WE20

Partner type : LS , Logical System

Partner number : SAP02_800

Partner function : blank

Message type : SYNCH
Receiver port : ZSAP02
Idoc Basic type : SYNCHRON

3) Maintain inbound parameters for the partner profile generated in earlier step on
source system for message type MATMAS.
Tcode ; WE20

4) Maintain inbound parameters for the partner profile generated in earlier step on
source system for another message type SYNCH.
Tcode ; WE20
Step 4 : Basic configuration for Distribution model

1) Maintain Distribution model on source system

Tcode : BD64

Technical Name for Distribution model : MASTERDATA

Sender : SAP04_555
Receiver : SAP02_800
Message Type : MATMAS

2) Generate Partner profile

Tcode : BD64, Select Distribution model and then Environment->Generate partner
profile
Partner System = SAP02_800

For Partner SAP02_800 , outbound parameters should be maintained for message

type MATMAS, SYNCH. Message type SYNCH is used for distributing the
“Distribution model’

Ref : 711181685.doc Created by Vitthal Shelar Page 4 of 5

 ALE Setting for typical Business scenarios

3) Distribute the ‘Distribution Model” to target system (ie.SAP02_800)

Tcode : BD64
Select “MASTERDATA” distribution model. Select “EDIT””Model View” 
“Distribute model”

On next screen, select “SAP02_800” as a receiver for the distribution model

4) On Target system, (SAP02_800) , Check Whether Distribution is imported .
Tcode : BD64
Check for distribution model : MASTERDATA

5) On Target System (SAP02_800), check whether partner profile SAP04_555 is

created automatically after distribution of ‘distribution model’

Tcode : WE20
Check for partner number : SAP04_555

6) Maintain Inbound parameters for partner profile SAP04_555 on Target System

Tcode : WE20

Partner Profile : SAP04_555

Partner Type : LS
Message Type : MATMAS
Message Code : MATM

To check the idoc status:

We05

Ref : 711181685.doc Created by Vitthal Shelar Page 5 of 5