Show TOC

Adjusting System ResponsibilitiesLocate this document in the navigation structure

Use

Before the 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.

Table WP3ROLESYS determines responsibility for role maintenance.

Prerequisites

You have authorization to maintain the table view for WP3ROLESYS.

Procedure

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

  1. Launch the table view maintenance (transaction SM30)for table WP3ROLESYS.

  2. Make an entry for each system whose roles are to be maintained in the current system and set the Role maintenance active flag.

Example

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

Logical System

Role maintenance active

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

Result

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

  • DEV-A for DEV-A and PRD-A

  • PRD-A for no system

  • DEV-B for DEV-B and PRD-B

  • PRD-B for no system

For role assignment, the following responsibilities are transferred (this data is derived from the system landscape - you do not need to maintain is manually):

  • DEV-A for DEV-A

  • PRD-A for PRD-A and PRD-B

  • DEV-B for DEV-B

  • PRD-B for no system

Note

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.