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: 

Disabling insert/delete condition records in VA02

Former Member
0 Kudos

Hi All, I am doing a authorization check on the user logged in and based on that disabling the condition records from being changed/displayed on the condition records screen of VA02. I am able to do this from the user exits provided in the include LV69AFZZ. But, this being a subscreen, it wont allow me to set the PF-STATUS excluding the function codes of the insert/delete condition records of the conditions table. I tried to look for user exits in the PBO of the main screen (SAPMV45A, screen 5003), but looks like there are none provided. Has anyone done this before or have any idea of implementing this. Any pointers would be much appreciated.

1 ACCEPTED SOLUTION

vijaymanikandan
Contributor
0 Kudos

Hi Avinash,

I can find some Enhancement points in the program and may be we can try to use that.

Enhancement Spot ES_SAPMV45A in the include MV45AO0P_PRIC_SUBSCR_SET_DATA.

enhancement implementation OIC_SAPMV45A

I didnt try it out but just a random check in the system.

Regards,

Vijay V

4 REPLIES 4

vijaymanikandan
Contributor
0 Kudos

Hi Avinash,

I can find some Enhancement points in the program and may be we can try to use that.

Enhancement Spot ES_SAPMV45A in the include MV45AO0P_PRIC_SUBSCR_SET_DATA.

enhancement implementation OIC_SAPMV45A

I didnt try it out but just a random check in the system.

Regards,

Vijay V

0 Kudos

Thank you Vijay. I will give it a try and post an update.

vinod_vemuru2
Active Contributor
0 Kudos

Hi,

This can be achieved through transaction variant. Create a transaction variant in SHD0 by disabling the required buttons.

In MV45AFZZ subroutine USEREXIT_MOVE_FIELDS_TO_VBAK assign this transaction variant name to field TVKO-VARIANT based on your authorization checks.

Now assign this transaction variant as the standard variant of VA02 in t-code SHD0. It will work fine.

There are many threads related to transaction variant for VA01/02/03 for help.

Thanks,

Vinod.

0 Kudos

I was able to disable the buttons by identifying the screen name and then setting them to inactive in my code. The include LV69AFZZ, which contains the user exits for condition table screen, is called from the PBO module.

To my knowledge, MV45AFZZ is no more used for processing the condition table in recent releases (4.6 +). The condition table is being displayed using a sub screen and the associated user exits are called from the include LV69AFZZ.

Thank you all for your time and suggestions.