Use

You can use this function to display structures from the Organizational Management application component of the ERP system in the form of a list or tree structure in a Web Dynpro application, and thereby display this information in a portal iView. Depending on how you configure the Object and Data Provider (OADP), you can use it to provide users with an overview of cost centers or employees, for example. You can also allow users to view additional detailed information about the objects displayed. Alternatively, users can trigger processes directly from the objects displayed, for example, they can create a personnel change request.

Integration

The Object and Data Provider is used in the following business packages:

Business Package for Manager Self-Service (mySAP ERP)

Business Package for HR Administrator (mySAP ERP)

Prerequisites

In the ERP system, you have set up the organizational plan of your company using the Organizational Management application component. This plan comprises the organizational structure and staff assignments.

In the ERP system, you have made the Customizing settings for the Object and Data Provider. For these settings, see, for example, Manager Self-Service (mySAP ERP) Customizing and Personnel Management Customizing, under HR Administrative Services

If until now you have implemented the Organizational Management column framework in Manager's Desktop for example, you can reuse the defined columns and column groups in the Object and Data Provider. To do this, use the conversion report PWPC_TO_CONVERT_TABLES to transfer entries from tables of the column framework to tables of the Object and Data Provider. For more information, see the documentation for this report.

Features

You use object selection rules, which are grouped in object selections, to define which target objects users see. You can also provide users with a navigation area with navigation objects, in which they can further restrict the target object view. Instead of displaying target objects and, where necessary, navigation objects, you can provide users with a search function for objects.

When a user logs on to the portal, the system determines which objects to display for the user as follows:

It determines the root objects.

Example: the system determines the organizational unit for which the manager is responsible. To do this, it checks the chief position of the user, or person, to which the user is assigned in the Communication infotype (0105).

Starting from the root objects, the system determines the navigation objects, if required.

Example: all organizational units located below the manager’s organizational unit that is responsible.

When the user selects one of the navigation objects, the system determines all related target objects.

Example: the employees who hold the positions that belong to the selected organizational unit.

Depending on the Customizing settings, the system uses an evaluation path or a function module to determine the root, navigation, and target objects. The following figure illustrates how the system uses evaluation paths to determine objects:

For more information, see the Implementation Guide (IMG) under Object and Data Provider → Object Provider.

You can use data views, which are grouped in data view groups, to define which additional information about the target objects is displayed for users.

For more information, see the IMG under Object and Data Provider → Data Provider

You can use organizational structure views, which are grouped in organizational-structure-view groups, to group object selections and data views.

For more information, see the IMG under Object and Data Provider → Organizational Structure Views

You assign the settings made in Customizing to the iViews that use the Object and Data Provider using the OADP parameters in the properties of these iViews.

In the standard system, the iView properties are configured in such a way that you can use iViews without having to make any additional settings. If required, you can tailor the properties to suit the requirements of your company.

The following OADP parameters are entered in the properties of the Employee Search iView:

Parameter OrgViewGroup

The organizational-structure-view group MSS_TMV_EE ( Employee Selection ) is entered here. The following organizational structure views are assigned to this organizational-structure-view group in Customizing:

MSS_TMV_EE_ORG1 (Employees from Organizational Units)

MSS_TMV_EE_ORG2 (Employees from Organizational Structure)

MSS_TMV_EE_DIR (Directly Subordinate Employees)

MSS_TMV_EE_SRCH (Employee Search)

Parameter OrgView

In the standard system no value is defined for this parameter.

If Employee Search is to display directly subordinate employees only, as opposed to the organizational-structure-view group Employee Selection , enter the organizational structure view MSS_TMV_EE_DIR in this parameter. In this case you may not define a value for the OrgViewGroup parameter.

Parameter NavListOrgViews

The organizational structure view MSS_TMV_EE_ORG1 is entered for this parameter. This defines that the navigation objects for this organizational structure view are displayed in a list instead of a tree structure.

In the standard system, navigation objects are displayed in a tree structure for organizational structure views that include a navigation area, provided that the iView properties do not dictate otherwise.

Example

See Example: Customizing Settings for the Object and Data Provider .