Ale configurations for IDoc?

hi..
     What are the ALE configurations need for an IDOC?
bye.

Hi,
Perform the following ALE configurations
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Also gothru this Blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points

Similar Messages

  • ALE Configuration for PEXR2002 IDoc  and PAYEXT message type sending to XI

    Hi all,
              I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
    I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
    I need ALE Configuration doc/pdf??
    Please give me some guidline for this..
    Regards,
    Umesh

    Umesh,
    I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI. 
    I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
    Any help or direction would be great.
    Thanks,
    Dave

  • ALE configuration for Outbound Idoc - Help me

    Hi Experts,
    I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
    I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
    and then everything went well and i saw success messags in all the steps.
    I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "<i><b>No service for system SAPRDI, client 800 in Integrion Directory</b></i>"
    And all the messages are hanging in the TRFC queue.
    Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
    Thank you in advance. Pls help me its very urgent.
    Thanks,
    Surya

    I created RFC destination (SM59) and Port (IDX1)
    Then i sent another material (BD10)  and checked tRFC queue. i found bunch of error in the Queue.
    <b>1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
    No service for system SAPRDI, client 800 in Integration Directory
    partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
    connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error</b>
    Note: i have noticed entries for R3 in SLD as below
                      System Name:  <b>RDI </b>  ( not <b>SAPRDI</b> as mentioned in the error message)
                      System Home:  r3ides
    That might be reason. If so, how to change it in R3 box? Any suggestions?
    Please send me if you guys have any links or docs to address this issue.
    Thanks,
    Surya

  • Issue with ALE configuration for creating the idoc for Purchase orders

    Hello,
            I am trying to send the purchase order through message type configuration using ALE.
    I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
    In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
    I have done ALE distribution using BD64.
    Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
    In NAST table, the entry is there but on executing RSNAST00 nothing happens.
    Please provide me the pointers to solve the given problem.
    Regards,
    Mayank

    Hi,
    Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
    It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
    Check and let me know if all is fine at the output type configuration.
    Cheers
    VJ

  • ALE configuration for printer

    Hi all,
    Can u tell me how to configure printer setting using ALE.
    Senario:
    As we have 2 clients 200 and 500. 200 is open and 500 is closed.
    If we configure printer from spad in 200 client the same should reflect on 500.

    Umesh,
    I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI. 
    I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
    Any help or direction would be great.
    Thanks,
    Dave

  • ALE Configurations for JDBC to PROXY scenario

    Can some body tell me what are the ALE configurations that needs to be done in both the systems and also in XI system.

    Hi there
    No need for ALE confihuration unless you are using IDocs in your scenario.
    You need to configure the integration engine in the Proxy system using SXMB_ADM and create an RFC for the Integration server.
    on the JDBC side you'll need the database bridge configured in the communication chanell...
    what is your scenario specific...which system types and versions?
    Nimrod

  • 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 Configuration for Transactional Data (Purchase Order)

    Dear Experts,
    I want to configure ALE for Purchase Orders(Transactional Data).
    For that:
    I have done neccessary Condition  Records at NACE with necessary Output Type Configuration. Configured Port and Partner Profile with Message Types: ORDERS and ORDECHG (as Outbound Parametrs) .Assigned those Message Types against defined Sender and the Receiver at Customer Distribution Model . Configured Port and Partner Profile at the Receiver System also.
    Now I have 2 queries.
    i) Is this much of ALE configuration is enough for Transactional Data for communication between 2 systems or I have to do something more?
    ii) For Master Data we configure Change Pointer(we can see field assignments against Change Document Object at BD52 for Master Data Messaage Types) . Is it necessary to configure Change Pointer for Transactional Data or it will autometically handled by the system(field assignments cannot be seen against Change Document Objects at BD52 for Transactional Data Messaage Types)?
    Regards
    Arnab

    Hi kumar,
    what Alexander  said is absolutely correct .
    from your second question no master data distribution configuration is required for the transactional data distribution.  
    let us know once if you face any problems.
    ~linagnna

  • 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

  • Dynamic Configuration for IDOC

    Hi,
    Whenever an IDOC is send from SAP R3 system to PI (SAP R3 -> SAP PI -> Target), we get an additional node of Dynamic Configuration under the SOAP Header in SXMB_MONI.
    Why is this happening? Does this happen for all the versions of SAP XI (PI)?
    This issue does not occur when the IDOC is send by SAP PI to SAP R3 system (Source --> SAP PI --> SAP R3)
    I am using SAP PI 7.1.1
    Thank you,
    Pankaj.

    Hi,
    Why this is an issue for you?
    I am trying to send IDOC from SAP System to PI system.
    Ideally there should be no DynamicConfiguration step under SOAP Header folder in SXMB_MONI (I tested a SOAP -> PI -> FILE and the Dynamic Configuration does not come); unless and until we make use of the ASMA properties (UDF/ Module). Is this understanding correct?
    For example, if I send an IDOC i get the below details in SXMB_MONI:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Response -->
    <SAP:DynamicConfiguration SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">SAPPI</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">SAPPISYSTEM</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPECC</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">SAPECCSYSTEM</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP"/>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">Z_VALIDATION_ACK01</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">Z1VALIDATIONACK</SAP:Record>
    <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
    </SAP:DynamicConfiguration>
    Is this behavior as expected?
    Thank you,
    Pankaj.

  • Integration Directory configurations for IDOC - XI - File

    Hi all,
    I have a scenario as above: IDOC-XI-FILE
    The IDOCs come from an R/3 system - NHGDDBS01.
    I've configured 2 BS:
    1) BS_NHGDDBS01
    -> TS: NHGDDBS01, type: WebAS ABAP
    -> SWCV: BASIS 6.20
    2) BS_DEV1_NAUTICUS_OOTS
    -> TS: TS_DEV1_NAUTICUS_OOTS, type:Third Party.
    -> SWCV: SWCV_DEV1_NAUTICUS_OOTS, type: Third Party
    -> PDT: PDT_NAUTICUS_OOTS
    With this setup, can someone help me by showing me how to configure the Integration Directory in order to receive IDoc from R/3 (nhgddbs01)?
    Please help.
    Thanks.
    Ron

    > This is known issue.....Check the below
    > steps.............
    >
    > Go to XI system ->and IDX1 transaction.. And check
    > the port number + RFC destination is given correctly.
    > this should point to SAP system ..
    > Check thsi RFC destination is having all the entires
    > and test connection success
    >
    > And the port should have the naming convention
    > SAP<System Id>.
    >
    > ........................Check this SAP Note -940313
    Hi,
    I followed the SAP Note.
    The SAP System ID is DV1.
    I've configured IDX1 with the following port:
    Port: SAPDV1
    Client:108
    Description: <blank>
    RFC_Destination: PI_001 (This RFC destination points to DV1, despite the naming. Connection test is successful)
    I recreated metadata on IDX2:
    IDoc Types: ZPATINFO
    Source Port: SAPDV1
    IDoc Types: ZADMINFO
    Source Port: SAPDV1
    However, when I test the message from R/3 using WE17, <b>SM58 on R/3 </b>it's still showing the error:
    Transaction IDX1: Port SAPDV1_108, client 108, RFC Destination error.
    May I know where did this error occur and how to rectify this?
    Please advise.
    Thanks.
    Ron

  • How to remove the complete ALE configuration for a given system

    Hello everybody,
    Through ALE ,data is transferred between a number of SAP systems and the necessary ALE setups are in place.
    Now,a particular SAP system,which used to be a receivor to the central SAP system,is to be retired.
    Hence,the associated ALE set up is to be completely removed from the central SAP system.
    Is the following sequence correct?If not and I have missed something,please enlighten me with the correct sequence.
    1.Removal of the receivor logical system  and its assignment to client ,through transaction SALE.
    2.Removal of partner profile, through transaction WE20.
    3.Removal of RFC destinations,through transaction SM59.
    4.Removal of transactional ports for the logical system,through transaction code WE21.
    5.Removal of Distribution model between the retiring system and the central SAP system.
          (a)Regarding distribution model,I have a question-if the distribution model is maintained such that it contains the linking relationships between the central system and several receivor systems(in addition to the one I wish to remove),then is it possible to remove only the desired linkage and not touch the rest?   
          (b)Through BD64,I have tried but I am able to delete only the entire distribution model  as a whole,while I would like to keep the distribution model and delete just one of the nodes,so as to cut  the connection between only central system and the retiring system.
    This is so because the other receivor systems are working fine,involving a lot of batchjobs and I am afraid that deleting the distribution model wholly will create unnecessary trouble.
    Any help will be appreciated.Thanks
    Papri

    HI Nicolas,
    I chatted with Rev-Trac support earlier today and here is what they have come back to me with.
    Assuming the change in question was carried out in the development  system. Changes to fields in tables should in most cases be captured in transports. Assuming it was a transportable change then go to the development system and execute transaction SE16 and query Rev-Trac table /RSC/T_MFM_4T filtering by TABLENAME.
    On executing the query you should see a list of transports involved with changes to the transport. You can then check to see if there is a recent transport associated with the change - if so then you can find out who created the transport by using standard SAP functionality."
    If you find this doesn't help, then please contact your Rev-Trac Administrator who can then log a support request on our support portal at www.xrsc.com
    Hope this helps, Rick

  • ALE Configuration Again !!!

    Hi All,
    I am trying to do ale configuration for idoc to file scenario. I created two RFC connection one for XI system and one for R3 system. Then I created ports for both the RFC. After that I created two Logical system having same name as the two RFC above. But as per the instruction , i should assign client to above logical system. But problem is that the client number ie 030 is already defined to R3 system. My XI system have same client id, so when i am trying to assign client 030 to XI logical system, it is giving as client number is already present. I don;t understand the logic of assigning client to LS.
    what should i do here?
    Second thing: Can we create more than one  logical name for the same system. I asked this because in the RFC list of R3 system, i already have RFC for R3 system , logical name is also present. So can i create another logical system for R3 system?
    Ranjeet Singh.

    An excerpt from SAP documentation on Logical System Names. 
    Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>.  Refer to url
    http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
    SCC4 should already have been set.  So I assume that you are creating your logical systems in the IMG to then assign in WE20 (Partner Profiles).  As the XI SystemID will be different to your R3 SystemID, CLNT should not be an issue.
    If not then please clearly define the issue to include where you want to create the logical system and which way your IDOC will travel.  We currently send IDOCs from CRM to XI and vica versa

  • Idoc Communication Configurations and Proxy Runtime Configurations for PI

    We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
    is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
    1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
    2. Configuring for IDOC communication between ECC6 and PI 7.1
    3. Configuring for IDOC communication between 4.6C system and PI 7.1
    It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
    Pls suggest any step-by-step instructions docs/blogs available.
    thanks in advance.
    Madhu.

    Madhu,
    Refer the links below:
    1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    2& 3 :
    https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
    http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Also, I  think u hv just started learning XI ..so following link might help:
    http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

Maybe you are looking for

  • Open SQL is not working in EAS

    Hi, I'm trying to load the data into Essbase using the RDBMS. Following are the steps I followed: 1. Created a DataSource 2. Opened the DataPrep Editor in EAS. 3. Click on File --> Open SQL. 4. Given the Essbase server, application and Database. Now

  • Planned Conditions in Scheduling Agreement

    Dear Expert, We are using Scheduling Agreement for external procurement of materials,for few materials Condition like ZNMC Cess are applicable,In Purchase Order these conditions are automatically pickup if it is maintain  in MEK1,In Scheduling Agreem

  • The new "Creative Zen&qu

    Creative is came out with a new Creative zen. im not so sure if it out now or if its coming out soon. but i was just wondering if anyone has it and can tell me if you can rotate the screen so it would be easy to click the buttons with your left hand.

  • TREX creation process fails - directory name is invalid

    Hello All, I've installed a TREX instance to be linked up to two SRM instances (SRD and SRT).  I had done this successfully on a prior server, but recently we got a new server to run TREX on. When I reinstalled TREX on the new server, I have success

  • Migration weblogic portal 4.0 to weblogic portal 8.1

    I am trying to migrate weblogic portal 4.0 to weblogic portal 8.1. I need help how to do this ? thanks