Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to realize a ALE scenario completely

Former Member
0 Kudos

Hi Experts,

It is actually a hard job to totally understand ALE principles and operations.Would you provide me

some materials for illustrating ALE realization.

I mean the whole steps from creating logical system,IDoc types to transfer data successfully.What I

care more is the IDoc Type creation and its corresponding Inbound and Outbound Processing.So expect you can teach me the basic steps of connecting IDoc type with Inbound/Outbound Processing

Maybe I didn't express myself clearly,it is so complex.Thank you for your help

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

please go through the following data.even though if you are not clear ask me any doubts you have in ale.i am sure that i will clarify.

IDOC Administration

Step 1: Tcode: WE 46

Setting the Global Parameter for IDOC Interface

Step 2: Maintaing a Logical System

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Logical Systems, Define Logical systems

Go to Spro transaction

Step 3: Allocating Logical systems to the Client

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Logical Systems, Assign Client to Logical systems

Go to Spro transaction

Step 4: Setting up an RFC destination

Tcode: SM 59

Path: From the ALE Customizing in IMG, choose Communication, Define RFC

Destination

You can also do the Advanced Settings in the RFC Destination

Step 5: The PORT definition

TCode: WE 21

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Systems in Network, Asynchronous Processing, Assign Ports, Define Port

Step 6: Generating Partner Profiles

TCode: BD 82

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, PArtner Profiles and Time of Processing, Generate Partner Profiles

Step 7: Distributing the Model

TCode: BD 64

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, Maintain Distribution Model and Distribute Views

Technques for Distributing the Master Data:

Technique 1: The Push Approach

Executing the Process:

TCode: BD 10

Path: from the ALE Main Menu, choose Material Data Distribution, Cross

Application, Material, Send

Technique 2: The Change Pointer Technique

Enable Change Pointers Globally

TCode: BD 61

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution, Replication of Modified Data, Activate

Change Pointers

Enable Change Pointers Globally

TCode: BD 50

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution, Replication of Modified Data, Activate

Change Pointers for Message Type

Specify the Fields for which Change Pointers are to be written

TCode: BD 52

Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define

Change-Relevant Fields

How the Classification system works:

Creating a Class Type

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Status for the Class Types:

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Classification Status:

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Classes:

TCode: CL 01 (it is zero)

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes

Allocating classes to the Logical Syatems

TCode: BD 68

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Assign classes

to Logical systems

Filering at the IDOC level:

Identify the Filter Object:

TCode: BD 59

Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects

Type to IDOC Field

Modify the Distribution model

How Segment Filtering Works:

Configuration:

Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered

TCode: BD 56

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments

The Reduced IDOC Type:

The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.

The System still needs the fields, but this has no effect on the recieving system because each field has a null value,

represented by a forward slash(/) in the field.

TCode: BD 53

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,

Create Reduced Message Type

IDOC:

Complete Documentaion on any IDOC using TCode: WE 60

IDOC Display Tool: TCode: WE 02 or WE 05

IDOC DEfinition components:

Segment Components:

1. Segment Type (E1, Z1)

2. Segment Definition(E2, Z2)

3. Segment Documentation(E3, Z3)

E- SAP Defined

z- Custom Defined

IDOC runtime componets:

control Record:

Data Record:

Staus Record:

First Create the Segments using TCode: WE 31

and then create the IDOC using TCode: We3 30

first release the segments and then IDOC.

Creating a new Basic IDOC Type:

STEP 1: Analyze the Data:

STEP 2: Create Data Elements:

STEP 3: Create Segments:

STEP 4: Create Basic IDOC Type:

1. Execute TCode: WE 30

2. Select the Create new option and enter a description for your basic IDOC type

3. click the IDOC name, and click the create icon.

Enter the segment type and its attributes.

4. Keep on adding the segments as in step 3.

5. Save the basic IDOC type

Step 5: Release the Segment Type and Basic IDOC Type

STEP 6: Transport the Segments and Basic IDOC Type

Extending a Basic IDOC type:

STEP 1: Analyze the Data:

STEP 2: Create Custom Segments:

STEP 3: Create the IDOC Type:

STEP 4: Release the custom Segment and IDOC Extension

Develop the function module for fteching the Data and then inserting the data into IDOC using

EDIDD(for control Record) and EDIDC table(for DATA Record)

Configuring the Systen for IDOCs

Configure an Outboubd Process that uses Message Control

Step 1: Create a new Message Type

TCode: We 81

Path: From the Area menu of EDI, choose Development, IDOC Type/ Message

Step 2: link the IDOC type to the Message Type

TCode: We 82

Path: From the Area menu of EDI, choose Development, IDOC Type/ Message

Step 3: Create a new Process Code

TCode: We 41

Path: From the Area menu of EDI, choose Control,Outbound Process COde

Step 4: Create or Change a Partner Profile

TCode: We 41

Path: From the Area menu of EDI, choose IDOC,Partner Profile

Configure an Outboubd Process for Stand-Alone Programs

1. Create a new message type

2. Link the IDOC type to the Message Type

3. Add the message to the ALE Distribution Model(use BD 64)

4. Create or change the Partner Profile

3 REPLIES 3

Former Member
0 Kudos

Hi,

please go through the following data.even though if you are not clear ask me any doubts you have in ale.i am sure that i will clarify.

IDOC Administration

Step 1: Tcode: WE 46

Setting the Global Parameter for IDOC Interface

Step 2: Maintaing a Logical System

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Logical Systems, Define Logical systems

Go to Spro transaction

Step 3: Allocating Logical systems to the Client

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Logical Systems, Assign Client to Logical systems

Go to Spro transaction

Step 4: Setting up an RFC destination

Tcode: SM 59

Path: From the ALE Customizing in IMG, choose Communication, Define RFC

Destination

You can also do the Advanced Settings in the RFC Destination

Step 5: The PORT definition

TCode: WE 21

Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,

Systems in Network, Asynchronous Processing, Assign Ports, Define Port

Step 6: Generating Partner Profiles

TCode: BD 82

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, PArtner Profiles and Time of Processing, Generate Partner Profiles

Step 7: Distributing the Model

TCode: BD 64

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, Maintain Distribution Model and Distribute Views

Technques for Distributing the Master Data:

Technique 1: The Push Approach

Executing the Process:

TCode: BD 10

Path: from the ALE Main Menu, choose Material Data Distribution, Cross

Application, Material, Send

Technique 2: The Change Pointer Technique

Enable Change Pointers Globally

TCode: BD 61

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution, Replication of Modified Data, Activate

Change Pointers

Enable Change Pointers Globally

TCode: BD 50

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution, Replication of Modified Data, Activate

Change Pointers for Message Type

Specify the Fields for which Change Pointers are to be written

TCode: BD 52

Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define

Change-Relevant Fields

How the Classification system works:

Creating a Class Type

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Status for the Class Types:

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Classification Status:

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types

Maintaing Classes:

TCode: CL 01 (it is zero)

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes

Allocating classes to the Logical Syatems

TCode: BD 68

TCode: O1 CL(it is CAPITAL O)

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Distribution using Object Classes, Assign classes

to Logical systems

Filering at the IDOC level:

Identify the Filter Object:

TCode: BD 59

Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects

Type to IDOC Field

Modify the Distribution model

How Segment Filtering Works:

Configuration:

Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered

TCode: BD 56

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments

The Reduced IDOC Type:

The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.

The System still needs the fields, but this has no effect on the recieving system because each field has a null value,

represented by a forward slash(/) in the field.

TCode: BD 53

Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business

Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,

Create Reduced Message Type

IDOC:

Complete Documentaion on any IDOC using TCode: WE 60

IDOC Display Tool: TCode: WE 02 or WE 05

IDOC DEfinition components:

Segment Components:

1. Segment Type (E1, Z1)

2. Segment Definition(E2, Z2)

3. Segment Documentation(E3, Z3)

E- SAP Defined

z- Custom Defined

IDOC runtime componets:

control Record:

Data Record:

Staus Record:

First Create the Segments using TCode: WE 31

and then create the IDOC using TCode: We3 30

first release the segments and then IDOC.

Creating a new Basic IDOC Type:

STEP 1: Analyze the Data:

STEP 2: Create Data Elements:

STEP 3: Create Segments:

STEP 4: Create Basic IDOC Type:

1. Execute TCode: WE 30

2. Select the Create new option and enter a description for your basic IDOC type

3. click the IDOC name, and click the create icon.

Enter the segment type and its attributes.

4. Keep on adding the segments as in step 3.

5. Save the basic IDOC type

Step 5: Release the Segment Type and Basic IDOC Type

STEP 6: Transport the Segments and Basic IDOC Type

Extending a Basic IDOC type:

STEP 1: Analyze the Data:

STEP 2: Create Custom Segments:

STEP 3: Create the IDOC Type:

STEP 4: Release the custom Segment and IDOC Extension

Develop the function module for fteching the Data and then inserting the data into IDOC using

EDIDD(for control Record) and EDIDC table(for DATA Record)

Configuring the Systen for IDOCs

Configure an Outboubd Process that uses Message Control

Step 1: Create a new Message Type

TCode: We 81

Path: From the Area menu of EDI, choose Development, IDOC Type/ Message

Step 2: link the IDOC type to the Message Type

TCode: We 82

Path: From the Area menu of EDI, choose Development, IDOC Type/ Message

Step 3: Create a new Process Code

TCode: We 41

Path: From the Area menu of EDI, choose Control,Outbound Process COde

Step 4: Create or Change a Partner Profile

TCode: We 41

Path: From the Area menu of EDI, choose IDOC,Partner Profile

Configure an Outboubd Process for Stand-Alone Programs

1. Create a new message type

2. Link the IDOC type to the Message Type

3. Add the message to the ALE Distribution Model(use BD 64)

4. Create or change the Partner Profile

Former Member
0 Kudos

Hi Alex,

You have to understand the following points to understand the process and for practical knowledge follow the above steps.

Reward points if useful

The Outbound Process

The outbound ALE process in SAP sends data to one or more SAP systems. At a very high level, an outbound process involves four steps.

1.Identify the need for sending an IDo-c. This step can occur immediately upon creating an application document, can relate to a change to a master data object, can be user initiated, or can simply be a point in a process that necessitates the exchange of data. The outbound ALE process for the IDoc data is started.

2.Generate the master IDoc. The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called a master IDoc. At this point, think of IDoc as yet another format in which a document can be represented. You know how a date can be stored in different formats, so imagine the date as a document with three components: day, month, and year. You can represent the date as MM/DD/YYYY, the standard American way. To make the information meaningful to a German business partner, though, you have to represent the date as DD.MM.YY. IDocs are based on a similar concept of representing one set of data in various ways.

3.Generate the communication IDoc. The ALE service layer generates a separate IDoc from the master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the master IDoc. These recipient-specific IDocs are called communication IDocs and are stored in the database. The recipients are determined from a customer distribution model that maintains a list of messages exchanged between two systems and their direction of flow.

4Deliver the communication IDoc. This step delivers IDocs to the appropriate recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receive or process the IDoc.

The Inbound Process

The inbound process receives an IDoc and creates a document in the system. At a very high level, the inbound process can be seen as a sequence of steps

1.Store the IDoc in the database. First, an IDoc is received in the system and stored in the database. Then, the IDoc goes through a basic integrity check and syntax check. If everything is fine, the next step is performed.

2.Invoke the posting module. The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.

3.Create the document. The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.

ALE configuration & IDoc process

http://www.saptechnical.com/Tutorials/ALE/ALEMainPage.htm

You will get complete information regarding ALE& Idocs

manubhutani
Active Contributor
0 Kudos

give me ur email address

will send u some useful docs.