6 Replies Latest reply: Jul 1, 2010 7:45 AM by Guest RSS

ALE , EDI and IDOC with MM??

MM team
Currently Being Moderated

hii

 

What is ALE, EDI and IDOC in SAP??

 

How its linked with MM??

 

Explain the above things with example

 

Thanks

  • Re: ALE , EDI and IDOC with MM??
    Erika Szanto
    Currently Being Moderated

    Hi!

     

    IDOC = Intermediate Document

    IDoc or Intermediate Document is a standard SAP document format. IDoc's allow different application systems to be linked via a message-based interface.

    For more detailled information look in SAPNET under

    http://service.sap.com/EDI

    For exapmle in purchasing:

    The IDoc message type ORDERS is used to send a purchase order to a vendor.

     

    ......................................................................................................................................................................................................

    EDI = Electronic Data Interchange

    EDI stands for Electronic Data Interchange, which means that data is electronically transmitted from one system to another. The main requirement of EDI is that the systems of the communicating partners understand each other. Usually, the data from one partner gets mapped into the format of the other partner and vice versa.

    Supporting this there exist EDI standards (named EDIFACT, ANSIX12, ODETTE, VDA, TRADACOMS, SPEC2000, ...), where the data formatting for exchanging documents are specified. Normally the partners agree using a special standard message (for example EDIFACT message ORDERS for a purchase order).

    In the SAP system the outgoing data are stored in IDoc format. When processing a receiving document, the Inbound SAP system receives the data in IDoc format too.

    Further processing (converting/mapping from IDoc in another format and vice versa) depends on the partner agreement:

     

    If the partners have agreed using a special EDI standard, mapping between IDoc and  the  EDI standard is necessary. This mapping is not supported by SAP, external converters or EDI subsystems must be installed by the customers for this purpose.

    If both systems use SAP software, there is usually no need for mapping  (which can save users a lot of money). The two systems are often connected via ALE (Application Link Enabling).

    If partners are using XML, the SAP Business Connector can be used. The business connector is a tool used to help customers connect via EDI. It includes routing and mapping and is XML compatible. To read more about XML at SAP go to SAPNet Alias 'XML' (http://intranet.sap.com/XML).

    For example:

    Vendor can send the invoice by EDI creating an IDoc with message type INVOIC using IDoc Type INVOICxx. He can determine (depending on the partner agreement) how to create an IDoc for Inbound processing with FI or MM-IV.

    ...............................................................................................................................................................................................

    ALE  = Application Link Enabling

    ALE is short for Application Link Enabling. Special Basic programs support this functionaliity (see documentation of BC_MID_ALE).

    To link applications you have to configure an ALE model. It contains all relevant data about how a system's configuration (normally a central system and assigned local systems) exchange data.

    With help of the ALE technology, the distribution of contracts is possible in MM via the following business process:

     

    Contracts that a central purchasing organization distributes to local purchasing organizations to allow the latter to utilize the more favorable conditions they contain for the procurement of materials or external services.Each local purchasing organization sends information on its own release orders back to the central purchasing organization.

     

    For this purpose the contract in the central system can be copied to the local systems (with message BLAORD and COND_A). When a release order to a distributed contract is created in a local system, the release docu is automatically sent to the central system (with message BLAREL) updating the release docu of the contract in the central system.

    Precondition for this scenario is, that in all systems the used master data (material, vendor, sources of supply, ...) are the same. This master data can be distributed by ALE, which should be done before sending the contract from the central system. Available message types  for distribution of master data are:

     

    MATMAS (ARTMAS in retail system) for material master

    CREMAS for Vendor master

    INFREC for  info record

    SRCLST for source list

    COND_A for conditions of info record

    SRVMAS for service master data

    ...

    Technical documentation to ALE can be found by path:

              Basis Components / Middleware (BC-MID) / Application Link Enabling (BC-MID-ALE)

    .................................................................................................................................................................................................

    The most important Transactions for testing Idoc:

     

    WE02 Display IDOC

    WE05 IDOC list

    WE19 Testing IDOCs

    BD87 Status Monitor for ALE Messages (reprocess)

     

    ................................................................................................................................................................................................

    Notes:

    456127 FAQ: Electronic Data Interchange (EDI) in Purchasing

    536411 Sample scenario for ALE contract distribution (only internally released)

     

    I hope I could help you fruther

    Best regards

    Erika

  • Re: ALE , EDI and IDOC with MM??
    Raja Ramasamy
    Currently Being Moderated

    ALE - Application link enabling - To connect different SAP systems or connect SAP system to non- SAP system for document /master data exchange

     

    IDOc- it is data container whcih carries the business data (transaction data or master data)to other system.

     

    With refence to MM:

    PO created in our SAP system will flow to vendor as a IDOC and create SO in vendor system provided both systems are connected through ALE /EDI to avoid processing time.

    For more  info refer

    http://wiki.sdn.sap.com/wiki/display/ABAP/ALEandIDocs

     

    To understand more you should have worked in big organisation which has multiple systems for their day to day business transactions .

  • Re: ALE , EDI and IDOC with MM??
    Currently Being Moderated

    ALE

     

    Outbound:

    Step 1. Application document is created when transaction is saved.

    2. Message control is invoked.

    3. Messages are processed by system.

    4. Messages are Edited (if desired).

    5. Output (ALE / EDI) is checked

    6. Validate against Message control record from Partner Profile

    7. Application Document is saved.

    8. Entry NAST table is created for every selected output program

    along with Medium & Timing.

    9. Check for Process Immediately .

    If (yes)

    Determine Processing Program from TNAPR Table.

    ELSE

    Execute RSNASTED Program.

    10. Read Partner Profile to determine Process Code.

    11. Process Code points to the Function Module & Invoked.

    12. IDoc is generated.

    13. Check for ALE Request.

    if (Yes)

    Perform Filters, Conversions, Version Changes etc.

    Else.

    IDoc is stored in DATABASE.

     

    INBOUND:

    Step 1. EDI Subsystem creates an IDoc file from EDI Messages

    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.

    3. Data in Control Record is validate against the Partner Profile.

    4. IDoc is generated in Database and syntax check is carried out.

    5. IDoc file is deleted once file read.

    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.

    7. Check for Process Immediately.

    If NO

    Execute RBDAPP01 Program

    Else

    Read Process Code from Partner Profile

    Process Code Points to Function Module

    Application Document Posted.

    • Re: ALE , EDI and IDOC with MM??
      Currently Being Moderated

      EDI = Electronic Data Interchange

       

      Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.

       

      Refer

      http://www.erpgenie.com/sapedi/index.htm

      http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm

      https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp

      http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/

      http://www.erpgenie.com/sapedi/index.htm

      http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd

       

      EDI FLOW :

       

      Here is some thing which helps you and here the purchase order is taken as example too..

       

      Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.

       

      What parts of the business cycle can be supported by EDI?

      Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.

       

       

      How does EDI get started?

      EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.

       

       

      What is the flow of EDI?

      The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.

      • Re: ALE , EDI and IDOC with MM??
        Currently Being Moderated

        IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

         

        A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

         

        IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

         

        An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

         

        Check these links for IDOCs

        http://www.sappro.com/downloads/OneClientDistribution.pdf

        http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

        http://www.sapgenie.com/sapedi/idoc_abap.htm

  • Re: ALE , EDI and IDOC with MM??
    Currently Being Moderated

    HI,

     

    What is 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, 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 are 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.

     

     

    pherasath

Actions