mss new object_data_provider_(oadp)

© SAP AG 1

©SAP AG 2005

Manager Self-Service mySAP ERP 2005

Object and Data Provider & Employee Search

© SAP AG 2

© SAP AG 2006

Agenda

4

Object Selections based on Object and Data Provider1

5

Front-End Components2

Backend Components3

Views and View Groups

Data Provider

Object Provider

Organizational Management

Front-end and Backend Connection

Overview of Backend Comp. and corresponding Frond-End Comp.

© SAP AG 3

© SAP AG 2006

Features for ERP 2005

New feature:

Multiple instance capability of OADP, e.g. to use several OADP tables within one application

Event mechanism: Triggering of client events passing event parameters to other applications

Launching of links - to call other applications or portal pages - with parameter handling.

Allow different Data Views on a constant object set via a Data View Selector on the user interface.

Simplify handling of Navigation Objects in backend customizing and on the user-interface Navigation objects visualized

as list of single- or multi-selection capabilityAs tree-like structure with single-selection capability

Reduction of data load on the front-end by use of Navigation Objects and a “load on demand”mechanism in their tree visualization

Completely new “Explorer-like” screen layout for the OADP withOrganization View Group Selector (optional), Navigation Area (optional), Data View Selector (optional) and Data Area.

New Search functionality – as example

Multiple Instance capability of OADP: with mySAP ERP 2005 it is possible to place more than one OADP tabel on one screen. This is realized in the review screen of the new Enterprise Compensation Planning scenario. On the review screen each compensation plan one OADP table is available on the screen.

Event mechanism: is used for the Employee Information Pages.

Launching of links: one example is the link within the Employee Search that calls the Position Profile page

Different Data Views: This requires the possibility to assign several Column Groups to one Organization View in backend customizing (requires customizing re-design).

Search functionality: is integrated in the Navigation Area, search results are displayed in the Data Area. The new Search is realized as backend search only the result is displayed on the front-end Suche. In the past only front-end search was possible. This kind of search is still possible by using the filter functionality of OADP at the front-end.

© SAP AG 4

© SAP AG 2006

Manager is Responsible for a Number of Employees

Employee Search within Employee Information

Employee Selection - ECM

Employee Selection – PCR

Employee Selection Screen and the Employee Search iview are based on Object and Data Provider (OADP)

Employee Selection Screen and the Employee Search iview are based on Object and Data Provider (OADP)

The Object and Data Provider enables you to displays structures from Organizational Management as a list or tree structure in a WebDynpro application and thereby display such structures in the SAP Enterprise Portal. Furthermore, you can use columns to provide users with additional information about organizational objects.

© SAP AG 5

© SAP AG 2006

Employee Search iView and Eventing

EE Search iview is the successor of the Team

Viewer

EE Search iview is the successor of the Team

Viewer

The Employee Search is an iView that is used for the Employee, Position, and Org Unit Profile pages. It enables managers to select an organizational object from the list. The other iViews on the same portal page react on this selection. This function is called Eventing.

The Employee Search iView acts as a sender whereas the other iViews on the portal page act as a receiver: once the manager has selected an Object (e.g. an employee) from the Employee Search , the object ID is sent to the other iViews. These iViews compares the sent ID with the current ID. In case the sent ID differs from the current ID, the iView retrieves the appropriate data of the new ID from the backend system and displays it in the iView.

© SAP AG 6

© SAP AG 2006

Employee Selection – Based on OADP

Employee selection in Applications

In Enterprise Compensation Planning (ECM) the first step is to select employees for which the manager wants to conduct the compensation planning. In this first step the ECM provides an employee selection that looks similar to the Employee Search iview , but it is not the Employee Search iview known from the EE Profile pages.

The employee selection screen belongs to the ECM application and is a front end component that is part of the Compensation Planning WebDynpro. With other words the Employee Search iview is not just included into ECM, but ECM provides its own screen for employee selection that is based on OADP.

However, applications like ECM or PCR use the Object and Data Provider (OADP) to provide the manager with the right people and a certain number of views on his/her area of responsibility.

The different HCM based application in MSS use the Object and Data Provider (which is a table framework in the backend customizing). The Employee Search iview is only used for the

EE Profile

Org Unit Profile

Position Profile

pages.

© SAP AG 7

© SAP AG 2006

Agenda

4


5


Backend Components3


Data Provider

Object Provider




© SAP AG 8

© SAP AG 2006

Object and Data Provider (OADP)

OAPD consists of two components:Front-end component (data visualization on user interface)A backend component

Object Provider (evaluation of organizational structure and the org objects to be displayed in the selection screen)Data Provider (evaluation of additional data of displayed objects – column information)

Note: With mySAP ERP 2005 new tables are used for object selection by the Object and Data Provider!

The front-end component comes with the Business Packages MSS

The Object and Data Provider backend component consists of a number of tables of the backend system. You can maintain these tables via the IMG -> Integration with other mySAP Components -> Business Packages/Functional Packages -> Manager Self-Services (mySAP ERP) -> Object and Data Provider

© SAP AG 9

© SAP AG 2006

Object and Data Provider - Front-end - Areas

Organizational View Selector Area- Drop Down List BoxOrganizational View Selector Area- Drop Down List Box

Navigation Area- Tree- Table- Search

Navigation Area- Tree- Table- Search

Data View Selector Area- Drop Down List BoxData View Selector Area- Drop Down List Box

Data View Area- TableData View Area- Table

The Object and Data Provider (OADP) is a tool that enables you to depict organizational structures in the form of a list or a hierarchy, providing that these structures were created and maintained in the SAP Organizational Management component. It also allows you to display additional information on the elements of such organizational structures, i.e. information on the organizational objects, in tabular form. In the following, the organizational structure together with the information on its objects is referred to as an Organization View.

The screenshot shows the user interface of the ERP 2005 version of the OADP, containing different areas, e.g. a drop-down list box for the Group of Organization Views on top of the screen, a navigation tree on the left-hand side and a table for the object data on the right-hand side.

A typical example of an Organization View is a tree-like representation of a manager’s organizational units together with assigned positions and their holders, or a list of employees who report directly to the manager. The employee list could contain any additional employee information, e.g. the office phone number, personal data, address data etc.

© SAP AG 10

© SAP AG 2006

Views – Directly Subordinate Employees

Different viewsDifferent views

Directly Subordinated EmployeesList of people reporting directly to themanager

Directly Subordinated EmployeesList of people reporting directly to themanager

There are different views provided on the managers area of responsibility.

Directly Subordinated employees

Employees from Organizational Structure

Employees from Organizational Units

Employee Search

The view Directly Subordinated Employees: provides a list of employees reporting directly to the manager. This is similar to what is already known from the former MSS Team Viewer – a list of employees

© SAP AG 11

© SAP AG 2006

Views – Employee from Org Structure

Different viewsDifferent views Employee from Organizational StructureManager is provided with a structure of

his/her org units. Once he/she has selectedan org unit from the structure the list of employees assigned to this org unit is

displayed on the right hand side

Employee from Organizational StructureManager is provided with a structure of

his/her org units. Once he/she has selectedan org unit from the structure the list of employees assigned to this org unit is

displayed on the right hand side

Only single selection of org units

Only single selection of org units

© SAP AG 12

© SAP AG 2006

Views – EE from Org Units

EE From Organizational UnitsManager is provided with a list of his/her org units. One or more orgunits can be selected from the list. Employees assigned to the selectedorg unit(s) are displayed on the right hand side of the screen.

EE From Organizational UnitsManager is provided with a list of his/her org units. One or more orgunits can be selected from the list. Employees assigned to the selectedorg unit(s) are displayed on the right hand side of the screen.


Multiple selectionpossible

Multiple selectionpossible

The view „Employees from Organizational Units“ provides the manager with a list of Org Units he/she is responsible for. The manager can select one or more org units form this list. Once he/she clicks on the Go-button the list of employees assigned to the selected org units are displayed on the screen.

To select a second org unit from the list use ctrl + mouse click on the second object in the list.

© SAP AG 13

© SAP AG 2006

Views – Employee Search

Employee Search Manager canenter search criteria, e.g. fist name, last name and is provided with the right employee(s)

Employee Search Manager canenter search criteria, e.g. fist name, last name and is provided with the right employee(s)


This search function is delivered as an example.

© SAP AG 14

© SAP AG 2006

Data View Selection Area – Data View Area

Different Data ViewsDifferent Data Views

The Data View Area provides users with a list of objects for selection. In addition it includes further columns with related to the object in the first column.

In the Data View Selection Are the user is provided with a list of Data Views in the drop down list box. This allows the manager to switch to another Data View including different columns. The first column includes the Object (e.g. Employee Name) which can be selected by the user and will not be replaced when another data view is active.

Note: The object columns must be included in all Data Views. With other words: at least one column - the column that provides the object for selection - must be included in the view. For more information see Column Framework.

© SAP AG 15

© SAP AG 2006

Data View Area

Employee Search - Data View AreaEmployee Search - Data View Area

ECM - Data View AreaECM - Data View Area

PCR - Data View AreaPCR - Data View Area

Depending on the application multiple or single object selection from the Data View Area is possible

Employee Search iview

In the Data View Area of the Employee Search only one employee can be selected by clicking on the EE name. The other iviews on the portal page react on this action and display the appropriate employee information on the screen.

Enterprise Compensation Management

In the Data View Area within the employee selection of ECM it is possible to select more than one employee from the list. Multiple selection supports the manager in selecting those employees he/she wants to focus on in compensation planning.

Personnel Change Requests

With Personnel Change Request the manager is only allowed to trigger a request for one employee. In PCR managers are provided with a single selection in the employee selection screen.

© SAP AG 16

© SAP AG 2006

Data View – Filtering, Sorting, Configure Displayed Columns

Choose columns to be shown in the Data View Area

Front-end filter is possible

Choose columns to be shown in the Data View Area

Front-end filter is possible

The end user can choose the columns he/she wants to see in the EE Search iView.

The Filter-button can be used to activate the filter, e.g. to get all employees with a certain job.

Note the filter is a front-end filter and is based on data already available at the front-end

© SAP AG 17

© SAP AG 2006

Agenda

4


5


Backend Components3


Data Provider

Object Provider




© SAP AG 18

© SAP AG 2006







Note: in ERP 2005 the Object Provider part of OADP has changed. For the Object Provider new tables are available in the backend customizing. The Data Provider part (Column Framework) remains unchanged.

© SAP AG 19

© SAP AG 2006

Backend Customizing of Object and Data Provider

Transfers Customizing settings you made prior to mySAP ERP 2005 for the Object and Data Provider to the Customizing tables that are used as of mySAP ERP 2005

Transfers Customizing settings you made prior to mySAP ERP 2005 for the Object and Data Provider to the Customizing tables that are used as of mySAP ERP 2005

Object Provider – evaluation of org objects along the structure

Object Provider – evaluation of org objects along the structure

Data Provider: evaluation of additional data of displayed objects – column information

Data Provider: evaluation of additional data of displayed objects – column information

Create Org Views and View Groups for the Org View Selector Area.

Create Org Views and View Groups for the Org View Selector Area.

Transfer Existing customizing Settings: In this IMG activity, you transfer the Customizing settings you made prior to mySAP ERP 2005 for the Object and Data Provider to the Customizing tables that are used as of mySAP ERP 2005.

Report RP_OADP_MIGRATE_CUSTOMIZING is used for the transfer.

You can migrate Customizing settings according to view groups (view clusters) and/or views. You must distinguish between the following:

View groups/views delivered by SAP

View groups/views you have created in the customer namespace (for example, Y* or Z*)

View groups/views in the standard system you have not overwritten

View groups/views in the standard system that you have overwritten

The report migrates view groups/views that lie in the customer namespace. In the case of view groups/views delivered by SAP, a dialog box is displayed in which you can transfer the view group/view to the customer namespace. If the name you enter in this dialog box already exists in the new tables, the system informs you that you must enter a different name. If you terminate this operation, the view group/view is not migrated to the new tables.

If you have overwritten view groups/views in the standard system, the report migrates the overwritten entries and ignores the entries that were originally in the standard system.

Before you can migrate view groups, you must have first migrated all the views that belong to a particular view group.

It is recommended to execute a test run.

© SAP AG 20

© SAP AG 2006

Overview - Backend Tables

View Group

View 1

Object selection

Object selection rule 1


Object selection rule3

Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

© SAP AG 21

© SAP AG 2006

OADP - Views and View Groups

With the OADP the manager is provided with a number of organizational views on his/her area of responsibility. Views are grouped to View Groups.

View Groups are then assigned to a Web Dynpro Application.

Each Organizational View is related to a column Group

© SAP AG 22

© SAP AG 2006

OADP – Object Provider

To provide managers with an improved overview of the number of objects displayed – especially when using the list display – the OADP allows you to restrict the number of objects for an Organization View by using Navigation Objects. The manager can then pre-select entries from the list of Navigation Objects in order to get information on the depending target objects.

In case of Compensation Planning, for example, the planning manager does not always want to plan for all the employees in her/his area of responsibility but just for the employees belonging to a single organizational unit. Therefore, it makes sense to allow the manager to pre-select the organizational unit first before displaying the planning sheet and the compensation-relevant employee data.

© SAP AG 23

© SAP AG 2006

OADP- Data Provider

Which additional information on organizational objects is displayed and how this data is determined can be specified within the OADP by defining data columns. Those data columns can be grouped to Column Groups and assigned to an Organization View.

Compared to MSS for ERP 2004, the column configuration is is untouched. Used tables are still the same and customer specific columns can still be used in ERP 2005.

© SAP AG 24

© SAP AG 2006

Agenda

4


5


Backend Components3


Data Provider

Object Provider




© SAP AG 25

© SAP AG 2006

View Groups and Views

ViewView

View Group includes a number of views on the managers area of responsibility.Views are based on Object Selections which include Rules to determine the objects to be displayed in the Navigation Area.Rules are also used to determine the objects to be displayed in the Data View Area

View Group includes a number of views on the managers area of responsibility.Views are based on Object Selections which include Rules to determine the objects to be displayed in the Navigation Area.Rules are also used to determine the objects to be displayed in the Data View Area

View GroupView Group

To allow managers to switch between different Organization Views on the user interface, the Organization Views can be grouped into a so-called Group of Organization Views. On the user interface such a group is then represented as a drop-down list box containing the Organization Views as elements. In this way, a user just needs to select a drop-down list box entry in order to display another Organization View.

© SAP AG 26

© SAP AG 2006

Define Organizational Views

Views are grouped to view groups.Views are grouped to view groups.

V_TWPC_ORGVWV_TWPC_ORGVW

Each entry in the drop down list box of the employee selection represents a view on the managers area of responsibility, e.g.:

Directly Subordinate Employees: a list of all employees belonging to the org unit the manager is assigned to and all managers of the direct subordinated org units are displayed in a list. Along the structure the system checks the direct subordinated org units, whether or not a chief position is assigned. If no chief position is found, the systems selects all employees of the subordinated org unit, and displays them as direct reporting employees. The same procedure is done for the next level of org units.

Employees from Organizational Units: Once the manager has chosen one of his/her org units from the list in the Navigation Area, the employees of the selected org unit are displayed in the Data View Area. The manager can now select one or more employees from the list to start the Web Dynpro application.

Employees from Organizational Structure: the manager can choose an org unit from the tree-structure in the Navigation Area, the employees of the selected org unit are displayed in the Data View Area.

Employee Search: example of a search function. The user can enter the employee’s name he is looking for. The system provides the search result in a list.

Table V_TWPC_ORGVWGRP is used to group the views to a view group. The view group is then assigned to the Web Dynpro application.

© SAP AG 27

© SAP AG 2006

Define Organizational Views

V_TWPC_ORGVWV_TWPC_ORGVW Views consist of a Object Selection and a Data View Group.

Views consist of a Object Selection and a Data View Group.

For each view, in the drop down list box, an entry is needed in table V_TWPC_ORGVW.

An Organizational View consist of an object selection and a Data View Group:

Object selection determines how and what objects are selected along the organizational structure.

With Data View Groups you determine the column information displayed Data View Area of the selection screen.

© SAP AG 28

© SAP AG 2006

Create View Groups

V_TWPC_ORGVWGRPV_TWPC_ORGVWGRP

Assign views to a view groupAssign views to a view group

WebDynpro ApplicationWebDynpro Application

V_TWPC_ORGVWGRP

Views are grouped together to View Groups. View Groups are then assigned to the MSS Web Dynproapplication. All Views of a View Group are shown in the drop-down list box of the employee selection.

© SAP AG 29

© SAP AG 2006

What Has Been Done + Next Step

View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

Next step

© SAP AG 30

© SAP AG 2006

Agenda

4


5


Backend Components3


Data Provider

Object Provider




© SAP AG 31

© SAP AG 2006

How to Find and Select the Employees a Manager is Responsible for?

The Object and Data Provider (OADP) enables you to display objects and object information from Organizational Management.

OADP uses the organizational structure maintained in Organizational Management to find the employees a manager is responsible for.

OADP uses different evaluation paths to determine the employees of a manager.

It is possible to change the evaluation paths used by OADP to select the manager’s employees in a different way along the structure.

An evaluation path is an instruction to the system which determines which object types and relationship(s) are to be included in an evaluation of your organizational plan.

© SAP AG 32

© SAP AG 2006

Object and Data Provider – Use of Evaluation Paths

OADP uses evaluation paths to determine the objects along the structure to be displayed in the object selection screen of Manager Self-Service.

An evaluation path includes objects and relationships that describes a way through the structure from object to object. This path is used by the systems to extract object from Organizational Management structure.

In general, OADP uses three evaluation paths to select the objects from the system:

1. First evaluation path determines the org units the user (manager) is responsible for. The found org units are then used as root objects for the second evaluation with the second evaluation path.

2. Starting with the root object found by the first evaluation path (e.g. the manager’s org unit(s), the system uses a second evaluation path to select all objects along the structure and displays the relevant object types for navigation.

3. Once a object is selected in the Navigation Area, this object is used for as a root object for the third evaluation path, to determine the object to be shown in the Data View Area.

Depending of the Organizational View two to three evaluation paths are needed to select the organizational objects:

First evaluation path to find the root object that is used for the second evaluation.

Managers are assigned to different org units. To provide each manager with the right org objects (employees, positions, org units) the first evaluation path is used as a general path from the user to the org unit the manager’s PersNumber is assigned to.

The second evaluation path starts with the found object(s) of the first evaluation path, to determines the objects that are to be displayed for the navigation area.

For the view Direct Subordinated Employees (or views without navigation area) only two evaluations are needed: the first one to determine the root object and a second evaluation to determine the objects that are to be displayed in the list.

© SAP AG 33

© SAP AG 2006

Employee is in a managementposition

Chief position

Employee / Person

Start evaluation path Start evaluation path Org Unit

Start Start object(sobject(s) )

The Root Object - The Manager‘s Org Unit(s)

1

IT 105 (Communication)Assignment of SAP System ID

Area ofArea ofresponsibilityresponsibility

To use the Object and Data Provider, you must have created an organizational plan including a representation of your organizational and reporting structures (that is, the assignment of persons or users to positions) in Organizational Management.

The area of responsibility is determined by the position the user holds. The chief position relationship (A/B 012) is required to define the organization(s) the position manages.

A user may be directly related to the position or derived by the data stored in infotype 0105 for the person holding the position in Personnel Administration.

When a user (the manager) logs on to the system, all the organizational units that he/she is responsible for are determined.

© SAP AG 34

© SAP AG 2006

How to get the Objects for Navigation Areaand Data View Area

Chief positionEmployee / Person Org Unit

Start object Start object Start evaluation path Start evaluation path

Org Unit

Start object Start object

Employee is in amanagement position

+ EvalEval. . PathPath (O(O--O)O)

EvalEval. . PathPathOO--SS--PP

SelectedSelected navnav. . ObjectObject +

1

2

3

IT0105

Starting with the organizational unit, found by the first evaluation path, a second evaluation selects all the objects for the navigation area. For example, the second evaluation path (O-O) selects organizational units. These org units can be shown in the Navigation Area as a list or structure view.

Once the user has selected one organizational unit in the Navigation Area, a third object selection with the third evaluation path starts. With the third evaluation path the objects for the Data View Area are selected.

© SAP AG 35

© SAP AG 2006

Object Selections and Rules

To enable the Object and Data Provider to display an organizational structure view, it must first determine the relevant objects. Therefore, you must define an Object Selection that is composed of Object Selection Rules or a a class for an Object Search.

An object selection rule is composed of either an evaluation path including a technical evaluation depth or of a function module for determining objects.

In the context of object selection, the Object and Data Providerdistinguishes between different types of object selection rules.

Example

As standard, a rule for selection root objects should comprise an evaluation path that determines the organizational units for which the manager holds the chief position.

Alternatively, you can store a function module with a predefined interface that determines the root objects. The function module HRWPC_PATHROOTS (function module for determining root objects) is included in the standard system as an example.

© SAP AG 36

© SAP AG 2006

Rules for Object Selection

The Object and Data Provider distinguishes between the followingthree types of object selection rules:

Rule for the selection of root objects (the user who is logged on is always the start object for the evaluation path)Rule for the selection of navigation objectsRule for the selection of target objects

© SAP AG 37

© SAP AG 2006

Define Rules for Object Selection

VC_TWPC_OBJSELRULEVC_TWPC_OBJSELRULE

Rules for the Employee Search iView of EE Information

Rules for the Employee Search iView of EE Information

A rules includes either an evaluation path, or a function module to determine objects along the organizational structure

A rules includes either an evaluation path, or a function module to determine objects along the organizational structure

To enable the Object and Data Provider to display an organizational structure view, it must first determine the relevant objects. Therefore, you must define an object selection that is composed of object selection rules or a class for an object selection search.

An object selection rule is composed of either an evaluation path including a technical evaluation depth or of a function module for determining objects. In the context of object selection, the Object and Data Provider distinguishes between different types of object selection rules.

© SAP AG 38

© SAP AG 2006

Rules for Employee Search iView


Start evaluation path

2nd evaluation path for list of org units in Navigation Area

1

2

3

3

2 2nd evaluation path for structure of org units in navigation Area

3rd evaluation path -> provides all employees assigned to an org units

Evaluation path to find direct reporting employees

Evaluation Path: Enter an evaluation path which will be used as a rule in the Data Provider part of OADP.

Depth of Structure: Specifies the level to which the system should evaluate the structure containing the organizational units.

The entry that you make in this field affects how the structure is evaluated. The system evaluations the structure to the level that you specify as structure depth.

Delete Duplicates: In case an object, e.g. a person, is assigned more than once to the structure, the system would display this object twice. To avoid this you can set the flag ‘Delete Duplicates’

Exclude Managers: The manager is also assigned to the org unit he/ she is responsible for and would therefore be selected and displayed in the Employee Search . To avoid this select ‘Exclude Managers’. This flag excludes all managers assigned to the same org unit as the user/manager who logged on to the system.

© SAP AG 39

© SAP AG 2006

Navigation Area

2

SAP_MANG:US-P-S (via 012)-OSAP_MANG:US-P-S (via 012)-O


Rules for EE Search iView ofEE Information


© SAP AG 40

© SAP AG 2006

Rules for Employee Search iview of EE Profile

MSSDIREC

O-P

ORGEH_T; depth of structure =2

ORGEH_T

SAP_MANG

Evaluation Path Name

Evaluation PathNameRule

O-O-S-P-US = includes the relationship B900 between O-S and O-O. B900 is a relationship that includes a program. This program selects employees of the root org unit, selects managers of subordinated org units, selects employees of subordinated org units without manager position.

Directly Subordinate Employees

MSS_TMV_RULE5

O-S (skipped)-PEmployees of an Organizational Unit

MSS_TMV_RULE4

O-OOrganizational Structure Up to Level 2

MSS_TMV_RULE3

O-OAll Organizational UnitsMSS_TMV_RULE2

US-P-S-O = used to determine the start object (org unit) for the second evaluation path

MSS_TMV_RULE1

© SAP AG 41

© SAP AG 2006

Define Object Types




Using an evaluation path the system selects certain objects along the organizational structure. In some cases the evaluation path includes object types which should not be shown in the Navigation Area or Data View Area.

Example: with the evaluation path O-S-P, used in rule MSS_TMV_RULE_4, the system selects the object types organizational units and persons along the structure. In the Data View Area only the object type person (P) should be displayed.

If you want to restrict the result of a selection rule to several object types, you must create entries for this selection rule in the Restrict Object Type table. Make an entry for each object types that are to be displayed in the employee selection (Navigation Area or Data View Area).

© SAP AG 42

© SAP AG 2006


View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

VC_TWPC_OBJSELRULE

Next step: Create object selection and assign rules

© SAP AG 43

© SAP AG 2006

Define Object Selection

For each view in the employee selection (e.g. Employee Search iview) an Object Selection must be created

For each view in the employee selection (e.g. Employee Search iview) an Object Selection must be created

V_TWPC_OBJSELV_TWPC_OBJSEL

Here you define the objects of the organizational structure that are to be displayed for the user.

You also define whether the user can use navigation objects to restrict the view to include target objects only.

If there is a large number of target objects, this enables you to provide the user with a clearer overview.

Alternatively, you can allow the user to use predefined search parameters to find specific objects. In this case, the user can enter values for the search parameters in the search template displayed.

© SAP AG 44

© SAP AG 2006

Search Classes

If you want to allow managers to search according to a selection ID, you can use the search class CL_HRWPC_SEARCH_VIA_SELID, which is included in the standard system.

Since this search class was created generically, you do not need to create a new implementation. To add additional search parameters, you simply need to create a selection ID that contains the relevant fields. You create the selection ID in the IMG activity Define Selection IDs in Customizing for Personnel Management under Human Resources Information System ->Selection IDs.

If the class requires particular parameters, a parameter group must exist that contains these parameters. The search class must be able to evaluate the pairs of parameters and parameter values that are assigned to the parameter group. For more information, see Group Parameter for Object Search.

© SAP AG 45

© SAP AG 2006

Object Selection and Rules

Rule to determine the root objectRule to determine the root object

Rule to determine the objects for navigationRule to determine the objects for navigation

Rule to determine the objects for Data View AreaRule to determine the objects for Data View Area

If a predefined set of objects is to be displayed for the user, set the Rules for Object Selection indicator. You must define an object selection rule for root objects and at least one rule for navigation objects or a rule for target objects. If you enter two rules only, the system determines the result set for the second rule based on the set of root objects.

If you want to allow the user to search directly for specific objects, enter a class for the object search and, if required, assign a suitable search class.

© SAP AG 46

© SAP AG 2006


View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

V_TWPC_OBJSEL

VC_TWPC_OBJSELRULE

Next step: Assign Object Selection to view

© SAP AG 47

© SAP AG 2006

Assign Object Selection to Views

The Object Selections created before must be assigned to views. This is done in a table already known from creating Views: V_TWPC_ORGVW

© SAP AG 48

© SAP AG 2006

Assign Object Selections to Organizational Views


Enter table V_TWPC_ORGVW. Select a view for which you what to assign the Object Selection.

Enter the corresponding Object Selection into the appropriate field.

As you can see on the slide a View consists of Object Selection and a Group of Data Views.

More information on Data View Groups can be found in the next part of this presentation.

© SAP AG 49

© SAP AG 2006

BAdIs for Object Provider

The following BAdIs are available for the Object Provider part of OADP:

To exclude managers: This BAdI enables you to remove objects from the results for an object selection ruleTo change Navigation Objects: This BAdI enables you to edit the navigation object texts displayed for the userDetermine RFC Connection for Object: You use this BAdI if you use Application Link Enabling (ALE) to replicate data from the organizational structure in a central system and the detailed data for the distributed objects (such as personal data) –displayed in the Data View Area as columns information - is stored in a different system.

Exclude Manager: In the IMG activity Define Rules for Object Selection, you have set the indicator Exclude Managers for the relevant object selection rule. If you do not create an implementation of your own, the system runs the default implementation that uses the function module HRWPC_OADP_EXCLUDE_MANAGER. This function module excludes all persons from the result list that are assigned to the root org unit via chief position. With other words all managers responsible for the root org unit are excluded from the result list.

Change Navigation Object: In the navigation area only the S_text of the object is displayed. If you want to change the displayed text for the objects (e.g. to display the ID or the long text) you use the BADI to do so.

This Business Add-In (BAdI) is used in the Object and Data Provider. In complex distribution scenarios, it enables you to determine the original system of Personnel Development objects.

Determine RFC Connection for Object: You use this BAdI if you use Application Link Enabling (ALE) to replicate data from the organizational structure in a central system and the detailed data for the distributed objects (such as personal data) is stored in a different system to the one from which ALE distribution was started. This is the case if specific information (such as infotype records) does not exist in the original ALE system. In the Data View area addition object information is displayed in columns. The BAdI can be used to select theses data from a different system that the one in which the object selection takes place. Object selection must be selected in one system.

© SAP AG 50

© SAP AG 2006

Agenda

4


5


Backend Components3


Data Provider

Object Provider




© SAP AG 51

© SAP AG 2006







Note: in ERP 2005 the Object Provider part of OADP has changed. For the Object Provider new tables are available in the backend customizing. The Data Provider part (Column Framework) remains unchanged.

© SAP AG 52

© SAP AG 2006

Data View Area

The Data View Area consists of columns and column headers. Columns are filled via function modules. However, several columns already exist and can be used.

Columns are grouped to Data Views.

© SAP AG 53

© SAP AG 2006

Data View Selector Area

Define Data Views and group them together. Data View Groups can then be assigned to a View

Define Data Views and group them together. Data View Groups can then be assigned to a View

The Data View Selector Area consists of Data Views. Data Views are grouped together to Data View Groups. Data View Groups are then assigned to Organizational Views.

For each Organizational View the number of Data Views and the content of the Data Views can differ.

© SAP AG 54

© SAP AG 2006

Column Group

Header Type


View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

V_TWPC_OBJSEL

VC_TWPC_OBJSELRULE

Next step: Columns and Column Groups

T77AW

Column 1

Column 2

© SAP AG 55

© SAP AG 2006

Define Columns

For Generic Use

This flag is purely for documentary purposes. It tells you that the column concerned can be displayed in any Column Group. The system can determine the content of columns with this flag independently from other columns.

Conversion Routine

Conversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.

Sorting Column Content

If you want to allow the user to sort the content of columns used in the Object and Data Provider, you must transfer the column content in a format that can be sorted. For more information refer to the IMG documentation.

If you want to reuse a function module that you have created for the Column Framework of the Personnel Management component, enter FM from Column Framework in this field.

Link

If you want to store a hyperlink for the text or icon in a column, specify the service the system can use to obtain information about the link. You create services in Customizing for the Column Framework under Services ->Define Services.

© SAP AG 56

© SAP AG 2006

Define Coherence Relationship

In this table you define the Coherence Relationship.In the IMG activity Define Column Groups you can use this

relationship to connect two or more columns together

In this table you define the Coherence Relationship.In the IMG activity Define Column Groups you can use this

relationship to connect two or more columns together

You do not want the user to be able to show or hide the Start Date and End Date columns separately that belong to the Organizational Data column group. In this IMG activity, therefore, you create the coherence relationship Org.Data Period. In the IMG activity, Define Column Groups, you assign this coherence relationship to the Start Date and End Date columns that belong to the Organizational Data column group.

The name of the coherence relationship is displayed in the dialog box for column configuration, which the user can call for each organizational view.

You assign coherence relationships to the appropriate columns in the IMG activity Define Column Groups.

© SAP AG 57

© SAP AG 2006

Column Groups

SAP entriesSAP entries

View to create customer specific Column GroupsView to create customer specific Column Groups

To overwrite SAP entriesTo overwrite SAP entries

The view for creating customer-specific column groups contains a customer namespace. You can create customer-specific entries in the namespaces Y* and Z*. You are not permitted to change the entries of the standard system in this view.

If you want to change a column group of the standard system, you must use the technical name of the relevant standard column group for your customer-specific entry in the IMG activity Create or Change Assignment of Columns to Column Groups. This enables you to overwrite the standard system entry.

© SAP AG 58

© SAP AG 2006

Group Columns Together

Column Group ColumnEnter coherence to display columns only together

You can make the following settings for each column group:

Define position of columns in column group

Set visibility attributes

Depending on these attributes, the user can show or hide columns individually.

Define coherence relationship between individual columns

© SAP AG 59

© SAP AG 2006

Hierarchical Column Groups

Hierarchical Column Groups are beneficial if a column group is used in more than one organizational structure view and you want to add a column to the column group in one

of these views

Hierarchical Column Groups are beneficial if a column group is used in more than one organizational structure view and you want to add a column to the column group in one

of these views

… consists of two columns /columns groups defined here… consists of two columns

/columns groups defined hereA new column…A new column…

In this IMG activity, you define hierarchies for columns and column groups. This is beneficial if a column group is used in more than one organizational structure view and you want to add a column to the column group in one of these views.

When you arrange columns and column groups in a hierarchy, the system displays the subordinate columns / column groups for a column group on the user interface.

© SAP AG 60

© SAP AG 2006

Redefine Column Headers

Column headers can differ dependent on the context

Column headers can differ dependent on the context

Note: entries are language specificNote: entries are language specific

In this IMG activity, you can store column headers that are dependent on the context or object type that is displayed.

© SAP AG 61

© SAP AG 2006


View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

V_TWPC_OBJSEL

VC_TWPC_OBJSELRULE

Next step: Define Data Views and assign Column Groups

Column Group

Header Type

T77AW

Column 1

Column 2

© SAP AG 62

© SAP AG 2006

Define Data Views –Assign Column Groups and Header Types

This entry is displayed in the

drop down list box

This entry is displayed in the

drop down list box

© SAP AG 63

© SAP AG 2006


View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

View 2

V_TWPC_ORGVW

V_TWPC_ORGVWGRP

V_TWPC_OBJSEL

VC_TWPC_OBJSELRULE

Next step: Define Data View Groups and assign Data Views. Assigning Data View

Groups to a View

Column Group

Header Type

T77AW

Column 1

Column 2

© SAP AG 64

© SAP AG 2006

Group Data Views

In this IMG activity, you group individual data views together in groups. The user can use the data views in such a group to display different column groups with additional information about the same object set.

You assign the group of data views to an organizational structure view

© SAP AG 65

© SAP AG 2006

Assign Object Selections to Organizational Views


The Data View Group created before must be assigned to views. This is done in a table already known from creating Views: V_TWPC_ORGVW

Enter table V_TWPC_ORGVW. Select a view for which you what to assign the Object Selection.

Enter the corresponding Object Selection into the appropriate field.

As you can see in on the slide a View consists of Object Selection and a Group of Data Views.

More information on Data View Groups can be found in the next part of this presentation.

© SAP AG 66

© SAP AG 2006

Test the OADP Customizing

The Function Module HRWPC_OADP_TEST can be used to test the OADP customizing

SE37 SE37

© SAP AG 68

© SAP AG 2006

Assign Views and View Groups to EE Search

Choose Self-Service categoryChoose Self-Service category

1 2

3

View GroupView Group

Single ViewSingle View

Enter the view for which the objects should be displayed as list in Navigation Area

Enter the view for which the objects should be displayed as list in Navigation Area

The connection between the backend and the front-end is usually done in the Portal. In the portal a view or view group is assigned to an iview or to a MSS application.

This assignment is done either in the Portal Content Directory (PCD) or Self-Service Administrator tool.

In this example it is the parameter is set for the iview Employee Search in the PCD (Content Administration –> Portal Content -> got to the appropriate iview by choosing Pages ->HCM -> General Information)

The organizational view or view group defined in the OADP tables of the backend system can be assigned to an application/iview as a parameter.

In this example the Org View Group MSS_TMV_EE is used for the iview.

© SAP AG 69

© SAP AG 2006

Table Views Relevant for MSS mySAP ERP 2005

Group of Data ViewsV_TWPC_DATAVWGRP

Group of Data Views - PositionV_TWPC_DATAVWG_P

Data ViewV_TWPC_DATAVW

Parameter GroupV_TWPC_PARAMGRP

Parameter Group - PositionV_TWPC_PARAMG_P

Restriction of Permitted Object Types for Object SelectionV_TWPC_OBJTYPERS

Rule for Object SelectionV_TWPC_OBJSELRUL

Object SelectionV_TWPC_OBJSEL

Group of Organizational ViewsV_TWPC_ORGVWGRP

Group of Organizational Views - PositionV_TWPC_ORGVWG_P

Organizational ViewV_TWPC_ORGVW

New Table Views

Hierarchical Column Groups - CustomerV_TWPC_HIERATP_C

Hierarchical Column GroupsV_TWPC_HIERATP

Definition of Coherence RelationshipsV_TWPC_FRIEND

Grouping ColumnsV_TWPC_COLMERGE

Definition of Column Header TypesV_TWPC_COLHTYP

New Definition of Column Headers - CustomerV_TWPC_COLHEAD_C

New Definition of Column HeadersV_TWPC_COLHEAD

Column DefinitionV_TWPC_COL

Definition of Column GroupsV_TWPC_ARRAYTP

Put Columns Together in a Column Group - CustomerV_TWPC_ACOL_C

Put Columns Together in a Column GroupV_TWPC_ACOL

Old Table Views – still used

© SAP AG 70

© SAP AG 2006

View Clusters – Relevant for MSS mySAP ERP

Parameter GroupVC_TWPC_PARAMGRP

Group of Organizational ViewsVC_TWPC_ORGVWGRP

Rule for Object SelectionVC_TWPC_OBJSELRULE

Group of Data ViewsVC_TWPC_DATAVWGRP

New View Clusters

© SAP AG 71

© SAP AG 2006

Prerequisites

You have depicted the organizational plan of your company in Organizational Management. This includes the organizational structure and staff assignments.

The user who is logged on or the person to which the user is assigned in the Communication infotype (0105), are holders of a chief position.

If you want to display cost centers, you must have assigned costcenters to the organizational unit or the chief positions.

Note: It is recommended to use structural authorizations for theObject and Data Provider.

© SAP AG 72

© SAP AG 2006

OADP – Customizing Steps

View Group

View 1

Object selection




Data View Group

Data View 1

Evaluation path

Function Module

Data View 2

or

© SAP AG 74

© SAP AG 2006


Board

ProductionHR

By relating objects via relationships, you create a network thatmirrors your organizational and reporting structures. In addition to this, you can create relationships to objects from other components(cost center, employee or R/3 User, for example).

© SAP AG 75

© SAP AG 2006

HR

PayrollEE Development

...

Task Qualification

Organizational Management - Staffing

Position

Position

Person/User

Person/User

In Organizational Management for every organizational unit in your organizational structure you can create relevant staff assignments. First you must create positions which are to be allocated to established organizational units. A position is based on a job which describes it, this is an advantage of the organizational model which contains your organizational plan. This means that a position inherits the description of the task. This lowers your administrative costs. You only have to describe the position using tasks which are not inherited.

A position represents the concrete form of a job, it is for the most part occupied by a person and is assigned to an organizational unit (or more than one organizational unit), secretary in the marketing department for example. A position has a definite profile and can become vacant.

A job is a business segment which is defined by task and requirement. Jobs (secretary or programmer, for example) will only appear once in a company. You can create jobs when they are necessary for your organizational structure but do not yet exist in your job index. If you create a position first, the jobs which you have assigned to the position will be displayed. Simple Maintenance lets you create several jobs at once.

Holders are then assigned to positions. You use this feature to determine which person (employee) or R/3 user occupies a position. By assigning a position, R/3 users in Workflow can, directly or indirectly - by their relationship with employees - be determined as agents of work items. In Simple Maintenance you can identify positions as chief positions of an organizational unit.

Once you have created your organizational structure and staff assignments, you can create and edit task and requirement profiles.

© SAP AG 76

© SAP AG 2006

HR

PayrollEE Development

...

Task

Qualification

Organizational Managment - Jobs & Infotypes

Position

Position

Person/User

Person/User

JobHeadcount

1. Q 2. Q 3. QSekretärinTechniker

Infotype

You identify the different attributes of an object by individually creating and maintaining infotype records.

These infotype information can also be used by OADP and be displayed as column information.

© SAP AG 77

© SAP AG 2006

Object Relationships: Data Model

Position

Cost Center

Work Center

Person/User

Task

OrganizationalUnit belongs to

incorporates

incorporates

belongs to

Holder

occupies

describes

is described by

describes

is describedby

Cost Center Allocation

describes

is described by

Cost CenterAllocation

reports to/is line supervisorof

Job

Objects are linked though relationships.

Several linked objects may represent a structure.

© SAP AG 78

© SAP AG 2006

Organizational Management - Evaluation Paths

B002

A008

B003

Evaluate all objects that are found in the evaluation pathstarting from the root organization

Create objects and relationshipsin general structure maintenancealong evaluation paths

Evaluation paths are chains of relationships that exist between certain object types.

O-S-P Staff assignments alongorganizational structureO B003 SS A008 PO B002 O

Example:

An evaluation path is an instruction to the system which determines which object types and relationship(s) are to be included in an evaluation of your organizational plan.

Evaluation paths define how a tree structure will be created. As objects may have multiple relationships, not all will be applicable or even possible in a single view.

Evaluation paths represent two or more relationships combined together branching out from a root object.

Example: To view Staff assignments along the organizational structure you would start with an Organizational Unit and identify relationships to incorporated positions then, from the positions, identify persons holding those positions. After the cycle is finished you go to any subordinate organizational units and start the cycle again.

© SAP AG 79

© SAP AG 2006

Copyright 2006 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

mss new object_data_provider_(oadp)

Documents