Runtime error RFC_NO_AUTHORITY has occurred

[Former Member]

I have searched in the internet regarding this problem but I don't think it's a authorization issue.

I created a function module and RFC-enabled it. Tested the FM not RFC-enabled, it's working fine but when RFC-enabled, it's giving a message (not a dump) "Runtime error RFC_NO_AUTHORITY has occurred". The account I'm using isn't having an error when calling other RFC enabled FM. Could you help me determine other possible causes or what should I check?

Thanks in advance!

[Former Member]

If you set break at statement "authority-check" you'll stop at

Also:

authority-check object 'S_DEVELOP'

       id 'DEVCLASS' field wa_tadir-devclass

       id 'OBJTYPE' field 'FUGR'

       id 'OBJNAME' field rs38l-area

       id 'P_GROUP' dummy

       id 'ACTVT' field '16'.

TWICE...

authority-check object 'S_CTS_ADMI'

                 id     'CTS_ADMFCT'

                 field  iv_adminfunction.

Are you passing all of these authority checks?

Neal

[Former Member]

Hi Neal,

Yes, I am passing those authority checks. Here's the actual screenshot i'm getting.

[Former Member]

Do you know how to use a where used on a message?

Do you know how to debug for only message statements?

Those would be my two next steps.

Neal

[anilkumar_kalkivai]

Hi Allan,

Try the steps in the following link.

http://www.saptechies.com/rfc-short-dump-rfcnoauthority/

Hope this might help you.

Regards,

Anil.

[former_member188827]

Run transaction SU53 after you get the message and check if it shows any failed authorization.

Regards

[satyabrata_sahoo3]

When RFC enabled ensure all importing exporting parameters should be pass by value and the FM should released if calling from external system.

also execute the FM in debug mode and check where exactly the error coming from.

-Satya

[Former Member]

Hi Satya,

I'm getting a system failure error message. This doesn't explain the problem well.

[satyabrata_sahoo3]

You check the RFC (DESTI value) in SM59 if Authorization for Destination has been set.

If set, then you need to have S_ICF authorization for this.

-Satya

[arindam_m]

Hi,

Just get the Authorization from your basis team that's all

Cheers,

Arindam

[Former Member]

Hi Allan,

I think you will have a missing authority for

   authority-check object 'S_RFC'

            id 'RFC_TYPE' field 'FUGR'

            id 'RFC_NAME' field functiongroup

            id 'ACTVT' field '16'.

You need the authority to execute function modules in the function group, where your new RFC function module is located.

Regards,

Klaus 

[Former Member]

Hi Klaus,

I created a new function group and I'm still having the error so does this mean I don't have authorization even I created this function group? Do you know what specific roles should I request to acquire authorization?

[ThomasZloch]

Look for the dump in the remote system, not in the local system. The user ID in the remote system requires the S_RFC authorisation per function group as outlined by Klaus. The user ID should be maintained in the RFC connection, or it is the user ID of the caller in case of trusted systems.

These are all system administration topics, not so much ABAP development. Also, there should be plenty of available RFC related documentation by SAP and other sources.

Thomas

[Former Member]

Authorizations have nothing to do with who creates things.  The security (basis) people give them out by what ever rules they have.  Those rules don't often seem reasonable to us.  However, don't expect them to care...

Neal

[Former Member]

Yes, you have to "publish" your new function group to some user roles for RFC authorization.

Regards,

Klaus

[RaymondGiuseppi]

Well, this error message is explained in the online (or F1) help of the statement like CALL FONCTION - RFC and in help.sap.com in documents like RFC Authorizations.

Regards,

Raymond