cancel
Showing results for 
Search instead for 
Did you mean: 

problem in mss - java null pointer exception

Former Member
0 Kudos

Hi,

I am facing a problem with the my team page in MSS. Whenever the user is trying to view the MSS page he is trying to view the page, he is getting a java null pointer exception.

The exact error message was :-

java.lang.NullPointerException

at com.sap.xss.hr.eeprofile.personaldata.vac.PersonalDataView.wdDoModifyView(PesonalDataView.java.138)

at com.sap.xss.hr.eeprofile.personaldata.vac.PersonalDataView.wdp.InternalPesonalDataView.wdDoModifyView(InternalPesonalDataView.java.397)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

Below is the analysis which we have done from our end.

Accordingly, first we tried to understand if any masterdata related gaps are there from HR Functional dimension. We could find that the qualifications were not maintained for the affected employeeu2019s position and there was no relationship maintained between this position and job. Later, we ruled it out since this had nothing to do with the existing issue. We have also checked for other relevant masterdata and found it to be intact.

The next step was to check from Portal u2013 ESS / MSS angle. For this, we have checked for the relevant authorizations of the user like, whether is he authorized to access the MSS page? Is he assigned a Manageru2019s role? Then we found that this information was also intact.

Later, we have checked if his password was expired. To rule out this query, we got the new password re-set with kind coordination from the authorization team. Because of this, the user was able to access from backend (SAP), but his portal issue still remained the same.

We initially analyzed it to be a JCo issue. But the issue is pertaining to only one user. Can it be possible that it is a JCO connector issue?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

I doubt it tho, that it is your JCo connection, because like you said, it happened to one user.

Can you please give us more info about your error, from nwa?

Former Member
0 Kudos

Hi ,

Do you mean the error logs? We dont have any error logs .

Former Member
0 Kudos

Hi,

I think the problem is with personal data (infotype 2 ) of one of the reportees of the manager who is trying to login. To check this

you can go to PPOME of the managers org unit, find all the reportees and then check IT2 for each of the reportees.

Srini