New team in ESS / MSS calendar
Once more a small post on an easy modification of the ESS / MSS standard. This one works for all versions of the ESS / MSS (WebDynpro Java, WebDynpro ABAP, UI5...) and allows the addition of specific teams / population to the ESS / MSS calendars in a standard way (i.e. no reparation).
Principes
The use of teams in calendar is based on a hierarchy of components that define when the teams are displayed, and how their content is extracted.
Calendar mode (usage of calendar)
|
+-- Group of organisational views ("list of menus")
|
+-- Organisational View A (menu)
|
+-- Organisational View B (menu)
|
+ Selection Object (method to get the content of calendar)
|
+-- Source selection rule
|
+-- Object selection rule
All this is available in spro under "Human resource Management / Manager self service / Object and Data provider" :
A group of organisational view is akin to a list of menu. Each group is associated with an ordered list of organisational view.
Organisational View are akin to a menu. It is associated with a title, and a selection object.
The selection object indicate how the content of the calendar (i.e. employees) will be extracted. This is based on two rules. The first one indicate what will be the source(s) of the extraction (for example, units managed by the connected employee), while the second perform the extraction for each source (for example the employees in a given unit)
The selection rules are based either on an OM evaluation path or on a module function. In the first case, you just indicate the evaluation path's id and the depth. In the later, the function must be modelled from the template HRWPC_PATHROOTS (source selection rule) or HRWPC_EVAL_PATH (object selection rule).
We're going to change the standard team so that external people are removed from the calendar. external people, in this case, is defined as people with IT0001-PERSG equal to '8' or '9'.
The selection object indicate how the content of the calendar (i.e. employees) will be extracted. This is based on two rules. The first one indicate what will be the source(s) of the extraction (for example, units managed by the connected employee), while the second perform the extraction for each source (for example the employees in a given unit)
The selection rules are based either on an OM evaluation path or on a module function. In the first case, you just indicate the evaluation path's id and the depth. In the later, the function must be modelled from the template HRWPC_PATHROOTS (source selection rule) or HRWPC_EVAL_PATH (object selection rule).
Realisation
We're going to change the standard team so that external people are removed from the calendar. external people, in this case, is defined as people with IT0001-PERSG equal to '8' or '9'.
- First we create a function to get our specific content. This is an object section rule, thus based on HRWPC_EVAL_PATH. It will receive the concerned unit. We 'only' have to get the employees of the each unit and remove the one that are externals.
- We add a selection object rule ZMSS_LEA_RULE5 that refers to our function module
- We then create a selection object ZMSS_LEA_EE_DIR, copied on the selection object MSS_LEA_EE_DIR. We change the object rule for our own.
- Then we create an organisational view ZMSS_LEA_EE_DIR, that refers to our selection object.
- Then we duplicate the standard group of organisational views MSS_LEA_EE into our own, and change the organisational view for our own.
- Last, we associate the group of organisational view to the calendar mode "Leave Approval"
No comments:
Post a Comment