Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Call transaction to bypass authorization

Former Member
0 Kudos

Hi,

In transaction MCK2, I need to allow certain users to be able to change certain hierarchies only.

On initial discussion with basis they told me that they can split it only at the transaction level (or maybe that's how the client does it.. Because, I do know in certain SAP transactions we can give authority based on the field values.)

Anyhow, I created a shell transaction that calls MCK2 transaction and skips the initial screen (I do a set parameter ID before the call).

The problem I have is when we press the BACK button it comes back to the initial screen of MCK2 and there they have access to all hierarchies. My question is there a way to solve the problem without modifying SAP code.

Thanks,

Ani

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

Try creating the shell with tcode- "shd0" Transaction Variants. They are very easy to create and maintain.

Viren.

5 REPLIES 5

Former Member
0 Kudos

Hi,

Try creating the shell with tcode- "shd0" Transaction Variants. They are very easy to create and maintain.

Viren.

0 Kudos

Thanks Viren..

The problem I have is not how to create the transaction (I will be creating a shell program which does some validations and then does the CALL transaction MCK2 skip screen)

I need to find out, if I can bypass the initial screen on pressing the BACK or CANC button.

PS: Another way I assume would be to copy the whole SAP program into ZProg and put the needed authorization in

the Zprog/Ztrans..

Let me know your thoughts..

0 Kudos

Hello Ani

You probably have to combine the two approaches:

(1) Define a small report having only the select parameter as the standard transaction.

(2) Use the same logic as in the standard program (MODULE hiernm_f4_help INPUT.) to define the search help (AT SELECTION-SCREEN ON VALUE-REQUEST FOR <parameter>). Here you restrict the selection specifically for each user.

(3) Define transaction variants for MCK2 that disable the input field (or you can even skip the screen).

(4) Define a z-transaction for your report.

Now the user calls your z-transaction starting your z-report. The user chooses a hierarchy and presses F8. Your report call the transaction variant.

Regards

Uwe

0 Kudos

Hi Uwe,

Thanks for your help. I think, it is working fine.

One problem that I have right now is:

I created a test variant and selected 'Do not display screen'.

Created a variant transaction for this variant and exucuted it. It takes my directly to the desired hierarchy, but the EXIT, CANCEL and BACK buttons are not working in the screen.

Let me know if any inputs.

Thanks,

Ani

0 Kudos

Hi Uwe/Viren,

I have not been able to award points, as the point system is down.

I will award points once it's up and running.

thanks,

Ani