Application Link Enabling (ALE)

[Bhuvnesh_Mudgal]

Introduction

Application Link Enabling (ALE)

ALE stands for Application Link Enabling. ALE in SAP is used for exchanging business data between different systems. This form of communication requires IDOC interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the Idoc.

If packet is being created in Q system and sent to P system then, outbound parameters of PCLNT100 will be checked in Q system and inbound parameters of QCLNT100 will be checked in P system.

Prerequisites

The ID & Password should be in working condition and we should be able to access both the clients in the system.

Set-up

1 Settings on Sender side (Q):

1.1 Defining Logical System

T-code: SALE

IDoc Interface / Application Link Enabling (ALE) -> Basic Settings -> Logical Systems -> Define Logical System

QCLNT100: Logical system for sender system (Q Client 100) - Sender

PCLNT100: Logical system for receiver system (P Client 100) - Receiver

1.2Assigning Logical system to Client

T-code: SCC4

• Select one line.
• Choose: Goto -> Details.
• The 'Client Details' screen appears. In the field Logical system, enter the name of the logical system to which you want to assign the selected client.

• Save your entries.

1.3 RFC destination for Partner

T-code: SM59

• Select one of the types (for example, SAP connections) and choose Edit -> create
• Enter the parameters required for that type.
• For an SAP connection, these are, for example, the name of the RFC destination, the name of the partner system, logon parameters (see example).

Specify message server in target host.

On Log On and security Tab, Enter User and password details of user from receiver. For the current set up, user is PDR_BATCH and a password is set as provided by administrator.

Select Unicode connection type for transferring the data as it is.

Test the connection just created by clicking on ‘Connection Test’.

1.4 Maintain Distribution model.

T-code: BD64

The distribution model consists of separate model views in which all the associated, cross-system message flows in your organization can be defined. These views must be distributed to the receiving systems.

In addition to the message types for the object, you need two other message types that have been introduced for PLM product data distribution.

• Message type UPSMAS (distribution packet)

Distributes the ALE distribution packet to the recipient systems from the central system.

• Message type UPSRCP (receipts)

Sends receipts via ALE distribution packets from the recipient systems for product data distribution to the central sending system.

Distribution model after adding all relevant message types is shown below.

1.5 Generate Partner Profile

Partner profile can be generated either by WE20 manually or automatically by WE82. From distribution model screen also the partner profile can be generated. To generate from distribution model screen, select generate partner profile.

Check in WE20 for partner profile created above and correct the process codes generated for the inbound messages for receiving partner.

2 Settings on Receiver Side (P Client 100)

2.1 Define logical systems:

T-code: SCC4

Define logical systems for both sender and receiver as in previous section for sending side. Assign logical system for receiver (P Client 100) to client.

2.2 Maintain RFC Destination

T-code: SM59

Use the steps similar to those in section 2.1.3.

Maintain the User and password details for P system as provided by the Basis team. In this set up, the user is RFCUSER1.

2.3 Distributing and Transporting Model Views

Model views are distributed between systems on the same level (development systems, test systems, productive systems) via the Change and Transport System. You have to create a transport request for the model view from sending system. Choose Edit -> Model view -> Distribute.

Go to transaction BD64 in RR3.

Now go to BD64 in P (Production System), the model is distributed from Q to P. Correct the entries/process codes if necessary and Generate Partner profile for sending system. You can view partner profile in WE20.

Conclusion

ALE in SAP improves and optimizes the business performance ensuring good flow of data between systems through RFC and so on. It is an versatile technology which is required to meet some specific needs in SAP to SAP systems or external connectivity.