ESS Leave Approval: No authorization to start service

Hello,
User is not able to approve leave requests of sub-ordinates.
When user clicks on Approve or Reject button, nothing happens.
But when I checked in Default trace, I found below error:
You do not have the authorization to start service
sap.com/ess~lea/LeaveRequestApprover.
[EXCEPTION]
I checked portal content permissions for this user and found that those
are ok.
In ECC there is no dump (ST22) related to authorization.
Can you please suggest the solution.
Regards,
Vinod

Hello Karthik and Vivek,
Thanks for replies. But we have created ZMSS role in ECC which is assigned to all managers.
For all other managers the leave approval is working fine. The problem is with only 1 user.
So I dont think there is any issue in ECC authorizations.
Also there is no ABAP dump. Is there any other way like some trace from where we ll come to know about the missing authorization.
With Best Regards,
Vinod Patil

Similar Messages

UWL ESS Leave Approval Workitem link

Hello,
I am trying to launch a ESS Leave Approval UWL Work item via URL from an external application. Can anyone help me what is url to use... I am using UWL apis to get the details of the workitems but not able to create the exact url to launch the work item directly.
Thanks and Regards
Avijit

Hello,
Please check the SWFVISU to check for the corresponding task the parameters and the application name. Also you can the XML of the UWL for the corresponding task , the relevant url.
Hope this helps.
Best Regards
Saujanya

Best way to implement ESS, Leave approval matrix.

Hi Gurus,
Please suggest me the best possible way to map the leave approval matrix for ESS.
we had a plan to prepare our leave approval matrix based on "Position". Just wanna know Is it the right way to figure out the Leave approval matrix. Initially We received a suggestion to prepare the Leave approval matrix with Employee number but by seeing the attration rate/separation/inter org.unit transfer etc., It'll be very difficult to maintain the post seperation data maintenance.
We had maintained a unique position id for each position(at present), If in near feauture if the same piece of task is assign to two person, we'll descriminate through there entry date(i.e. date of confirmation/Date of Joining).
IS it the right way of doing it. Seeking expert suggestion.
Thanks for your continuous support.
Thanks,
SMrinal
Edited by: smrinal on Oct 29, 2010 12:21 PM

This is usually pretty easy. Place all the files/pages you wish to appear as the sub domain in a folder on your site, then have your host create a "A" record for the subdomain you wish to create - so it will look like this http://YourSubDomain.YourDomain.com - then route this "A" record to the folder. Be sure the home page in this folder is a default page, such as index.htm or default.htm, or whatever your server uses for the default home page file name.
Hope this helps.
Lawrence Carmer - *Adobe Community Professional*
http://www.Cartweaver.com
Complete Shopping Cart Application for
Dreamweaver, available in ASP, PHP and ColdFusion
Stay updated - http://blog.cartweaver.com

ESS Leave Approver

Dear All,
I hv a problem regarding leave approval.
There are two Employees A & B.Both of them belong to same PA & PSA and their approver is same.
When I run report(PTARQ-Leave Approver) to know their approver I get the approver of A and not B.
The rule group for A is as follows:
PERNR -WEBMO - MOABW - MOZKO - MOPGK - MOBDE - ZEITY ( Working Fine)
A - 1 - 7 -7 -2 -1 - 2
The rule group for B is as follows:
PERNR -WEBMO - MOABW - MOZKO - MOPGK - MOBDE - ZEITY ( Not showing Approver Name)
B - 1 - 7 -7 -1 -1 - 2
Plz let me know the solution regarding any config changes for leave approval.
Thanks & Regards,
Param

Hi,
To check the approver of employee B, go to PP01 and check the reporting relationship between Position of B and Position of the Approver. If the relationship exists, that means, Approver will appear on ESS

ESS Leave Request error - Processing of the service was terminated.

Dear All,
I am getting the below error on the leave request page in ESS
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
let me know what could be the reason for this error?
Thanks

Suresh,
Please search in scn this has been discussed many times
Thanks
Bala Duvvuri

ESS Leave Approver Problem

Hi,
Any employee XYZ used to report to MR. A.
For testing purpose I changed his reporting to Mr. B.
( Changed A002 - reports to Mr. B).
Now I want the Original situation that XYZ shud report to Mr. A.
I changed his A002 to Position of Mr. A.
However the system is still showing his approver as Mr. B.
( In Report RPTREQAPPRCHK -
In Check Application Function - I m getting Mr. B - wrong one
In Check Basic Function - I m getting Mr A - right)
I want XYZ to report to Mr. A.
Plz. let me know the solution.
Regards,
Param

Dear Sir,
1. Rule Group is 00000001 SAP Standard.
2. Determine Next Agent : Last Agent, Then Line Manager
3. PTARQ>Determine Approver - Shows Mr. B
( I Want Mr. A - Original Approver).
Waiting for an Answer.
Thanks & Regards,
Param

Time/LEave approval in Business Package for Manager Self-Service 60.1

Hi all,
Currently implementing ESS MSS on 4.7 system with EP 6.0 SP19.
The BP we plan to use is Business Package for Manager Self-Service 60.1.
My basic question is, we approve leave requests in BP for my SAP ERP (2004s) in the Universal worklist. How do we do the same in Business Package for Manager Self-Service 60.1. There i sno mention on time approval and leave requests approval in the MSS standard documentation ( or probably i missed it).
Any inputs in this regards are highly appreciated.
regards
Sam

Balaji,
in mySAP we had the opition to lauunch the applications in web dynpro. like launch leave approval in web dynpro. do we have this kind of optiion where the manager can approve the work item on the portal application or will it call a transaction based iview to open the work item in the R/3
regards
Sam

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 - Change Approver

Hi,
We have a situation in which a employees dotted line manager will approve the leave request instead of a direct manager. We have a custom relationship to establish the dotted line manager. Now, In the ESS leave request there is a Approver field which shows the Employees direct manager. Can we customize the logic using a BADI or User exit to show the dotted manager?. Please let me know which enhancement is to be used for this requirement.
Thanks in Advance for your assistance.
Ramesh

in the customizing for the definition of the processes per rule group
you set the selection for the next processor to "Manual Entry".
or for the BADI
Another way is to use the BAdI Control Processing Processes for Time
Management Web Applications (PT_GEN_REQ) and implement the methode
IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
PT_GET_REQ might be utilised here.
Please have a look at the method
CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
If you are implementing the badi then make sure you copy all the methods
and implement the one, as mentioned.

Next level approver in ESS leave request

hi friends
Am working in ESS leave request workflow. In my scenerio there are 4 level approver. I have function module SWX_GET_MANAGER i have copied and customized to ZSWX_GET_MANAGER with my logic to get the next level approvers. If i entered the PERNR it return all the approver for that employee. How do the workflow know he is the 2nd level approver, he is the 3rd level approver. How can i achieve it. kindly help me...
Regards
vijay

Hi Vijay,
I think you will need to use a loop and a counter so you know the approval level. You can use this to get the manager who belongs to the level.
Regards,
Martin
PS I hope you will show in the thread which solution you got so others will benefit. This forum is about sharing knowledge and one way is to give the solution in your thread, or value the appropriate answers.

Leave Approver in ESS

Dear All,
I am facing some problem in the Leave Approver:
Employee A was previously reporting to Manager B.
Now Employee A is reporting to Manager C.
I have maintained the reporting relationship in the position for Employee A.( A reports to C -> It is Ok).
But when I execute the report RPTREQAPPRCHK, the system is picking up his old manager :
1. Check Applicaiton Function - It shows A reports to B (which is not right as per our expections)
2. Check Basis Function - It shows A reports to C (which is OK).
I have maintained the following values in the table V_PTARQ_TPROCESS
--> Determine Next Agent = MNGR Line Manager.
While applying for leave the approver for Emp A is still displayed as Manager B.( it should be Manager C).
Please let me know if any extra config is required for this?
Thanks & Regards,
Param

Param,
You have to get the workflow refreshed for that. As the Determine Next Agent would have already determined the old Manager and kept it in the cache. See the date on which the Agent Determination has taken place in the Workflow for that Task. If the Agent determiantion has taken place before the transfer then you have ask you workflow adminstrator to correct the workflow with the new manager details or kill that task and re-execute the branch of that task again.
Hope this helps.
cheers, Bharath.

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

You are not a receiver of the work item in ESS Leave

Hi,
We are using standard ESS leave application in our portal, where employee can raise leave and his manager can approve/reject his leave. But I want in case manager rejects the leave, the rejected leave should not come into MSS UWL of employee, we will send a mail to employee and he can again login to ESS leave application and where he will see the rejected leave and he can re apply/change/delete the rejected leave. We do not want rejected leave to come in UWL of employee as a work item.
As of now when manager rejects the leave rejected leave of an employee , it is coming in UWL of the employee which we do not want, so what we did, we went to standard leave work flow template WS12300111, in that we double clicked on Task (TS12300116, Process Request by Employee) and in that we clicked on agent assignment icon and than we clicked on attribute and we selected General forwarding not allowed radio button, by default general task radio button was selected.
After selecting General forwarding not allowed radio button, even when manager rejects employee leave, rejected leave is not coming in UWL of employee which we want exactly, but another error is coming when employee goes to ESS leave application again and change or delete this rejected leave he is getting the error You are not a receiver of the work item .
But if we select general task radio button in agent assignment in work flow , than eveything is working fine but employee is getting rejected leave in his UWL, that we do not want at all, so why after selecting different radio button this error is coming ?
Why employee is getting this error, why employee can not reapply/change his rejected leave. Is this portal error OR workflow error OR HR configuration error and what is the solution for this..

If you need this option then you need to change the WF Task.
General Forwarding Not Allowed
This indicator enables you to determine that work items for this task can only be forwarded to users who are agents for the task.
If this indicator is not set, a work item for this task can be forwarded to all users.
The best way to take care of User
Forwaring authorization is the Task Classification (PFTC -> Additional
Data -> Classification). Classify tasks with General Forwarding Not
allowed, will give you the oppotunity to let the user allow to forward
items JUST to the Possible Agents Assigned to the task
(Additional Data -> Agent Assingment -> Maintain)...
Clear that everything depends on How you have developed your workflows
definitions. In that cases the best think to do is
create Different Tasks definition (TSxxxxxx) and let they start
depending on Company Code (That can be driven via Conditions steps in
the workjflow definition, for example). This will allow you to define
Just the responsible Agents per each task, depending on the Companny
Code. This definitively Resolve the Forwarding frelated Question.

Two step Leave Approval Process

Dear All Gurus,
Please help me in this ESS issue. I am facing this issue in ESS Leave Request Application which I will explain with following scenarios.
I have employees Ram and Sham Reporting to Ajay.
1. Line Manager of Ram and sham is Ajay
2. Line Manager of Ajay is Mohan.
Ram has applied leave which came to Ajay inbox for approval. Ajay couldnu2019t able to see it so it went for an escalation to Mohan (who is line manager of Ajay).
Now Ajay donu2019t have Ram request in his UWL and as well as in his SAP Business workplace inbox.
Now Sham has applied leave which again went to Ajay ((who is line manager of Sham).this time Ajay saw the one sham request in his UWL and when he tries to approve it he is getting one more screen in which he is seeing Ram and sham request in the table.
When Ram request already went to mohan why it is coming in the absence table list under the request of sham??
Please help me in solving the same.
Regards
Priya Latha

Hi Priya,
I would suggest you to post your query in the below forum so that HR functional experts can respond to your query...
ERP HCM Employee Self-Service
Thanks,
Jagadish.

Custom Leave approval task problem

Dear All,
I have a problem with my custom leave approval webdynpro task.
Actually I was using standard task , TS12300097 for leave approval. It was working fine from SAP worklist from portal. If someone tries to approve from SAP R/3 it was providing an information like, this cannot be executed from SAP R/3.
I had a requirement to add certain custom fields information to the task description, so I copied and created a new task similar to that and added the containers and filled the description to that. Then i cofigured the new task in SWFVISU also. It working fine from enterprise portal sap worklist.
But some tries to approve from SAP Inbox in R/3 the workflow results in error. Its not providing the same information which was coming earlier with standard task.
The error is as follow :
Work item 000000885207: Object CL_PT_REQ_WF_ATTRIBS method DUMMY cannot be executed
Dereferencing of the NULL reference
Dereferencing of the NULL reference
Error handling for work item 000000885207
Let me how we can solve this issue.
regards,
Sabari Prabhu.

We are changing our Leave Request workflow, and I also came across this problem while testing.
In our situation, the problem is that we changed the approval task. We used to have it as a call to report RPTARQAPP, but then changed back to the standard method of calling CL_PT_REQ_WF_ATTRIBS DUMMY.
For us, it is only the old work items that go into error if the user tries to execute them in R/3. If the workflow is then re-started, the item is once again available and can be processed in the UWL. New work items come back with the pop-up message "The request cannot be started from the Business Workplace", like in the standard workflow.
I think we will just add some encouraging wording to the task so that people will (hopefully) not attempt to execute the work items in R/3, like this:
Please log on to ESS to approve this Leave Request through the Universal Worklist (UWL).
It is not possible to complete this work item from within R/3, DO NOT execute this work item here.
Once you have processed the request in ESS, this work item will automatically be completed.
Good luck

ESS Leave Approval: No authorization to start service

Similar Messages

Maybe you are looking for