Error when applying leaves through ESS.

Hi experts,
I've a problem which I'm not sure if it's a problem of customizing or maybe a note not applied. I've searched in the forum and the solution is not working, could you please help me?
We have a mass save absences button from ESS which creates absences for infotype 2001 for all the employees selected. If you create a massive absences for employees in the same personnal group no error is displayed, but if you create a massive absence for mixed employees, it returns the following error: "HRTIM00REC 006 Attendance/absence type ENEM requires minimum of 1"
Does anybody know why? Could you please help me?
Thank you so much in advance for your help.
Regards,
Rebeca

Dear all,
First of all thanks for your support
I've been checking and yes, I have that the Absence ENEM is at minimum 1 and maximum 999. That absence doesn't have quota (because it is for illness) so this couldn't be the problem. Also I have seen that if I select in the portal all the employees for the same group, the absence is saved correctly, but when I saved for different group, it generates an error. I will explain with an example
employee: 2222 -> Personnel group 01
Employee: 3333 -> personnel group 01
Employee: 4444 -> Personnel group 02
Employee: 5555 -> Personnel group 01
Employee: 6666 -> Personnel group 01
If I create a massive absence for all the employees above, the absence will be created correctly for the first 3 ones, but the fourth and the fifth will return an error.
Do you know why?
Thanks again for your support.

Similar Messages

Error while applying leave through ESS

Hi All,
In portal Employee is unable to apply any leave. The system is giving the error message as
"As per policy, Casual Leave cannot be taken for more than 1 working day consecutively,
Please utilise Privilege leave for this purpose. In case you do not have Sufficient PL balance, Please apply for LOA."
But when trying to raise a "Privilege/ Sick" leave , he is still getting the same message.
So he is not able to raise any kind of leave.
So can anyone please suggest a solution.
Regards,
Muni.

If the issue is with 2-3 users. Then either its data or authorization issue. Do on thing after performing the same application execute SU53 and ST22 transaction. If there issue with authorization or data then you can find out it from here.
Regards,
Sandip

Employee is trying to apply leave through ESS

When an employee is trying to apply leave through ESS he is getting a error message. below is the error " employee 00000000 has no valid organization assignment for 27.08.2010". we have checked all the configurations in SAP back end.

Navigate to t.code HRUSER and see the assignment.
This should resolve the issue.
Cheers-
Pramod

WSR not found while apply leave in ESS

Dear SAP Gurus,
We changed the holiday calendar for some PSA.
In the new calendar, some of the unused WSR for the PSA is removed.
(e.g. Remove a Shop WSR in a Office PSA with Office Calendar)
In this change, we find that some personnel have wrong WSR, so we corrected the personnel records too.
(e.g. A office staff with shop WSR)
After this change there are a few records with WSRwhich do not exists in the current holiday calendar setting, but all of them are in the pass.
(e.g. The Shop WSR, becuase it is the Office Calendar)
But we found that some of these staff will have a error because ESS try to locate the removed WSR while apply leave in ESS, but most of them do not have problem at all.
I think for some reason ESS need to access the WSR in the pass, but I am not sure what it is and I have no right to check the live personnel data too.
So, I would like to know what's the possible cause, so I can tell the user to check.
Thanks in advance.
Regards
Bill

Hi Vamshi,
Thanks for the reply.
Already generate the WSR for the new holiday calendar.
I think the problem is for some reason, ESS required to access the old WSR which do not exists in the new holiday calendar, but I don't know how to find this out because I have no right to read the personnel data in the production environment.
Regards
Bill

Error when applying a XSLT transformation: No valid XSLT pro

Dear All,
I am getting following error when opening the "General Supplier Data" from Pre-Select Supplier.
Error Message: "Error message: Error when applying a XSLT transformation: No valid XSLT program supplied"
I have already read the related threads on SDN and checked the SAP Note 883896 and others. Even tried running the program UXS_DEL_NAVIGATION_NODE and UXS_ADD_MISSING_XSLT_NAME. But not able to solve the issue.
Kindly Help.
Regards,
Sagar

Hi Masa,
Thanks for reply. I have checked this note. As note suggests, S_DEVELOP auth object is assigned to the user. and it has value *.
Do I need to check anything else?
Regards,
Sagar

Error when applying a XSLT transformation

central instance
transaction SURVEY
Extras->Target Group Hierarchy-> Import from file
select file
Error when applying a XSLT transformation
dialog instance working

Hello Andrey Kuryanov,
Could make sure you describe the problem more clear as much as you can so that community can help you better.
Please provide more details with more detailed steps and actual error messge.
Thanks
Raja Pamireddy
Moderator

Error when executing DBMS_ERRLOG through Stored Procedures...

Hi,
We have TWO schemas like IDWH_ODS and IDWH_ERR running on Oracle 10g Rel.2.
The schema IDWH_ERR has direct SELECT privilege on all the base tables in IDWH_ODS schema. (As Pl/sql doesn't support ROLE, we have granted direct SELECT on each of the tables)
IDWH_ODS schema has tables like ACCOUNT & CUSTOMER, for which I need to create DML Error logging tables in IDWH_ERR schema.
I have one procedure 'Cr_Errlog_Tabs' in IDWH_ERR schema which gets all tables in IDWH_ODS and creates Error logging table in IDWH_ERR schema using DBMS_ERRLOG package. My problem starts here,
When I execute the DBMS_ERRLOG package in IDWH_ERR through SQL*Plus LIKE,
> exec DBMS_ERRLOG.CREATE_ERROR_LOG('idwh_ods.ACCOUNT','ERR$_ACCOUNT','idwh_err');
it's creating the error log table 'ERR$_ACCOUNT' in IDWH_ERR schema.
(...the same will be working when execute through Anonymous plsql block)
BUT, when i execute the DBMS_ERRLOG package with same parameters through the stored Procedure 'Cr_Errlog_Tabs', it throws the following error...
ORA-01031: insufficient privileges
Please let me know how the solution at the earliest.

WHY DO YOU FEEL YOU HAVE TO START A NEW THREAD FOR YOUR PROBLEM!?
Insufficient priv error when executing DBMS_ERRLOG through PLSQL

Error when applying patch 3171663(11.5.9 CU2 )..

hi..
error when applying patch 3171663(11.5.9 CU2 )
below error in log file:
Assigned: file mscplan.odf on worker 1 for product msc username MSC.
Time is: Sat May 22 2010 21:58:03
FAILED: file mscplan.odf on worker 1 for product msc username MSC.
Time is: Sat May 22 2010 21:58:04
ATTENTION: All workers either have failed or are waiting:
FAILED: file mscplan.odf on worker 1.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.
below error in workerlog.. in adworker1
===============================================================================
The table is missing the index MSC_TRADING_PARTNERS_U2
or index MSC_TRADING_PARTNERS_U2 exists on another table.
Create it with the statement:
Start time for statement below is: Sat May 22 2010 21:58:04
CREATE UNIQUE INDEX MSC.MSC_TRADING_PARTNERS_U2 ON MSC.MSC_TRADING_PARTNERS
(SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID) LOGGING STORAGE
(INITIAL 4K NEXT 40K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0
FREELIST GROUPS 4 FREELISTS 4 ) PCTFREE 10 INITRANS 11 MAXTRANS 255
COMPUTE STATISTICS TABLESPACE MSCX
Statement executed.
AD Worker error:
The index cannot be created as the table has duplicate keys.
Use the following SQL statement to identify the duplicate keys:
SELECT SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID, count(*)
FROM MSC.MSC_TRADING_PARTNERS
GROUP BY SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID
HAVING count(*)>1
AD Worker error:
Unable to compare or correct tables or indexes or keys
because of the error above
Time when worker failed: Sat May 22 2010 21:58:04
====================================================================
My application version :11.5.9
my database version 8.1.7.4
Regards
Jaffer Ali

>
Use the following SQL statement to identify the duplicate keys:
SELECT SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID, count(*)
FROM MSC.MSC_TRADING_PARTNERS
GROUP BY SR_INSTANCE_ID, SR_TP_ID, PARTNER_TYPE, COMPANY_ID
HAVING count(*)>1
>
Pl post the output of the above statement
HTH
Srini

Error when applying opatch

Recently upgraded from Oracle 10.2.0.1 to 10.2.0.5 & since then i cant run OEM, so oracle suggested Apply Patch 8350262 to your Oracle Home installation using OPatch.
OS : Windows 2003 32 bit
DB : Oracle 10.2.0.5
I get below error when apply opatch.
C:\oracle\product\10.2.0\db_1\OPatch>opatch apply 8350262
Invoking OPatch 10.2.0.4.9
Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : C:\oracle\product\10.2.0\db_1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 10.2.0.4.9
OUI version : 10.2.0.5.0
OUI location : C:\oracle\product\10.2.0\db_1\oui
Log file location : C:\oracle\product\10.2.0\db_1\cfgtoollogs\opatch\opatch2013-
01-02_23-02-41PM.log
Patch history file: C:\oracle\product\10.2.0\db_1\cfgtoollogs\opatch\opatch_hist
ory.txt
ApplySession applying interim patch '8350262' to OH 'C:\oracle\product\10.2.0\db
_1'
Running prerequisite checks...
Prerequisite check "CheckApplicable" failed.
The details are:
Patch 8350262: Required component(s) missing : [ oracle.sysman.agent.core, 10.2.
0.4.0a, higher version 10.2.0.5.0a found. ]
ApplySession failed during prerequisite checks: Prerequisite check "CheckApplica
ble" failed.
System intact, OPatch will not attempt to restore the system
OPatch failed with error code = 74
C:\oracle\product\10.2.0\db_1\OPatch>
Any help would be appreciated.
Thanks,
Vikhar

Do you mean this "The patch is also included in 10.2.0.5 database patch 5 and 10.2.0.5.3 (PSU3)" which is quoted in (DOC ID 1222603.1), if so, i have downloaded. However, can you give me patch # for 10.2.0.5 version in order to double check , may be by mistake i download wrong version.
Thank you,

HELP: Keep Getting Error When Applying Magic Bullet Looks

get this error when applying Looks.
"After Effects error: crash occurred while invoking effect plug-in "Looks".
and then it says
"After Effects error: Crash in progress. Last logged message was: <2280>
<MCExportInfo: Destruct> <5> Destruct for 420462944"
I try to apply Looks to another video and I get a different error saying language registry key. I apply Looks to a third video and I get the dynamiclink error. It's like different error for different video. All 3 videos shot with different cameras.

Same problem here ! I have Vista 64 bit and Intel 4500 Mhd
driver. The issue is Magic Bullet Misfire works fine in Adobe After
Effects CS5 but it crashes with Magic Bullet Looks.
Have checked OpenGL in AE CS5 which are by default OFF, that is if you open Adobe After Effects CS5 and into edit and then click 'preferences'. Under previews there is ur OpenGL info. Click OpenGL, its says need to update driver or get a better OpenGL above 2.0. I think updating to new OpenGL may fix the issue. I have made a video with Magic Bullet Misfire and it works fine but the issue is with only 'Magic Bullet Looks' presets where the AE crashes.
So it cant be Windows 7, Vista or 32 bit or 64 bit issue. Probably a driver error or an internal Magic Bullet 1.4 or Adobe After Effects CS5 64 bit error.

Issue in ESS i.e. gives dump error while availing a leave through ESS

Hi All,
In My client place, system gives a dump error when employee is maintaining its leave in ESS system.Here TM is not integrated with payroll.
Plz help me how to resolve the issue.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:862)
     at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:259)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:104)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:842)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1072)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:782)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Error while applying leave request though poratl

Hi All,
In portal Employee is unable to apply any leave. The system is giving the error message as
"As per policy, Casual Leave cannot be taken for more than 1 working day consecutively,
Please utilise Privilege leave for this purpose. In case you do not have Sufficient PL balance, Please apply for LOA."
But when trying to raise a "Privilege/ Sick" leave , he is still getting the same message.
So he is not able to raise any kind of leave.
So can anyone please suggest a solution.
Regards,
Muni.

Hi Binu,
It is a Std error which you r getting in the system while maintaining EL on that day. Is 07.03.2012 is a paid holiday ?? Then it will give the same error while applying the leave on that day...
You need to check the Holiday class for that abs type in the system.
Regards,
Prasad Lad

Error when creating project for ESS

I am getting the folowing error when creating a project in Dev Studio for the ESS leave application ess~lea. Pls help
Failed to sync DC "sap.com/ess/lea(sap.com_SAP_ESS_1)" in configuration "JDI_XSSTrack_D". File "C:\Documents and Settings\User\.dtc\0\DCs\sap.com\ess\lea\_comp\.dcdef" does not exist locally after sync but it exists on the serve
Regds
Thirur

Uninstalled and reinstalled the dev studio. Now it works.

500 internal server error when using attendance in ESS

Hi All,
when the user clicks on attendance & its related activities in ESS, the following error is displaying frequently and after sometime it is working properly. why it is giving error frequently and how to avoid this error permanently?
Related Activities
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
... 69 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:12:34[UTC], changelist=421181, host=pwdfm101), build date: Tue Oct 16 13:15:01 BST 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Session & Other
Session Locale en_GB
Time of Failure Thu Jan 24 11:58:41 GMT 2008 (Java Time: 1201175921417)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:52:59[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0010.20061002105236.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:53:17[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:58:51[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0010.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:50:36[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0010.20061002110156.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:55:32[UTC], changelist=419397, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
SapWebDynproGenerationCore 7.0010.20061002110128.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:59:00[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0010.20061016112122.0000 (release=645_VAL_REL, buildtime=2006-10-21:16:19:13[UTC], changelist=421181, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to read deployment descriptor.
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:297)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.getPart(AbstractDeployableObject.java:214)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObjectPart(DeployableObjectFactory.java:113)
at com.sap.tc.webdynpro.services.sal.deployment.api.WDDeployableObject.getDeployableObjectPart(WDDeployableObject.java:62)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:921)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createVACComponentUsage(FPMComponent.java:745)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:562)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to find deployment descriptor '.\temp\webdynpro\public\sap.com\msseeproarchiveddocuments\webdynpro\portalapp.xml' on the file system. Please check if the application 'sap.com/msseeproarchiveddocuments' is deployed correctly.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:278)
at com.sap.tc.webdynpro.serverimpl.core.deployment.AbstractDeployableObject.initializeDeployableObjectParts(AbstractDeployableObject.java:259)
... 58 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Unexpected IO exception on GET<sap.com/msseeproarchiveddocuments>
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:209)
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeploymentDescriptor(WebDynproRuntimeServiceImpl.java:354)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.getDeploymentDescriptor(DeployableObject.java:274)
... 59 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
at com.sap.engine.services.webdynpro.PApplication.load(PApplication.java:142)
at com.sap.engine.services.webdynpro.WebDynproContainer.getDeployableObject(WebDynproContainer.java:204)
... 61 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 0, 0, 0(:main:, row:1, col:3)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
... 65 more
Thanks in advance,
v

Hi,
We were also having the same problem; but we couldnt find a specific solution for that problem.
But when we upgraded the ESS support packages to SP13 for some other reason this issue was also got resolved.
May be helpful i guess.
Regards,
Vijay

Error when displaying OrgChart in ESS

Hi ALL
One of our employee is getting error "500   Internal Server Error" when he trying to display the OrgChart in ESS.
Please find below the exception :
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Invalid personnel number
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
     at com.sap.xss.hr.org.FcOrgBusinessLogic.getOrgChart(FcOrgBusinessLogic.java:248)
     at com.sap.xss.hr.org.wdp.InternalFcOrgBusinessLogic.getOrgChart(InternalFcOrgBusinessLogic.java:368)
     at com.sap.xss.hr.org.FcOrgBusinessLogicInterface.getOrgChart(FcOrgBusinessLogicInterface.java:128)
     at com.sap.xss.hr.org.wdp.InternalFcOrgBusinessLogicInterface.getOrgChart(InternalFcOrgBusinessLogicInterface.java:178)
     at com.sap.xss.hr.org.wdp.InternalFcOrgBusinessLogicInterface$External.getOrgChart(InternalFcOrgBusinessLogicInterface.java:247)
     at com.sap.xss.hr.org.chart.VcOrgChart.getOrgChart(VcOrgChart.java:202)
     at com.sap.xss.hr.org.chart.wdp.InternalVcOrgChart.getOrgChart(InternalVcOrgChart.java:207)
     at com.sap.xss.hr.org.chart.Orgchart.wdDoInit(Orgchart.java:100)
     at com.sap.xss.hr.org.chart.wdp.InternalOrgchart.wdDoInit(InternalOrgchart.java:216)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:793)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Have anyone come across similar issue . Please do let me know if any thing needs to be checked .
Any help is highly appreciated
Thanks in Advacne
BR
VN
Edited by: vishal_nam on Jul 25, 2011 1:29 PM

The issue was actually with OM. The problem was that the position was not connected to any org unit.
The functional consultant was able to fix it.
Thanks for your replies .
BR
VN

Error when applying leaves through ESS.

Similar Messages

Maybe you are looking for