ALE （Application Link and Enabling）介绍

纵横四海

　　　ALE 是Application Link and Enabling的缩写，是SAP专门为SAP与SAP之间所设计的整合中间件。IDocs是中介文本 (Intermediate   DOCument) 的缩写，是SAP提供的系统整合专用的数据/消息格式。ALE在SAP 3.0版本开始就作为SAP整个应用体系的一部分，为分布式数据交换提供了可靠安全的通讯机制。ALE的设计，原本作为两个SAP流程之间的一种消息传递服务(Messaging Service) ，使SAP与SAP的业务流程之间企业数据能够有效的交换，为两个独立的SAP之间提供了的系统整合服务。不过，随着应用的发展，ALE/IDocs接口机制也已然成为与其它非SAP系统的标准的整合方式。　　ALE的设计结构可以分为三层，即应用层，数据/消息分配层和通讯层。　　通讯层是SAP整合机制的基础，它利用远程功能呼叫RFC(Remote  Function Call)  调用SAP系统的功能模块。　　数据/消息分配层，主要提供三个关键服务：　　
1）按数据分配模型决定数据接收者。　　
2）消息的过滤和转换。　　
3）数据/消息的压缩，以提高传递效率。　　

应用层直接与SAP系统接口，生成或从其它系统接收含有路由信息的消息文本IDocs，包括消息接收者的姓名，要求发送的类型以及对消息进行处理的规则。
            　

ddhh5205

有没具体做的资料？
我知道个大概
1、SM59
2、WE21
3、WE20
4、BD64
但是不是很清楚

纵横四海

许多大企业把整个SAP system分布在多个instance上,每个instance专注于特定的业务.
例如: plant中的物料采购在一个本地的instance上进行处理(the local system).
向供应商付款和总帐处理在公司中心instance上处理(the central system).

分布(distribute)不是简单的数据分割!!!
分布就是把数据分布在多个地点,但同时又能保证数据在整体上的一致性和完整性.
分布用到分割技术, 但是分布不是简单的分割.为了保证不同地点的数据的完整性
和一致性different systems利用ALE进行沟通.
The ALE concept always relates to an entERPrise structure with areas that have central tasks
and areas with tasks that are decentralized.

 It may be practical for organizations to use separate application systems so that application components can be installed and operated on decentralized systems that are technically independent of each other.
 The ALE concept supports the implementation and operation of distributed SAP applications. It is based on business-controlled messaging with consistent data storage on loosely coupled systems. The applications are integrated through the message exchange, not via a central database.
 To implement a distributed, yet integrated system, the customer must specify in a logical model, which applications are to run on which systems and how the applications are to exchange data with each other.
 On the technical side, the data exchange is carried out via IDocs (intermediate documents) as used in the EDI (Electronic Data Interchange) interface. On the application side, EDI supports information exchange between R/3 systems in different enterprises, whereas ALE supports information exchange within one enterprise. The ALE distribution mechanism is similar to the EDI mechanism. In ALE, business processes are distributed at the transaction level.

 The procurement of materials via the plant in a company code can be handled in a local system. However, payments to vendors and the general ledger are managed in a central system.
 In order that both organizations use the same master data, the head office distributes the master data to the local system. Thus the transaction data in the local systems for which IDocs exist can be sent to the head office without inconsistencies.
 Examples of data that can be distributed:
­ Master data: Customers, vendors, G/L accounts, cost centers, cost elements, activity types
­ Transaction data: Incoming invoices, outgoing invoices, Financial Accounting line items, Controlling documents
 The SAP standard system is delivered with some ALE scenarios. For example:
­ Central contract management in Purchasing
­ Distributed Inventory Management
­ Central Materials Management master data
 The message types required for the distribution via IDocs are also delivered by SAP. You can also define your own ALE scenarios.
 Business to Business Procurement works through ALE with an R/3 backend system

heimayanchuan

长知识了,以前只是在用的过和中出现ALE通讯问题但就是不知道是怎么回事现在看了算是明白了很多.谢谢.