2015 Oct 07 7:54 AM
Hi Experts,
I need to create an RFC function module and pass the exporting parameter a deep structure(nearly 10 structures). It seems very difficult to create a structure in SE11 and its very time taken to create all these stuff, so I created a deep structure in type group and try to use this in my function module. It is working fine with normal function module but when comes to RFC function module i am getting an message that it was not exists even though i declare that type groups in the top Include of function module.
Can anyone help me regarding this issue.
Thanks and regards,
Girish Kumar.
2015 Oct 07 8:43 AM
AFAIK you MUST use ddic definition for RFC enabled FM...
from 458283 - Error message Fl 385 "Type &1 is unknown"
Types from the type pools are not allowed for RFC-compatiblefunction modules. The FL 385 error message should correctly read:
"Type &1 is unknown or forbidden".
Regards,
Raymond
2015 Oct 07 8:08 AM
Hi Girish,
Did you mention function module as “Remote-enabled module” in the attributes tab?
2015 Oct 07 8:14 AM
Hi Vishnu,
Yes I have mentioned RFC in attributes,
Thanks and Regards,
Girish Kumar V.
2015 Oct 07 8:22 AM
Didi you followed the below steps while creating the RFC.
1. Create a FM in SE37 in Target system enabling Remote-Fucntion Enabled Usin attributes of FM.
2. Create the same FM in the Local system ( It's recommended for later debugging) create only the structure - NO Need to put the code and all.
3. Creata a RFC connection in SM59 mentioning Usernam and Password.
4. Using this RFC connctin name, Call the FM in u program using CALL FUNCTION ABC DESTINATION 'YZ'.
sy-subrc value
1 - System Failure
2 - Communication Failure
it is default sy-subrc values in RFCs
2015 Oct 07 8:43 AM
AFAIK you MUST use ddic definition for RFC enabled FM...
from 458283 - Error message Fl 385 "Type &1 is unknown"
Types from the type pools are not allowed for RFC-compatiblefunction modules. The FL 385 error message should correctly read:
"Type &1 is unknown or forbidden".
Regards,
Raymond
2015 Oct 07 12:33 PM
Hello Girish,
Exporting parameters in an RFC enabled function module is not recommended as it can cause performance issues and as suggested by Raymond we do need to use DDIC type.
I would recommend you to use TABLES parameter instead of EXPORTING parameters.
Cheers,
Varun
2015 Oct 07 2:22 PM
Well you have to choose:
- Using TABLES parameters for remote-enabled function modules for RFC can be significantly faster than passing by means of the CHANGING parameter.
- The additional option of defining table parameters using TABLES is obsolete.
Regards,
Raymond