Adjusting System Responsibilities 

Use

Before the Enterprise Portal copies role data to an SAP system, the SAP system informs the portal which systems it is responsible for. The portal can then select the right data and copy it to the system.

Responsibility for role maintenance is defined in database table WP3ROLESYS, which you can maintain with Transaction SE16.

Prerequisites

You have authorization to maintain database table WP3ROLESYS (authorization group: SUSR).

Procedure

To define that systems A and B in the example in the section System Landscape are responsible for role maintenance:

  1. Start Transaction SE16.
  2. Call table WP3ROLESYS.
  3. Make an entry for each system whose roles are to be maintained in the current system.

This entry consists of the name of the logical system and an 'X' in the column ROLEMAINTENANCE.

Example

Make the following entries for system landscapes A and B in table WP3ROLESYS:

LOGSYS

ROLEMAINTENANCE

ROLEASSIGNMENTS

In System DEV-A

DEV-A

X

  

PRD-A

X

  

In System DEV-B

DEV-B

X

  

PRD-B

X

  

In System PRD-A

No entries

    

In System PRD-B

No entries

    

Column ROLEASSIGNMENTS is not used. The system determines who is responsible for role assignment at runtime.

Result

The SAP systems tells the portal that the following are responsible for role maintenance:

Responsibilities for role assignment are as follows:

Make sure that each transport track has only one system that is responsible for role maintenance:

An authorization role belongs to exactly one portal role and its services in a target system. If you maintain roles in multiple systems of a transport track, you cannot prevent roles with the same name from being created and an authorization role from being derived from multiple portal roles by the transport. Further system behavior is undefined in such a situation.