Transporting Roles to other Target Systems

Depending on the structure of your system landscape, you have to copy the authorization roles created and maintained in one system to the other systems and make them available there (see System Landscape). The system automatically copies the roles with customizing requests.

You have to enter a customizing request for all changes to authorization roles. This ensures that the roles as well as the administration data are distributed in the target system of the transport.

If a role transport is not required, you can deactivate the field for the automatic transport request on the initial screen for role distribution, for example if the role is created and used in the same system.

You can also trigger the transport manually by choosing Authorization role ® Transport. This is necessary for example if you temporarily deactivated the field for automatic transport requests for test purposes and later decide you want to copy your changes to the target systems after all.

Prerequisites

· To maintain the data copied from the portal to the SAP system you need role administration authorization (see Authorizations).

· You are on the Role Administration screen Follow-Up Processes for Portal Roles and have chosen the option Maintain Authorization Roles.

Procedure

To transport roles to another system:

...

1. Select one or more roles.

2. Choose Authorization role ® Transport.

The selected roles are transported.

You can also call the authorization role transport with transaction PFCG under Download/Upload. The administration data of the portal roles are not copied if you trigger the transport with this transaction.

You should therefore always start the transport from transaction WP3R.

Roles are always transported together with their profiles. The option to suppress the profile transport (table PRGN_CUST, entry PROFILE_TRANSPORT) is ignored.