webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Error posting IDOC from WM to SAP R3

    Posted Wed June 20, 2007 04:50 PM

    Hi All,

    We get the following error when we create an IDOC and post it to SAP R3 system. The IDOC is created in SAP system yet we get the error. As well when we post 1 IDOC 5 IDOCs are created and gives following error as below.

    PLEASE ADVISE.

    Regards
    Atul

    [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service pub.sap.transport.ALE:OutboundProcess.
    [SAP.102.9000] JCo error: (104) RFC_ERROR_SYSTEM_FAILURE - Exception condition “X_ERROR” raised.

    retryCount = 5
    maxRetryCount = 5


    #Adapters-and-E-Standards
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: Error posting IDOC from WM to SAP R3

    Posted Wed June 20, 2007 09:15 PM

    sending IDOC to SAP R/3 system, what service input values are specifying in the following service?
    pub.sap.transport.ALE:OutboundProcess

    Please mention what values you are specifing in following Service inputs…
    transportParams/server
    $action


    #Integration-Server-and-ESB
    #webMethods
    #Adapters-and-E-Standards


  • 3.  RE: Error posting IDOC from WM to SAP R3

    Posted Thu June 21, 2007 06:13 AM

    Server is IP address of SAP R3 system
    action is left blank as default.


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods


  • 4.  RE: Error posting IDOC from WM to SAP R3

    Posted Fri June 22, 2007 01:56 AM

    I think you can check ST22 transaction in SAP, to see if there is any dump. That will give you more details. RFC_ERROR_SYSTEM_FAILURE, most likely, means that there is a problem on the SAP side. Also check the RFC traces generated by SAP adapter.

    Following is from Sap Help with more detail:-

    "When a JCO$Exception has occurred, first of all you can categorize and so localize the cause of the error by the group the exception belongs to. For example, if you see an RFC_ERROR_LOGON_FAILURE error, you know that incorrect logon parameters were used. Whereas if you see an RFC_ERROR_SYSTEM_FAILURE error, you conclude something is wrong with the SAP system you want to connect to, so you have a look at the SAP system. Besides keywords, JCo exceptions return text that is often very helpful for determining the cause of the error.

    The above list of exception groups also comprises a column of “possible actions” that help to analyze the failure. If an error has occurred on a lower communication layer, for example an RFC_ERROR_COMMUNICATION or RFC_ERROR_SYSTEM_FAILURE exception, have a look at the dev_jrfc.trc files."

    [url]SAP Help Portal


    #webMethods
    #Adapters-and-E-Standards
    #Integration-Server-and-ESB