ALE Configuration Conceptual Questions

Hi Experts,
I need some help regarding the ALE configurations.
1. I know that we specify the RFC dest in the port and then specify the port in partner profile. What exactly is the significance of a port in case of outbound Scenario? we could have directly specified the RFC destination in the partner profile.
2. When we create the TCP/IP RFC destination it creates a TRFC Connection. However in the special options tab we have the option select QRFC version? What is the use of that?
3. Why does the port created is of TRFC for ALE? Is it that the RFC connection is of TCP/IP so we need a TRFC port?
4. Why do we need to create TCP/IP rfc destination for ALE, why not HTTP RFC destination?
5. Is distribution model is mandatory for all the ALE scenarios? If not then when its mandatory?
6. While creating process code we have option process with/without ALE service. What does that exactly means?
Thanks
Kumar
Moderator message: please search for available information/documentation, do not ask interview-type questions.
Edited by: Thomas Zloch on Apr 19, 2011 7:01 PM

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,
S.Nehru

Similar Messages

  • ALE Configuration Questions

    Hello Experts,
    I have a few questions regarding ALE Configuration, help appreciated
    1) Is it necessary to create user for ALE transfer in both sender and receiver system ?
    2) Is it necessary to create logical system for both sender and receiver in both the systems ?
    3) Can tRFC created in sender system have a different port name than the logical system name ?
    Is it ok, if only configuration is done in the sender system, if I am looking for one way transfer of Idocs from sender to receiver ? The receiver will receive the Idocs and process internally, sender is responsible only for sending in my case.
    I have referred the below link,
    7 Steps For ALE Configuration - ABAP Development - SCN Wiki
    Best Regards,
    Ameya B.

    Hi Mili,
    You do not need to generate partner profile during the ditribution model view process (BD64). You can add manually the partner profile via WE20 for inbound and outbound parameters. As long as distriburon model has been setup and distribute, you can continue the next step for example generating IDoc and so on.
    Sometimes, you may face an issue to generate partner profile from BD64 for some reason. I found by generating manually partner profile always quick, safe and stay away from any trouble shooting for an error.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Ale configuration question

    Hi,
    While doing the ale config as per blog...
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    all steps worked fine...except the step where we select model view and distribute....
    I get this message...
    Communication error occurred
    Name or password is incorrect(repeat logon)..
    Any ideas ....i believe its the uid/pwd combo i had specified in the rfc destination...just wanted some clarification
    Venkat

    Yes. That is correct.
    You will find the RFC destination with same as your receiving Logical System name. Test your RFC destination whether it is working fine using TC : SM59
    Hope this will help.
    Nilesh

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

  • Single Transaction code for ALE Configuration

    Hi All,
    I want to Know is there any Single Transaction code for the ALE Configuration instead of going through SALE, WEDI t-code or with defining logical systems assigning them to clients, creating RFC and Distribution Model, generate partner function and..so on.
    Please let me know if there is any t-code through which i can do the ALE configuration in a single T-code.
    Thanking you in advance,
    Bhanu

    hi ars
    i got a task saying that message type is DESADV01 ,but u told that DESADV01
    is basic type,can i know the difference.
    regards
    sagar

  • ALE Configurations?

    Hi All,
    Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system.  As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
    I've done the following ALE configurations at R/3 side.
    1. Created a logical system and RFC destination for TIBCO.
    2. created a TRFC port.
    3. Create a Partner profile and linked the TRFC port.
    4. posted an IDOC from WE19.
    but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
    pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
    regards
    Faisal

    HI
    SAP R/3
    R/3 to 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 (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.
    XI to 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 (IDX1) ( Create port to get IDOC Meta data from sender system)
    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) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    Refer the below links for further assistance
    4.create partner profile using idx2
    ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    IDOC testing using WE19
    /people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
    cheers

  • ALE Configurations in File to IDOC Scenario

    Hi All,
    We are doing File to IDOC Scenario.
    ALE Configurations done:
    R/3 Side:
    1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
    2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
    3. Created partner profile and assigned the ports to the message types.
    4. Created Logical system
    XI side:
    1.  Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
    2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
    <b>3. Unable to load metadata in XI.</b>
    Now we are unable to test the scenario as it provides an error message in MONI as "<b>Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors</b>".
    Also Let me know whether the steps mentioned above are correct for the scenario.
    Regards,
    Nithiyanandam

    Hello,
    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 XI 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 #####+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.
    In SLD – System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    With Regards,
    Vidya.
    *******Reward with Points if found useful

  • 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

  • Problem in ALE configuration

    Hi ,
    I am doing ALE configuration to transfer the Vendor information from 800 client to 700
    client.
    In client 800 while I am creating partner function I am getting
    error...Could you please help me to resolve.
    In "Generate Partner Profile" (in 800 client)
    I have given ....
    Model View : "VENDMODEL1"
    Partner  System : IDES_700
    Next screen "log for partner profile generation is displayed"
    Partner
    No error is displayed here...
    But in "port"
    the following message is displayed....
    System IDES_700   : Port could not be created
                        RFC destination IDES_700 not specified for system              
    ides_700
                  Enter the RFC destination and restart the generation
    After creating Model view with Sender and Receiver with Message type as CREMAS
    what we have to do...
    whether we have to distribute it ..
    I am getting error log as ...
    Targert system IDES_700  : RFC Destination for Synchronous                  
    communication(message type SYNCH)
                      Partner Profile LS IDES_700 SYNCH does not exist
    please  help me in this regard
    With Regards,
    Sagar.

    Hi,
    Please ensure the RFC destination for both logical system (client 800 and 700) are created in SM59.
    Also you can add manually message type SYNCH with IDoc type SYNCHRON in the partner profile (WE20) prior to generate partner profile for message type CREMAS via BD64.
    Message type SYNCH is a dummy message type for determination of RFC destinations and IDoc type SYNCHRON is a dummy IDoc type for synchronous communication.
    You can setup something like this.
    Outbound parameter options:
    Field          Value
    Message type   SYNCH
    Receiver port  A000000015 (Transactional RFC)
    PacketSize     100
    Output mode    Transfer IDoc immed.
    Basic type     SYNCHRON
    Hope this will help.
    Regards,
    Ferry Lianto

  • Help required in ALE configuration

    Hello All,
    I am working on SAP Demo version. I have created a logical system and saved it.
    After defining logical system i tried to create a distribution model but i don't see any logical system in the distribution model? Can anyone help me in this issue.
    Regards,
    Lisa

    <<Posting list of links is not permitted.  Please do not do it again.  Further violations can result in points being deducted, or your account being deleted>>
    Hi,
    Refer below links.
    Re: tell me about ale configuration
    reg:ALE Configuration
    Re: ALE and Idocs configuration
    Re: ALE Configuration
    Regards
    Md.MahaboobKhan
    Edited by: Matt on Jan 19, 2009 7:38 PM

  • ALE Configuration issues..

    Hi,
    I am trying to set up ALE configuration between two SAP systems. I have defined partner profile(WE20) in sender system, there is a tab 'Post processing : Permmitted Agent', I have chosen type as User and agent as system user Id. I would like to know on what basis value of type and agent should be chosen?
    I have another query....I am sending Idocs from one system to other. I am defining control records in a program in sender system. In control record I have mentioned sender port name(sndpor), sender partner number(sndprn) and sender partner type(sndprt). I would like to know whether i need to mention receiver port number(rcvpro), receiver partner number(rcvprn) and receiver partner type(rcvprt) ?? Please note that I am not receiving any data to my system but only sending Idocs to other system.
    Thanks.

    Hi,
    in the sender system you will have to define the sending options
    In the receiver system you will have to define the receiving options
    that is the partner profile.
    if you are not useful with this, you could play with BD64
    In WE20, you specify with this partner (the system receiver) I will send this kind of data.
    In the receiver system, in WE20, you will specify with this partner (the sender) I will received this kind of data
    so if you send other things, the receiver system will refused it
    You could also specify the system in some transaction, for example BD10 for material, but if the WE20 customizing is missing, the system will don't do anything
    regards
    Fred

  • Can we go with ALE configuration instead of receiver idoc adapter at target

    Hi Experts,
    Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI  to Target system instead of configuring receiver IDOC adapter at target side.

    Hi Raj
    Point 1:
    When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
    Point 2:
    When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
    i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
    Regards,
    Raj

  • IDOC and ALE Configuration with cross application with SD

    Hi Sap Gurus,
    Please send me some document on IDOC and ALE Configuration with cross application with SD.
    Please send me the material on my mail id [email protected]
    Regards
    shekhar

    Dear Shekhar,
    concerning EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.
    If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).
    So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.
    That's all concerning the SD-EDI.
    Additional processes in SD, where EDI are used:
    1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS
    2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD
    3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT
    4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.
    It is all processes which are realized in the SD module via EDI.
    I hope this info helps.
    Kind regards,
    Akmal Vakhidov
    Development Support SAP, Walldorf/Germany

  • Reg:ALE configuration

    Hi..
    I am trying to do ALE configuration for inbound IDOC.
    I have created  RFC destination on XI client using transaction SM59 and then a port  using IDX1.
    after that i have executed the transaction we20 on the  SAP system and added the IDOC basis type to the Inbound parameters of respective logical system of SAP.
    Now when i am trying to post an idoc on SAP.its showing an err"EDI: Partner profile inbound not available".
    what can be the reason of this err??

    hi
    follow below procedure then check for Error :
    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)
    Not mandatory.
    Goto BD64.
    Click on Create model view.
    Add message type.
    Step 6)
    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 7)
    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
    Regard's
    Chetan Ahuja

Maybe you are looking for

  • Error message while Solaris 10 installation

    I got that error message while installation without knowing the actual reason behind it : Searching for configuration file //cdrom/solaris_10/misc/install_config/sysidcfg Could not find file. Searching for Jumpstart directory : not found could not fi

  • Enable full sreen For API youtube into flash website

    Hie, simple question ,it is possible to have the fullscreen button on the youtube players when the API is load into a flash website ? I read this fs Values: 0 or 1. Default is 0. Setting to 1 enables the fullscreen button. This has no effect on the C

  • Assigning IP addresses to VPN users from Cisco ISE

    Hi all, I would appreciate if anyone could share his experience in assigning ip addresses (not static ones, but from a pool) to VPN users. The Radius is Cisco ISE and I am trying to configure this in the Authorization Results Tab. VPN gateway is ASA

  • Multiple applications in bdc

    hi.. sdn experts... how to process the multiple applications in bdc ....tell me one scenario..

  • Rich User interfaces with Java article

    http://www.theserverside.com/articles/article.tss?l=RiA