ALE settings for IDOC2FILE Scenario

Hi All,
I have the requirement to work on IDOC2FILE scenario. i am not able to do the ALE settings well in both R/3 side and XI side. Anybody have the full documentation with step-by-step analysis, please send me ASAP. Please help me in this regarding.
I am very thankful to you all in advance.
Regards,
Nag.

Hi Nagarjuna kumar  ,
The following websites give u step-by-step solution for ALE settings for IDOC2FILE Scenario:
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
cheers!
gyanaraj
****Pls reward points if u find this helpful

Similar Messages

  • Doubt regarding  ALE SETTINGS in IDOC scenario.

    Hi Friends,
            I have some doubts regarding ALE settings for IDOC scenarios,  can anyone  please clarify my doubts.
    For exmaple take IDOC to FILE scenario
    The knowledge i got from SDN is --
    One need to do at the  R3 side is  --- RFC DESTINATION (SM59)  for the XI system.
                                                       --- TRFC PORT  for sending IDOC  to the  XI system
                                                       --- CREATING LOGICAL SYSTEM
                                                       --- CREATING PARTNER PROFILE 
                   at the XI side is  --- RFC  Destination ( For SAP sender system)
                                           --- CREATING  PORT  for receiving IDOC from the SAP sending system(IDX1).
    1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
    In IDOC to IDOC scenario-------
      2.  Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
      3.  If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
    y we r creating receiver communication channel in the case of FILE to IDOC scenario?
      4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                    FILE to IDOC scenario,                                                                               
    IDOC to IDOC scenario individually.
    Thanks in advance.
    Regards,
    Ramana.

    hi,
    1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
    it is a mandatory step in doing ALE configurations
    2. We create 1 RFC destination each in R3 and XI.
        R3 RFC destination points to Xi and
        XI RFC destination  points to R3
    3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
    4. ALE settings for all IDOC scenarios are same  as follows....
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    Reward points if helpful
    Prashant

  • ALE Settings For File-IDOC  Scenario

    Hi All,
    While Doing IDOC-File Scenario we have to do the Following Settings
    In XI
    1) Create RFC Destination towards R/3
    2) Create Port
    3) Load Meta data
    In R/3
    1) Create RFC Destination towards XI
    2) Create Port
    3) Create PF
    Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
    Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
    Clarify me these Confusions
    Regards
    Bopanna

    HI,
    for IDOC TO FILE
    We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
    There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
    i.e for FILE-IDOC
    1) No need to Distribute the modal view
    2) For partner profile Specify the INBOUND PARAMETERS
    FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Receiving System in transaction code (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code  IDX1
    a)   Select Create New button
    b)   Enter the port name as SAP+SID (The starting char should be SAP)
    c)   Enter the destination client
    d)   Enter the RFC Destination created in XI towards R/3
    e)   Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (SM59)
    a)   Choose create
    b)   Specify the name of the RFC destination
    c)   Select connection type as 3 and save
    d)   In the technical settings tab enter the details SAP SID/URL and system number#
    e)   Enter the Gateway host as same details above SID/URL
    f)   Gateway service is 3300+system number#
    g)   In the Logon /Security tab, enter the client, user & Password details of Destination system
    h)   Test the connection and remote logon.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(We21)
    a)   First Select Transactional RFC and then click create button
    b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Inbound Parameters (WE20)
    a)   Create New
    b)   Create the Partner no. name as same the logical system name of the destination system
    c)   Select Partner type LS
    d)   Enter details for Type: US/USER, Agent, and Lang
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Message Type and Process Code.
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
    PLZ REFER THE LINK BELOW.
    PLZ REWARDS THE POINTS
    VIKAS JAIN
                                                                                    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
    Edited by: vikas jain on Jan 22, 2008 11:49 AM

  • ALE Configurations for IDOC2IDOC scenario

    Hi Experts,
    Can anyone list down wht r the ALE configurations are required for IDOC2IDOC scenario?
    1. Sender SAP ---> XI
    2. XI ---> Reciever SAP
    Please provide me the TCodes with the details that are needed for the above scenario?
    Your help is higly appreciated
    Rgds
    Faisal....
    Edited by: Abdul Faisal on Jul 28, 2008 11:49 AM

    Hey,
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create partner profile.
         Give the outbound or inbound message type based on the direction.
                    In your Sender R3:- outbound
                    In your Receiver R3:- Inbound.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    WE42 process code
    WE47 status info.
    <removed by moderator>
    regards,
           Milan
    Edited by: Mike Pokraka on Jul 28, 2008 5:04 PM

  • ALE Settings for IDOC Processing

    Hi,
    Can anybody tell me what all the ALE settings I have to look for any IDOC.
    Thanks,
    bsv.

    Hi,
    Please check this link for ALE setup for inbound and outbound processes.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    Regards,
    Ferry Lianto

  • ALE Settings for IDOC

    Hi,
    For configuration of IDOC adapter
    1) we need to create RFC Desination  both XI System and R3 System.For port creation if v given same port name  in both XI system and R3 system it will work or not ?
    2) On Receiver SAP system, we need to configure the logical system normally for XI system, were v can find logical system of XI System.
    3) Can RFC Destination  b same on both systems( R3 system, XI System)
    Regards,
    Praveen

    Hi
    The following configurations are needed for Idoc scenarios
    1) ECC Configuration :  a) Create RFC connections from ECC to XI in SM59. rfc connection name should be target XI logical system name .  BD54 or SALE are the tcodes for checking the logical system for respective client.
                                       b) Create port in we21 & provide the above RFC destination.
                                       c) Now Create Partner Profile in we20 ...partner profile name should be target logical system name.
                                            assign the outbound parameters with receiver port created in we21.
    2) XI Configuration : a) Create a RFC connection for XI to ECC ...rfc name should be target logical system name(ecc).
                                      b) Create port in IDX1...it should be SAPXXX..where XXX is the ecc system id.
                                      c) Import the idoc metadata in IDX2.
    For Outbound idocs generate the model view in BD64.
    Regards
    Abhijit

  • Configuring settings for proxy scenario.

    Hi experts,
    I have SAP R/3 and XI system, need to execute a proxy scenario.
    What all configuration settings have to be done for the proxy part in both XI and SAP system.
    Please help with links to some good blogs.
    Thanks,
    Younus

    Hi,
          There are two Types of proxies which can be done by ABAP or JAVA
    ‘client’ proxy is used by an application to send messages outside of the system it resides in (normally to the IS in this context).
    ‘server’ proxy is used by an application to receive messages from sources outside itself (again, normally the IS in this context).
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
    ABAP Proxy
    How do you activate ABAP Proxies?
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    ABAP Proxy Runtime
    http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
    ABAP CLIENT PROXY
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    ABAP SERVER PROXY
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies. [original link is broken]
    To test a connection - /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    XI: Debug your inbound ABAP Proxy implementation
    Testing proxy - /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
    JAVA Proxies:
    Asynchronous inbpund java Proxies
    /people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
    Hi,
    Proxy Generation- For ABAP and Java proxy, create a Message Interface and then generate a proxy for that message interface.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
    More on Java Proxy-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
    ABAP Proxies:
    Integration Builders through proxy server (Part - 2)
    /people/sap.user72/blog/2005/12/13/integration-builders-through-proxy-server-part--2
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    ***Assign points if you found helpful
    Regards.,
    V.Rangarajan

  • ALE settings for MIRO outbound IDOC

    PLz tell Output Type, Process Code etc...for MIRO outbound.
    for inbound i am using INVOIC01..
    Thanks and regards

    Hi madan,
         u can use the transaction NACE to find out the output type of MIRO.
    If u know the function module u can able to find the process code easily.
    Since function module names are based on message types.
    Regards...
    Arun.

  • R3 settings for IDOC-IDOC scenario

    Hi,
    For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
    What are setting for both sender and receiver side.
    Thanks,
    Kishore

    Hi Kishore,
    http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
    http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
    http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    Refer this material..
    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.
    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.
    You can directly create an iDoc using some transaction like...
    Use TCODE bd10 - to Send Data
    and TCODE bd11 - to Get Data
    and you can check the IDoc List using TCODE we02.
    As you want step by step procedure.
    1. Define Logical System and Assign Logical System
    TCODE sale
    2. Define RFC
    TCODE sm59
    3. Define Port
    TCODE we21
    4. Define Partner Profile
    TCODE we20
    5. Define Distribution Model
    TCODE bd64
    6. Send Data
    TCODE bd10
    7. Get Data
    TCODE bd11
    8. IDoc List
    TCODE we02
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    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.
    Create IDOC Type
    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
    u can also check all these links related to 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
    Reward points if this helps
    Regards
    Pragathi.

  • ALE settings error   "Too many recipients found for message type" urgent

    Hi all ,
    please help me to solve this issue !!!!!!!!
    i done with ale settings .
    in the bd64 , orders message type is used in 2 different model view for 2 different systems
    when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
    how can i rectify this error.
    Thanks

    Hi,
    Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
    Regards,
    Jakub

  • Settings for Purchase Order output using services for MM-SUS scenario?

    Dear Gurus,
    I am configuring the service procurement classic and plan driven procurement for MM-SUS
    environment. We are on SAP SRM 7.01/ECC 6 EHP5.
    I need to maintain the below settings for PO output:
    1. RUN transaction SWETYPV
    2. IN the object types field, enter CL_SE_PUR_WF_OUT.
    3. In the event field, enter CREATED.
    4. In the receiver type field, enter WS53800008.
    5. In the receiver function module field, enter SWW_WI_CREATE_VIA_EVENT_IBF.
    6. Select the 'Linkage Activated' checkbox.
    7. Save your entries.
    Similarly, one more entry for the event CHANGED.
    However, the system is not allowing me to save the settings.
    If I choose BOR Object Type 'CL_SE_PUR_WF_OUT', it gives an error message 'Object type CL_SE_PUR_WF_OUT is not defined'.
    If I choose object category 'Business class for object type CL_SE_PUR_WF_OUT, it gives an error message 'Class CL_SE_PUR_WF_OUT is not a business class.'
    There are similar entries in the table SWETYPV for object type CL_SE_PUR_PO_WF_OUT' with object category CL.If we copy the entries and tries to replace the
    object type 'CL_SE_PUR_PO_WF_OUT' with CL_SE_PUR_WF_OUT and save it, it gives an error message 'CL is not used for workflow event'.
    Could you please help me on how to configure the settings for PO output from ECC system using services?
    Any input is highly appreciated.
    Thanks and regards,
    Ranjan

    Hi Ranjan,
    Please add the value 'CL' in the table SWF_CATIDS
    Then it will work.
    With Regards,
    Malay

  • How to test IDOC2FILE Scenario

    Hi All,
    Now i am working on IDOC2FILE scenario. I have done all ALE settings in R/3 side with RFC destination, port, Partner profile.
    At XI side i created RFC destination, Port and Partner profile also.
    And i pushed the idoc from R/3. I got the status messages  like
    "IDoc: 0000000000001018 Status: Data passed to port OK" and "IDoc sent to SAP system or external program".
    But in XI,  i got the following messages:
    "IDoc: 0000000000005005 Status: Application document not posted" and
    "Function module not allowed: APPL_IDOC_INPUTI".
    All my design time and configuration time objects are done and activated.
    Here i am using the business service for sender system. sender is R/3 system.
    Anybody, came across this problem, could you please revert back to me with solution. I want step-by-step testing procedure.
    Please getback to me with proper solution asap.
    Thanks & Regards,
    Nagarjuna.

    Hi Sarvesh,
    Thanks a lot. I already triggered the idoc in we19 and please go through the following once again:
    I have done all ALE settings in R/3 side with RFC destination, port, Partner profile.
    At XI side i created RFC destination, Port and Partner profile also.
    And i pushed the idoc from R/3. I got the status messages like
    "IDoc: 0000000000001018 Status: Data passed to port OK" and "IDoc sent to SAP system or external program".
    But in XI, i got the following messages:
    "IDoc: 0000000000005005 Status: Application document not posted" and
    "Function module not allowed: APPL_IDOC_INPUTI".
    All my design time and configuration time objects are done and activated.
    Here i am using the business service for sender system. sender is R/3 system.
    Anybody, came across this problem, could you please revert back to me with solution. I want step-by-step testing procedure.
    Please getback to me with proper solution asap.
    Thanks & Regards,
    Nagarjuna.

  • IDOC2FILE scenario

    Hi All,
    I am going to develop idoc2file scenario in XI. Any body have the full documentation with step-by-step process(including R/3 settings & XI settings), Please send me ASAP.
    I am very thankful to you in advance.
    Thanks & Regards,
    Nagarjuna.

    Hi nagarjuna,
    ALE configuration
    Steps to do ALE Configuration with respect to IDOC:
    Configuration in R/3:
    1. Create a RFC destination using Transaction = SM59
    2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
    3. Create a Logical System using Transaction BD54.
    4. Create a partner profile using transaction WE20.
    Also need to configure in XI:
    1. Create a RFC destination using Transaction = SM59
    2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
    3. The port has to be displayed in the IDX2 transaction and we should be able to view the idoc’s which we imported through integration repository otherwise we have to manually import the idoc’s from IDX2 using the port created above
    Please refer to these blogs:
    Complete process for Idoc to file scenario:
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    incase you are struck with any issues while creating the scenario refer to this blog;
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Hope this will help you:)
    reward points if helpful
    regards,
    Nithiyanandam

  • Trigerring idoc in idoc2file scenario

    Hi
         how the idoc is triggered in scenario idoc2file,in which idoc is on sender side and file on reciever side.
    regards
    prasad

    Hi,
    Once you configured the ALE settings, ask your functional people to generate the idoc. then goto we02 take the IDOC number fom there and paste it in WE19 ( IDOC Test Tool)
    And then u can send the IDOC from R/3 to XI in this way
    ALE Settings
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Reposting IDocs instead of Recreating - For Testing
    /people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
    IDOCXI-File Scenario
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    REgards
    Seshagiri

  • ALE settings in xi

    1) what are the ALE settings i have to maintain in R/3 system and XI in  Idoc 2 file scenario?(I know little bit RFC Destination, Port, Partner profile in R/3 system. is it required to maintain the port in XI also? )
    2) what is use of  Meta data ( IDX2 )? can we import it every time explicitly ?
    3) what are the ALE settings i have to maintain in R/3 system and XI in  File 2 Idoc scenario?
    4) should i create ports in both R/3 and XI systems?( idoc 2 file / file 2 idoc)

    Hey,
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    WE42 process code
    WE47 status info.
    reward points if useful.
    regards,
           Milan

Maybe you are looking for

  • HOW DO YOU ADD COMMENTARY TO A FINISHED PROJECT?

    Good evening, I have a finished movie project, made with iMovie 5.02, and am wanting to add a video commentary on another button. I can create an extra button in iDVD menu, but I can't figure out how to get the movie in there. iDVD says to go to pref

  • Can I use my old number for the new iPhone 5?

    I have an ordinary O2 SIM card that in would like to use for the new iPhone 5, I would love to keep my old number because it would be too much hassle with a new number, is this possible?

  • Updated to the latest and now I keep getting disconnected

    I use the MS Remote Desktop Client for Mac and it worked wonderfully until I accidentally updated to the latest version. Now I keep getting disconnected. sometimes I get disconnected when I am back at my local computer looking something up and then o

  • Problem with Checking In/Out Items in Content Area

    I've been reading the Portal On-Line help pages in regards to checking in/out items. The help states that when an item is checked out, the item is locked and a message "Checked out by: UserName" is displayed next to the item. When I check out an item

  • Export: command not found

    I have been trying to install something via MacPorts and was following a blog that described setting the PATH appropriately so that the port command would work, however when I updated .bash_profile as described in the blog and tried to source it, it