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: 

Disable update options in VA23

luis_rod
Participant
0 Kudos
423

Hi all,

I have a Z program that makes a call to the VA23 (Display Quotation) transaction. Is there any way to disable the edit option that calls to VA22?

Thanks in advance,

Luis Rodriguez

1 ACCEPTED SOLUTION

Jelena_Perfiljeva
Active Contributor
0 Kudos
366

I'm assuming you're using CALL TRANSACTION. It's not possible with a standard transaction. You could create a custom transaction using a variant with any pieces hidden and call that instead.

But I would question the value of doing this because authorizations already determine whether a user can have access to edit a document. I think the menu is supposed to be hidden if a user has no access (it doesn't happen consistently though). But if they do have authorization to edit, then what exactly would you solve if you just hide it when transaction is called from a custom report? What would prevent the users from just opening VA22 in another session?

2 REPLIES 2

Jelena_Perfiljeva
Active Contributor
0 Kudos
367

I'm assuming you're using CALL TRANSACTION. It's not possible with a standard transaction. You could create a custom transaction using a variant with any pieces hidden and call that instead.

But I would question the value of doing this because authorizations already determine whether a user can have access to edit a document. I think the menu is supposed to be hidden if a user has no access (it doesn't happen consistently though). But if they do have authorization to edit, then what exactly would you solve if you just hide it when transaction is called from a custom report? What would prevent the users from just opening VA22 in another session?

0 Kudos
366

Jelena,

Thanks for your post. In this particular case, the user calls a custom (Z) transaction that performs some steps before and after the CALL and, depending on certain conditions, calls either the VA22 or the VA23. What I would like to avoid is that the user calls back VA22 by mistake.

The idea of a custom transaction with a variant looks interesting. Also, it's possible that I'm overstating the problem and the users are more conscientious that I'm giving them credit for 🙂

Thanks again,

Luis