Blocking a function code in a standard transaction

[Former Member]

Hello Guys,

I have a requirement of blocking the create option in a standard Tcode if the transaction is done manually. On the other hand, if the transaction is through BDC, the creation should be enabled. Anybody have any experience on this?

Thanks and Regards,

Gregoo

[kesavadas_thekkillath]

Which transaction ?

[Former Member]

It is a HR transaction. PA30

[SuhaSaha]

I have a requirement of blocking the create option in a standard Tcode if the transaction is done manually. 

Ask the basis team to create a role for "display only" and assign it to all the users supposed to access the t-code/

On the other hand, if the transaction is through BDC, the creation should be enabled

CALL TRANSACTION does not check the user's authorization to execute the transaction implicitly (unless you explicitly use S_TCODE to check it). So for this you do not need any specific configuration to be made.

BR,

Suhas

[Former Member]

Hello Suhas,

Thank you for the reply. I forgot to mention that the disabling of the function code should be based on the data entered. For particular input, the create should be allowed and for other input, there should be an error message telling that use only the BDC program for creating.

If you are familiar with PA30, the user should get error message only if he tries to create for a particular infotype and subtype. For the rest of the infotypes, he should be able to create.

Any inputs on this?

Thanks and Regards,

Gregoo

[Former Member]

Hello Can u check the below exit.

HRPBAS01 : User Exit for HR Master Data.

put the below code .

if sy-tcode eq ' PA30'.

message ' Not allowed'.

endif.

for bdc

check sy-tcode ne 'PA30'.

With Regards,

Sumodh.P

[Former Member]

Hello Guys,

I solved this by usinf the system variable 'BINPT'. Thanks for your support!!

Thanks and Regards,

Gregoo