ALE/EDI : IDoc Setup

Hello...
While setting Partner Profile when I am assigning the process code & FM Name it giving me the following error
Application object type is not planned
Message no. B1405
Diagnosis
The application object type '' is not permissible for the input function module 'Z_IDOC_INPUT_ZORDER01'.
Something wrong with the FM I guess.... Some setting I am missing...
Let me tell What all I have done....
(1) WE30
(2) WE81 - Message Type
(3) BD59 - Object Type
(4) WE57 - Linking Message type to FM
(5) BD51 - FM settings
(6) WE20 - Partner Profile....
On step six its giving the above error....
Please Guide how to resolve this issue....
Thanks & Warm Regards
Ankur Jain

Hai Ankur
check the following Links
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
ALE and IDOCs
iDocs
IDOCs !!!!!! need your help
idocs
ALE, EDI and IDOCS
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
ALE---IDOC Creation Steps
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & regards
Sreenivasulu P

Similar Messages

  • ALE,EDI,IDoc,OLE and BAPI

    plsease give the detailed concept for ALE,EDI,IDoc,OLE and BAPI
    awaiting reply
    thanks
    Moderator Message: The long waiting ended...
    Edited by: kishan P on Jan 9, 2011 7:38 PM

    <<non-detailed concept definitions removed by moderator>>
    Edited by: kishan P on Jan 9, 2011 7:36 PM

  • ALE/EDI/IDOC  Material

    Hi Experts,
    i never worked on ALE/EDI/IDOC .. Please send me the links and material about ALE/EDI/IDOC.
    Thanks in Advance
    Thanks,
    Venkatt.

    Hi
      Look at this links
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    http://www.esnips.com/web/ALEIDoc
    Regards
    Haritha.

  • Ale, Edi, & Idoc Technologies by Arvind Nagpal Soft Copy

    Does any one have Ale, Edi, & Idoc Technologies by Arvind Nagpal Soft Copy.
    Please send an attachment to [email protected]
    Or do send me the link

    Hi,
    Based on the business requirements, you may need to do the following actions:
    1) Extending standard Idocs.
    2) Complete custom idoc scenario
    3) Enhancing standard Idoc population programs using exits.
    4) Creating custom segments
    5) Creating partner profiles
    etc

  • ALE, EDI , IDOC'S

    Hi experts,
    I am working in 4.7 and company told me to learn ALE, EDI , IDOC'S.
    As per my knowledge from next version (4.7 onwards) new features are replacing ALE , EDI & IDOC's..
    am i true..do you think this learning help me in coming version also...
    please suggest me..
    thanks
    raj

    hi..
    its true only..but before going into the advanced topis such as <b>XI</b> know some basics of inteface.
    <b>Reward points if useful</b>
    Regards
    Ashu

  • Would you like to send me some Document about ALE EDI IDOC

    hi experts:
    I am learning about ALE,EDI,IDOC,would you like to send me some Document about ALE EDI IDOC?which can include the details of Steps,best it can have the Pictures,thanks a lot.

    Hi Niel,
    There may be a problem with the definition of the rule to delete the characteristic. If you go to transaction RSMRT
    and use the 'check' option to check the rule you created are there any errors for the check?
    If not when you get the error message that you mention is there any additional error messages created in sm21
    or dumps in ST22?
    If not there may be a problem with the consistency of the cube if you goto RSRV>All Elementary tests>Transaction data
    and run these tests for the cubes are there any error messages? If yes please try to use the repair function in RSRV
    to correct any errors.
    If none of the above helps you should delete the run you created, make a dummy change to the cube (e.g add a '.'
    to the description of the cube, save the change and then activate the cube, please then try and create the
    remodelling rule again.
    Best Regards,
    Des.

  • What is Ale, Edi,IDoc tech for sap

    Hi all,
    What is Ale, Edi,IDoc tech for sap?
    Thanks.

    hi deniz,
    <b>ALE</b>
    ALE
    Triggering OB via Change Pointers:
          When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
    Outbound Process:
    When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
    Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
         To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
    Asynchronous Communication:
    The data  that is IDocs and the function module are  stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
    Inbound Process:
    The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
    In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
         Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
    In the table TBD51 there will be entries to find which option is used.
    Transactions:
    SALE - IMG ALE Configuration root
    •     WE20 - Manually maintain partner profiles
    •     BD64 - Maintain customer distribution model
    •     BD71 - Distribute customer distribution model
    •     SM59 - Create RFC Destinations
    •     BDM5 - Consistency check (Transaction scenarios)
    •     BD82 – Generate Partner Profiles
    •     BD61 – Activate Change Pointers - Globally
    •     BD50 – Activate Change Pointer for Msg Type
    •     BD52 – Activate change pointer per change.doc object
    •     BD59 – Allocation object type -> IDOC type
    •     BD56 – Maintain IDOC Segment Filters
    •     BD53 – Reduction of Message Types
    •     BD21 – Select Change Pointer
    •     BD87 – Status Monitor for ALE Messages
    •     SALE – Display ALE Customizing     WEDI - ALE IDoc Administration
    •     WE60 - IDoc documentation
    •     SARA - IDoc archiving (Object type IDOC)
    •     WE47 - IDoc status maintenance
    •     WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    •     WE05 - IDoc overview
    •     BD87 - Inbound IDoc reprocessing
    •     BD88 - Outbound IDoc reprocessing
    •     BDM2 - IDoc Trace
    •     BDM7 - IDoc Audit Analysis
    •     BD21 - Create IDocs from change pointers
    •     SM58 - Schedule RFC Failures
    <b>EDI</b>
    EDI(Electronic Data Interchange )
    RFC DESTINATION:
                           A logical name used to identify the remote system on which a function needs to be executed.
    Partner Profile:
          It defines the characteristics of data being exchanged with the business partner.
    Partner Function:
         Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
    Partner type:
              The type of your business partner .
         EDI        – KU/LI
         ALE     --  LS.
    Archiving:
         -Need to archive the important transmitted document
    -Created in SARA
         -Assigned in WE20.
    PartnerProfile Tips:
    •     RSECHK07- Consistency check for Partner Profile.
    •     If you want to modify partner profile; copy it and then modify. If you can’t modify it , u have  to delete it.
    •     To move partner profile to production system choose Partner ->  Transport
    Port defintion:
         It defines the medium through which data is exchanged between systems.
    •     tRFC    -   Used by ALE
    •     FILe     -   Used by EDI
    •     R/2 system system port  – For R/2 system
    •     Internet port           - to connect with internet applications
    •     It also depends on the  receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
    Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
    Startrfc                                         -   Program to execute RFC – enabled Fun.mod. in SAP
    EDI_DATA_INCOMING             -   To send data as inbound
    EDI_STATUS_INCOMING         -   To send status to SAP
    RSPARAM               -   To know the gateway service of the SAP system.
    Message Control:
    •     Output controller
    •     A service program for determining the output type
    •     To generate and manage various outputs from an application and control their medium and timing of exchange.
    •     To retransmit the document without duplicating it
    Procedure:
    •     A procedure defines a set of possible outputs for an application
    •     There may be more than one procedure but only one can be active
    •     Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
    Output type:
    Defines the characteristics and attributes of the output.
    Access Sequence :
    Defines  a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
    Sapfans Q & A
    SREL_GET_NEXT_RELATIONS   -
    Function Module that will provide me the number of the document that was created by an IDoc
    RLSUB020
    Program which uses the above function module.
    Upgradation problem
    When the old version program is upgraded in to newer version(4.0b &#61664; 4.6c) the SE38 editor won’t allow u get thru’ the programs normally to get rid of this.
    Solution:
    EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
    When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
    this fixes the links
    ALE( Application Link Enabling )
    Disk Mirroring:
    Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disk’s contents.
    Replicas:
    Maintaining redundant data across multiple systems.
    ALE:
      It provides distributed environment to integrate non-SAP systems
      Provides guaranteed delivery of data regardless of network problem to application.
    Logical system :
         The systems involved in distributed environment  are assigned a logical name which uniquely identifies a system in a distributed  environment.
    Data Mapping:
         Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
    Message Types:
    •     Represents a business function
    •     Technical structure is the IDoc type
    •     Or can say an instance of IDoc.
    <b>IDoc  :</b>
         They are containers used to exchange data between any two process.
         It represents an IDoc type and IDoc data
         IDoc type is structure and IDoc data is an instance of it.
    <b>Pls reward if helpful.</b>

  • ALE EDI /IDOC Documents needed

    Hi All,
      Can any body send the ALE ,EDI and IDOC Dcouments with live examples.
      My mail id is : [email protected]
    Thanks and Regards,
    Muralikrishna

    Hi
    IDOC
    Data Creation in Idoc
    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.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Check these links.
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    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
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    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.
    check this.
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.sapgenie.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
    ALE
    Application Linking and Enabling (ALE)
    In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
    For our purpose we have two clients
    namely Client 100 and Client 200.
    System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
    Distribution of Material Master Data Between two Systems
    1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
    To do this follow the following steps
    Execute SALE Transaction Code
    On The Screen Click on Sending and Receiving Systems.
    Then Click on Logical Systems.
    Then Click Defining Logical Systems.
    Click New Entries Button
    (E.g. (LG100 sending system)
    (LG200 receiving system))
    Enter two logical system names and their description.
    Save
    Comeback to SALE Transaction Code screen.
    2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
    LG100 assign to client 100
    LG200 assign to client 200
    To do this, do the following.
    Click Assigning Client to Logical System.
    Ignore the message that comes up on the screen.
    Select client 100
    Click details button on the toolbar icon or press F2.
    In the logical system box, enter LG100.
    Click on the save Icon
    Click the back button.
    Now select client 200.
    Click details icon or press f2.
    In logical Systems box, enter LG200.
    Save
    Back.
    Comeback to SALE Transaction Code screen.
    3) Maintain RFC Destination: (TR.CODE:SM59)
    (Note: Do Not Create This Step)
    Click Create Button on the Screen
    On the Screen Maintain RFC Destination i.e LG200.
    Enter LG200 in RFC destination box.
    Connection type is 3
    Give a description for the RFC destination.
    Maintain Technical Settings on Details on Technical Settings tab
    Target Host as : SAPKDC (NOTE: Save it as a Host Name)
    Maintain Logon Details on Logon/Security tab.
    Language: EN.
    User: MMUSER200 (This is the logon for dist.)
    Client : 200
    Password: MM1234.
    Save.
    Click on create to do the above process for Client 200 in
    The client 200 system.
    4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
    Execute Maintain distribution model directly for
    creating the model.
    Click on change mode button on App tool bar of the Screen.
    Create Model View pushbutton on App tool bar of the Screen.
    A pop screen will appear in which you specify
    Short text as Distribution for MM Data.
    Enter Technical Name as LGMODEL.
    Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as LGMODEL.
    Sender as LG100.
    Receiver as LG200.
    Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
    A popup screen will appear in which you specify
    Model View as LGMODEL.
    Sender as LG200.
    Receiver as LG100.
    SAVE.
    On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Logical System as LG200.
    Then execute the screen.
    Click back.
    Again On the same screen goto Menubar and select EDIT.
    Again select Model View and then select Distribute.
    ****LOGIN to client 200.
    Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
    And then select Generate Partner Profiles , then execute it.
    On the Screen specify the Model View as LGMODEL
    And Specify the Logical System as LG100.
    Then execute the screen.
    Click back.
    *******Switch back to client 100 Session.
    5) Create Material using MM03 Tr.Code.
    Enter the material name as LGMATERIAL
    Industry sector as Mechanical Engineering
    Material Type as Finished Products.
    And then Click on Data Pushbutton on the App tool bar.
    Select views.
    In the select views box for materials check basic data 1 AND 2.
    Click enter icon.
    In the next screen that you get
    Give the text of the material as NEW MATERIAL.
    Base unit of measure as KG.
    Gross Weight as 200.
    Net Weight as 100.
    Weight Unit as KG.
    In the description area language (E) and material description.
    Click Save.
    Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
    6) Execute BD10 to transfer the material in which you specify
    the material as LGMATERIAL and
    message type as MATMAS (client100).
    Then a Screen will be displayed in which it shows that
    1 Master Idoc Generated .. Enter
    1 Communication Idoc Generated..Enter.
    *******LOGIN to Client 200.
    7) Execute BD11 to get the material in which you specify
    the material as LGMATERIAL and
    message type as MATMAS (client200).
    8) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    If not follow these steps.
    9) Execute Tr.code WE19( for rectification of errors in client200).
    Specify the Existing Idoc Number and Executes it .
    A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
    10) Execute Tr.code MM03 and give the material as LGMATERIAL
    and see that the material is displayed as it was in Client 100.
    Now the Material is correctly displayed in Client 200.
    11) Monitoring of IDOCS.
    Transaction Codes:
    IDOC Display of Status: WE 05.
    IDOC Date and Time: WE07.
    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.
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Regards

  • ALE ,EDI ,IDOC?

    hi SAP gurus
    can u send me steps on ALE,EDI and IDOC s
    [email protected]
    points will be rewarded

    Hi,
    ALE and IDOC:
    ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .
    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.
    It is the the combination of Segements.
    Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).
    Idocs Type is a Structure by lot of segments.
    IDOC is generared at the time of run time .
    It will have the data.
    There are basically two types of IDOCs.
    Basic IDOCs : Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs : Extending the functionality by adding more segments to existing Basic IDOCs.
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    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
    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
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Need info on automatic determination of tax code at PO
    Hope this will help.
    Regards,
    Naveen.

  • ALE/EDI/IDOCs

    Hi Friends,
    Please send me some good documents on ALE,EDI and IDOCs.
    Some step by step documents and documents related to all the related transactions will be most welcome.
    Mukesh Kumar

    Hello,
    I have created a customised IDOC scemnario and have a document designed by me with all the minute steps and with screen shots.
    Please have a look at http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
    Please reward points if useful.
    thnx
    Link for that is:
    http://www.erpgenie.com/sap/ale/whitepaper.htm
    ==============================
    Other helpful links
    http://www.sapgenie.com/whitepapers/ale.htm
    http://www.sapgenie.com/ale/index.htm
    http://www.sappoint.com/abap.html
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
    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/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    Please reward points if useful.
    thnx

  • Learning map - XI, ALE, EDI, IDOC

    Hi all!
    I´m trying studying IDOC but it´s complicated. I found many documents talking about EDI, ALE and XI.
    I don´t know many things about EDI, ALE and XI. So, my question is: Have i to start studying about this topics (ALE, EDI and XI)?? I think that i need understand this terms for after to learn IDOC.
    If the answer is YES, wich one should be first one?
    Somebody has any document or link about this topics? I lookup in SDN Articles and Blogs but i didn´t find anything.
    Thanks a lot!

    Hi,
    Please go through  following Link,
    https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
    https://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS
    https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
    Thanks & Regards,
    ShreeMohan

  • Need Material on ALE,EDI & IDOCs

    Hi Friends,
    i need some material and some example code on ALE or IDOCs.. or plz let me know if u have anygood links.
    Thanks
    Kali Pramod

    Hi,
    ale/idoc
    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
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    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
    http://www.allsaplinks.com/idoc_sample.html
    Regards,
    Sailaja.

  • ALE/EDI /IDOCs(sap-abap)

    Hi Friends,
        Could u pls send one simple example of Inbound Interface and Outbound Interface with screen shots  and also programings.
    MY id - [email protected]
    every suitable answers will be reward points.
    Thx and Regds,
    Bapi

    HI,
    i am sending one pdf file check it.
    also check this link
    http://www.erpgenie.com/ale/why_ale.htm
    reward if helpful
    rgds,
    bharat.

  • 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.

  • Documentation of ALE and IDOC

    Hi,
    I am Beginer of ALE and IDOC .Could you please provide the processing documentation of ALE and IDOC with an example.
    Thanks
    Satya

    Hi,
    Read out ALE, EDI & IDOC of Arvind Nagpal. Its a very good book to understand the ALE\IDOC Concept.
    or
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
    Regards,
    Narendra
    Edited by: Narendra GSTIT on Jun 14, 2010 3:01 PM
    Edited by: Narendra GSTIT on Jun 14, 2010 3:03 PM

Maybe you are looking for

  • Safari and the messages app dissapered on my iPad.

    Safari and the messages app dissapered on my iPad and I don't know what happened or how to get them back. The restrictions are off and I treys to search for them but they still didn't show up. I need help!

  • [SOLVED] Sound card not recognized

    I tried following the ALSA setup guide on the Wiki to get my sound working but I don't think Arch recognizes my sound card.  I found out from lshwd that the module is snd-intel8x0 so I modprobed that and snd-pcm-oss, changed the values in alsamixer,

  • Big Delay

    Hi Everyone I mirror my Imac to the TV screen using Airparrot. Why Do I see A big delay bitween the Imac and the TV screen? I'm talking about 3-5 seconds delay thanks

  • Privileges on script from another partition

    Hello all, I currently encounter an error when I try to execute a process chain using indirectly the script RSI.RSI_RUN_BW_CHAIN though a customized script. Here is the idea: I use a script "P.S", that belongs to a distinct partition P, in which ther

  • Where to find SOS.dll for silverlight 5

    I wan to use windebug to debug a Silverlight issue, and some doc told me that SOS.dll is needed to analyze managed  code. However, I cannot find SOS.dll under C:\Program Files (x86)\Microsoft Silverlight\5.1.30514.0 or C:\Program Files\Microsoft Silv