Application Development and Automation 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: 
Read only

control from custom Tcode goin back to STD Tcode screen on save / back.

Former Member
0 Likes
452

Hi all,

I have a coustom transaction ZTVF02 which calls the STD transaction VF02. After entrting into the custom transaction and save after making changes to the document, the control comes back to the Tcode VF02 rather than going to the ZTVF02.

Because of this the users who do not have direct access to VF02, gets an error message for no authorization when they do a save. The values are getting saved but the error message is giving the users a impression that the changes are not saved.

I checked creating a custom tcode for VF01, but that is returning to the screen of ZTVF01 itself. This probelm seams to happen only for ZTVF2.

Please let me know what can be done to get over this issue.

2 REPLIES 2
Read only

mithun_shetty4
Contributor
0 Likes
425

Why don't you do an authority check before calling the VF02 transaction ? This will avoid the error message and freeze in screen

Read only

0 Likes
425

Hi Mithun,

I dont think u have got the issue,

I have a transaction varient for the std transaction. This varient is for the users who do not have access to the std transaction.

Usually when we do a save to the custom Tcode we go back to the main screen of the transaction varient, but here it is going to the main screen of the original transaction. i want the control to go to the transaction varient.