Kontakt

Ansicht
Dokumentation

PRGN_COPY_T_RY_AGRS - SAP Note 156196: Copy T_ Roles and RY Roles

PRGN_COPY_T_RY_AGRS - SAP Note 156196: Copy T_ Roles and RY Roles

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Title

Copy T_ and RY roles

Purpose

Activity groups are renamed during an upgrade to SAP R/3 4.5A or higher.

The previous technical key is linked with the short text to form the new activity group name.

Integration

See SAP Note 156196

Prerequisites

Activity Groups were created before SAP R/3 4.5A.

Features

As of SAP R/3 4.5A, the activity group names are 30 characters long. This means that the SAP standard namespace can be used for activity groups. The standard customer namespace that allows all names that do not begin with the prefix "SAP" or with a namespace identifier(/.../) can, of course, also be used. The previous technical name of an activity group, before SAP R/3 4.5A, was a numerical key, with which the use of the SAP standard namespace was not possible.

There are no disadvantages associated with the renaming, as the activity group texts are retained, as is all of the data assigned to the activity group(user assignments, menus, assignments of authorization profiles). The contents of the activity groups are not changed by the renaming.

A frequently asked question is: How do I find an activity group after it has been renamed, if I cannot select using the previous short text.

The answer to this is simple: The old short text is part of the new activity group name. You can therefore search for this old short text in transactionPFCG by entering the short text for which you are searching in the entry field (Activity group), with a "*" before and after it, and then choose F4. The system then displays a list of activity groups that contain the short text in their key.

However, if you still want to rename the activity groups, the best way to do so is as follows:

Create a transport request that contains all activity groups in the old status and export it. If the following procedure does not produce a satisfactory result, you can restore the original state by importing this transport request.

  • Then use this report to copy all activity groups that begin with "T_" or "RY_" to a new name. The report places the latter (meaningful) part of the name in front of the technical part. If you check the checkbox on the selection screen, the technical part (for example, T_1234556) is left out completely. However, this has the disadvantage that conflicts can occur far more frequently due to the non-uniqueness of the names, as the meaningful part of the name did not have to be unique under the old concept (before SAP R/3 4.5). It is therefore better to start the report with the default settings.
  • If there are problems during the renaming, the copy is not created and the system displays an error message. In this case, you should create the copy manually (in transaction PFCG).
  • When the activity groups are copied, the associated profiles are not yet generated. You can now use transaction SUPC to go to the authorization data for the new activity groups, where you can assign a new name for the authorization profile (if desired) and generate the profile.
  • If you want to use the same profile names for the copied activity groups as those used for the original activity groups, read the documentation for the "DELSRC" parameter below.
  • You should then perform the user master comparison for the affected activity groups, and, after a check of the new activity groups, you can then delete the old activity groups. This must be done manually. To transport the deletion, the activity groups must be entered in a transport request before the deletion.
  • The deletion can be performed automatically during the copy operation using the parameter "DELSRC". For more information, please read the input parameter documentation below. If you want to transport the deletion, you must enter the activity groups (roles) that are to be renamed in a transport request before the renaming and export this transport request after the renaming.

Selection

  • "NO_T_"
  • If this parameter is checked, the new name is assigned, as described above, with the technical part of the name left out, with the disadvantages mentioned above.

  • "DERIVED"
  • If this parameter is checked, the new name is replaced in all derived roles. The prerequisite for this is that the entire derivation cluster is converted in one operation.

  • "DELSRC"
  • If this parameter is checked, the copy source is deleted, as long as the copy action was successfully performed. The deletion of activity groups (roles) with derived roles (previously responsibilities) will only work if the complete derivation cluster (the role with all derived roles) was renamed in the same operation.

  • Note: Logged-on users of the source roles (with the names "T..." and "RY_....") lose their authorizations during this operation.

  • If the deletion of the original roles is to be transport, you must enter these in a transport request before the operation, and then export the transport request after the deletion.

  • If the "DELSRC" parameter is checked and the original role was correctly deleted, the profile name of the old role is automatically used as the profile name of the new role. You can then generate the profile using transction "SUPC".

Standard Variants

Output

Activities

Example






ABAP Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 6285 Date: 20240520 Time: 083430     sap01-206 ( 135 ms )