topic ALE Flow in Application Development and Automation Discussions

ALE Flow

Former Member — Wed, 14 May 2008 08:19:18 GMT

Can i have the ALE Flow along with the transaction codes ?

Re: ALE Flow

Former Member — Wed, 14 May 2008 08:26:43 GMT

Hope it will help you.

Reward pts if help.

Application Linking and Enabling (ALE)

In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients

For our purpose we have two clients

namely Client 100 and Client 200.

System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).

Distribution of Material Master Data Between two Systems

1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)

To do this follow the following steps

Execute SALE Transaction Code

On The Screen Click on Sending and Receiving Systems.

Then Click on Logical Systems.

Then Click Defining Logical Systems.

Click New Entries Button

(E.g. (LG100 sending system)

(LG200 receiving system))

Enter two logical system names and their description.

Save

Comeback to SALE Transaction Code screen.

2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)

LG100 assign to client 100

LG200 assign to client 200

To do this, do the following.

Click Assigning Client to Logical System.

Ignore the message that comes up on the screen.

Select client 100

Click details button on the toolbar icon or press F2.

In the logical system box, enter LG100.

Click on the save Icon

Click the back button.

Now select client 200.

Click details icon or press f2.

In logical Systems box, enter LG200.

Save

Back.

Comeback to SALE Transaction Code screen.

3) Maintain RFC Destination: (TR.CODE:SM59)

(Note: Do Not Create This Step)

Click Create Button on the Screen

On the Screen Maintain RFC Destination i.e LG200.

Enter LG200 in RFC destination box.

Connection type is 3

Give a description for the RFC destination.

Maintain Technical Settings on Details on Technical Settings tab

Target Host as : SAPKDC (NOTE: Save it as a Host Name)

Maintain Logon Details on Logon/Security tab.

Language: EN.

User: MMUSER200 (This is the logon for dist.)

Client : 200

Password: MM1234.

Save.

Click on create to do the above process for Client 200 in

The client 200 system.

4) Maintain Distribution Model.(BD64). (ABAPer role starts here)

Execute Maintain distribution model directly for

creating the model.

Click on change mode button on App tool bar of the Screen.

Create Model View pushbutton on App tool bar of the Screen.

A pop screen will appear in which you specify

Short text as Distribution for MM Data.

Enter Technical Name as LGMODEL.

Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG100.

Receiver as LG200.

Again Click on Add Message Type Pushbutton on App toolbar of the Screen.

A popup screen will appear in which you specify

Model View as LGMODEL.

Sender as LG200.

Receiver as LG100.

SAVE.

On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Logical System as LG200.

Then execute the screen.

Click back.

Again On the same screen goto Menubar and select EDIT.

Again select Model View and then select Distribute.

****LOGIN to client 200.

Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.

And then select Generate Partner Profiles , then execute it.

On the Screen specify the Model View as LGMODEL

And Specify the Logical System as LG100.

Then execute the screen.

Click back.

*******Switch back to client 100 Session.

5) Create Material using MM03 Tr.Code.

Enter the material name as LGMATERIAL

Industry sector as Mechanical Engineering

Material Type as Finished Products.

And then Click on Data Pushbutton on the App tool bar.

Select views.

In the select views box for materials check basic data 1 AND 2.

Click enter icon.

In the next screen that you get

Give the text of the material as NEW MATERIAL.

Base unit of measure as KG.

Gross Weight as 200.

Net Weight as 100.

Weight Unit as KG.

In the description area language (E) and material description.

Click Save.

Now I Created a Material in Client 100 , I want to transfer this data to Client 200.

6) Execute BD10 to transfer the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client100).

Then a Screen will be displayed in which it shows that

1 Master Idoc Generated .. Enter

1 Communication Idoc Generated..Enter.

*******LOGIN to Client 200.

7) Execute BD11 to get the material in which you specify

the material as LGMATERIAL and

message type as MATMAS (client200).

😎 Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

If not follow these steps.

9) Execute Tr.code WE19( for rectification of errors in client200).

Specify the Existing Idoc Number and Executes it .

A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.

10) Execute Tr.code MM03 and give the material as LGMATERIAL

and see that the material is displayed as it was in Client 100.

Now the Material is correctly displayed in Client 200.

11) Monitoring of IDOCS.

Transaction Codes:

IDOC Display of Status: WE 05.

IDOC Date and Time: WE07.

Outbound:

Step 1. Application document is created when transaction is saved.

2. Message control is invoked.

3. Messages are processed by system.

4. Messages are Edited (if desired).

5. Output (ALE / EDI) is checked

6. Validate against Message control record from Partner Profile

7. Application Document is saved.

8. Entry NAST table is created for every selected output program

along with Medium & Timing.

9. Check for Process Immediately .

If (yes)

Determine Processing Program from TNAPR Table.

ELSE

Execute RSNASTED Program.

10. Read Partner Profile to determine Process Code.

11. Process Code points to the Function Module & Invoked.

12. IDoc is generated.

13. Check for ALE Request.

if (Yes)

Perform Filters, Conversions, Version Changes etc.

Else.

IDoc is stored in DATABASE.

INBOUND:

Step 1. EDI Subsystem creates an IDoc file from EDI Messages

2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.

3. Data in Control Record is validate against the Partner Profile.

4. IDoc is generated in Database and syntax check is carried out.

5. IDoc file is deleted once file read.

6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.

7. Check for Process Immediately.

If NO

Execute RBDAPP01 Program

Else

Read Process Code from Partner Profile

Process Code Points to Function Module

Application Document Posted.

further help:

check url

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/ale/configuration.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapdevelopment.co.uk/training

And also u can get lots of inof from the below link.

http://www.sapgenie.com/ale/why_ale.htm

Re: ALE Flow

Former Member — Sat, 28 Jun 2008 12:24:36 GMT

it was good to see step by step ale.

but how did u create client 200 or client 100.

i mean to say ,is it possible to create 2 clients in IDES software.

plz help me out.

regards,

yateendra.

Re: ALE Flow

Former Member — Sat, 28 Jun 2008 12:42:05 GMT

hi check this..

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/03e6e790-0201-0010-9d98-ab8102817a92

Re: ALE Flow

Former Member — Sat, 28 Jun 2008 12:46:45 GMT

hi,

refer to the link

http://hosteddocs.ittoolbox.com/KW122906.pdf

BD64 to define logical in/out

SCC4 assign client

sm59 RFC

we20 partner profile in/out

we21 port

bd64 distribution model

bd10

bd11

regards,

pritam.

Edited by: Pritam Ghosh on Jun 28, 2008 2:47 PM

Re: ALE Flow

Former Member — Sat, 28 Jun 2008 19:46:11 GMT

Setting up Clients

First of all, you have to set up two clients to enable communication between logical systems. The

two clients may be located in the same R/3 System or in separate systems.

You can either use existing clients or you can create new clients by making copies of existing

ones (for example, a copy of client 000 or a client of the International Demo and Education

System (IDES)). To set up a new client, from the SAP standard menu choose Tools

Administration Administration Client administration Client maintenance.

Clients 100 and 200 are provided. Both are copies of client 000.

Defining Logical System Names for Clients

To avoid any confusion, participating systems in a distributed environment must have an unique

ID. The name of the logical system is used as the unique ID. This name is assigned explicitly to

one client in an R/3 System.

When you have set up two clients for the exercise, you must notify them which logical systems

exist in the distribution environment and what the description of their own client is. You can find

the functions required for this in the R/3 Implementation Guide under Basis Application Link

Enabling (ALE) under Sending and Receiving Systems Logical Systems.

Client 100 is named logical system LOGSYS0100.

Client 200 is named logical system LOGSYS0200.

To maintain the logical systems in the distribution environment (function Rename Logical

System):

Execute the function and enter a logical system (LOG. SYSTEM) and a short text for each of

your clients.

Save your settings.

If you are using two clients in different systems, make sure your settings are the same in both

systems. When using two clients in one physical R/3 System, you only have to make the settings

once, since the entries are client-independent.

Log. System Short text

LOGSYS0100 System A, client 100

LOGSYS0200 System B, client 200

Assign the respective logical system to both the clients. Choose Assign Logical System to Client.

Execute the function in both clients.

To display the client maintenance screen, double-click on a client.

In the Logical system field, enter the logical system to be assigned to the individual client.

Save your entry.

Client Logical system

100 LOGSYS0100

200 LOGSYS0200

Defining the Communication Parameters

For the two logical systems to be able to communicate with one another, they must know how to

connect to each other. The RFC destination provides this information.

In each of the two clients, you must assign the RFC destination for the other logical system. In

Customizing for ALE choose Sending and Receiving Systems Configure Systems in Network

Define RFC Destination.

Execute the function.

Choose Create.

Enter the RFC destination:

Use the name of the logical system that is to be the destination (use UPPERCASE

letters).

For client 100 enter the RFC destination LOGSYS0200.

For client 200 enter the RFC destination LOGSYS0200.

Select 3 as the Connection type,.

Enter a description of the RFC destination.

For example, u2018RFC destination for the logical system LOGSYS0200u2019.

As logon parameters, enter the logon language (for example, EN), the logon client

(for example, 200 for LOGSYS0200) and the logon user (user ID with target system

password).

Select Continue.

Enter the target system and the system number:

The target system indicates which receiving system application server is to handle

the communication. The specifications could be the UNIX host name, the host name

in DNS format, the IP address or the SAP router name.

The system number indicates the service used (TCP service, SAP system number).

In SAP logon you can determine the target system and the system number by

selecting the button Server:

Select the relevant system and then select Generate list. The system displays a

list of all available application servers. To display the system number (instance),

select an application server and choose Add. A window appears displaying the

system number.

In Transaction SM51 you can display a list of the SAP servers in the target system.

u2013 Save your settings.

After saving the RFC destination, you can use Test connection to test the connection, and try

to logon via Remote Logon. If you succeed, the system displays a new window for the other

system. To check that you are in the correct client choose System Status.

Modeling the Distribution

The systems involved in the distribution must know which messages are to be distributed. They

must know where the messages are coming from and where they are going to. This information

is specified in the distribution model. The distribution is based on the distribution model and is

directly controlled by it.

The following sections show you how to model a message flow between your two logical

systems. You are going to distribute material master data from one logical system to another.

Modeling involves maintaining model views of the distribution model. To create a new distribution

model view follow the steps below:

Logon to the logical system from which you want to send materials to another system

(sending system LOGSYS0100).

From the R/3 Implementation Guide screen, choose Basis Application Link Enabling (ALE)

Modeling and Implementing Business Processes Maintain Distribution Model.

Create the model view. Select Create model view. Enter the technical name

GETSTART and a description for it.

Define the sending and receiving systems and the message type. Position the cursor

on GETSTART and select Add message type.

A dialog box appears.

Enter the logical system name of the sender LOGSYS0100 and the receiver

LOGSYS0200 and the message type MATMAS.

Save the distribution model.

Generating Partner Profiles in the Sending System

When you have created the distribution model, you must tell the participating systems how ALE

is to execute the transfer the data. This is done in the partner profiles.

First, generate the partner profiles in the sending system (LOGSYS0100). To do this, log on to

the relevant logical system.

In the R/3 Implementation Guide under Basis, choose:

Application Link Enabling (ALE)

Modeling and Implementing Business Processes

Partner Profiles and Processing Time

Generate Partner Profiles

Enter GETSTART as the name of your distribution model.

Without changing the parameters proposed by the system, execute the program.

The partner profiles required have now been generated on the sending system.

Distributing the Distribution Model

To be able to generate the partner profiles in the receiving system, this system must be informed

of all the messages flows in the distributed environment. This is achieved when you transport the

distribution model views from the sending system to the receiving system.

Carry out the following steps in the sending system:

In the R/3 Implementation Guide under Basis Components, choose:

Application Link Enabling (ALE)

Modeling and Implementing Business Processes

Maintain Distribution Model

Edit Model View Distribute.

Enter the model view GETSTART.

Select LOGSYS0200, the name of the receiving logical system.

Execute the program.

Your distribution model view will be copied to the receiving system.

Generating Partner Profiles in the Receiving System

When you have copied the distribution model to the receiving system, you can also generate the

partner profiles here. To do this, log on to the receiving logical system (for example,

LOGSYS0200).

In the R/3 Implementation Guide under Basis Components, choose:

Application Link Enabling (ALE)

Modeling and Implementing Business Processes

Partner Profiles and Processing Time

Generate Partner Profiles

Enter the name of your distribution model view, in this case, GETSTART.

Without changing the parameters proposed by the system, execute the program.

The required partner profiles will be generated in the receiving system.

Creating Material Master Data

Once you have made all the settings required to distribute materials, you can create a material

and then distribute it.

Log on again to the sending system and follow these steps:

Choose Logistics Materials management Material master from the material master

maintenance.

Choose Material Create (general) Immediately.

Enter the material, industry sector and material type.

Make sure that the industry sector and material type you enter are known in the

receiving system. Otherwise, errors will occur when you post the material in the

receiving system.

Material: Material001

Industry sector: mechanical engineering

Material type: finished product

Choose Select view and then Basic data.

Enter the basic data of your material.

To avoid any errors occurring during data transfer, make sure that the receiving

system will understand the information you have entered.

Material short text: Material for ALE: First steps

Base unit of measure: ST

Save the material.

Sending Material Master Data

You are now going to send the material you have just created to the receiving system.

Choose General Material Send:

Enter the material you have created (for example, Material001).

Use u2018MATMASu2019 Message type:

Enter LOGSYS0200, the logical receiving system

Execute the program.

You should now be able to display your material in the receiving system. If the material is not

available here, either the transmission has not yet finished or an error has occurred. The next

step shows you how to check the communication and detect any errors.

Checking Processing Status

The system provides functions for monitoring communication. These functions enable you to

confirm whether ALE messages have been processed and transferred correctly or whether errors

occurred. If an error did occur, the type of error is indicated.

You can monitor the processing status in both the sending system and the receiving system.

Choose Tools ALE Administration Monitoring Status monitor for ALE messages.

Execute the function, and select the IDocs of the logical message type MATMAS which you

created today.

A list of inbound and outbound IDocs grouped by status is displayed:

Outbound IDocs:

Status Description of Status

03, 12, 38 IDoc successfully transferred

02, 04, 05, 25

26, 29

Processing error

30 Waiting status (still processing...)

>=50 Inbound IDoc (not relevant in this context)

Other Not relevant in this context

Inbound IDocs:

Status Description of Status

53 IDoc successfully updated by application

64 Waiting status (still processing...)

<50 Outbound IDoc (not relevant in this context)

51, 56, 60, 61,

63, 65

Inbound error

Other Not relevant in this context

To display a list of IDocs with a particular status, double-click on a line. For detailed information

on one of these IDocs, double-click on it. If an error occurs, you can display information about the

cause of it by choosing Process Incorrect segments.

Error Handling

If an error has occurred, use the monitoring function to resolve it. The cause of the error is likely

to be a value in your material that the receiving system does not know and therefore cannot

process it. Try to eliminate the cause of the error and send your material again.

If your IDoc in the sending system was successfully transferred (status 03) but does not appear

in the receiving system, a technical communication error is the likely cause. You can use the

status monitor in the sending system to check this. Choose Goto Transactional RFC

Display calls.

Re: ALE Flow

Former Member — Tue, 15 Jul 2008 03:51:02 GMT

I Myself solved the issue.