System Landscape
To define the system responsibilities within your ABAP system landscape, you must enter the system responsible for role maintenance in table WP3ROLESYS. For more information, see Adjusting System Responsibilities .
Note that responsibility for user assignment is not defined using table WP3ROLESYS. This data is derived from the ABAP system landscape and you do not have to maintain it manually.
Afterwards, you must modify the ABAP system landscape to suit the portal system landscape. For more information, see Assigning Logical Systems .
The following example shows how roles and user data are assigned to SAP NetWeaver Portal and two connected ABAP system landscapes.
In this case the ABAP system landscapes consist of a development system (DEV-A, DEV-B) and a production system (PRD-A, PRD-B) each. Production system PRD-A performs the functions of a Central User Administration (CUA) with global role assignment.
The figure below shows the system landscape and functions that the individual systems perform for role and user administration.
The portal defines roles with services in system landscapes A and B. The corresponding authorization roles are created and tested in development systems DEV-A and DEV-B and transported to the relevant subsequent production systems with the role transport.
The data for user assignment is transferred from the portal to the relevant systems (see Adjusting System Responsibilities ) (DEV-A, PRD-A and DEV-B). System PRD-B is not responsible for user assignment. It is linked to the central user administration of system PRD-A. Central system PRD-A therefore also receives user data for system PRD-B as well as for itself.
The system landscape described above is a complex example. A landscape consisting of a single system is also possible.