You execute a function module directly from SE37. The system does not check the same authorizations as if the module is started from a certain transaction.
In the menu of transaction SE16N, there are branches that are not required in this environment.
There is another transaction 'N', which branches to SE16N.
Other terms
Transactions: SE37,
SE16N_START, RK_SE16N, SE16N, N
Reason and Prerequisites
Function modules have been developed to perform certain processing steps within a transaction. The authorization check is then generally performed by the calling transaction. All modules that are released (that is, which can also be called by customer programs) are exceptions.
In most cases, an authorization check within the module would prevent the correct processing of the transaction. (For example, in cases where a transaction uses techniques of which the user is not aware (for example, generating codes)).
Solution
- 1. Implement the program changes described below.
The program changes are delivered with the Support Packages assigned to this note.
Note that you must perform the manual tasks up to ERP Release 603. These are not delivered in advance by Support Package.
- 2. Delete the transaction code 'N' in transaction SE93.
- 3. Delete the menu code in the status '0100' of the function group 'SE16N'.
Goto -> RKCOVIEW
Goto -> TSCUST
Goto -> TSRUN
To do this, proceed as follows:
Call transaction SE80 for the function group 'SE16N'.
Expand 'GUI Status' in the tree and double-click status '0100'.
Switch to change mode.
Choose '+' beside 'Menu Bar'.
Double-click 'Goto' and position the cursor on the menu codes mentioned above, one after the other.
Choose 'Delete entry (Ctrl+F9)' for each line.
Activate the status.
Affected Releases
|
No comments:
Post a Comment