Kontakt

Ansicht
Dokumentation

PROFGEN_CORR_REPORT_2 - Exchange of Obsolete Transactions in Role Menu

PROFGEN_CORR_REPORT_2 - Exchange of Obsolete Transactions in Role Menu

BAL Application Log Documentation   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Transactions in the SAP system are occasionally deleted or replaced by other transactions.

In this step, you create a list of all roles that contain obsolete transactions in the role menu. This does not include roles with target system attribute and transactions with target system. This means the following:

  • The transaction no longer exists.
  • The application start lock has been set by SAP (transaction SM01_DEV).
  • In S/4HANA: The transaction is obsolete and can no longer be used.
  • The SU22 status of the transaction is deprecated or obsolete.
  • The transaction is replaced by one or more other transactions.

You can use this program to delete or replace entries in the role menu.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

The output shows the selected roles with the following information:

  • Name of the role
  • Obsolete transaction:
  • Node ID in menu

  • Type of menu entry (transaction or authorization default)

  • Name of the old transaction:

  • Name and type of the application group in case the transaction belongs to a group (for example SAP Fiori Launchpad Catalog). This column is hidden in the default setting.

  • Automatic adjustment: Action to be executed if the menu is adjusted automatically.
  • Information: If the menu option cannot be changed, the system displays an info button detailing possible reasons for this happening.
  • Status of obsolete transaction:
  • The old transaction no longer exists.

  • The application start lock has been set by SAP (transaction SM01_DEV).

  • In S/4HANA: The transaction is obsolete and is no longer supported.

  • Name of the new transaction (if available)
  • New transaction is a Fiori transaction. This column is hidden in the default setting.
  • New entry contained in menu as transaction or authorization default. The system checks whether the new transaction is already in the menu. If so, the type of the menu entry (transaction or authorization default) is displayed.

Change

If you want to make a change to the role menu, the automatic adjustment option is available. For each selected entry, the Automatic Adjustment column contains the action to be executed.

  • Entry is replaced
    A menu entry is inserted for the new transaction. If the menu entry to be replaced is an authorization default, the new menu entry is also created as an authorization default. The old menu entry is then deleted. The new entry has the same position in the menu as the old entry.
  • New entry is added
    A menu entry is inserted for the new transaction. Its type depends on the type of the menu entry being replaced (transaction or authorization default). The new menu entry is inserted immediately after the old transaction.
    If the old transaction has already been deleted by the program, the new transaction is inserted beneath the parent node of the old transaction.
  • Old entry is deleted
    The old menu entry is deleted.

Notes:

  • If changes have been made to the role menu, the current authorizations have to be merged with the new authorization default values. You can simulate the merge by using the mass generation function (transaction SUPC).
  • Instead of replacing entries immediately, you can just add the new entries first and merge the authorizations. You then delete the old entries in a second step, and check the authorizations again. It is helpful to use this method if there are substantial differences between the authorization default values in the old and the new transactions, as you don’t lose the authorization values.

Role Transport

On the selection screen, you can see whether a setting is active for transporting client-specific customizing objects in transaction SCC4, and if so, which one.

For the "Automatic Recordings of Changes" setting, you can select the generated authorization profiles and the personalization data as optional transport components and enter the required customizing request for role recording. The text in parentheses after the input field indicates that the specified request is only used for roles that are not set in another request by existing recordings. If you do not specify a request on the selection screen, but it is still possible to select a request for at least one of the roles you have selected, you will get the usual dialog window for selecting the request later on when you save the mass changes.

For detailed information about using the SCC4 setting in relation to role maintenance, see SAP Note 1723881.

Activities

Example






ROGBILLS - Synchronize billing plans   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 6139 Date: 20240520 Time: 044611     sap01-206 ( 90 ms )