Difference between ALE / EDI

Hi,
I have a question from long time. What is the difference between ALE & EDI.When I ask my friends They say in simple way. SAP - SAP (ALE) . SAP - NON SAP (EDI).
Today I read in a book .ALE/IDOC method can be used to connect to SAP - NON SAP (LEGACY). Now I am more confussed .
If any one can explain me the real difference I really appreciate the time.
Thanks,
Andy

Hi Andy,
I am just sharing a few lines which i read some where. Hope that would be helpful.
ALE(Application Link Enabling)  refers to the losely coupled systems whereas the EDI speaks about the Electronic Document Exchange. We need to enable ALE in order to use the EDI feature. ALE builds the bridge and EDI is the means by which the data moves in and out of the SAP system just like vehicles moving over the bridge. IDOC(Intermediate Documents) are the data containers which will be moving in and out of SAP carrying data.
Thus summarising we need to establish ALE between the systems in order to use EDI between them. In case we need to use EDI between SAP and some other target system then we need a EDI subsystem which understands these IDOCs and converts into the format understood by the target system.
  Hope this is useful.
Regards,
Pooja

Similar Messages

  • What is the difference between ALE & EDI

    What is the difference between ALE & EDI ? [in case of its configuration.]

    hi,
    chk out this
    ALE Configuration     1
    1     ALE Introduction – Transaction SALE     
    2     The 3 ALE methods     
    2.1     Push     
    2.1.1     First create logical system (In SPRO / SALE)     
    2.1.2     Assign Client to Logical System (In SPRO)     
    2.1.3     Create RFC Destination – SM59     
    2.1.4     Create Distribution Model – BD64     
    2.1.5     Send Material – BD10     9
    2.1.6     Check IDOC sent – WE02     
    2.2     Pull     
    2.2.1     Create Model View – BD64     
    2.2.2     Login to 810     
    2.2.3     Get Material – BD11     
    2.2.4     Check IDOCs – WE02     
    2.2.5     Check Material – MM02     
    2.3     Change Pointer     
    2.3.1     Activate change pointers for message type – BD50     
    2.3.2     Activate Change Pointers – BD61     
    2.3.3     Execute RBDMIdoc – SE38     
    2.3.4     Check IDOCs – WE02     
    2.3.5     Check Material – MM02     
    EDI configuration
    1) have to configure EDI subsytem
    2) Configure basic edi components
    3) Configure Partner Profiles
    4)    "             Message Control
           The main difference is that you have to configure the subsytem in case of EDI where as this is not the case of ALE.
         EDI uses memory buffer while ALE uses file port.
    <b>Reward useful points</b>
    ALE/EDI
    Regards
    SIva

  • What is the difference between ALE and EDI

    Hi,
    Can any one please explain what is the difference between ALE and EDI ?
    Thanks in advance.
    Ramana

    Hi Ramana
    ALE: used to trnasfer IDOC with in the R3distributed system.
    EDI: used to transfer IDOC from R3system to nonsap system
    IDOCS:
    IDOCS are intermediary documents which are like CARRIERS of the data
    IDOCs are safe to transfer data, but less volume of data. User is not allowed to access (modify) the data like PSA. IDOCs have 3 parts.
    1. Control Record - SOURCE & TARGET details,
    EDI
    EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE
    are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to
    deliver data to the receiving system.
    check these links also
    EDI document
    http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983331,00.html
    http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci879631,00.html?NextURL=http%3A//searchsap.techtarget.com/ateQuestionNResponse/0%2C289625%2Csid21_gci879631%2C00.html
    http://sapabap.iespana.es/sapabap/sap/faq/ale_idocs_bapi.htm
    Reward all helpfull answers
    Regards
    Pavan

  • Difference between ale and edi

    Hi experts,
    I know this topic was discussed in the forum lot of times. i want to clarify one thing here.
    1) can EDI be used to transfer the between tow SAP systems.
    2) can ALE be used to transfer data between SAP and non SAP system.
    if the answer to the questions is yes then is there any case where we can not use ALE in place of EDI and vice versa.
    Also, in what situation we use the BAPI- ALE interface to distribute the data??
    thanks
    sankar

    EDI, stands for Electronic Data Interchange, is the electronic exchange of structured business data between different applications.  The EDI architecture consists of
    EDI-enabled applications :They support the automatic processing of business transactions.
    The IDoc interface: This was designed as an open interface. The IDoc interface consists of IDoc types and function modules that form the interface to the application.
    The EDI subsystem: This converts the IDoc types into EDI message types and vice versa.  This component of the EDI architecture is not supplied by SAP.
    Advantages of the EDI Process
    Reduced data Entry Errors
    Reduced Processing cycle time
    Availability of data electronic form
    Reduced Paper Work
    Reduced Cost
    Reduced Inventories and Better Planning
    Standard Means of Communicating
    Better Business Processes
    Competitive Advantage
    ALE
    PURPOSE
         ALE supports the distribution of the business functions and process across loosely coupled R/3 systems. Connections from   R/2  and non SAP systems is also supported.
    IMPLEMENTATION CONSIDERATIONS
         Distributing business applications and at the same time ensuring data consistency is practical because:
    The increasing globalization of markets has led to the physical division of organizational units.
    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.
    The performance of an R/3 System can be improved by distributing the business applications.
    Features
    ALE supports:
    Distribution of applications between different releases of R/3 Systems
    Continued data exchange after a release upgrade without requiring special maintenance
    Customer-specific extensions.
    Communication interfaces that allow connections to non-SAP systems.
    Coupling of R/3 and R/2 Systems.
         ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.
    Differences between the two:
    ALE is used to support distributed yet integrated processes across several SAP systems whereas EDI is used for the exchange of business documents between the systems of business partners
    ALE is SAPu2019s technology for supporting a distributed environment whereas EDI is a process used for exchange of business documents which now have been given a standard format
         Both ALE and EDI require data exchange. An Idoc is a data container which is used for data exchange by both EDI and ALE processes.

  • Different between ALE/EDI/XI

    hi all
    goood morning
    i want to know the differences between the ALE & EDI.
    let me know at which situation we can use ale and
    at which situation we can use edi.
    and what is the different betweeen xi and ale/edi also.
    if possbile could explain with some small senario.
    thanks
    mahi

    Hi,
    Exchange Infrastructure (XI) is an Integral part of SAP Net weaver. Position of XI is in the process integration layer of Net weaver stack.
    The aim of XI is to integrate different versions of both SAP and non-SAP systems implemented on different platforms (Java, ABAP, and so on). XI enables you to implement cross-system business processes.
    XI is based on an open architecture, makes use of open standards and offers services that are essential in a heterogeneous and complex system landscape: namely a runtime infrastructure for message exchange, configuration options for managing business processes and message flow, and options for transforming message contents between the sender and receiver systems.
    The application-specific contents are transferred from the sender to the receiver in a freely defined XML schema (XML: extended Markup Language) using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.
    The central concept is that, during the design phase, all interfaces required are initially developed independently of a platform and made available in the form of a WSDL description(WSDL: Web Service Description Language). Using this description you can, for example,
    define mappings between interfaces without this having an effect on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, the configuration phase, you can
    select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes, and assign them to each other in logical routing. The data resulting from this configuration process is saved in the
    Integration Directory and you can call and evaluate it from the runtime of the Exchange Infrastructure.
    Exchange Infrastructure can be used as a Middleware Engine to communicate in a distributed environment. The heart of XI is Integration Engine that is used for integrating different technologies using Standard Messaging techniques e.g XML. Different mapping tools are avilable for mapping the distributed system which can be mapped without having any expertice of Technical Details. As a real world example, XI can be helpful in integrating different banks with SAP R/3. XI Engine also support previous releases of SAP R/3 like 4.6C and have many more adapters to communicate with legacy systems.
    SAP XI is an integration technology and platform for
    1.      SAP and Non-SAP systems,
    2.    A2A and B2B scenarios,
    3.       Synchronous and Asynchronous communication,
    4.       Cross component Business Process management and it include built-in engine for designing and executing   integration process (Business process).
    5.     The goal of SAP XI is to provide single point of integration of all systems inside and outside the corporate boundary across technologies and organizational boundaries.
    6.      The important feature of XI is openness, flexible and transparency to the integration process. It is based on ESA and SOA.
    7.      The overall key concept of SAP XI is to drive integrated business process across heterogeneous and highly dynamic landscapes in a more manageable cost effective way.
    8.      The basic idea is to provide runtime infrastructure which allows heterogeneous systems to be tied together with fewer connections and at the same time, in order to connect those applications and let messages flow from one application to other, have a centralized storage of integration knowledge.
    Regards,
    Iff
    Note: Reward suitable points.

  • ALE/EDI and RFC

    Dear All,
    Please, can anyone tell me what is the difference between ALE/EDI and RFCs?
    Thanks in advance.
    Kind Regards,
    Umesh.

    Hi prasad,
    1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
    2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
    These r some major difference b/w ALE and EDI:
    ALE: used to transfer IDOC with in the R3 distributed system.
    EDI: used to transfer IDOC from R3 system to non sap system
    ALE --This method is used to transfer master data
    EDI--This method is maximum used to transfer transactional data.
    ALE--RFC port is used
    *EDI*-- FILE port is used
    ALE--Data transfer takes place from one mother client to N different clients
    EDI-- one partner 2 other partner thru customer distribution model
    The philosophical difference between EDI and ALE can be pinned as follows:
    If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to
    reliable replicate data between trusting systems to store a redundant copy of the IDoc data.
    The difference is made clear, when we think of a purchase order that is sent as an IDoc.
    If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order.
    However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    ALE
    ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
    ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
    ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
    The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
    ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    REWARD IF USEFUL
    THANKS AND REGARDS
    SUMA SAILAJA PVN

  • Relation of ALE , EDI  and idoc

    HI
         what is relation of these ALE, EDI, IDOC , i know the definition of these , i want know ( while the transfer of sap to sap ALE tool is used ,) where this idoc is used ,
    regards
    shivaji

    Hi Shivaji,
    What is EDI…?
    Electronic Data Interchange
    •     The computer-to-computer electronic exchange of machine processable business documents in a standard format
    •     An electronic alternative to paper, fax, and phone-based transactions used by companies to communicate with one another
    Purpose:
    •     Allows for better time management and relieves the entering of duplicate information while cutting down on discrepancies and human intervention.
    •     The Electronic Data Interchange component in Sales and Distribution consists of an Intermediate Document (IDoc) [Ext.] interface. You can use this interface to
    –     send messages (outbound processing) such as an order confirmation through Electronic Data Interchange (EDI)
    –     receive messages (inbound processing) such as a sales order through EDI
    EDI:
    •     What…?
    –     The technology of transmitting documents electronically
    •     Why…?
    –     For Electronic Data Interchange between a company and trading partners
    •     How…?
    –     By means of an electronic document - the IDoc
    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 Remote Function Call (RFC) is implemented to define the time of transfer for a
    file between the two systems. The following data can be transferred using the EDI interface:
    Outbound Idocs: IDocs are transferred from the R/3 System to the EDI subsystem.
    Inbound Idocs: IDocs are transferred from the EDI subsystem to the R/3 System.
    Status report: The EDI subsystem sends a status report to the R/3 System on the progress of
    the processing of the outbound Idoc.
    Contents of IDOC
    The data in every IDoc is exchanged between the SAP system and a subsystem in the following three record types, irrespective of the IDoc type:
    •     Control record (Table: EDIDC): Contains information about Sender and Receiver. There is only one control record per IDoc. It consists of
    • IDoc Number
    • Sender and Receiver information
    • IDoc Message Type* / Port.
    • IDoc Type / Direction / Current status / Partner No / Partner Type (Vendor/customer)
    •     Data record (Table: EDIDD): Contains the message to be exchanged between Sender and Receiver. An IDoc can contain multiple data records, as defined by the IDoc structure. Data records store application data such as purchase order / sales order header information, sales order details like sales doc #, Material / Qty and other relevant information.
    •     Status record (Table: EDIDS): Contains Status of IDoc at various stages, during the transmission of IDoc between Sender and Receiver. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process like status code, date and time at every stage
    Know Me
    Basic Type: The form of IDOC type that is originally created in the system. Like ORDERS01 is a basic type IDOC for order messages. It is using the basic types only you would be able to enhance them to suit new requirements within the same IDOC structure. Any enhancement to the basic type IDOC will produce an Extension IDOC that would be more or less similar to the basic type with some new additions (of segments or fields). Here, I would go on to say that IDOC type and Basic type is the same thing that would be referred to interchangeably.
    Message type: Again, obvious from the name, it’s the message that is being conveyed. A message type is assigned to the Basic type. Here, logical messages are assigned to the basic type to reflect a business message being transacted. For example, ORDERS is the message type for a purchase order sent by buyer to vendor. The use of which Basic type in this message will differ from buyer to vendor. Basic types used for ORDERS are ORDERS01/02/ etc...Also, one may come up with a custom built IDOC type (or basic type as you can say)...But it is essential to associate a message type with a basic type IDOC. This feature will enable the same IDOC type to be used for a related message. For example : ORDERS01 can be used for message ORDERS for posting a order, the same IDOC can be associated with message ORDCHG to indicate that the message is an order change and so the processing of this IDOC will change accordingly.
    IDoc Type:
    &#61607;     Defines the structure of data records
    &#61607;      IDoc Type is used to understand the message in string form available in the data records.
    &#61607;      IDoc type is version dependent i.e an Idoc type can be used only in versions in and above the version in which IDoc is released. 
    &#61607;      Transaction WE30 is used to define and release IDoc Types
    &#61607;      Newly created Idoc is a BASIC IDoc and modifications
                 (Additions of segments) to IDoc after it has been released can be done by creation of extension      of IDoc.
    &#61607;      IDoc type can be defined by structuring Segments
    Function Module: The most important player in the IDOC processing. This is nothing but an ABAP program to process the IDOC. SAP has supplied function modules to process all standard basic IDOCs and messages. A function module is determined based on the Basic IDOC type and the message type (also message code). So from the above descriptions about basic and message type, the combination of two would primarily determine which IDOC will process this idoc. As an instance, ORDERS01 with message ORDERS is configured to be processed by FM IDOC_INPUT_ORDERS. Similarly, ORDERS01 + ORDCHG will be processed by IDOC_INPUT_ORDCHG. Likewise, you can see all associations in WE57 for inbound. For out bounds, you would refer to process codes (WE41).
    Segments: The idenfiers in the IDOC structure which indicates the data, their level, state of occurrence....You can take them as records in the IDOC. Each individual segment will come to you as a record in the IDOC. (Go to EDID4, provide an IDOC # and it will list all included segments as records.) Segments are logically nested to indicate various levels of data (header, item etc).
    Qualifiers: Inside the segments, there are fields that can carry actual data often signified by use of qualifiers. A qualifier for a segment field would provide the exact meaning of the data. For example, E1EDK03 segment is configured for dates related data. Segment field IDDAT qualifies the date type and the DATUM field gives out the actual date. So you may see a date qualified as 002, which can be interpreted as requested delivery date. Likewise you can see all qualifiers and their meanings in the associated segment fields in SE12. Give the segment name and go to the domain the ranges for the ID fields.
    How EDI Works
    Sending Data
    •     Computer system serves as a data repository.
    •     EDI extracts information from existing computer applications.
    •     Transmits paperless, computer-readable documents via telephone lines.
    Receiving Data
    •     Fed directly into a computer system.
    •     Automatically processed and interfaced with internal applications.
    Processing Time
    •     Accomplished in minutes.
    •     No re-keying.
    •     No paper shuffling.
    •     No attendant costs of manual document processing and delivery.
    What is the difference between ALE, EDI, IDocs and BAPI?  
    The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    ALE/EDI - Purpose
    Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used for exchanging business data between different systems.
    For both these forms of communication, you require the IDoc Interface. The IDoc interface is made up of the definition of a data structure and the processing logic of this data structure. The data structure is the IDoc. The IDoc is the general exchange format of the communicating systems. IDocs can be sent using different methods (for example,  RFC or as a file).
    Application Link Enabling (ALE)
    You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems. ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
    1.     ALE enables the integration of business processes across several SAP or non-SAP systems.
    Electronic Data Interchange (EDI)
    You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor). The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12). This enables communication with non-SAP systems.
    1.     By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message. 
    IDoc Interface/ALE
    Purpose
    The IDoc interface exchanges business data with an external system.
    The IDoc interface consists of the definition of a data structure, along with processing logic for this data structure.
    The data structure is the IDoc. The IDoc is the exchange format common to all the communicating systems. You can specify exception handling in the SAP Business Workflow, with IDocs, without the data already having to exist as SAP application documents.
    You need the IDoc interface in the following scenarios:
    Electronic data exchange (EDI)
    Connect other business application systems (e.g. PC applications, external Workflow tools) by IDoc
    Application Link Enabling (ALE).
    Application Link Enabling (ALE) is a technology to create and run distributed applications
    Hope this would help you.
    Reward points if helpful.
    Vamsi.

  • Diff... between  ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify

    Hi All
        I am learning XI and the difference between " ALE, IDOC, RFC, BAPI, BADI "
        Not clear and when to use what and how in point of XI ?
       Pl..clarify me
    Adv..thanks and points
    --- Rakesh Behera

    Hi
    This will expalin you every thing ...pl..go through
    The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    I hope this will help you to understand the difference bet..those
    regards
    --- prasad

  • ALE / EDI as used in Sales and Distribution

    Hi All,
    I know the basic difference between ALE and EDI and the commonalities too.
    I just read the info at http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5bea85b11d6b28500508b5d5211/content.htm
    With regard to Sales and Distribution
    What I seek now is real world example(s) of where to use ALE / EDI or more importantly
    WHERE NOT TO use ALE / EDI.
    Simply put what would be the ideal candidate (scenarios) for using ALE / EDI or not using them.
    Thanks in advance.

    hi,
    this is to inform you that,
    wwwdotsaptechnicaldotcom
    in this go for tutorials and select ALE/IDOCs
    balajia

  • Diff. b/t ale & edi

    Hello,
         Tell me exact difference between ALE and EDI in Idoc's.which is used for sap to sap and sap to non-sap.

    The diff betn EDI and ale can be as follow,
    1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
    2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself
    Check the link below:
    ALE:
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Please check this online document for ALE and IDoc.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Also check this links for additional information.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    IDOCS
    http://idocs.de/www5/books/IDocBook/IDOCS_CHAP09-11.pdf
    http://idocs.de/cookbooks/idoc/cb12_idoc_20_outbound/idoc_outbound_45_rsnast00/docu.htm
    IDOC / ALE Blogs
    /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
    /people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
    EDI:
    Advanced guide to EDI configuration
    http://www.erpgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc
    EDI Architecture
    http://www.cs.jyu.fi/el/tjtl63/Antin_esitys/sld003.htm
    Overview of EDI and the IDoc Interface in SAP
    http://sap-idoc2edi-consulting.com/pdfFiles/EDI_IDoc_Overview.pdf
    How to Build a Basic EDI Interface Using an Imported Schema and Map
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/818a20be-0601-0010-e3b8-ac3d5f975319
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d98675ca-0d01-0010-c5a0-c70389f1a314
    EDI Functional Design
    http://www.erpgenie.com/sapgenie/docs/interface_function_specification.doc
    Thoughts on EDI in an SAP XI Environment
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    Reward points if this helps.

  • Hi gurus what is the difference between EDI & ALE.

    hi gurus what is the difference between EDI & ALE.

    HI,
    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 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 u2013 Benefits
    Improves data accuracy u2013
    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  of orders. When  scheduling information is transmitted with ordering  data, companies can plan production more accurately and thus reduce stock investments.
    Reduces technical complexity related to data interchange u2013
    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 u2013 ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers.  Application Services  Distribution Services  Communication Services
    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 u2013 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

  • Difference between EDI and ALE.

    Hi gurus,
         Let clarify my confusion in difference between EDI and ALE.please give a proper example for the same.
         please have a look my confusions as mentioned below:
        Case 1--In same company,suppose we r using two clients 417 and 416 and want to transfer sap data between these two clients.Then which process (EDI or ALE) has to be follow?
         Case2--Suppose want to transfer data from SAP system to non SAP system then which process(EDI or ALE)  has to be follow.
    Regards
    Ashish K

    Hi,
    Follow the links on ALE and EDI
    http://help.sap.com/erp2005_ehp_02/helpdata/en/a5/63240543a211d189410000e829fbbd/frameset.htm
    http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
    http://www.wb.nic.in/internet/edi.html
    In both cases you can use any one either ALE or EDI.
    Rgds,
    Suman

  • DIFFERENCE BETWEEN BAPI AND ALE

    HI
    COULD ANYBODY TEL ME
    DIFFERENCE BETWEEN BAPI AND ALE

    Hi Kalyan
    ALE is a SAP specific method how to distribute data from and to SAP. It uses the asynchronous calls based on IDOC structures.
    However in the distribution modell of ALE can also be used BAPIs. They will then automatically converted into IDOC structures. After creating the IDOCs they will be passed over to the receiver using the tRFC protocol.
    Wheras the BAPIs are using the sRFC protocol.
    fir more information please check this:
    http://www.sap-img.com/abap/ale-bapi.htm
    regards
    Srinivas

  • Differences between rfc and ale/idoc.

    hi ..
           will u please send the differences between rfc and ale/idoc's.

    Hi,
    Please reward with points if helpful................
    ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
    For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
    Means of creating and operating distributed applications.
    The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
    Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
    Application Link Enabling comprises the following three layers:
    application services
    distribution services
    communication services
    Two Development Models
         Distribution using BAPIs
         Distribution using Message type
    The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
    Defining message types and IDoc types:
    If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
    The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
    Writing ABAP code:
             Outbound Processing
               Inbound Processing
    You can find information on other ALE functions under:
                                   Master Data Distribution
                                  Communicating with Non-R/3 Systems
    1. The Remote Function Call facility allows you to call an R/3 Function module on a “remote” machine.
    2.  To communicate between two R/3 Systems and also with an External System.  External Application program also can call these function module for integration.
    3. RFC or sRFC  - Synchronous RFC
                     aRFC - Asynchronous RFC
                      tRFC - Transactional RFC
                      qRFC - Queued RFC (I.e. Serialization of tRFC)
    Types of RFC Call
    Synchronous
    CALL FUNCTION Func Destination Dest
    CALL FUNCTION func DESTINATION 'NONE' ...
    CALL FUNCTION func DESTINATION ’BACK' ...
    Asynchronous
    CALL FUNCTION func … STARTING NEW TASK taskname
    PERFORMING form ON END OF TASK
    RECEIVE RESULTS FROM FUNCTION func
    Thanks
    sivaparvathi

  • Dieffrence between ALE (Application Link Enabling ) and EDI

    Dear Experts
    can you pls. explain me the dieffrence between ALE (Application Link Enabling ) and EDI (electronic data interchange)
    especially regarding transfer (transmission).
    Regards
    Marco
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Jan 25, 2012

    Dear Experts
    can you pls. explain me the dieffrence between ALE (Application Link Enabling ) and EDI (electronic data interchange)
    especially regarding transfer (transmission).
    Regards
    Marco
    Moderator message: please search for available information/documentation.
    Edited by: Thomas Zloch on Jan 25, 2012

Maybe you are looking for