Error while applying ESS Leave Request in Portal

Hi,
I configured ESS in EP and i'am trying to apply a leave.I'am using the Workflow "WS12300111",i also assigned Agents to the WF.But when i try to apply a leave from EP it is giving me this error
"Unable to send the request"
"You are not one of the possible agents of task WS12300111"
In agent assignment of WF i had given the approver name in the Approval Process step but i dnt know why it is saying that you are not the possible agent, for a person who is applying for a leave.
Please guide me with a solution.
With Regards,
Pardeep.B

Hi,
I Solved my Problem.Actually in WF WS12300111 in Header agent assignment is not set to General task.Now i made it to general task and it solved my problem

Similar Messages

BSP error while applying a Leave request in ESS

Dear Friends,
Reposting an issue which I posted earlier in ESS Forum as I didn't get solution there and the issue is more technical and moved towards Netweaver applications.
While applying a leave request in ESS portal, I am getting an error page saying Business Server Page error.
Checked related SPRO Nodes: Both ESS UI5 and ESS (Java) nodes. They are maintained. Being HCM Functional Consultant, this error I am not able to analyze anyway. So asking Portal /Netweaver experts here.
Error screen attached-
My earlier thread posted in ESS forum
http://scn.sap.com/thread/3675714
Expecting a quick solution for this as I am stuck in this issue for last 4-5 days .
Regards,
Niladri

Sorted out . Detail can be seen in the Referal link. Closing this thread
Regards,
Niladri

Error while accessing ESS Loan Request.

Hi Experts,
While accessing ESS Loan request for Country grouping 40 India am getting below mentioned error saying that 500 Internal Server Error.
I have maintained the settings for Leave request and maintained Infotype 45 Loans for employee.
But it is giving the below mentioned error.
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
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.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 74 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
Version null
DOM version null
Client Type msie8
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.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:28:44[UTC], changelist=91834, host=pwdfm256), build date: Fri Feb 11 16:31:03 IST 2011
J2EE Engine 7.02 PatchLevel 91789.
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_28-b03, vendor: Sun Microsystems Inc.
Operating system Windows Server 2008 R2, version: 6.1, architecture: amd64
Session & Other
Session Locale en_US
Time of Failure Fri Feb 18 11:17:24 IST 2011 (Java Time: 1298008044828)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:36[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0205.20100813133727.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:18:40[UTC], changelist=91776, host=PWDFM256.wdf.sap.corp)
SapGenerationFrameworkCore 7.0205.20100813133737.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:08:53[UTC], changelist=91781, host=PWDFM256.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:53[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
SapMetamodelCommon 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:28[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
SapMetamodelCore 7.0205.20100813133815.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:09:25[UTC], changelist=91800, host=PWDFM256.wdf.sap.corp)
SapMetamodelDictionary 7.0205.20100813133729.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:16:20[UTC], changelist=91777, host=PWDFM256.wdf.sap.corp)
SapMetamodelWebDynpro 7.0205.20100813133929.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:20:37[UTC], changelist=91833, host=PWDFM256.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
SapWebDynproGenerationCore 7.0205.20100813133926.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:22:57[UTC], changelist=91832, host=PWDFM256.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0205.20100813133935.0000 (release=NW702_05_REL, buildtime=2010-09-13:15:30:09[UTC], changelist=91834, host=pwdfm256)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.model.loan.types.Extdl could not be loaded: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:268)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:231)
     at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
     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.createBLCComponentUsage(FPMComponent.java:761)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.ess.in.loan.overview.VcOverviewESS.onInit(VcOverviewESS.java:244)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESS.onInit(InternalVcOverviewESS.java:611)
     at com.sap.ess.in.loan.overview.VcOverviewESSInterface.onInit(VcOverviewESSInterface.java:162)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface.onInit(InternalVcOverviewESSInterface.java:144)
     at com.sap.ess.in.loan.overview.wdp.InternalVcOverviewESSInterface$External.onInit(InternalVcOverviewESSInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     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:783)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
     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:876)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1355)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:357)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:597)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:870)
     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)
Caused by: com.sap.dictionary.runtime.DdException: Type com.sap.model.loan.types.Extdl does not exist
     at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
     at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:596)
     at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:296)
     at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:94)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
     at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:260)
     ... 72 more
Please suggest me the solution for this.
Regards,
Ksanj.

Please   check that the ESS/ERP packages fit together according to
the page
https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACK+
MISMATCH+ISSUES
Please check again the componentinfo and the SPlevels of the testlandsca
pe, that the same level is used on the prod landscape.
So ensure you are on correct levels!

Error - While changing existing leave request from ESS

We are trying to use the standard leave request application in ESS/MSS. The basic required standard configurations are done. Since we wanted custom notifications, the related workflow is copied into custom workflow and we have included required custom notifications. The custom workflow is also configured properly.
Now, the standard functionalities like making leave request, triggering notifications, approving leave request and posting information into backend are working fine from the ESS/MSS.
When the employee tries to change the existing leave request (before approval) from ESS, at the 2nd step (Review and Send), it is displaying one error message General task: can be edited by all users. But, it still allows submitting the records.
Once it is submitted, the system throws one java error at the final step (after pressing SEND button) u2013 Failed to process request. Please contact your system administrator. - java.lang.NullPointerException. The complete error information is provided in the attached word document. Even though, it throws error the submitted data is getting saved into the backend.
Please help to solve this issue.
Thanks,
Prabhu
Edited by: Prabhu T on May 18, 2011 1:53 PM
Edited by: Prabhu T on May 18, 2011 1:54 PM

What custom notifications you require in leave request? We have all available in standard using Rptarqemail
First of all, the WF task should be set as
General task: can be edited by all users, which you have done presumably under task classification
Now, for checking purposes, can you check with standard WF in table v_t554s_web for one absence only?
ie WS12300111.
Please test this and let us know if you have errors
Also please check your custom WF whether it is working correctly or not?

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

Portal - ESS error in Wroking time-- Leave request.

Hello Masters in ESS/EP,
I am getting the following error in EP for Leave request in Working time:-
com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcForm.Orig_Request.Item_to_Check_Orig): structure field Umskd not found
Are there any settings needed to be done in R/3 or EP or in PTARQ related to leave request activation. Kindly let me know. Its urgent!!!!!!!!!!!!!!!!!
Thanks ,
Gaurav J.

Hello all,
we solved this issue with applying the following patch:
Patch for SAP ESS 600 Support Package 11
which you can download from SAP Service Marketplace at:
-> [Support Packages and Patches|http://service.sap.com/patches]
     -> SAP Application Components
          -> SAP ERP
               -> SAP ERP 2005
                    -> Entry by Component
                         -> SAP XSS (Self Services)
                              -> SAP ESS 600
                                   -> #OS independent
We also applied Patch for SAP PCUI_GP 600 Support Package 11.
-> [Support Packages and Patches|http://service.sap.com/patches]
     -> SAP Application Components
          -> SAP ERP
               -> SAP ERP 2005
                    -> Entry by Component
                         -> SAP XSS (Self Services)
                              -> SAP PCUI_GP 600
                                   -> #OS independent
After applying those two patches everything was fine.
Regards, Michael

ESS Leave Request - Error while creating a leave record

Hi Friends,
Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.

May be
Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post.

Error after second level approval in ESS leave request

Hi Experts
I am using custom workflow for Ess Leave request process which is copied from WS21500001.
I have added custom class methods to change status from approved to sent.
Then another method i have set next appovaer.
The problem i m facing is that I am getting an error on portal after second approval approves the request.
i.e Field syomol has not been assigned yet.
from st22 i found its generating from
Include LPT_ARQ_REQUEST_UIAF06 - Form   execute_approver_update
By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
This results in unassigned field symbol. and then error.
Please help me resolve this issue.
Please confirm why next approver is not found in method.

Hi All
Thanks for your reply.
I checked why it was giving a dump.
This execute_approver_update subroutine takes approval data from table ptreq_approver .
I filled this with resp actor id after request is approved and status is changed to sent.
For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
   SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
    wa_appr-mandt = sy-mandt.
    wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
    wa_appr-version_no = version_no. "Req.Version ( from Workflow )
    wa_appr-seqnr = seqnr. "Same as version no but in char
    wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
    wa_appr-status = 'T'. "Manual
    append wa_appr to it_appr.
    INSERT PTREQ_APPROVER FROM TABLE it_appr .
    commit work and wait.
This resolved my issue.
Thanks

Team Calendar in ESS Leave Request (Error)

Hello,
we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
java.lang.Exception: No Views found: Missing customizing
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
     at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
     at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
I have maintained the Customzing in IMG for Team Calendar as the following:
00000001     SAP Standard     01.01.1800     31.12.1999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Attendance Overview     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Administrator Mode     View Group (MSS)
00000001     SAP Standard     01.01.1800     31.12.1999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.1999     Team View Mode     View Group (MSS)
Would you please help?
Many Thanks and Regards,
Nazih

Hi Bryan,
1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note 704604)
2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
a. Tcode: PTARQ -> Customizing
b. Working Time -> Team Calendar
c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
Example.
00000001     SAP Standard     01     0100     Leave     01.01.1800     31.12.9999
f. Node Select Employee -->
Here you need to set the Group of your Employee which should be displayed in the team calendar:
Example.
00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     MSS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     CATS Approval     View Group (MSS)     MSS_LCA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Attendance Overview     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
00000001     SAP Standard     01.01.1800     31.12.9999     Request Mode     View Group (MSS)     ESS_LEA_EE
00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     MSS_LEA_EE     PPOME_P
---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
Regards,
Nazih

ESS leave request workflow WS04200009...error-u r not one of the possible a

hi all
i m working on ESS leave request workflow WS04200009....but when i create a leave request from user's A/c i got an error at that leave req create screen that's-- u r not one of the possible agent of the task...
pls do help if anyone no solution.
thanks in advance .
Raj

Try making this task a General Task..use tcode PFTC and change the attribute of this task to a general task. That might help solve the issue.

ESS Leave request - Agent selection @ &Agent_0001.Agents&

Hi,
when i apply a leave request from ESS it triggers workflow WS12300111. In the agent selection of the task TS12300097 use the expression &Agent_0001.Agents& to send the work item to UWL. I just want to know where this container is populated from.
The container BOR of AAGENT has &Agent_0001.Agents& to send the workitem.
Please clarify.
Thanks!
Richard A

Ok. I will try to clarify it. Try the following,
Goto PFTC -> Choose "Workflow Template" from the drop down -> Enter the workflow template id "12300111" in the text box -> now click on "change" button -> Now goto the menu addional data -> agent assignment -> maintain -> select the task text -> and set it as general task.
I guess you have done the same for the standard task TS12300097 but failed to do it for the workflow template (WS12300111). Or have you done it already?
I hope this shud be the problem as you have problem in initiating the workflow and not while approving the workflow.
Also once you make this change "Refresh your buffers" once before checking it out.
Thanks,
Prasath N

ESS Leave request workflow : ws12300111 : Customizing

Dear experts,
I need to customoze ESS leave request workflow WS12300111.
Can you please tell me do I need to Copy this to a NEW workflow generating a new WF no or can I simply generate a new version for this only ? What is ideal ?
1. Can anyone tell me step by step process(config) in ESS leave application workflow?.(SWFVISU????)
2. Is workflow WS12300111, the only workflow that I need to look for leave application ?.
3. If it is WS12300111 I dont see any start event for this workflow. So how is it getting triggered?
4. For the approval task TS12300097, agent determination is done by expression &Agent_0001.Agents&. How does it interact with Org.Structure.
5. In my scenario, approver should be supervisor of the employee applying for leave. If it is pending with this approver for 5 days it should go to the next up level manager.
For identifying first level approver is &Agent_0001.Agents& enough.? For identifying 2nd level approval do I need to write a rule ?
Kindly help.

Hi Sourav,
Try this step by step process(config) in ESS leave application workflow.
ESS Scenario
Workflow Process 20000081 u2013 Create Leave Request with HTML
Steps for triggering the workflow:
1) The employee logs with his user name in the ESS web page.
2) The employee creates a leave request with an optional note and sends it to the appropriate approver (usually his supervisor). The approveru2019s name is automatically displayed in the leave request form and the employee can replace him with another if such a change is needed.
3) The approver (us approver) logs on to sap system or to ESS
web pages and reads his mails in the SAP Business Workplace. The employeeu2019s leave request form appears in the workflow inbox with approve and reject options.
A) If the us approver approves the leave request, he pushes the
button approve from his mailbox (processing status A with
approve). A screen is appeared with a box (Table entry: 0001)
and the approver must push the button continue in order that
the workflow is continued. Then the form is sent to the
employeeu2019s mailbox in Sap. When the employee opens his mails, he receives a note in his inbox that u201Cthe absence from u2026. To u2026..has been approved byu2026.u201D.After that the absence is
automatically created in the sap system. Then the approver gets a mail (notification of completion & Return u2026u2026).
B) When the approver cancels a leave request, he pushes the
button reject and the processing status changes to u201CRu201D.
Then the same form appears
Realative OSS Notes:588262, 480103, 717560, 452841, 359197, 321439, 428394, 321439, 693368, 451998 (ITS), 197746 (ITS), 419297 (ITS)
ITS - ESS stand-alone solution for 4.7
This solution allows customers to schedule the 4.6C or 470
install / upgrade independently from the Enterprise Portal or
mySAP Workplace implementation and will be supported at least as long as SAP R/3 4.6C and R/3 Enterprise is supported.
This ESS stand-alone menu is intended solely to allow independent scheduling of the 4.6C or 470 upgrade and the Enterprise Portal / mySAP Workplace installation. To use this solution, you have to take the following steps:
1. If you do not already have R/3 4.6C, HR support package 8,
please import HR support packages to at least this level. From
HR support package 8 and above, the correct services are
implemented. For 470, the corresponding recommended HR SP is 16 (See note 621589)
2. Verify that the ITS you want to use does not contain a service or service-related files (HTML templates, MIME files) for the services PZLE, PZM3 or PZM3_start. If you find these files,
delete them.
3. Publish the services PZLE, PZM3 and PZM3_start from your R/3 4.6C system (or R/3 470 system whichever is the case) to your ITS using the SAP@Web Studio or the IACOR service.
4. Maintain the username-employeenumber assignment in your system by customizing Infotype 0105, Subtype 0001 of those employees, who should be able to use ESS.
5. Verify that your users have proper authorizations for
executing RFCs (that is, authorization object S_RFC) from the
function group EH08. If you run into problems, this is most
likely due to missing RFC authorizations to start the service
PZM3.
6. Your users should now be able to access ESS by starting the service PZM3. They can do this by entering a URL like
http://<ITS server>:<http port>/scripts/wgate/pzm3/!
(the ! at the end is essential).
7. ESS 4.70 Unicode System ITS 6.10 patch level 29 and above (With IE and Netscape). ITS 6.20, patch level 6 and above (With IE only).
The ESS development tested these ITS versions.
8. For Release 4.6C, ESS has the same browser requirements as the HTML (see also note 178788) and the mySAP Workplace 2.11 (if ESS is accessed through the mySAP Workplace 2.11).
Hope it helps.Do award points if found helpful.
Regards,
Gourav

ESS Leave Request Data

Hi All,
While applying Leave Request in ESS used(Quota) value is coming 0.25 Days, But in ECC value is 0.50 Days. Please check below screen shots.
Please suggest how to solve this.
Regards,
Venkat.

HI Venkat,
In the ESS the start time and end time is been entered so the value is 0.25 , enter the timings(7.30 t0 11.49) in ECC too and check the quota used.
I hope the ESS leave request is just replica of the 2001 infotype so it must behave the same keeping in mind you are checking for the same absence type .
Regards,
Mithun K

ESS: Leave Request - How to use a custom Leave Workflow?

Hi Experts,
I am implementing ESS 1.0 for mySAP ERP05. I have a custom workflow for Leave Request which I want to use for the ESS Leave Request. Can someone tell me what are the configuration steps required for this?
I have already performed the following activity:
SPRO --> Personnel Information --> ESS --> Service Specific Settings --> Working Time --> Leave Request --> Specify Processing Processes for Types of Leave
Here I have defined the WF ID of New Request as the custom Workflow ID.
Now when I trigger the Leave Request from EP-ESS, the message comes that the request was sent successfully.
But in the backend no workflow gets triggered. I even tried to write an implementation for the BADI PT_ABS_REQ to trigger the custom workflow event, but still no activity in the ECC workflow upon submitting thwe portal request.
Can some one please advise.
Thanks,
Shobhit

Ohh.. So the standard WF also doesnt get triggered??
Are you sure u have done SWU3 config??
If u have, Try using SWU_OBUF to refersh the workflow buffer.
Try swi1 to check what is happening with ur WF.
Try login to requesters login ... SBWP ... check the outbox. Is there a WF with Error here.
Cheers!!
Ashutosh

Oracle Security Patch Error while applying --The filename, directory name,

Hello,
I am running into strange error while applying Oracle Security Patch 68 by using Opatch.
Supposedly, All the environment variables are set properly.
ACTIVE_STATE_PERL=true
DBMS_TYPE=ORA
dbs_ora_tnsname=YBQ
JAVA_HOME=C:\jdk1.3.1_10
OPATCH_DEBUG=TRUE
ORACLE_HOME=E:\oracle\ora92
ORACLE_SID=YBQ
Path=E:\oracle\OPatch;C:\jdk1.3.1_10\bin;E:\oracle\Perl\bin;E:\oracle\ora92\jre\1.4.2\bin\client;E:\oracle\ora92\jre\1.4.2\bin;E:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\Common Files\VERITAS Shared;\NetBackup\bin;C:\Program Files\Windows Resource Kits\Tools\;C:\Program Files\Support Tools\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;E:\usr\sap\YBQ\SYS\exe\run
Installed Active Perl. latest version
downloaded Opatch 1.0.0.50
and the patch number 3738339
I went to that directory and run the command :
perl opatch.pl apply
It started of well.
OPatch version is: 1.0.0.0.50
Using ORACLE_HOME/oui to look up oui libs...
Oracle Home = E:\oracle\ora92
Location of Oracle Inventory = E:\oracle\ora92\inventory
Oracle Universal Installer shared library = E:\oracle\ora92\oui\lib\win32\oraInstaller.dll
Path to Java = "E:\oracle\ora92\jre\1.4.2\bin\java.exe"
Location of Oracle Inventory Pointer = N/A
Location of Oracle Universal Installer components = E:\oracle\ora92\oui
Required Jar File under Oracle Universal Installer = jlib\OraInstaller.jar
find under OH/oui/jlib
found OraInstaller.jar
Checking if this is a RAC system...
Accessing inventory... This may take up to 300 seconds.
(retry 10 times, delay 30 seconds each time)
System Command: ""E:\oracle\ora92\jre\1.4.2\bin\java.exe" -Dopatch.retry=10 -Dopatch.delay=30 -DTRACING.ENABLED=TRUE -DTRACING.LEVEL=2 -Dopatch.debug=true -classpath "E:\oracle\ora92\oui\jlib\OraInstaller.jar;E:\oracle\ora92\oui\jlib\srvm.jar;jlib\opatch.jar;E:\oracle\ora92\oui\jlib\xmlparserv2.jar;E:\oracle\ora92\oui\jlib\share.jar;.:E:\oracle\ora92\jlib\srvm.jar" opatch/O2O "e:\oracle\ora92" "E:\oracle\ora92\oui" opatch.pl 1.0.0.0.50"
Result:
----- DEBUG is ON -------
oracle.installer.startup_location will be set to E:\oracle\ora92\oui
oracle.installer.oui_loc will be set to E:\oracle\ora92\oui
oracle.installer.scratchPath will be set to /tmp
opatch.local_node_only is OFF
retryOption is ON: 10
delayOption is ON: 30
Few more stuff here .. not pasting the entire contents
System Command: ""E:\oracle\ora92\jre\1.4.2\bin\java.exe" -Dopatch.retry=10 -Dopatch.delay=30 -DTRACING.ENABLED=TRUE -DTRACING.LEVEL=2 -Dopatch.debug=true -classpath "E:\oracle\ora92\oui\jlib\OraInstaller.jar;E:\oracle\ora92\oui\jlib\srvm.jar;jlib\opatch.jar;E:\oracle\ora92\oui\jlib\xmlparserv2.jar;E:\oracle\ora92\oui\jlib\share.jar;." opatch/CheckConflict "E:\oracle\ora92\oui" "e:\oracle\ora92" opatch.pl 1.0.0.0.50 3738339 "3741539 3528282 3516951 3622875 3668572 3371796 3239873 3356103 3543125 3666502 2800494 2824035 2964252 3617042 3320622 3571233 3253770 3492040 3566469 3354470 3625370 3583686 3150750 3617519 3635177 3597640 3749394 3542588 3698501 2954891 2918138 3559212 3518909 3412818 3430832 3172282 3358490 3637624 3458446 3179637 2810394 3668224 3609791 3566813 3475932 2338704 3412136 3388633 3540576 3571226 3575743 2690205 3240280 3509265 3177513 3575747 3811906 3554319 3752406 3323435 " E:\3738339\etc\config\actions"
Result:
opatch.pl version: 1.0.0.0.50
Copyright (c) 2001-2004 Oracle Corporation. All Rights Reserved.
The filename, directory name, or volume label syntax is incorrect.
Error in executing Java program to check conflict
ERROR: OPatch failed during pre-reqs check.
Now there is no problem with executing the last java program in the same prompt by removing the first and the last double quote "
Please advise.
Thanks in advance.

hi somnath,
this is the portal content management forum. for your database question please use the database forums:
http://forums.oracle.com/forums/index.jsp?cat=18
thanks,
christian

Error while applying ESS Leave Request in Portal

Similar Messages

Maybe you are looking for