
You can delete incorrect data or portal role data that you no longer need using transaction WP3R.
Typical situations where this could be necessary are:
The portal sent data to the wrong system.
Authorization roles were changed outside of transaction WP3R.
Role data was not completely transported.
Portal roles were deleted in the portal and are no longer required in transaction WP3R.
The portal role has no user assignment in transaction WP3R and can therefore be deleted.
To maintain the data transferred from the portal to the SAP system you need role administration authorization (see Authorizations ).
You are on the initial screen for either authorization role administration or role assignment.
To clean up the data in the SAP System, choose .
You can use this function in the following ways:
Authorization roles : An authorization role was assigned to a portal role, but later deleted or changed outside of transaction WP3R. This results in an error message. The function therefore removes the assignment.
Portal roles:
Portal roles that are flagged as deleted in the portal, are highlighted in red in transaction WP3R. These can now be deleted in transaction WP3R. In authorization role maintenance mode, you can delete a portal role that was distributed in WP3R if the authorization roles derived from this portal role have already been deleted.
Portal roles can be deleted in role assignment mode if they no longer belong to any user role assignment. For example, this can happen if the user assignment to a portal role is transferred to the SAP system, but no corresponding user can be found in the SAP system.
Portal roles without a user assignment appear in transaction WP3R with user name "<?>".
Users : All role assignments for a user can be deleted if this user is no longer assigned to any authorization role.
You can perform this function for a number of selected entries. For technical reasons, however, you cannot always delete all the selected entries at one time. Examples of this are:
Portal roles and the related incorrect authorization roles are selected. Initially the function cannot delete the portal roles because there are still dependent authorization roles. For this reason only the authorization roles are initially deleted. The next time the function is performed, the portal roles themselves can also be deleted.
You can delete roles assignments with the function for one user. The system cannot detect that there are unnecessary portal role records caused by these deletions (displayed with the user name "<?>") until the next time transaction WP3R is started. The portal roles can only be removed now.