topic Re: ale1 in Application Development and Automation Discussions

ale1

Former Member — Tue, 27 May 2008 13:00:02 GMT

hello SAP Gurus,

can anybody explain me the following topics ?

ALE Introduction

ALE Architecture

ALE Programming

Thank you very much in advance .

Regards,

Vijaya.

Re: ale1

Former Member — Tue, 27 May 2008 13:04:55 GMT

Please go through this link:

http://abapprogramming.blogspot.com/2007/05/ale-abap-cross-applications.html

Reward if useful.

BR,

Alok

Re: ale1

Former Member — Tue, 27 May 2008 14:00:54 GMT

ALE - Application Link Enabling

Process Flow:

An application creates a master IDoc containing the data to be transferred. The IDoc is passed to the ALE layer where it is prepared for dispatch.

After the IDoc has been transferred, it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually until is posted in the application.

Inbound and outbound processing can be carried out for individual IDocs or for packets of IDocs. In mass processing several IDocs are bundled together in one packet.

To develop a new custom ALE scenario, comprises 5 steps:

1. Design and develop the custom IDoc with itu2019s segments and a new message type

2. Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)

3. Develop the outbound process which does the following:

u2022 Populates the custom IDoc with control info and functional data

u2022 Sends the IDoc to the ALE layer for distribution

u2022 Updates status and handles errors

4. Configure the ALE inbound side (partner profiles with inbound process code)

5. Develop the inbound process which does the following:

u2022 Reads the IDoc into a BDC table; selects other data that is required

u2022 Runs transaction using call transaction or BDC session

u2022 Updates status and handles errors

Check the following links for ALE

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

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

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

http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp

Re: ale1

Former Member — Tue, 27 May 2008 19:34:34 GMT

hi vijayalakshmi,

ALE provides for the integration of distributed applications, but why would we distribute applications in the first place? There are several technical and business reasons:

System Performance: The transaction load is too heavy for a single

SAP system.

High Availability Requirements: The Company cannot afford downtime due to backups, maintenance, upgrades, etc.

SAP Release Coordination: Different units of the organization may require different releases of the SAP software.

Very Large Database: Companies with very large databases may need to distribute the data across multiple SAP systems.

Business Structure: Business units may require independence and autonomy for day-to-day operations, and yet still need to share some data and functionality with other units in the enterprise.

Interfacing with non-SAP systems: The Company may wish to maintain certain applications on non-SAP systems, while at the same time integrate these applications and their data with the SAP system.

Keep development system data in sync with production data: An organization may wish to keep the data on a development system the same as on a production system.

Maintain configuration and master data across clients: Organizations using multiple clients may wish to maintain certain data on a client-independent basis.

for more detailed explanation, Architecture and Programing please go through the following links,

[http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp][http://saptechnical.com/Tips/ALE/Why/WhyUseALE.htm]

Hope its clear to you,

Reward points if usefull,

Thanks,

kalyan.