ESS Leave request screen giving a critical Error in production server

Friends,
We are in a critical face of ESS implemetation.
We are doing an ESS MSS implementation for country grouping 99.
When we moved our changes to production server after succesful testing in quality, getting the following Critical error for Leave Request Screen.
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:512)
     at java.util.ArrayList.get(ArrayList.java:329)
     at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:272)
     at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
     at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2543)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
Other areas like personal Info & who is who are working fine.
Leave request was working fine in Development and Quality servers and it never worked in Production server.
It worked fine with same config, with same master data and same employee & org structure in quality server.
We tried the following things:
1. Checked and confirmed the sequence of transports for configs and Developments to Quality and Production.
Even compared the table level entries and ABAP codings B/n dev and Production. All are same.
2. Moved the workflow changes to production and activated the same. No change found after that.
3. Gave SAP all authorization in R/3 and full authorization from portal side as well.
4. Assigned the userid to different employees and checked the masterdata of employees.
5. Checked the note 1388426.Every thing mentioned in the note is there in the system.
6. Verified Rule groups and WEBMO feature are correct and same as in quality.
As our go live date is very near, request your help .Thanks in advance for your help.
Regards,

Customisation of Leave request is mising in your system, please check the rule group using PTARQ.

Similar Messages

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.

In ESS-Leave Request -A critical error has occured.

In ESS when tried to enter the Leave which is under Leave request the below error occured:
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
     at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
     at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     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:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     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:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     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: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(AccessController.java:219)
     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.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
     at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 60 more

I found out the solution and solved this issue.
Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
After deleting it check in the portal for the leave request.

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

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 in Leave Request screen

Hi All,
Particular group of employess are facing problem in accessing leave request screen in the portal. They are getting the following error.
*********Error**************
"There are no customizing settings for absence type".
Please guide me in resolving this.
Thanks,
Steffler.

Hi,
Can you check if the absence is correctly maintained, also make sure absence which were available earlier are customised correctly and not delimited or removed.
Check t-code "PTARQ" .
Hope the tasks are set to "General Task"
SPRO> Time Management>Web Application>Leave Request(new)>Link Absence types and workflow templates.
Regards
Puneet

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

Add a custom button in Ess Leave Request

Hi Gurus,
I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
Thanks,
Mohammed.
Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

Hi Gurus,
I have requirement, add a custom button in a Standard ESS leave request (Webdynpro Java). When i click the the button it has to call popview(custom view). I am new to webdynpro Java, If possible explain me with step by step preocedures(if possible with screen shots).
Thanks,
Mohammed.
Moderator message: this is the wrong forum, please have a look in the "Web Dynpro Java" forum, but always search for available information before posting.
Edited by: Thomas Zloch on Jun 17, 2011 9:54 AM

In ESS- Leave request -RFC_ERROR_SYSTEM_FAILURE occurs

In ESS - Under Working TIme ->Leave request : the following error occurs.
When the employee tries to apply leave in the leave request it throws the following error message:
Create Object:The class was not found,.error key:RFC_ERROR_SYSTEM_FAILURE

In this scenario - check the work flow and if any previous error work item exist in the work flow delete it and check again to apply leave in Leave request. It will not throw any error.

Enhancement in ESS Leave Request

Hi Gurus,
I am new to webdynpro Java. I have a requirement to add a custom button in a Standard ESS leave request (Webdynpro Java) view. When i click the the button it has to call popview(not sure is it possible to call a webdynpro abap view). If possible explain me with step by step preocedures(with screen shots).
Thanks,
Mohammed

Hi,
          Good, you are now able to do modification in Standard ESS package. If you want to navigate to another WDABAP iView from your WDJAVA application, you can use the below code on some button or link action to navigate to another iView.
Check this link:-
http://help.sap.com/javadocs/NW04/current/wd/com/sap/tc/webdynpro/clientserver/navigation/api/WDPortalNavigation.html
public void onActionnavigateToToAbapiView(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionnavigateToAbapiView(ServerEvent)
     try
                    WDPortalNavigation.navigateAbsolute(
                     "ROLES://portal_content/com.demo.DEMO_PCD/com.demo.ESS_SAP/com.demo.iview_ESS/demo.com.java_demo_com_demodc_demo_com_DemoApp",
                     WDPortalNavigationMode.SHOW_INPLACE,
                     "Window Title", WDPortalNavigationHistoryMode.NO_DUPLICATIONS,
                     "Title",
                     "",//ContextURL
                     "param1=10&param2=portalID");
     catch (Exception e)
          e.printStackTrace();
You will find your WDAbap PCD location in Content Admin, copy it and repace PCD: with ROLES at start.
also you can pass parameters between 2-iViews, in the above code snippet you can find that.
the above code needs to be written in your source iView so as to navigate to destination iView which is mentioned using its PCD location.
to retrieve the parameters you need to check ABAP syntax to retrieve URL parameters.
In java we retreive using below syntax:-
String param1 = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param1");
String loginID = WDProtocolAdapter.getProtocolAdapter().getRequestObject().getParameter("param2");
to show it as a Pop-Up you need to find some work-around to achieve it, If i get time will do it and let you know, but if you find something for that do share.
Regards
Tushar Shinde.

ESS Leave Request Confirmation Link Issue

Hi
We have implemented ESS/MSS on EP7-EC6.0 system. In Leave Request application once an employee submits a leave and clicks on the confirmation link "Request Further Absence" it takes back to the intial leave request screen. But a extra label "Valid For: " comes in between the Roadmap and CAP links. I need to remove it. That label comes only if we click on the confirmation link for requesting a leave. It doesnot appear if u click on Request for leave from overview page or subarea page or from detailed navigation pane. Please help me with the issue
Renu.
Edited by: Renu Sumith on Apr 22, 2010 4:26 PM

Hi ,
Can you personlalize that link and hide that lable.
goto content admin of the page and Ctl+ right click after previewing the page.
Thanks,
Nachy

ESS - Leave Request Display Fields

Hi:
On the leave request screen in ESS, the following fields are displayed at the bottom of the screen:
Type of Leave
Date
Time
Duration
Approver
Note for Approver
Does anyone know if it is possible to hide the Time fields? If so, where are the changes made? These fields will not be used as part of our leave request process.
Regards,
Brian

Yes personalisation
or
Make sure in the counting rule you have defined this absense
Condition < 1 day? Is this checked? if not checked you ll not
see the Clock Times
ALso check the T554s customisation for the absence?
Minimum duration is given as ?
Please check the configuration of the
absence type does it allow the partial day to be booked?
ie In the Counting Rule ( T556C) can you book only full day or partial
day.
Also
Feature HRSIF had value '0'. So the system
generated clock times itself. But when you set the feature to '1' then
the probleme is solved.

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

ESS Leave request screen giving a critical Error in production server

Similar Messages

Maybe you are looking for