Authzorization check

[Former Member]

Hi all,

I have to solve following issue:

In a function module there is a call of a transaction (ICLCDC02) via BDC to update data in another module. The issue now is, that the user has not the authorization for this transaction and is also not allowed to access this transaction (it is not in the menu, but he could be able to type it in the commando field) - but for the call tarnsaction is the authorization needed.

Is there any idea/ workaround/ solution? Is it possible giving the user the authzorization but catching this when he tries to access the transaction by typing? Or can I override the Authorization Check in a call transaction?

Thanks in Advance for your help,

Regards Fabian

[Former Member]

Hi all,

I have to solve following issue:

In a function module there is a call of a transaction (ICLCDC02) via BDC to update data in another module. The issue now is, that the user has not the authorization for this transaction and is also not allowed to access this transaction (it is not in the menu, but he could be able to type it in the commando field) - but for the call tarnsaction is the authorization needed.

Is there any idea/ workaround/ solution? Is it possible giving the user the authzorization but catching this when he tries to access the transaction by typing? Or can I override the Authorization Check in a call transaction?

Thanks in Advance for your help,

Regards Fabian

[Former Member]

What is the transaction being called in the function? Also let me know the authorization object if you know it already.

-Kiran

[Former Member]

first find out what are the Authorizations required to access this Tcode .

or else

before calling this Tcode just check authorization for this Tcode

<b>AUTHORITY_CHECK_TCODE</b> and raise eroor message.

regards

Prabhu

[christian_wohlfahrt]

Hi Fabian!

In general: if a user has to do something, than he should have the authorization. At least the authorization for the objects / areas are necessary, but the authorization for the transaction itself can be different. Have a look at documentation of call transaction:

"At the statement CALL TRANSACTION, the authorization of the current user to execute the called transaction is not checked automatically. If the calling program does not execute a check, the called program must check the authorization. To do this, the called program must call function module AUTHORITY_CHECK_TCODE."

So the tcode-authorization is not checked during call transaction -> you should be able to forbid the transaction, but user needs to be able to create / change / delete the objects.

Regards,

Christian