RFC error handling

Hi gurus !
i have created RFC and that rfc is called in dotnet application. but when i pass data to dotnet system. how to track that my data is passed successfully.

As Rudra already stated this is usually checked on the dotnet side which is requesting the data. If you would like to be able to track a successful passing of data to the dotnet application they would need to call another RFC and send back a confirmation that they received the data.
You can go more and more complex from there depending on your requirements - e.g. when you send infos to dotnet you could store what you have sent and dotnet sends the information they received from you back and you can compare what they sent and waht you stored.
Or just a number of records back from dotnet. Again it all depends on the requirements on how detailed you need the tracking to be.
Hope that helps,
Michael

Similar Messages

  • Error Handling on RFC - XI - File Scenario

    I have an R/3 RFC -> XI -> FILE scenario that works, but does not adequately handle the error of my R/3 to XI connection being down.
    The RFC call is async since I was under the impression that I had to do a "to file" scenario that way.
        CALL FUNCTION 'ZXO_SAP2RFC'
          IN BACKGROUND TASK
          DESTINATION  wa-rfc_dest_1
          EXPORTING
            request          = request
            rfc_header       = rfc_header.
        COMMIT WORK AND WAIT.
        IF sy-subrc <> 0.
          [error handling]
    If my rfc destination is down (for example when XI is down), this RFC call is still getting a sy-subrc of '0' (so my error handling does not kick in).
    Any suggestions?

    Hi Keith,
    your scenario is working correctly. If XI is down you will find your message queued in transaction SM58, where you can restart it manually. Usually there should be standard job for report RSARFCEX, which is periodicly trieing to restard the message.
    Asynchr Call (tRFC) means that your program continues completly undependent from that call.
    Make a test: Change temporary the called machine in SM59 destination to senseless value and execute your programm. Your message should be in SM58. Then correct the destination and wait a few minutes...
    Regards,
    Udo

  • Error handling with Sync RFC

    Hi @ all,
    I have following scenario: a BPM doing some stuff on DB and map this values to a RFC request (sync) to a SAP R/3 system. Within this RFC I define 2 exceptions.
    I did map the RFC exception in interface mapping to a fault message.
    In BPM I put my RFC call into a Block with an Exception "RfcError" and insert a Exceptionbranch - which should send a email.
    Put anyhow it doesn't work - every RFC exception ends as an error in SMBX_MONI...
    Anyone a idea how to solve it??
    Regards Matt

    Hi Bhavesh,
    thanks for your tip, I see an error within my block their. But I don't know what it means to me
    Während des Anwendungs-Mappings com/sap/xi/tf/_MM_ Rfc_Error_to_Mail_ wurde eine com.sap.aii.util Work item 000000120730: Object CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot be executed
    No exception defined for system errors
    Error handling for work item 000000120729
    Runtime handle of object type  could not be created
    Runtime handle of object type  could not be created
    No exception defined for system errors
    Regards
    Matt

  • Regarding Error handling and customisation in RFC, Idocs and Proxy

    Hi,
    I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
    Please let me know in detail if possible.
    Regards,
    Sampada

    Hi ,
    Check this blog to know when to use which adapter:
      /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    we use proxy in sap 6.0 version or higher.
    Basically used for adapter less communication
    & very high volume of data has to be transfered.
    Step for Configuration fo IDOC in 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)
    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.
    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.
    In Transaction SALE
    Define and Assign the logical system name.
                                                                                    Regards,
                                                                                    Vinod.

  • Handling RFC errors

    When an RFC calls fails I get the standard Rails page with the dump; how to detect and handle rfc errors (like subrc check);
    thanks

    Hello Samuel,
    Just to close this thread and finish up my own search, where I met your discussion, here I'm quoting two experts of this forum:
    "you cannot catch the exception's value in the XI "
    (see posting from Michal Krawczyk, Jun 12, 2006, in thread catch the exception)
    "The content of a fault message are not accessible inside a BPM."
    (see posting from Bhavesh Kantilal, Oct 3, 2007, in thread Notify user about Exception in BPM)
    Regards,
    Dennis

  • Error handling in File - XI - SOAP scenario without BPM

    Hello!
    We have a File -> XI -> SOAP scenario without BPM. The problem is that if the Web Service sends back an error XI tries to reprocess the same message again and again instead of taking the next one.
    We do not want set the retry interval to NULL because most error cases are temporary connection problems and then also those messages would not automatically be reprocessed any more.
    We also have to use BE instead of EO, otherwise the Web Service will not return a response. But we need the response to be sure that the processing was successful. The message volume in this scenario is quite high and we do not want to use BPM only for the error handling.
    I know that from SP19 some additional adapter modules are available for async - sync scenarios without BPM. I tried to configure it like described in File - RFC - File without a BPM - Possible from SP 19. but it did not solve the problem. Does anybody have any other ideas? Thanks.
    Regards, Tanja

    Hi Tanja,
    >>>The volume is 3000 messages/day on business days and 700 messages/day during weekends but the traffic will increase in the future
    I think, you should check that out. It is assumedly only 2 days work to build a scenario:
    IDoc -> BP
    BP <-> SOAP/HTTP
    BP -> IDoc (Acknowledgement)
    In the process you need a condition branch, where you decide success or not. You need 2 Interface Mappings for filling the ALEAUD.
    Just send 1000 IDocs to the Test-XI and look to performance monitoring at Runtime Workbench, to find out, how many message will be processed in one hour. Assumedly 3000 and more per day should be possible. The advantage would be to reduce number of systems (no file system) and messages (better monitoring) and using the standard (better maintenance).
    >>>So you are suggesting I should use HTTP adapter and then add the SOAP header manually in a mapping?
    Yes, build the SOAP envelop during the mapping. Most easy is to use XSL or, if your mapping is ready, an additionsal XSL. You can put the error into the Acknowledgement to see it in ERP transaction WE02.
    Filling of ALEAUD fields:
    E1ADHDR/MESTYP: original message type
    E1ADHDR/E1STATE/DOCNUM: original IDoc number
    E1ADHDR/E1STATE/STATUS: 68 in case of error, 53 in case of success
    E1ADHDR/E1STATE/STATXT: Short description for R/3 user what has happend
    I ve done such a scenario several times. That works without any problems.
    Regards,
    Udo

  • BPM for error handling and acknowledgements

    Hi,
    Can any one tell me how to handle BPM for error handling and acknowledgements in one scenario.
    Please send me the link if you have other wise give me the solution on the same.
    Thanks,
    Nagesh

    Hi !
    Just check out these links This might help you.
    Usually Application Level Acknowledgement is considered during Sync communication. If you are using RFC, you can make use of Sync communication. So you can handle it without bpm, provided your both sender and receiver are sync interfaces.
    To know about Ack-
    http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
    you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
    The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
    <b>The following link has entire configuration of Receiver XI Adapter (including acknowledgements)</b>
    http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
           <b>   eror handling in BPM.  
    </b>
    1. CCMS monitoring
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
    2. BPM Monitoring
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
    3. Monitoring XML Messages http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
    Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
    Also see the below BPM related links
    check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
    /people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Many other examples can be found under the following link at help.sap.com
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    And some weblogs
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
    /people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    /people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    /people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
    Also have a look at these seminars,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
    Thanks !!!
    Regards
    Abhishek Agrahari
    Questions are welcome here!!
    <b>Also mark helpful answers by rewarding points</b>

  • RFC ERROR       timeout during allocate

    Hi all,
    We are trying to connect our ECC 6.0 system to ECC 5.0 system thru RFC we get the following error. Both the systems are available running
    Timeout during connection setup. Please check partner availability
    [abrfcio.c    8139]
    A  *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 2799
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
    Timeout during connection setup. Please check partner availability
    DEST =RQ3CLNT300
    HOST =168.189.35.139
    SERV =sapdp11
    GWHOST =dcecqv1
    GWSERV =sapgw02
    [abrfcio.c    8139]
    A  TH VERBOSE LEVEL FULL
    A  ** RABAX: end RX_GET_MESSAGE
    M
    M Wed May 14 05:41:59 2008
    M
    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Gateway on host dcecqv1 / sapgw02
    M  *  ERROR       timeout during allocate
    M  *
    M  *  TIME        Wed May 14 05:41:59 2008
    M  *  RELEASE     700
    M  *  COMPONENT   SAP-Gateway
    M  *  VERSION     2
    M  *  RC          242
    M  *  MODULE      gwr3cpic.c
    M  *  LINE        1872
    M  *  DETAIL      no connect of TP sapdp11 from host cpchrpq1.clorox.com after
    M  *              20 sec
    M  *  COUNTER     1679
    M  *
    M  *****************************************************************************
    M
    A  RFC 2318  CONVID 77332474
    A   * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPCMINIT
    A  RFC> ABAP Programm: RSRFCPIN (Transaction: SM59)
    A  RFC> User: DDIC (Client: 300)
    A  RFC> Destination: RQ3 (handle: 2, , {482AC1FF-A0EE-2871-E100-0000A8BD2A0B})
    we have mentioned the system no, hostname..every thing correctly
    Any help
    Thanks
    Senthil

    Hi Senthil,
    I had faced a similar issue working with my previous company. Upgrading the kernel had done the trick. I am not sure of the SAP note but please check Note, 827872 - Work process waits for registered RFC server
    Regards,
    Atul Lotlikar.

  • RFC Error when using SAPRFC against a Unicode System

    Hi Everybody,
    I try to use the PHP SAPRFC extension against a Unicode System. When I call the client.php which comes with the source package from http://saprfc.sourceforge.net/ where I added:
                   "CODEPAGE"=>"4103",                  // codepage Unicode
                   "UNICODE"=>"1",                      // Unicode
    to the $LOGIN array I get this error:
    Warning: RFC Error Info : Group : 103 Key : RFC_ERROR_LOGON_FAILURE Message : D
    in /var/www/saprfc/client.php on line 48
    RFC connection failed with error:RFC Error Info : Key : C
    Status : EXCEPTION SYSTEM_FAILURE RAISED Message : D Internal:
    there are two trace files after the call. One called dev_rfc.trc with this content:
    **** ERROR file opened at 20060605 050220 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
    T:1079532480 Error in program 'apache2': ======> D
    T:1079532480 Error in program 'apache2':
    <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
    and a file called rfc27443_1079532480.trc:
    **** Trace file opened at 20060605 050500 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
    <<< RfcOpenEx failed
    >TS> Mon Jun  5 05:05:06 2006
    resize I/O buffer to 16000 bytes
    >>>> [7] <unknown>    : EXT  <ac: 74> L sapserver.test.com >>> OPEN  
    UUID: ab_drvstate create uuid {44839DD5-9DCE-6B32-E200-12FDBA107532}
    >>>> [7] <unknown>    : EXT  <ac: 75> L sapserver.test.com >>> 45573492 (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    >>> RfcOpenEx ...
    Got following connect_param string:
       ASHOST=sapserver.test.com SYSNR=00 CLIENT=002 USER=developer PASSWD=*******
    LANG=EN CODEPAGE=4103 UNICODE=1 TRACE=1
    Send RFCHEADER: 01/LIT/IEEE/SPACE/4103
    Send UNICODE-RFCHEADER: cp:4103/ce:IGNORE/te:REJECT/cs:1/rc:0x00000023
    UUID: send_rfcuuid {44839DD5-9DCE-6B32-E200-12FDBA107532}
    >>> Logon check: calling RFCPING
    >>> RfcCall [7] ...
    *> RfcCall
      FUNCTION RFCPING
            handle = 7
            parameter   = <NULL>
            tables      = <NULL>
    UUID:  RfcCallNew send the uuid to the partner {44839DD5-9DCE-6B32-E200-12FDBA107532}
    >>>> [7] <unknown>    : EXT  <ac: 76> L sapserver.test.com >>> WRITE (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    000000 | D9C6C3F0 F0F0F0F0 F0F0F0E3 01010008 |................|
    000010 | 01010101 04010003 01010103 00040000 |................|
    000020 | 020B0103 0106000B 04010003 01000100 |................|
    000030 | 00002301 06000700 0F313237 2E302E30 |..#......127.0.0|
    000040 | 2E312020 20202020 00070011 00014500 |.1      ......E.|
    000050 | 11001200 04363430 20001200 13000436 |.....640 ......6|
    000060 | 34302000 13000800 20736172 67652D77 |40 ..... sarge-w|
    000070 | 77772020 20202020 20202020 20202020 |ww              |
    000080 | 20202020 20202020 20000800 0600803C |         ......<|
    000090 | 756E6B6E 6F776E3E 00000000 00000000 |unknown>........|
    0000a0 | 00000000 00000000 00000000 00000000 |................|
    0000b0 | 00000000 00000000 00000000 00000000 |................|
    0000c0 | 00000000 00000000 00000000 00000000 |................|
    0000d0 | 00000000 00000000 00000000 00000000 |................|
    0000e0 | 00000000 00000000 00000000 00000000 |................|
    0000f0 | 00000000 00000000 00000000 00000000 |................|
    000100 | 00000000 00000000 00000000 00000000 |................|
    000110 | 06051400 10D59D83 44CE9D32 6BE20012 |........D..2k...|
    000120 | FDBA1075 32051401 30000761 70616368 |...u2...0..apach|
    000130 | 65320130 01110009 44455645 4C4F5045 |e2.0....DEVELOPE|
    000140 | 52011101 17000D56 F94AFD31 E72211B4 |R......V.J.1."..|
    000150 | 1DCED7F3 01170114 00033030 32011401 |..........002...|
    000160 | 15000145 01150501 00010105 01050200 |...E............|
    000170 | 00050200 0B000336 3430000B 01020007 |.......640......|
    000180 | 52464350 494E4701 02051400 10D59D83 |RFCPING.........|
    000190 | 44CE9D32 6BE20012 FDBA1075 320514FF |D..2k......u2...|
    0001a0 | FF0000FF FF000000 00000000 00000000 |................|
    >>>> [7] <unknown>    : EXT  <ac: 77> L sapserver.test.com >>> FLUSH(WRITE) (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    <* RfcCall [7] : returns 0:RFC_OK
    >>>> [7] <unknown>    : EXT  <ac: 78> L sapserver.test.com >>> FLUSH(WRITE) (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    >>>> Listen/WaitForRequest (counter = 4)
    >>>> [7] <unknown>    : EXT  <ac: 79> L sapserver.test.com >>> LISTEN (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    000000 | 01010008 01010101 04010003 01010103 |................|
    000010 | 00040000 020B0103 0106000B 04010003 |................|
    000020 | 01000200 00002301 06001600 08310031 |......#......1.1|
    000030 | 00300030 00001600 07001E31 0030002E |.0.0.......1.0..|
    000040 | 00310032 0038002E 00330036 002E0031 |.1.2.8...3.6...1|
    000050 | 00350020 00200020 00000700 11000233 |.5. . . .......3|
    000060 | 00001100 12000836 00320030 00200000 |.......6.2.0. ..|
    000070 | 12001300 08360032 00300020 00001300 |.....6.2.0. ....|
    000080 | 08004064 00650063 00720030 0034005F |[email protected]._|
    000090 | 00430052 0034005F 00300030 00200020 |.C.R.4._.0.0. . |
    0000a0 | 00200020 00200020 00200020 00200020 |. . . . . . . . |
    0000b0 | 00200020 00200020 00200020 00200020 |. . . . . . . . |
    0000c0 | 00200000 08000601 003C756E 6B6E6F77 |. .......<unknow|
    0000d0 | 6E3E0000 00000000 00000000 00000000 |n>..............|
    0000e0 | 00000000 00000000 00000000 00000000 |................|
    0000f0 | 00000000 00000000 00000000 00000000 |................|
    000100 | 00000000 00000000 00000000 00000000 |................|
    000110 | 00000000 00000000 00000000 00000000 |................|
    000120 | 00000000 00000000 00000000 00000000 |................|
    000130 | 00000000 00000000 00000000 00000000 |................|
    000140 | 00000000 00000000 00000000 00000000 |................|
    000150 | 00000000 00000000 00000000 00000000 |................|
    000160 | 00000000 00000000 00000000 00000000 |................|
    000170 | 00000000 00000000 00000000 00000000 |................|
    000180 | 00000000 00000000 00000000 00000000 |................|
    000190 | 00000000 00000000 00000000 00000000 |................|
    0001a0 | 00000000 00000000 00000000 00000000 |................|
    0001b0 | 00000000 00000000 00000000 00000000 |................|
    0001c0 | 00000000 00000000 00000605 140010D5 |................|
    0001d0 | 9D8344CE 9D326BE2 0012FDBA 10753205 |..D..2k......u2.|
    0001e0 | 14050000 00050004 03002E43 0041004C |...........C.A.L|
    0001f0 | 004C005F 00460055 004E0043 00540049 |.L._.F.U.N.C.T.I|
    000200 | 004F004E 005F004E 004F0054 005F0046 |.O.N._.N.O.T._.F|
    000210 | 004F0055 004E0044 00040304 02004046 |.O.U.N.D......@F|
    000220 | 0075006E 00630074 0069006F 006E0020 |.u.n.c.t.i.o.n. |
    000230 | 006D006F 00640075 006C0065 00200022 |.m.o.d.u.l.e. ."|
    000240 | 00524643 50494E22 0020006E 006F0074 |.RFCPIN". .n.o.t|
    000250 | 00200066 006F0075 006E0064 002E0004 |. .f.o.u.n.d....|
    000260 | 02FFFF00 00FFFF00 00000000 00000000 |................|
    <* RfcListen [7] : returns 0:RFC_OK
    >>> RfcReceive [7] ...
    Received RFCHEADER [7]: 01/LIT/IEEE/SPACE/4103
    Received UNICODE-RFCHEADER [7]: cp:4103/ce:IGNORE/te:REJECT/cs:2/rc:0x00000023
    UUID: ab_rfccheck_uuid compare uuid's {44839DD5-9DCE-6B32-E200-12FDBA107532}
    Error in program 'apache2': ======> F
    >>>> [7] <unknown>    : EXT  <ac: 80> L sapserver.test.com >>> CLOSE abrfcrcv_mt.c 429 (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    *> RfcReceive
            handle = 7
            parameter   = <NULL>
            tables      = <NULL>
             Data conversion On
    Error in program 'apache2': <* RfcReceive [7] : returns 3:RFC_SYS_EXCEPTION
    >>>> [7] <unknown>    : EXT  <ac: 81> L sapserver.test.com >>> FREE abrfcio_mt.c 3517 (45573492)
      -{44839DD5-9DCE-6B32-E200-12FDBA107532}
    **** Trace file opened at 20060605 050506 CEST, SAP-REL 640,0,119 RFC-VER 3 818129 MT-SL
    <<< RfcOpenEx failed
    Our SAP Environment is:
    - SAP Web AS 6.20 Unicode Kernel Patchlevel 1602
    - Windows 2003 Server
    - Oracle
    On the PHP Side I use:
    - Debian GNU/Linux 3.1 (Sarge)
    - Apache 2 2.0.54-5
    - PHP4 4.3.10-16
    - SAPRFC 1.4.1
    - SAP RFC SDK non Unicode 6.20 and 6.40 (The problem occurs in both versions)
    Had anyone had sucess using SAPRFC against a Unicode System?
    Regards
    Gregor

    Hi Anton,
    I've just tried your suggestion. I've commented out the CODEPAGE and UNICODE values in my Array and placed:
    [code]saprfc_set_code_page($rfc, "4103");[/code]
    after the
    [code]$rfc = saprfc_open ($LOGIN);[/code]
    The error message I get now is:
    [code]Warning: RFC Error Info : Key : Status : EXCEPTION FU_NOT_FOUND RAISED Message :
    Internal: in /var/www/saprfc/client.php on line 58
    Discovering interface of function module RFC_READ_REPORT failed[/code]
    In the trace File I see:
    [code]>>>> [3] <unknown>    : EXT  <ac: 40> L sapserver.test.com >>> WRITE (80999721)
      -{44839E3E-9E3B-6B30-E200-0534B0CD3057}
    000000 | 05020000 0502000B 00063600 34003000 |..........6.4.0.|
    000010 | 000B0102 00385200 46004300 5F004700 |.....8R.F.C._.G.|
    000020 | 45005400 5F004600 55004E00 43005400 |E.T._.F.U.N.C.T.|
    000030 | 49004F00 4E005F00 49004E00 54004500 |I.O.N._.I.N.T.E.|
    000040 | 52004600 41004300 45005F00 50000102 |R.F.A.C.E._.P...|
    000050 | 05140010 3E9E8344 3B9E306B E2000534 |....>..D;.0k...4|
    000060 | B0CD3057 05140201 00104600 55004E00 |..0W......F.U.N.|
    000070 | 43004E00 41004D00 45000201 0203001E |C.N.A.M.E.......|
    000080 | 5246435F 52454144 5F524550 4F525420 |RFC_READ_REPORT |
    000090 | 20202020 20202020 20202020 20200203 |              ..|
    0000a0 | 03010010 50004100 52004100 4D005300 |....P.A.R.A.M.S.|
    0000b0 | 5F005000 03010330 00040000 00010330 |_.P....0.......0|
    0000c0 | 03020008 000000D8 00000000 0302FFFF |................|
    0000d0 | 0000FFFF 00000000 00000000 00000000 |................|
    >>>> [3] <unknown>    : EXT  <ac: 41> L sapserver.test.com >>> FLUSH(WRITE) (80999721)
      -{44839E3E-9E3B-6B30-E200-0534B0CD3057}
    <* RfcCall [3] : returns 0:RFC_OK
    >>> RfcReceive [3] ...
    >>>> [3] <unknown>    : EXT  <ac: 42> L sapserver.test.com >>> FLUSH(WRITE) (80999721)
      -{44839E3E-9E3B-6B30-E200-0534B0CD3057}
    >>>> [3] <unknown>    : EXT  <ac: 43> L sapserver.test.com >>> READ (80999721)
      -{44839E3E-9E3B-6B30-E200-0534B0CD3057}
    000000 | 05000000 05000415 00044600 4C000415 |..........F.L...|
    000010 | 04160002 45000416 04170006 30003400 |....E.......0.4.|
    000020 | 36000417 04010018 46005500 5F004E00 |6.......F.U._.N.|
    000030 | 4F005400 5F004600 4F005500 4E004400 |O.T._.F.O.U.N.D.|
    000040 | 0401FFFF 0000FFFF 00000000 00000000 |................|
    >>>> [3] <unknown>    : EXT  <ac: 44> L sapserver.test.com >>> FLUSH (READ) (80999721)
      -{44839E3E-9E3B-6B30-E200-0534B0CD3057}[/code]
    Regards
    Gregor

  • Error handling in XI

    Hi All,
    I am implementing several scenarios in XI. They are mainly dealing with RFC, JDBC adapter, file.
    The main communication is between SAP R/3 and Oracle via XI, both to and fro.
    Pls tell me what are the standard error handling mechanisms in XI.
    The main focus areas are as follows:
    1. If the sender XML format in XI has error, how to inform the sender system.
    2. If receiver Oracle system finds some error in the received msg, how to inform the sender system.
    This is urgent, pls help asap.
    Regards
    Neetu

    Hi Neetu,
    You can use Alerts for the same..... Please go through the information below to know more...
    For alerts take a look at this blog,
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
    For CCMS monitoring, this document,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
    From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
    If you are blow SP14, then also check this blog,
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
    To send an EMAIL, assign an EMAIL ID to the corresponding user in the transaction SU01 and then set up SCOT and you can send emails when the ALERT is triggered.
    Once you have configure Alerts, you will get the Alerts into ALERT INBOX in RWB of the user. To also get the email, the following needs to be done,
    1. In SU01 -- Assign the Email ID for the Recipient of the ALERT.
    2. In , RWB>ALERT INBOX> PERSONALIZATION--> Time Independent Delivery and Email are selected.
    3. Finally, SCOT needs to be set up to send Emails. Check this for the same. You can ask your BASIS team to do this step.
    http://help.sap.com/saphelp_nw04/helpdata/en/23/1edf098ea211d2b47300609419ed29/frameset.htm
    Also, to test your Alerts, execute the report RSALERTTEST in SE38.
    Regards,
    Abhy

  • SAP NetWeaver Gateway and JSON Error Handling

    Hello All,
    I am developing a small test application using Netweaver Gateway to understand the error handling.  I am using Postman to test the Gateway service.  I have developed small RFC FM to read return list of deliveries for a shipment.  The RFC reads in a shipment number and returns the list of deliveries.  The RFC also has Return parameter of type BAPIRET2 that stores the error message if shipment is not found.  We want to use only JSON format for the application.  So, I have set the 'Accept' parameter at request header to 'content/json'.  I am also aware of the exception /IWBEP/CX_MGW_BUSI_EXCEPTION that allows to throw an error message from backend suite.  I have that by having a Return parameter of type BAPIRET2, the generated method automatically handles the error message and sets the correct HTTP status.
    Now the Problem:
    As mentioned earlier, we want to use JSON format.  When I set the header parameter or specify $format=json in the URI the HTTP status code is always set to 500 when there is an error.  The error message about invalid shipment also is not returned.
    When I remove the JSON format parameters, the XML format is returned and HTTP status is set to 400 with appropriate error message.
    How can we get the Gateway to set the HTTP status code to 400 along with error message in the event of an error in RFC.  I have tried with the exception /IWBEP/CX_MGW_BUSI_EXCEPTION and BAPIRET2 return parameter but still does not work.  Is this a known issue in Gateway/JSON?
    Please see attached screenshots.
    Thanks,
    Rutul Thakkar

    Anyone have encountered this issue?  Any suggestions?
    Thanks,
    Rutul Thakkar

  • Error handling using BPM

    hi all
           I would like to do an error handling scenario using BPM in XI. As i haven't done it before, can somebody give me links to good blogs and materials in this regards.
    Thanks
    Sumayya

    HI,
    Check the below links
    monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
    Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
    Also see the below BPM related links
    check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
    /people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
    http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Many other examples can be found under the following link at help.sap.com
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    And some weblogs
    https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    /people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    /people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
    /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    /people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
    /people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
    Also have a look at these seminars,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
    Regards
    Chilla

  • Client ABAP proxy error handling. Please help!

    Hi Experts,
       I have following scenario:
       SAP ECC (ABAP Client Proxy) -> PI(XI)-->(SOAP) Third party web service System
       This is Asynchronous.
       What will happen when ABAP client Proxy in ECC sends data to PI but PI is down?
       Will the message be queued in ECC? Can the queued message be processed automatically when PI is UP later?
       Please help.
    Thanks & Regards
    Gopal

    Hello Gopal,
    Correct, it should be an automatic entry into the queue!
    refer below for a detailed understanding!
    /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies     XI: Reliable Messaging u2013 EOIO in ABAP Proxies
    /people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy     Monitoring for Processed XML messages in ABAP Proxy
    Weblog to send Response from RFC to File in Asyn Mode Using Proxy [original link is broken]     Weblog to send Response from RFC to File in Asyn Mode Using Proxy
    /people/michal.krawczyk2/blog/2009/06/20/pixi-abap-proxies-say-goodbye-to-executeasynchronous-method     PI/XI: ABAP Proxies say goodbye to Execute_Asynchronous method
    /people/krishnakumar.ramamoorthy3/blog/2008/11/02/error-handling-framework-for-abap-proxies--part-1     Error handling framework for ABAP proxies - Part 1
    /people/krishnakumar.ramamoorthy3/blog/2008/12/19/error-handling-framework-for-abap-proxies--part-2     Error handling framework for ABAP proxies - Part 2
    Regards,
    Jilan

  • Error Handling Framework

    Can anybody point or give me a good document on Error handling (Monitoting and Alerting) Framework in XI.
    Thanks in advance.
    Mukesh

    Hi Sudhir,
    Suppose the below is an Error XML message in Monitor in transaction sxmb_moni. Can we Catch these kind of error log messages and send an alert for it. Please suggest any kind of way thru which we can catch these kind of error messages. The below is just an example of an RFC destination error.
    <?xml version=”1.0” encoding=”UTF-8” standalone=”yes” ?>
    <!--  Response   -->
    <SAP:Error xmlns:SAP=”http://sap.com/xi/XI/Message/30”
       xmlns:SOAP=”http://schemas.xmlsoap.org/soap/envelope/” SOAP:mustUnderstand=””
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP: Code area=”IDOC_ADAPTER”>ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1:Port ABCDE, client, RFC destination contains errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace=”” />
      <SAP:Stack>Error: Transaction IDX1: Port ABCDE, Client, RFC destination contains errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Your help will be appreciated.
    Regards
    Ashish

  • Error Handling in XI3

    Hi all,
    I am new to XI. Can anyone guide me how to handle error in XI. To elaborate more, if we use asynchronous or syncronous scenarios and if there are any problems or errors during execution of those scenarios, how to handle that?
    thanks,
    KP

    Hi,
    first you have to distinguish between error handling in the applications and monitoring. As writen before, there is the CCMS and the alerting functions of the XI Runtime Workbench for the monitoring.
    The error handling differs in synchronous and asynchronous scenarios and by the adapters you use. If you are using proxies (ABAP or JAVA) the receiver application can raise an exception. In a synchronous scenario the exception is transported by XI to the sender and a exception is raised there too. You can define different exceptions in the XI repository and add datatypes for specific error data. These fault messages are assigned to an interface and exception classes are generated for the proxies. Unfortunately most adapters don't make it that easy. In RFCs you can use the message structure sy-msgid, sy-msgty, sy-msgno and sy-msgv1 to sy-msgv4. It depends on the adapters what is possible.
    If you are in an asynchronous world, there is no return message to the sender. If a receiver proxy raises an exception, you can see the exception in the inbound monitoring (SXMB_MONI or MessagingSystem) of the receiver system. Then you can use the error monitoring via ccms or alerting, to monitor and report the errors to the operating.
    Another way is to use Acknowlegments to send back the status of the process. In this case you don't handle errors, but send back success messages. If the success messages is not coming back, you know there is a problem. but you need to keep track of your outgoing messages.
    Notice, that if you use the XI messsaging (standard functionality) for error messages, you can not report errors, if the messaging system is broken down. CCMS is working parallel, and low level, to the messaging functionality of XI and can operate, even if XI is not working. It may be good to have a seperate monitoring server like SAP Solution Manager.
    Regards,
    Christian

Maybe you are looking for

  • What is the best way to make my file in FCPX Compatible for a DVD.

    I am working with a file that is about 53 minutes in length.  The video is broken up into 14 3to5 minute videos.  During my project, as I completed each video, I saved a master file and shared as APPLE PRO RES so that I wouldnt lose anything as this

  • Creating directory

    How can I create directory(folder) in the file system with pl/sql. I know you can create file or write in to a file, in any folder in file system with utl_file. but what about creating a folder then a file in to it.

  • Playback level after burning a cd in waveburner

    after reading a number of posts concerning lower volume levels after burning a cd in WB: just tested this. from what i can see and hear: there is no difference between the levels in the original WB file and the resulting cd. anyone getting a lower le

  • Please help-image problem (display)

    Can someone please help with this? I keep receiving an error (below) while trying to execute the code... 2001-07-19 11:55:02 - Ctx( /dev ): IOException in: R( /dev + /servlet/getImage + null) Connection reset by peer: socket write error My setup is T

  • ¿pero cómo puede ser tan difícil el escoger 4 fotos y que el programa te las ponga una junto a otra?

    Pero cómo puede ser tan difícil el que tú escojas 5 fotos y que luego te las junte una junto a la otra? Es una m... Es una pena lo poco intuitivo que es el programa. Te tienes que poner a estudiar antes de poder mover un elemento. Más que ayudar lo q