on 05-20-2015 12:26 PM
Hi experts,
we have implemented HR Renewal 2.0 FP2. on NWBC.
In ESS/MSS we have now problems with chip 'My Info'. We doesn't seen the photo of the employee, only information of name, vacation and incomplete time recording.
If we start leave request, all work's fine. But if we start the employe Profil, there aren't any data exxept the employee number and name. If we start the organization Chart, there are a blank window without any data.
The Gateway error_log Shows error: the request URL or the metadata Definition is incorrect.
Any idea what might be the reason of this problem?
Thanks a lot!
Regards,
Claudia Janecek
Dear Siddharth,
thanks for your reply. We have almost check note 1797736 and error log, but there aren't good informations which will solve the problem.
We have implemented the odata Services: /ui2/launchpad, if we load the metadata, there aren't any errors.
If we start the request-uri: /sap/opu/odata/ui2/launchpad in sap netweaver Gateway Client, the status is ok.
If we start the request-uri (which is on error in the error log): /sap/opu/odata/ui2/launchpad/result?$skip=0&$top=10&$inlinecount=allpages the code 404 not found is displayed.
We have analysed, that the error is processed in method: /IWFND/IF_MED_MDL_SERVICES_GRP-get_entity_set.
The documantation of this method explain, that, if the entry not found, the corresponding model (metatdata) ist corrupt. Most likely caused by a coding error in the BEP meta data Provider class.
But we still have implemented the standard odata Services, not done any modifications.
Could you help here?
Thanks a lot!
Best Regards,
Claudia Janecek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
in this case, please reactive the service once again if it is corrupted and since you are using standard, best way is to rechect the services etc and whats yours EAHR version? 2131763 - Navigation from the Action Menu of the employee profile to any application is not working
1976670 - Employee Profile application fails to launch
Dear Siddharth,
we have now implemented not 2131763, which wasn't in our System. We have EAHR Version 608 SP10.
If you mean to reactive the Service with load metadata in maintain odata Service - we have executed.
But if we start now the function of ess 'my Info' -> employe Profile loading time is much more longer, like bevore we have implemented the note. If we click on employee Profile the error log in the backend is still the same!
Should I delete the Service launchpad and implemented new?
Thanks,
Claudia Janecek
Not lpd_cust. There we use also standard.
To reactive the Service: Transaction: /IWFND/MAINTAIN_SERVICE
and then 'Load Metadata'. (Service /ui2/Launchpad). Is this correct? Or how to reactive the Service once again?
In our error log the Service /ui2/launchpad is on error! Should I reactive this one? There aren't any changes in note 2131763 with this services!
It is really strange - thince I implemented the note - all application in chip 'My Info' have a really long loading time!
Thanks,
Claudia Janecek
Dear Siddharth,
now I have deimplement the note and the application is almost faster. The error in gateway is also there. I have create an http trace. What shoud I do with this trace?
We have an error in /sap/opu/odata/ui2/launchpad/results
Note 1976670 is implemented. Launchpad ess menu is ok.
Thanks for your help!
Claudia Janecek
What I have done is to clean up the model Cache and load the metadata for the the Service '/ui2/Launchpad' in TA /IWFDN/MAINT_SERVICES. It shows 'metadata was load sucessfully'!
Is that enaugh? Or is something else to do? What you mean with deactivate und reactivate again?
If I start now the application there are also the error for /ui2/Launchpad with request-URL and Metadatadefinition is wrong.
But another error is now displayed:
Error: Shared Memory: ESS:MENU:0000000005!
I get this error only one time. If I start the application once again, there is only the /ui2/launchpad error!
Regards,
Claudia Janecek
Dear Siddharth,
have follow errors if I trace the application:
http://servername/sap/opu/odata/ui2/launchpad/results/$count
=> error: 404 not found
Note 2149238 is implemented!
Thanks for reply.
Claudia Janecek
the note above 1797736 talks about gateway errors, you can download the pdf, as its general guidebook as it might be some services are not activated etc in your case and hence you see incorrect results. you can do a Http trace or developer trace using f12 too
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.