function module call with destination

[Former Member]

Hi,

how can check if a function module call with destination works or not ?

How can I debug.

What can be the reason if it is not calles

regards

ertas

[Former Member]

* to chcek the rfc Destination By pass RFC destination name and Connection Type..
RFC_CHECK_DESTINATION

or

RFC_CHECK_DESTINATION_ID

or

You can use this FM RFC_VERIFY_DESTINATION if your release is greater than 4.6C.

Check this sample code from Craig Cmehil's weblog.

CALL FUNCTION 'RFC_VERIFY_DESTINATION'
  EXPORTING
    DESTINATION = TMP
        TIMEOUT = 10
  EXCEPTIONS
    INTERNAL_FAILURE           = 1
    TIMEOUT                    = 2
    DEST_COMMUNICATION_FAILURE = 3
    DEST_SYSTEM_FAILURE        = 4
    UPDATE_FAILURE             = 5
    NO_UPDATE_AUTHORITY        = 6
    OTHERS                     = 7.
 
  IF SY-SUBRC EQ '0'.
    "* Do code here
  ENDIF.

Prabhu

[Former Member]

Hi,

To debug go to transaction se37. After displaying your FM go to source code tab and in the code place a session break point.

When the FM will be called from your code you can see whats the issue in FM.

Hope it helps.

Regards,

Ibrar Munsif

[Former Member]

hai ilhan

just chekc the function module u have called exists in target system

and check paramters are proper and check the rfc destination in sm59 wether it is workign properly

m.a

[Former Member]

how can I debug such a Function Module call (it has Destination additional ).

[Former Member]

i hve replied it in ur previous thread

[Former Member]

Hi Malik,

this way didn' t work.

Is it necessary to have an special user (RFC User ???)

>in se38 goto utilites

>settings ->debugging then in the field user give the id by which you are logging in your srm application

>

>Then in se38 wherever you want to put a break point press ctrl shift f9 to set a external breakpoint

>

>Then run your srm application with the same user id

Regards

ertas

Edited by: Julius Bussche on Jun 13, 2009 8:38 AM

Code tags replaced by quotes to fix formatting.

[Former Member]

Yes, the RFC user entered in SM59 will need authority for display debugging (S_DEVELOP object type DEBUG) and the user type will need to be capable of attaching a SAPGui to the session (user type = SERVICE).

For the procedure and constraints, type "debugging single-step" into the OSS search. The first 3 notes are the ones you are looking for.

905364 Authorizations for single step debugging of RFCs

300208 Single step debugging of RFC calls

1328076 Single-step debugging of a synchronous RFC from HTTP session

If it still does not work, then debugging might have been disabled at the system level.

Cheers,

Julius