on 01-05-2015 6:29 AM
Guys.,
Finally Sorted it out by Dragging Leave Request (URL) to Inactive Applications and Dropping Webdynpro based Leave Request application to Main applications.
I just swapped the positions of both Leave request as shown in figure. It worked out !!
Learnt bit of Portal being HCM Functional. A good break-through
Closing this thread !!
Thanks,
Niladri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
did u assign "EVERYONE " role for this user in portal or else give everyone role for this user in portal and try again from user admin ask portal guy to give everyone role for this user and check once ,....u have to assign ESS ROLE And Everyone for employees and for managers u need to assign ess and mss and everyone role ... and ensure 105 0001 subtype is properly assigned for that user ...check once
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Siddharth,
Today I've checked logs and traces as mentioned. There are so many line items for this error . For one of these error providing screen shot. It seems error related to system alias . Trying to resolve myself if I can , otherwise I need to go to Netweaver guy as we are in Realization phase and traces are from Test client linked to DEV server.
Regards,
Niladri
HI Niladri,
The is issue is with the permission of the system objects, From the logs i can see both the SAP_ECC_HumanResource and SAp_HCM_Proxy system objects are not assigned to the user.
Take the help of the portal consultant and ask him to assign Read permissions for the above system objects , if the above system objects are not available in the system landscape in portal create the system alias to the system which is connecting to the backend system.
Please share your system landscape screenshot in the portal
let me know if anything required.
HI NIladri,
Can you please ask the portal guy what error message he is getting the NWA and paste the screenshot here.
We can't analyze the issue with the above screenshot,there could several reasons for the portal runtime error in the portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Niladri,
If above is the issue then you need to assign the portal id to the backend pernr in the Communication info type (0105).
Check the below link which is having same kind of problem and solved after mapping
http://scn.sap.com/thread/3557022
In the above link you can see the steps to assign the employee to the pernr.
Let me know if anything required
Reproduce the error and then login to the portal using nwa like http://portal:50000/nwa -->trouble shooting-->logs and Traces-->Log viewer-->VIew-->developer view and check the error message their.
Take the help of portal guy to get the developer trace
User | Count |
---|---|
88 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.