ALE and EDI
来源:互联网 发布:网络延迟测试在线 编辑:程序博客网 时间:2024/06/02 03:15
Difference Between ALE and EDI
By : Paresh Trivedi
What is the main difference between ale and edi?
EDI – Definition
EDI is a technique used to communicate business and information transactions between computer systems of different companies and organizations. These transactions include such documents as purchase orders, invoices, inquiries, planning, acknowledgements, pricing, order status, scheduling, test results, shipping and receiving, payments, and financial reporting
EDI System Components Standards
ANSI X12 Transaction Sets
EDIFACT
EDI Introduction
The EDI interface is intended to connect an EDI subsystem with the SAP system. EDI subsystems perform the following tasks related to EDI processing:
1·Conversion of data·
2.Message and Interchange Handling.
3.Communication·
4.Administration of partner profiles·
5.Monitoring of processing
From the SAP side, the EDI interface is based on IDoc technology, which is independent of EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem. Synchronous RFC (Remote Function Call) is implemented to define the time of transfer for a file between the two systems.
EDI – Benefits
Improves data accuracy –
With EDI business can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors. Additionally, the cost of processing an electronic requisition is estimated to be one-tenth the cost of handling its paper equivalent
Lowers personnel costs-
EDI can help companies reduce the need for personnel involved in orders and accounting processing. Speeds up information exchange- EDI systems can shorten the lead time between receipt and fulfillment
Reduces technical complexity related to data interchange –
With EDI companies use standardized data formats to exchange documents. EDI allows companies using different business applications and systems to achieve computer-to-computer electronic exchange of business documents.
Application Link Enabling
ALE Objectives – ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers.
Basic principle of ALE is to provide a distributed and fully integrated R/3 system. Each application is self-sufficient. The use of self-sufficient system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.
General Steps Involved in Configuring EDI – ALE Interface
- Maintaining the Condition Table
- Maintaining the Access Sequences
- Maintaining the Output types
- Assign output types to the partner functions
- Maintain output determination procedure
- Assign output determination Procedures
RSNAST00: Selection Program for Issuing Output
RBDAPP01: Inbound Processing of IDocs Ready for Transfer
RBDMANIN: Start error handling for non-posted IDocs
RBDMIDOC: Creating IDoc Type from Change Pointers
RBDMOIND: Status Conversion with Successful tRFC Execution
RSEOUT00: Process all selected IDocs (EDI)
RSEIDOCM: CA-EDI: Active monitoring for IDoc processing
- ALE and EDI
- ALE&IDoc& EDI(1)--OverView
- ALE&IDoc& EDI(8)--Serialization
- ALE&IDoc& EDI(9)--others
- ALE&IDoc& EDI(1)--OverView {转载}
- ALE&IDoc& EDI(2)--一般流程{转载}
- ALE&IDoc& EDI(3)--change point01 {转载}
- ALE&IDoc& EDI(4)--change point02 {转载}
- ALE&IDoc& EDI(5)--Inbound Function {转载}
- ALE&IDoc& EDI(6)--Filter & Conversion {转载}
- ALE&IDoc& EDI(7)--IDoc Extension {转载}
- ALE&IDoc& EDI(8)--Serialization {转载}
- ALE&IDoc& EDI(9)--others {转载}
- ALE&IDoc& EDI(2)--一般流程
- ALE&IDoc& EDI(3)--change point01
- ALE&IDoc& EDI(4)--change point02
- ALE&IDoc& EDI(5)--Inbound Function
- ALE&IDoc& EDI(6)--Filter & Conversion
- NVARCHAR versus VARCHAR (zz)
- Xcode调试
- 数据库连接池的作用
- 穿透全透明
- ubuntu shell 命令一点一点学
- ALE and EDI
- Screen 设计
- APP性能终极优化之如何提高终端适配率
- jstl+el 获取枚举元素
- IOS学习-----课程体系-----坚持就是胜利
- C++ 简单读写文本文件、统计文件的行数、读取文件数据到数组
- 初级X编程
- 一语惊醒梦中人
- 微博营销与网络营销有什么不同