Error for connectivity to transfer IDOC from SAP R/3 to PI.

Dear All,
While transferring IDOC from R/3 to PI, Outbound IDOC is sucessfully transferred in R/3 but when i check in PI IDOC is not recieved . Checking the Status in TCODE: SM58 we get the following error:
No_Run_Permission
All the RFC and Port Connections are fine and in place.
Kindly guide through...

Just check the RFC user has correct authorization to post IDOC to PI. Your Basis person can help you in this.
-Gouri

Similar Messages

  • Error while pushing idocs from SAP to XI

    Dear All,
    For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    I am able to create the  model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
    <b>Target system XIDEV       Communication error occurred
                                              User is locked. Please notify the person responsible</b>
    please tell me what is the error ie which user is locked and how should i proceed now.
    Waiting for your reply.
    Warm regards,
    N.Jain

    hi krishnamoorthy,
    i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
    Please suggest.
    Warm Regards,
    N.Jain

  • Steps of EDI is used to transfer IDOC from R3 system to non sap system

    Hi Experts,
    Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
    Full points will be assigned.
    Thanks in advance!
    Sapna

    Hello,
             The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
    1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
    2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
    3. After that, assign the IDoc Type to Message Type in WE82.
    4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
    5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
    6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
    7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
    8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
       i. In Message Control Configuration, we'll maintain
          a. Condition Tables
          b. Access Sequences
          c. Output Types
       ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
       iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
       Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
       For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
       However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
    Hope the above procedure was clear.
    Thanks and Regards,
    Venkat Phani Prasad Konduri

  • I just used a firewire connection to transfer files from an older MAC to a newer MAC. My newer MAC has lost all that was on it, and all the applications are opening like they have never been used before and asking for Rosetta. Help!!!

    I just used a firewire connection to transfer files from a PowerBook G4 to a MacBook Pro. The MacBook Pro has lost all that was on it, and all the applications are opening like they have never been used before and asking for Rosetta. How do I find all my files on the MacBook Pro, or undo what I have done???

    IGNORE the last post: he thought you are using Lion or Mountain Lion.
    Since you are using Snow Leopard, you need to install Rosetta.  It can be found on your Snow Leopard Install DVD in the Options section.
    Once installed all should be well again.
    Also, if your computer is connected to the internet when the Dialog Box about PowerPC applications comes up, it MIGHT allow you to download Rosetta from the internet.  There has been some discussion that Apple has discontined internet download of Rosetta into Snow Leopard.
    Someone else will have to address your lost files problem.

  • Problem when pushing IDOC from SAP to XI

    Hi,
        I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

    Hi,
    It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
    Can u check Receiver Determination  created in the XI once again. And also check for RFC destinations created in the R/3.
    Hope it helps ..
    -Moorthy

  • Sending IDOC from SAP ECC to SAP MII

    Hello,
    Issue while configuring.
    I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got  error as timeout during allocate of registered program and I have attached the screenshot of the error page.
    I would request a reply asap.
    Thanks,
    Praveen

    Hi Praveen,
    First, I would suggest that you identify what version, and SP, of MII and ECC.  Also the NW version and SP if applicable.
    Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59.  There are many discussions on IDoc Listeners going back a number of years.  Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well.  I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener?  If not, you should review your configuration and setup procedure against it.
    I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1.  So the document is still applicable.
    Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID.  Deleting it in one place, generally does not work.  Use it in one place only.  Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance.  Save yourself a lot of headaches.  Never, ever reuse ProgIDs!!!
    Fourth, most of the other issues involve a PI/XI system in the middle.  Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI.  Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved.  Sometimes a CSS ticket is required.
    Regards, Mike
    SAP P&I Technology RIG

  • "An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

    Hi all,
    While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
    Only a particular Idoc type is having this issue.
    Below are the checks done before posting this query:
    1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
    2. Reloaded the meta data in PI for  the particular Idoc type in issue.
    3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
    4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
    5. Restarted the inboundRA service in PI AEX.
    Is there anything still missing. What could be root cause of this issue.
    If anyone has encountered it before, pleases share the resolution.
    Thank you
    Younus

    Hi Amit,
    Thanks for the reply. Log viewer doesn't provide much help on the error.
    The error desc says
    "JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
    regards,
    Younus

  • ** Not able to import IDoc from SAP ECC system

    Hi Friends,
    I am not able to import the IDoc from SAP ECC system in IR. I have checked that, hostname, client, server no. everthing is correct. I checked in SLD also. Host Name is correct.
    While import (after giving the user name and password), I am getting the following error.
    Problems to reach R3 System
    What could be the probelm ?
    Kindly help me friends.
    Thanking you.
    Kind regards,
    Jegathees P.

    Hi,
    Just counter check following step
    1. Go to SWCV definition tab select radio button for Import of RFC....
    2. In Connection Data for Import from SAP System maintain correct System and correct Client.
    3. Make sure you maitain ECC system in Central SLD.
    4. In Import Screen check at the top of the screen have SAP System, is that system from where you want to import the IDOC.
    With Regards
    Sunil

  • How to Trigger an IDOC from SAP R/3 to two systems at a time

    Hi experts,
    Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
    My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
    I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
    Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
    Can any one tell me how can we do that ?
    Regards
    Ram.

    Hello Ram,
    Do you have connectivity between your production & XIQ?
    What does "connectivity" mean?
    1. RFC destination is maintained.
    2. Port defined for the RFC destination.
    If no, create these. (Search in SDN for details).
    If yes, proceed:
    1. Define the logical system for XIQ.(BD54)
    2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
    3. Create a distribution model view with sender as "your production" & receiver as XIQ.
    3.1. Add the messages which you want to distribute.
    3.2 Generate Partner profiles.
    No coding is reqd. for this.
    BR,
    Suhas

  • Unable to send an idoc from SAP R/3 to XI

    Hi,
    We are trying to send Z_CREMAS_SUSMM.CREMAS03 idoc from R/3 system to XI using IDOC adapter.
    We have done the following steps.
    On  SAP R/3 system:
    1.created a RFc Destination which points to the XI system using transaction SM59
    2.created a port in which we have selected  this RFC Destination   using tansaction WE21
    3.logical system for R/3  with transacion BD54
    4.In WE20 transaction,we have configured the PartnerProfile by adding the IDOC message type to the outbound Parameters of XI Logical system.
    On XI Sytem:
    1.Created RFC destination
    2.Created a Port
    3.Loaded metadata
    While trying to Post IDOc from SAP R/3,it is throwing an error"External segment name E2LFA1M001 cannot be interpreted"
    and "Basic type CREMAS03 does not exist" on XI side.
    Can anyone please provide a solution to this?

    HI Jagruthi,
    Have you loaded the metadata into the XI system by using IDX2?
    If it is done then try to delete once and do once again.
    And also delete the IDoc from IR and reimport the IDoc and activate it once again.
    Regards
    Goli Sridhar

  • Problem in  Outbound IDOC from SAP R/3

    Hi,
    I am working on to send an IDOC from SAP R/3 to XI.
    I configured all necessary things as follows:
    1. Created for XI in sender system -- RFC dest, PORT and a partner profile with an outbound parameters and reciever port as XI port.
    2. created for sender system in XI -- RFC dest, PORT(as SAP<SID>) in IDX1 and assigned an idoc type(coming from sender system) to the port.
    Now I am trying to push the IDOC from sender system using Test IDOC transaction and gets success message as data is passed to port.
    My problem is I am not able to see any message in SM58 of XI server.
    Could anyone help me out?
    Thanks In Advance.
    Yaseen.

    Yasseen,
    you hardly see the idocs in Xi in sm58. Try sxmb_moni.
    If you see anything there try sm58 on the sending R/3. There you see if you have connection problems (eg authorization in XI or missing receiver determinitions).
    Hope it hellps,
    helge

  • Transfer data from SAP TABLES to a SQL table

    Hi,
    I need to transfer data from SAP tables to a SQL table. Please suggest the best way as well as the steps please.
    Regards,
    Kamlesh

    Hi
    Step 1: Create an entry for the External database in DBCON table using Trxn: DBCA.
    Field Name Description Value (For: E.g.:)
    CON_NAME Logical name
    for database con RAJ
    DBMS Database system MSS
    USER_NAME Database user <username>
    PASSWORD Password for setting up
    the connection
    to the database <pwd>/<pwd>
    CON_ENV Database-specific MSSQL_SERVER=depotserver MSSQL_DBNAME=HOF_INDORE
    DB_RECO Availability type for an open database connect
    Then, you can define internal table and code the following way:
    DATA: BEGIN OF wa,
    c_locid(3),
    c_locname(50),
    c_locstate(5),
    END OF wa.
    EXEC SQL.
    CONNECT TO 'RAJ' AS 'V'
    ENDEXEC.
    EXEC SQL.
    SET CONNECTION 'V'
    ENDEXEC.
    < Populate SAP data into an internal table >
    Loop on itab.
    EXEC SQL.
    < code here for populating data into MS-SQL Server table>
    ENDEXEC.
    Endloop.
    Regards,
    Raj

  • Help needed in transferring IDoc from SAP CRM to XI

    Hi All,
    We are facing an issue in sending an IDoc from SAP CRM to XI system.  The IDoc is triggered and the status is showing as 03 in SAP CRM system(WE05 is used) but it is not getting replicated in XI System. This is verified by logging into XI System and cross checked the records retrieved by executing the transaction IDX5. No entry is found for this IDoc.
    In SM58 transaction, it is giving the status text as EDISDEF:Port SAPRIO segment defn E201CRMXIF_BILLI. 
    Any pointers on this issues will be very helpful. We are able to send information from XI to CRM.
    The project is an upgrade one and the IDocs are developed earlier and were working fine one week back and no changes were made recently.
    Thanks,
    Udaya

    Hi Kapil,
    Thanks a lot for your help. We need to delete and recreate Metadata. This is a typical problem that is encountered during upgrade projects.
    Thanks,
    Udaya

  • How to Trigger an IDOC from SAP R/3 to two XI systems

    Hi experts,
       Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
    My current production R/3 system sends a DELCERY01 IDOC to Production XI system ( Name : XIP) .
    I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
    Problem is production R/3 system triggers an IDOC once.
    Regards
    Ram.

    Hi Ravi,
      Thank you very much for your answer.
    As I am not completely aware of R/3 side,I am getting little problem in understanding your answer.
    Could you please explain the same in some what beter way.. Thank you ..

  • Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

    Hi,
    I try to send idoc from SAP r/3 4.6C to PI 7. I had made  ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
    Is somebody can help me ?

    Hi,
    In R/3 :
    my RFC destination is type 3 and point to XI. The port in the partner profile  point to this RFC destination. ( all seems good !).
    In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
    When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038  "1 master IDocs set up for message type MATMAS" and just after
    the XI logon screen  appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
    Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

Maybe you are looking for