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.
You can do this with authorisations. Create your maintenance screen with a unique authorisation group and only give update access to users in one client.
Alternatively, if this is a customising table define the standard recording routine and use the client settings to restrict access in non-config clients.
As mentiond in the previous post you ca use authorization or you can use the event 25 'Individual Authorization Check' , in the subroutine you create for it , you can check the client and exit if required:
This event will be called when the user starts the table maintenece.
As far as events in the table maintenence is concerned , please check th ehelp of that .
What is generally done , is we decide which event to use of the many provided by sap and once we select it , we need to create a subroutine containing the code which we want to be executed .
Comming specific to the event i mentioned , it iw triggred when the user enters the maintenence screen , thre you can check the client and if the client is not allowed to make modificaton , you can give an error message and exit from the maintenence.
Bluesky
