Various tools that do not (completely) belong to the ABAP Workbench give you the option to display ABAP Workbench objects on their processing screens.
The central interface function module RS_TOOL_ACCESS is frequently called for this navigation.
Typical of this are transactions SE01, SE09, and SE10 of the correction and transport systems. If a transport request contains a particular program, for example, you can double-click the program name to navigate to the program display, that is, to the ABAP Editor. From this processing tool, you have many options for navigating to other Workbench tools. These tools also often have separate transaction codes. In many cases, you can access them only using the Object Navigator (transaction SE80).
Therefore, being authorized to execute transaction SE80 is of central importance for the assignment to user profiles.
Therefore, when the user executes the first navigation step that leads to an object that will be processed by the Object Navigator, the system should check whether or not the user profile is authorized to call transaction SE80 (Object Navigation).
Previously, the caller had to perform this check themselves when navigating using RS_TOOL_ACCESS, and they had to check before calling RS_TOOL_ACCESS.
Other terms
CTS, Change and Transport System
Reason and Prerequisites
This is due to a missing authorization check in RS_TOOL_ACCESS.
Solution
Use the Note Assistant to implement the correction instructions or import the relevant Support Package.
After you do this, the authorization for transaction SE80 is checked at the beginning of the source code of the function module RS_TOOL_ACCESS. Therefore, the check is performed even if the caller does not execute it themselves (as in the case of transactions SE01, SE09, and SE10).
For releases lower than Release 46C, you can implement the 46C correction instructions for the module RS_TOOL_ACCESS.
Affected Releases
|
No comments:
Post a Comment