ALE is a middleware that able for SAP to connect to other SAP/Non SAP system. Data is exchanged between applicaitons and remains consistent in all applications.
Application systems are loosely coupled in an ALE integrated system. Data is exchanged asynchronously, whereby the data arrives in the receiver system, even if the receiver system cannot be connected to at the time the data is sent. ALE uses synchronous communication for reading data only.
Applications are integrated using a local database rather than a central one. There is no data retention. ALE guarantees the distribution and synchronization of master data, Customizing data and transaction data through asynchronous communication.
Synchronous communication is used in ALE to read data only.
ALE Benefits:
- Application data can be distributed between different releases of R/3 Systems
- Data can continue to be exchanged after a release upgrade without requiring special maintenance
- Customers can add their own enhancements
- Communication interfaces enable connections to non-SAP systems.
- R/3 and R/2 Systems can communicate with each other.
ALE has functions for monitoring messages flows and handling communication problems.
Implementation Considerations:
Things to be thought thru during implementation:
- Determining functions and processes
- Specifying global settings
- Modeling company structure
- Modeling control data and master data
Data across particpating system need to be uniform in term of definition. For connecting to non sap system, it is acheived with the help of external converter (ALE converter).
ALE Process
Then the IDoc is transferred to the target system.
In the target system the IDoc starts inbound processing. The data is processed and then posted in the application either fully automatically or part manually. Inbound and outbound IDocs can be processed individually or in a packet. In mass processing several IDocs are processed together in one packet.
No comments:
Post a Comment