‎2005 Sep 02 8:48 PM
Is the following statement true or false?:
"For every RFC function that you can call,
you can also access its signature
(using RFC_GET_FUNCTION_INTERFACE_P)"
‎2005 Sep 02 9:11 PM
Sure......why? You got an argument against that statement?
report zrich_0002 .
data: signature type table of rfc_fint_p with header line.
parameters: p_func type tfdir-funcname.
call function 'RFC_GET_FUNCTION_INTERFACE_P'
exporting
funcname = p_func
* LANGUAGE = SY-LANGU
tables
params_p = signature
* EXCEPTIONS
* FU_NOT_FOUND = 1
* NAMETAB_FAULT = 2
* OTHERS = 3
.
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
loop at signature.
write:/ signature-paramclass,
signature-parameter,
signature-tabname,
signature-fieldname,
signature-exid,
signature-position,
signature-offset,
signature-intlength,
signature-decimals,
signature-default,
signature-paramtext,
signature-optional.
endloop.
Regards,
Rich Heilman
‎2005 Sep 02 10:52 PM
I'm not SAP insider. So, I'm not aware of possible pitfalls, sorry. Typical C-Java guy think that in С you can not ask function signatures in run-time, in Java, you can.
1. How is this implemented in SAP?
2. If my external RFC server registers function using RfcInstallFunction(), how RFC_GET_FUNCTION_INTERFACE_P would know its signature?
3. Calling RFC_GET_FUNCTION_INTERFACE_P for itself in QEC (non Unicode) expose extra parameter <b>NONE_UNICODE_LENGTH</b> in my RFC application (Unicode) but do not expose it in my SAPGUI (non Unicode?). Where can I read about this?
4. What about Unicode and RFC_GET_STRUCTURE_DEFINITION_P?
Sorry for too many questions - expect many bonus points!
‎2005 Sep 02 11:22 PM