Manager Self-Service (MSS) - MSS team view,

managers who do not hold chief position

Posted by Mohsin Syed in SAP ERP HCM Employee Self-Service on Feb 7, 2014 12:57:01 PM
Problem Description: I have gone through so many discussions regarding MSS team view access for
those managers who do not hold chief position, I thought to give a glance on this that we can get this
by doing some configuration changes and with custom Function Module.
Solution:
Usually, managers can have access to employees not only from his Organization but different
organization. The standard Evaluation path is an example to do so, but usually it doesn't meet the
requirements so as to enable different possibilities you can use the benefits of OADP.
You can use your custom evaluation paths and FM to get the employees according to the relationship.

To achieve the solution go with the below steps.

1. Create custom evaluation path S-S-P
Go to -> SM30 -> Enter T77AW table and click on Maintain -> Click on New Entries

2. Check the IMG step

Integration with Other mySAP.com Components -> Business Packages/Functional Packages -> Manager
Self-Service (mySap ERP) -> Object and Data Provider -> Organizational Structure Views -> Group
Organizational Structure Views.
MSS_TMV_EE is assigned to MSS_TMV_EE_DIR and MSS_TMV_EE_ALL as shown below

And then these Organizational Views are defined at IMG step: Define Organizational Structure Views
as shown below

Open the Object Selection view of MSS_TMV_EE_DIR, as we need to customize this Org View, you will
find as shown below.

Then you can check the rules for Object Selection: IMG Object Provider -> Define Rules for Object
selection: Object Selection Rule: MSS_TMV_RULE1
EVALPATH is SAP_MANG Org. Units Managed by persons or users.
This will get only the Org Unit. This won't serve our requirement so we need to customize. In the step 1
you can see the Custom Evaluation Path S-S-P which would be useful for our requirement as this will
give you all the positions of employees who are reporting directly to the Manager.
In the above screen Rules for Root Objects should be changed to MSS_BIZ_RULE1 as this will get the
position and personnel number of a user. The Restrict Object type for this should be S Position.
EVALPATH is SAP_US_S - Positions and Personnel Number of a User.
After Customizing Object Selection looks like below.

MSS_BIZ_RULE1 looks like below

3. Rules for Navigation Objects should be assigned to MSS_BIZ_RULE2 and need to Customize

Assign our custom

Evaluation path: S-S-P
Depth of Structure: 2 (up to Level 1) or 3 (up to Level 2)
Function Module: Z_HRWPC_EVAL_PATH
We have to create the Z function module for Object Set. So we will copy the standard FM
HRWPC_EVAL_PATH (Function module for Object Set) into Z FM Z_HRWPC_EVAL_PATH to set all the
Positions retrieved through S-S-P evaluation path to the OBJECT.
The Restrict Object type for this should be S Position.

4. Z_HRWPC_EVAL_PATH Function Module Source Code is as below

We are not going to Change Rule for Target Objects it should be MSS_TMV_RULE5 Direct Reports.
OUTPUT
Login into Portal with Reporting Manager Credentials. You will see the output as shown below where he
can able to see his Direct Reportees with his Absence Details.

Login into Portal with HOD Credentials. You will see the output as shown below.

If you don't have an access to login into Portal with HOD are Manager. The alternate way to check the
Output or Result is Use the Function Module HRWPC_RFC_OADP_GET_OBJECTS through SE37 Tcode and
execute as per the suggestions given by Dhiraj Pednekar in the below link
http://scn.sap.com/community/erp/hcm/employee-self-service/blog/2013/10/14/function-module-to-getsubordinates-of-a-manager
Thanks for Reading this post ends here. Any comments or suggestions are most welcome.
6131 Views Tags: teamcalendar, mss_team_error

Average User Rating

(5 ratings)

52 Comments

Yugandhar Reddy Feb 11, 2014 5:17 PM

Thanks Mohsin Syed for sharing the information, it helps us. Keep coming up with more blogs.
Like (0)

MALYADRI JWALA G Feb 11, 2014 6:28 PM

hi syed ,

Awesomee. really ..waiting from so many days this scenario ....finally you made this ...really
apprecaite your hard work .we expect more blogs from you in coming days.
Like (0)

Srikanth Naidu Akula Feb 11, 2014 6:45 PM

Hi Mohsin,
Excellent work, most awaited document in ESS & MSS Space and most of the customers
requirement. Thanks a lot. Keep rocking.
Like (0)

Mike Wolfe Mar 13, 2014 8:08 PM

Hi Mohsin,

This is an amazing guide! I need to implement this same thing right now, but am struggling.
I have set up everything as the guide states and have tested both the custom function module
and the function module referenced by Dhiraj Pednekar and get the results expected in R3 for
a manager not set up as a chief.
When I log into MSS as that manager, I do not see any of my direct reports in any of the views.
Do you have any idea what I might have missed or where I could look?
Thank you!
Like (0)

Mohsin Syed Mar 18, 2014 6:50 AM (in response to Mike Wolfe)

Mike,
Sorry for late reply, I saw your comment on the posted date but I was busy and I went
on leave and came back today. If you have implemented same as per the guide it
should work, have you correctly restricted the objects at the "Define rule for object
selection'. At what version your system is let me know.
Regards,
Mohsin.
Like (0)

Mike Wolfe Mar 18, 2014 1:55 PM (in response to Mohsin Syed)

Mohsin,

Thank you for the reply. We are on ECC 6, support pack level 66.
I have checked all of the config and it matches your guide.
MSS_BIZ_RULE1 has the SAP_US_S eval path and is restricted by position
MSS_BIZ_RULE2 has the custom S-S-P eval path with a depth of 2 and the
custom function module Z_HRWPC_EVAL_PATH. This is also restricted by
position.
MSS_TMV_EE_DIR has a root of MSS_BIZ_RULE1, navigation of
MSS_BIZ_RULE2, & a target of MSS_TMV_RULE5.
Thanks again for your help!
Mike
Like (0)

Mohsin Syed Mar 19, 2014 8:15 AM (in response to Mike Wolfe)

Hi Mike,
If you have done the same as you mentioned it should work, but It
seems some authorization problem is there please check that the
managers who are not chief has authorizations to access the TEAM
VIEW page and also check whether is there any refresh problem.
Regards,
Mohsin.
Like (0)


Mike Wolfe Mar 19, 2014 3:13 PM (in response to Mohsin Syed)

Is it possible that the portal is referencing some other

configuration? I deactivated MSS_TMV_EE_DIR and checked a
manager set up as a chief and they still functioned properly.
Like (0)

Mohsin Syed Mar 20, 2014 11:37 AM (in response to Mike

Wolfe)

Hi Mike,
After Deactivating MSS_TMV_EE_DIR you are still able
to see the team for Manager who is chief, I think that
is because of Cache Validity and it would remain for
one day.
Regards,
Mohsin.
Like (0)

Mike Wolfe Mar 20, 2014 3:11 PM (in response to

Mohsin Syed)

Hi Mohsin,
I really appreciate your help with
troubleshooting my issue. MSS_TMV_EE_DIR
has been deactivated for over a day and the
cache validity is also set to -1. If I understand
the cache validity correctly, -1 would ensure
that the system rereads the data each time a
user access the webdynpro or refreshes.
It still appears to work for the Chief
manager, even though MSS_TMV_EE_DIR has
been disabled. Do you know of a function
module I could set a breakpoint in to see
what evaluation path our team calendar is
referencing? I think this may help me
determine what is not linking to
MSS_TMV_EE.
EDIT:
I was able to hit a breakpoint in function
module HRWPC_RFC_RD_DATES_GETLIST.
This seems to be checking the function
HRWPC_READ_TWPC_V_T. This table
V_TWPC_V seems to be a different
configuration point than what your guide
shows. DO you have any idea of where the
connection point may be to the configuration
in your guide?
Thank you!
Mike
Like (0)


Mohsin Syed Mar 21, 2014 7:29 AM (in
response to Mike Wolfe)

Hi Mike,

You can put a breakpoint inside the

function module
'HRWPC_RFC_OADP_GET_OBJECTS'
where it calls the FM
'HRWPC_RFC_OADP_GET_NAVOBJECT
S' and in this again it goes to this FM
' HRWPC_GET_PATHROOTS' here you
need to put break point and check
the Evaluation path is correct as per
the rule MSS_BIZ_RULE1 'SAP_US_S'.
Regards,
Mohsin.
Like (0)

Mike Wolfe Mar 21, 2014 3:22

PM (in response to Mohsin
Syed)

Mohsin,
I was able to debug
yesetrday and found that
the configuration being
called is not entirely the
same as your guide. The
view that was originally
being referenced was A_ALL
and A_DIR. These were
found on table TWPC_V, but
do not exist in the config
section of the guide you
wrote.
Setting up the view for
these seems similar,
though. I am able to call a
custom view Z_DIR that
references SAP_US_S for the
Eval Path for Root Objects
and S-S-P for the Eval Path
Objects(with the custom
function module
referenced).
When I debug I do get to
both SAP_US_S and S-S-P
eval paths. Inside the
custom function module,
OTYPE = US and OBJID = my
user name. Upon exiting the
RH_STRUC_GET, result_tab
is empty so root_objects is

never updated with the

employees that report to
me. Is that where I am
experiencing this issue?
Should OTYPE and OBJID be
US and a user name or
should they be a P and a
personnel number or S and
a position?
Thanks,
Mike
Like (0)

Mohsin Syed Mar 24, 2014

12:29 PM (in response to Mike
Wolfe)

Hi Mike,

This might be some

authorization issue, yes
OTYPE and OBJID should be
US and a Username.
Regards,
Mohsin.
Like (0)

o
Mike Wolfe Mar 27, 2014 12:18
PM (in response to Mohsin
Syed)

I was able to finally get this

to work.

In case anyone else has the

same issue, I had to create
views via table
V_TWPC_V_C, then assign
these to the ATTEND and
REPORTING groups in table
V_TWPC_VG_C.
Each of these views had to
reference a custom function
module for root objects and
eval path. We did not utilize
the RH_STRUC_GET function
module for eval path, but
instead retrieved all
subordinate employees via
table reads of HRP1001(I
can post code if needed).
Similarly, we retrieved the
necessary information in the
custom root object function
module by pulling data from
PA0001 using the username

on PA0105(this data was

appended to pathroots).
Thanks for all your help
Mohsin! Without this guide
to get me started, we
wouldn't have been able to
implement this!
Mike
Like (2)

Mohsin Syed Mar 27, 2014 5:46

PM (in response to Mike Wolfe)

Hi Mike,
Its good that you achieved
your requirement
, it
would be better that you
can post your problem and
the solution with some
explanation using
screenshots so that it would
be helpful to others and the
code which you
implemented, that would be
a great contribution from
your end to others.
Regards,
Mohsin.
Like (0)

Mike Wolfe Apr 10, 2014 9:45

PM (in response to Mohsin
Syed)

Below are the steps I had to

use to achieve these results.
Table: T77AW
-Created Eval Path S-S-P
per Mohsin's specifications
Table: V_TWPC_V_C
-Created new view Z_DIR
Eval Path for Root
Objects: SAP_US_S
Function Module for Root
Objects:
Z_HRWPC_ROOT_OBJ
Evaluation Path Objects:
S-S-P
Function Module Object
Set: Z_HRWPC_EVAL_PATH
Initial Evaluation Depth:
2
Column Group: ATTEND

-Check 'Delete
Duplicates'
-Created new view Z_RPT_D
Eval Path for Root
Objects: SAP_US_S
Function Module for Root
Objects:
Z_HRWPC_ROOT_OBJ
Evaluation Path Objects:
S-S-P
Function Module Object
Set: Z_HRWPC_EVAL_PATH
Initial Evaluation Depth:
0
Column Group: RPT_EMPL
-Check 'Delete
Duplicates'
-Check 'Excl. Managers'
Table: V_TWPC_VG
-Removed A_DIR from
ATTEND viewgroup
-Removed RPT_PD from
REPORTING viewgroup

Table: V_TWPC_VG_C

-Assigned A_ALL and

Z_DIR to group ATTEND
-Assigned ZRPT_D to
group REPORTING
Table:V_TWPC_OTYPES_C
-Created Z_DIR with a
object type of P(Person)
Table: V_TWPC_ORGVW ->
MSS_TMV_EE_DIR
Object Selection:
MSS_TMV_EE_DIR
Group of Data Views:
MSS_TMV_EE
Table:
VC_TWPC_ORGVWGRP
-Assigned
viewsMSS_TMV_EE_DIR,MS
S_TMV_EE_ORG1,
MSS_TMV_EE_ORG2, &
MSS_TMV_EE_SRCH
Table: V_PTREQ_TEAM
-Assigned MSS_TMV_EE to
Team View Mode
Custom Function
Modules:
FUNCTION
Z_HRWPC_ROOT_OBJ.

*"--------------------------------------------------------------------*"*"Local Interface:
*" IMPORTING
*"
REFERENCE(USER)
LIKE SY-UNAME
*"
REFERENCE(BEGDA)
LIKE OBJEC-BEGDA
*"
REFERENCE(ENDDA)
LIKE OBJEC-ENDDA
*"
REFERENCE(EVALPATH)
LIKE GDSTR-WEGID
OPTIONAL
*"
REFERENCE(DEPTH)
LIKE GDSTR-DEPTH
DEFAULT 0
*" TABLES
*"
PARAMVALUES
STRUCTURE
HRWPC_S_OADP_PARAMVAL
UE OPTIONAL
*"
PATHROOTS
STRUCTURE HRROOTOB
*" EXCEPTIONS
*"
NO_OBJECTS_FOUND
*"--------------------------------------------------------------------"-- Declare Variables
data:
result_tab
swhactor,
ls_tab
ls_pathroots
ob,

typetable of
typeswhactor,
typehrroot

lwa_obj
typetable of
HRWPC_S_KEYOBJEC,
lwa_test
S_KEYOBJEC,

typeHRWPC_

lv_pernr
pernr,

typepa0001-

lwa_0001
1.

typepa000

if sy-subrc = 0.
select single pernr
from pa0105
into lv_pernr
where subty = '0001'
and endda >= sydatum
and begda <= sydatum
and usrid = sy-uname.

select single *
from pa0001
into lwa_0001
where pernr = lv_pernr
and endda >= sydatum
and begda <= sydatum.
pathroots-otype = 'US'.
pathroots-objid = syuname.
append pathroots.
pathroots-otype = 'P'.
pathrootsobjid =lwa_0001-pernr.
append pathroots.
pathroots-otype = 'S'.
pathrootsobjid =lwa_0001-plans.
append pathroots.
endif.
ENDFUNCTION.

FUNCTIONZ_HRWPC_EVA
L_PATH.
*"--------------------------------------------------------------------*"*"Local Interface:
*" IMPORTING
*"
VALUE(DEPTH) LIKE
TWPC_V-DEPTH DEFAULT 0
*"
VALUE(EVPATH) LIKE
TWPC_V-EVPATH OPTIONAL
*"
VALUE(PLVAR) LIKE
OBJEC-PLVAR
*"
VALUE(BEGDA) LIKE
OBJEC-BEGDA DEFAULT SYDATUM
*"
VALUE(ENDDA) LIKE
OBJEC-ENDDA DEFAULT SYDATUM
*"
VALUE(LEVEL) LIKE
HRWPC_S_KEYSTRUC-LEVEL
DEFAULT 1
*" TABLES
*"
ROOT_OBJECTS
STRUCTURE HRROOTOB
*"
ROOT_OBJEC
STRUCTURE OBJEC
OPTIONAL

*"
ROOT_STRUC
STRUCTURE STRUC
OPTIONAL
*"
PARAMVALUES
STRUCTURE
HRWPC_S_OADP_PARAMVAL
UE OPTIONAL
*"
RESULT_OBJEC
STRUCTURE OBJEC
*"
RESULT_STRUC
STRUCTURE STRUC
*" EXCEPTIONS
*"
NO_OBJECTS_FOUND
*"--------------------------------------------------------------------DATA:
BEGIN OFlt_subordinates
OCCURS0,
pernr LIKE pa0001pernr,
begda LIKE pa0001begda,
endda LIKE pa0001endda,
plans LIKE pa0001plans,
ename LIKE pa0001ename,
END OFlt_subordinates.
DATA:
posno LIKE hrp1001sobid,
sobid LIKE hrp1001-objid.
DATA:
BEGIN OF lt_plansOCCUR
S 0,
endda LIKE pa0001endda,
plans LIKE pa0001plans,
END OF lt_plans.
DATA:
BEGIN OFlt_subordinates
_posOCCURS 0,
endda LIKE pa0001endda,
sobid LIKE hrp1001sobid,
objid LIKE hrp1001objid,
END OFlt_subordinates_p
os.
DATA:
BEGIN OF lt_pernrsOCCU
RS 0,

pernr LIKE pa0001pernr,

END OF lt_pernrs.
DATA: pernr LIKEpa0001pernr.
SELECT SINGLE pernr
FROM pa0105
INTO pernr
WHERE subty = '0001'
AND endda >= sydatum
AND begda <= sydatum
AND usrid = sy-uname.
SELECT endda plans
FROM pa0001
INTO TABLE lt_plans
WHERE pernr = pernr
AND endda >= sydatum
AND begda <= sydatum.
IF sy-subrc EQ 0.
SORT lt_plans BYendda D
ESCENDING.
READ TABLE lt_plansINDE
X 1.
SELECT endda sobid
FROM hrp1001
INTO TABLElt_subordina
tes_pos
WHERE otype = 'S'
AND plvar = 'C1'
AND objid = lt_plansplans
AND rsign = 'B'
AND relat = '002'
AND begda <= sydatum
AND endda >= sydatum
AND sclas = 'S'.
IF sy-subrc EQ 0 .
SORTlt_subordinates_po
s BYsobid
enddaDESCENDING.
DELETE ADJACENTDUPLI
CATES FROMlt_subordinates
_posCOMPARING sobid.
LOOP ATlt_subordinates
_pos.

lt_subordinates_posobjid =lt_subordinates_possobid.
SELECT SINGLEsobid
INTO posno
FROM hrp1001
WHERE otype = 'S'
AND objid =lt_subor
dinates_pos-objid
AND plvar = 'C1'
AND rsign = 'A'
AND relat = '008'
AND sclas = 'P'
AND begda <= sydatum
AND endda >= sydatum.
IF sy-subrc = 0.
lt_pernrspernr =posno.
APPEND lt_pernrs.
CLEAR posno.
ENDIF.
ENDLOOP.
IF lt_pernrs[] IS NOTINIT
IAL.
DELETE ADJACENTDUP
LICATES FROMlt_pernrs.
SELECT pernr begda
endda plans ename
FROM pa0001
INTO TABLElt_subordi
nates
FOR ALL ENTRIESIN lt
_pernrs
WHERE pernr =lt_per
nrs-pernr
AND begda <= sydatum
AND endda >= sydatum.
SORTlt_subordinates B
Y pernr endda DESCENDING.
DELETE ADJACENTDUP
LICATES FROMlt_subordinate
sCOMPARING pernr.
LOOP ATlt_subordinate
s.
result_strucseqnr =sy-tabix.
result_struc-level =1.
result_strucotype ='P'.

result_strucobjid =lt_subordinatespernr..
APPENDresult_struc.
result_objecplvar ='C1'.
result_objecotype ='P'.
result_objecobjid =lt_subordinatespernr.
result_objecbegda= lt_subordinatesbegda.
result_objecendda= lt_subordinatesendda.
result_objecstext =lt_subordinatesename.
result_objec-istat =1.
result_objecrealo =lt_subordinatespernr.
APPENDresult_objec.
ENDLOOP.
ELSE.
RAISEno_objects_found
.
ENDIF.
ELSE.
RAISEno_objects_found.
ENDIF.
ELSE.
RAISEno_objects_found.
ENDIF.
ENDFUNCTION.
Like (0)

Mohsin Syed Apr 11, 2014

12:24 PM (in response to Mike
Wolfe)

Thanks Mike...
Regards,
Mohsin.
Like (0)

Thomas Devassy Mar 19, 2014 11:55 AM

Thanks Mohsin Syed ,

this a steaming issue for a long time,

regrds
Thomas

Like (0)

Mohsin Syed Mar 19, 2014 12:04 PM

Thanks to all
Like (0)

Thomas Devassy Mar 20, 2014 11:09 AM

hi mohsin Syed,
you have mentioned to assign Restricted object type 'S' position to
rule MSS_BIZ_RULE1 ,where as standard already have restricted object type 'P' Person. why is
this change.and Do i need to remove the restricted object type 'P'?
thanks
Thomas
Like (0)

Mohsin Syed Mar 20, 2014 11:42 AM (in response to Thomas Devassy)

Hi Thomas,
Yes, remove the Object type 'P' in MSS_BIZ_RULE1 and assign it to 'S' because we
need to fetch the Position of the Manager and just assign it to next rule
MSS_BIZ_RULE2 where we need to fetch 'S-S-P' i.e., nothing but based on position we
are retrieving the reportees of that manager.
Regards,
Mohsin.
Like (1)

praneeth kumar m Mar 24, 2014 7:44 AM

Hi,

Good Document.
Like (0)

o
Mohsin Syed Mar 24, 2014 12:30 PM (in response to praneeth kumar m)

Thanks Praneeth.
Like (0)

Pradyp Parakala Mar 24, 2014 8:18 AM

Gr8 work Mohsin

Really it's a long await documents from all ESS/MSS consultants. surely i appreciate ur work.
Keep coming with more docs like this...
Cheers
Pradyp
Like (0)

Mohsin Syed Mar 24, 2014 12:31 PM (in response to Pradyp Parakala)

Thanks Pradyp..
Like (0)

Thomas Devassy Mar 26, 2014 2:44 PM

hi mohsin,
i have done the changes mentioned in the document.
but i am getting position number(30004401) of that employee in the screen and MSS
application is not able to recognize.

(
MSS_BIZ_RULE1 is the SAP_US_S and is restricted by position
MSS_BIZ_RULE2 is the S-S-P with a depth of 2 and the custom function module
ZHRWPC_EVAL_PATH. This is also restricted by position.
Like (0)

Mohsin Syed Mar 27, 2014 11:32 AM (in response to Thomas Devassy)

Hi Thomas,
What is the version of your sap system and ESS/MSS. Are you using NWBC.

Regards,
Mohsin.
Like (0)

Thomas Devassy Mar 29, 2014 11:45 AM (in response to Mohsin Syed)

i am using portal.

MSS ADDON 1.0

BP_ERP5ESS - 1000.1.41
BP ERP05 MSS 1.51
regards
thomas
Like (0)

Thomas Devassy Sep 2, 2015 12:12 PM (in response to Mohsin Syed)

Hi Mohsin,
I have implemented all the config steps , however I am getting the same
errors asThomas Devassy mentioned in his reply.
i am getting position number of that employee in the screen and MSS
application is not able to recognize.

Please provide some suggestion here.

Thanks
Pradeep
Like (0)

Rajesh Kumar Apr 2, 2014 9:55 PM

Hi Mohsin,

Thanks for this post!

we want to apply similar concept in our project where travel admin should be able see the
team calendar of their department employees(for leave).do you think using this concept we
can achieve this.
Regards
Rajesh
Like (0)

o
Mohsin Syed Apr 3, 2014 12:11 PM (in response to Rajesh Kumar)

Hi Rajesh,

I didn't check for Travel management I think this would be done if you have already
Org structure maintained correctly with all required relationships.
Try with this guide which I have shown using NWBC portal else let me know, then I will
help what ever I can.
Regards,
Mohsin.
Like (0)


Barin DESAI Apr 8, 2014 3:44 PM

good work mohsin.

i have a query here. we have a drop down that is called direct reportees woudln't this work to
evaluate s to s (a002) path.
just a simple query if you can help.
Like (0)

Mohsin Syed Apr 9, 2014 8:37 AM (in response to Barin DESAI)

Hi DESAI,
Thanks,
No S to S wont work for Drop down that appears as Direct Reportees this has the
standard config which will use 'SAP_MANG' as its evaluation path.
Regards,
Mohsin.
Like (1)

Barin DESAI Apr 9, 2014 8:39 AM (in response to Mohsin Syed)

thank you mohsin.

Like (0)

Mike Wolfe May 21, 2014 6:07 PM

Mohsin,
I am trying to implement this for the Talent Information iView and I would say I am partially
getting the correct results. I did your above configuration, but assigned it to a
ZMSS_TMV_EE_DIR.
When a chief view, object selection = MSS_TMV_EE_DIR, their direct reports all show up within
1 window.

When the non-chief view, object selection = ZMSS_TMV_EE_DIR, their direct reports flow into
an organizational structure to the left of the window and the manager has to select each
position to view the employee in that position.

Any thoughts on how to prevent this view of showing employees in the org unit by position?
Like (0)

Namsheed K S Sep 2, 2014 4:31 AM

Dear Mohsin Syed,

I am searching for a document like this. Not only me many of my collegues are unaware of this
solution. This is absolutely wonderful.

I have only 1 query. Is this applicable to NWBC also..??

Or any changes are needed in the configuration steps..??
Waiting for your reply.
Thanks again,
Namsheed.
Like (0)

Mohsin Syed Sep 2, 2014 11:21 AM (in response to Namsheed K S)

Thanks Namsheed,
Why not it works with NWBC as well, when I was working on NWBC then I faced the
same issue then I have resolved by these steps which I captured as document and
posted for community to help others.
If it helps you then surely it will help your collegues, go ahead with sharing this link.
Make sure everybody reward points

once they go through document.

Regards,
Mohsin.
Like (1)

Namsheed K S Sep 5, 2014 1:46 PM (in response to Mohsin Syed)

Hi Mohsin,

I have done everything exactly like you told. But still I am not getting the
employee list in Manager's MSS Team.
How can check where I am wrong.
It will be a huge help if I could resolve it.
Thanks in advance,
Namsheed.
Like (0)

Mohsin Syed Sep 5, 2014 2:00 PM (in response to Namsheed K S)

Hi Namsheed,
As I suggested at last step of my document you can use the function
module and pass the relevent input parameters and check whether
you are getting the result or not, If you are getting the result in output
then it should have to give you employee list as a team for that
manager in NWBC.
Function Module to get subordinates of a manager
Function Module: HRWPC_RFC_OADP_GET_OBJECTS
Input Parameters.

OBJEL: MSS_TMV_EE_DIR (or) MSS_TMV_EE_ALL

BEGDA: CurrentDate
ENDDA: CurrentDate
USERID: ManagerID
Cache: default value

Regards,
Mohsin.
Like (1)

Namsheed K S Sep 5, 2014 2:16 PM (in response to Mohsin Syed)

Hi Mohsin,

I have executed the FM.

I cant find the reporting employees here also.

So what I can do now

Like (0)

Mohsin Syed Sep 6, 2014 4:10 PM (in response to

Namsheed K S)

Hi Namsheed,

Can you please check the OADP config that you Org
strucuture is linked to which structure you may be
referring to 'MSS_TMV_EE' I think you have to change
this to 'MSS_TMV_EE' for the above configuration
which you have made using my configuration guide.

Regards,
Mohsin.
Like (1)

Namsheed K S Sep 7, 2014 10:37 AM (in response

to Mohsin Syed)

Dear Mohsin,
Both you mentioned as MSS_TMV_EE.
Also can you mentioned the path for
checking the OADP config to check org
structure is linked with MSS_TMV_EE .?

Thanks,
Namsheed.
Like (0)

Mohsin Syed Sep 8, 2014 12:45 PM (in

response to Namsheed K S)

HI Namsheed,
That was actually typo mistake, the
path you can go and check is
whether you are using MSS_TMV_EE
is check
IN SPRO->PersonnelManagement>Employee SelfService(Webdynpro)->Service
Specific Settings->WorkingTime>TeamCalendar->Select Employees.
check that for you Rule Group
whether the Column 'Group of
Organizational Views' is filled with
'MSS_TMV_EE'.
Regards,
Mohsin.
Like (1)

Namsheed K S Sep 8, 2014

12:52 PM (in response to
Mohsin Syed)

Hi Mohsin,

No..its not MSS_TMV_EE.

As you mentioned in the

document, For
MSS_BIZ_RULE1 & MSS_BIZRULE2,
In Restrict object type,
Already P Person is there
and I am unable to delete it
as it is a SAP Entry. So I
added a new entry for S
Position like below.

Advice me what to do.

Regards,
Namsheed
Like (0)

Mohsin Syed Sep 8, 2014 1:21

PM (in response to Namsheed K
S)

Hi Namsheed,

As suggested by Jwala
please post your queries in
discussion threads, hope
you have already a thread
open. So it would be useful
to others to have a look for
a solution and to get the
reward points for the
contributors.
As per my understanding if
you have implemented all
the steps through my
Document. Then you need
to do as it is then only you
will see the output.
When you are able to create
a object type 'S' in
MSS_BIZ_RULE1 you can be
able to delete as well. If it is
SAP entry also you can
delete it, do that.
And you need to change the
'Group of organization view'
to MSS_TMV_EE in the above
screenshot at the last record
if your rule group is
'99999999'.
Regards,
Mohsin.
Like (1)

o
Namsheed K S Sep 8, 2014 2:47
PM (in response to Mohsin
Syed)

Dear Mohsin,
Thanks a lot

The issue is solved.

Now managers can view the
direct reportees without
holding the chief position.
I am sorry I can't give you
points here, anyway I have
shared the link with many of
my colleagues, they will
reward points for sure...I
liked all your comments also

(hope you will get some

points).

Jwala, Next time I will

comment in thread only.

Muhsin, Thanks a lot once
more
Namsheed.
Like (0)

Mohsin Syed Sep 8, 2014 3:30

PM (in response to Namsheed K
S)

Hi Namsheed,

Good to here that your

query resolved, but as said
by jwala it should be a
thread so that we can earn
some points, sad

that I

didn't get
. May be you
can give rating to the blog.
Regards,
Mohsin.
Like (1)

Namsheed K S Sep 14, 2014

2:51 PM (in response to Mohsin
Syed)

Hi Mohsin,
In PRD system, only for the
chief , all the employees
are coming in direct
reportees. eventhough only
2 direct reportees are there.
What could be the reason
for that.?
Thanks,
Namsheed.
Like (0)

Jwala ESS MSS Sep 8, 2014 1:08 PM

kindly post all ur queries in the threads not in blogs

Like (1)

Namsheed K S Sep 8, 2014 5:04 PM

Wonderful & Exceptional document...! No words to explain.

This document will be an asset to all HR & ESS/MSS Consultants.

Hope you will come with many such useful documents .
Thanks one more time !!
Namsheed.
Like (0)

Jazib Tariq Jan 12, 2015 9:34 AM

Hello Mohsin,

how are you,hope your fine... I need some help. In my organization , there are more than 120
employees in same org unit. there are 12 supervisor in org who are approving the leaves but
unable to see the team in mss. without making chief position within the same department . If i
do this configuration than what is the impact on other structure which are working fine.
Like (0)

Sai Balaji Apr 7, 2015 6:57 PM

Hi,

o
o

Much useful blog. I have couple of questions:

will patching or upgrading the system, overwrite these changes? Because, I presume
that we are modifying few standard objects.
What impact would this have on the 'Chief' positions? Will they continue to see their
reporting structure?
I know this is not the correct place to post questions, will create a thread so that you can
feedback there.
Thanks,
Sai