Hi Raveesh,
ALE--
Application Link Enabling (ALE) is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.
In a single SAP system different applications are integrated via a single database (e.g. finance, sales, production, and human resources). However, many companies do not have just one integrated system but a distributed environment with different applications running on different systems. To run the whole business in such an environment the distributed applications have to be linked. This can be done through Application Link Enabling (ALE).
ALE provides distributed business processes that can be used to link the applications on different platforms. There is some ALE business processes delivered in the standard SAP system. Furthermore, there are tools that can be used to change the existing ALE business processes or to implement new distributed business processes.
Besides the business processes there are special ALE services that are required to set up and control a distributed environment. These services include a distribution model, business object synchronization and tools for monitoring or error handling.
ALE is a major part of SAP's Business Framework Architecture. Besides the basis middleware, that provides the communication between components, and the interfaces (BAPIs), ALE business processes and ALE services enable the cooperation of the single components within the framework. That makes ALE the glue of the Business Framework
Benifits:
With ALE companies get the opportunity to improve business performance and to solve organizational or technical issues.
Through distribution you can decentralize your business, enabling local units to operate independently from each other. This flexibility enables the local units to return better business results than in a centralized environment. They have the necessary flexibility to optimize business processes in different organizational units and can ensure that information systems can handle the speed of change in rapidly expanding markets. Distribution allows a high level of freedom, provided that this level of freedom has been clearly defined.
On the other hand, some companies, that already have a distributed organization with different computer systems in the local units, have the opportunity to link their units through ALE business processes. This enables them for example to provide a 'one face to the customer' approach. Another area that can benefit through ALE is virtual organizations (partnerships between independent companies, joint ventures and mergers and acquisitions).
USE:
The functional scope in a distributed environment is restricted. Not all functionality that is available in an integrated SAP system can be used with distributed systems in the standard yet. Although ALE provides tools to create new ALE business processes or to enhance existing business processes, this does involve additional expenditure.
Each company needs some organizational standards and data harmonization. In a distributed environment less standards are required than on a single integrated system. However, in a distributed environment the maintenance of the standards and the data harmonization is more difficult than on a single system.
The administration of decentralized systems is more expensive. Support and service costs for hardware and software in decentralized systems are higher than these costs in a single centralized system.
EDI:
The SAP EDI architecture consists of:
EDI-enabled applications, to support the automatic processing of business transactions.
The IDoc interface, which consists of IDoc types and function modules that form the interface to the application. There are IDocs available that support orders and invoices. IDocs are identical for inbound and outbound processing.
Eg. ORDERS02
The EDI subsystem, which converts the IDoc types into EDI message types and vice versa. This component of the EDI architecture is not supplied by SAP, thus the existing ASI EDI subsystem will be used.
Eg: Gentran or Mercator
EDI Interface between SAP R/3 system and EDI subsystem. For inbound processing, this involves opening the inbound message file, and processing the IDoc messages. For outbound processing, this involves selecting the outbound documents, creating an outbound message file and writing this file to the shared directory. The exact transfer times are scheduled using batch jobs. Please refer to EDI Production Configuration Guide for further interface details
USE:
oEDI is used as a strategic tool to reduce expenses, streamline business procedures, and create a competitive advantage
It will be helpful for you..
if satisfied,,rewards me...
Kind Regards
Yogesh Gupta
