You use Transaction PFCG to transport an role. Enter the role and choose Transport. The system displays a dialog box that queries whether the user assignment should also be transported. Next, enter a transport request. The role is entered in a Customizing request. Use Transaction SE10 to display this.

The authorization profiles are transported along with the roles. Unlike in previous releases, the profiles no longer have to be regenerated in the target system using Transaction SUPC. However, you must compare the user master records for all roles that are imported into the target system.

If the user assignments are also transported, they will replace the entire user assignment of roles in the target system. If you want to lock a system against importing user assignments of roles, you can specify this in the Customizing table PRGN_CUST. You maintain this using Transaction SM30. Add the line USER_REL_IMPORT and the value NO.

After the import into the target system, you must compare the user master records for all roles involved. You can do this in two ways:

• Start report PFCG_TIME_DEPENDENCY
• In Transaction PFCG, choose Goto ® Mass compare. Enter the role in the Role field. Choose Complete compare and start the report.

You can also prevent authorization profiles from being transported with the roles using a Customizing entry. In the transport source system, make an entry in table PRGN_CUST called PROFILE_TRANSPORT with the value NO. In this case, you must regenerate the profiles in the target system using Transaction SUPC.

You can distribute roles in the Menu tab in the role maintenance if the target system has Release 4.6C.