Configuring the attaching of documents to leave request

Hi All,
The current leave request in ESS was not configured to upload any supporting documents. The cleint now want to have the functionality to attach doctors notes, or any additional documents to the leave request. Please advise on the procedure for doing that with or without DMS. We need to expolore the 2 options.
Regards,

A Pages '08 or earlier document is actually a package, a special kind of folder that appears as a single file, but isn't. You can't e-mail a folder which is why many mail clients balk. Apple Mail will automatically zip a folder, other e-mail clients don't, especially web-based e-mail. In the Finder, Control- or right-click on the Pages document & choose Create Archive… (Tiger) or Compress… (Leopard) from the contextual menu. You will now have a zipped Pages document that you can attach to your e-mail & send.
Your recipient must have Pages to be able to open your Pages file. If s/he doesn't, you can export the Pages document as Word or PDF & send that.
Pages 4/iWork '09 now saves a flat file by default (it can also save as a package). There is a Share menu that has the option to e-mail the document as Pages, Word or PDF.

Similar Messages

How to configure and test workflow for Creating Leave Request

Hi,
When I select leave request iView in portals I get an R/3 screen titled "Create Leave Request".And when I fill in the details for approver and press send I get this error message "You are not one of the possible agents of the task".
So help required to configure and test the workflow behind Create leave request iView.
Regards,
Pavanmeet.

Pavanmeet,
you have to set all activities in the workflow to "general task" as well, not only for WS12300111 itself (doubleclick on each symbol with the "triangle").
check the status of the sent leave request in transaction PTARQ (Display Documents). Here the "next agent" & the "pers. no" of the next agent is of interest.
logon with the user, that is saved in infotype 0105 of the above mentioned pers.no. there should be the approve request.
you can check the status of the workitems with SWI1 (i assume your system is prepared for workflows , check SWU3)
Message was edited by: Achim Hauck

Blank header appears when validating leave request from the UWL

Hello,
We are using SAP Portal 7.3 and BP_ERP5MSS 1.51 SP06 according note oss 1618269 with a backend ECC6 EHP5 SPS06.
We are facing the following issue :: "Leave Request Approval screen is poping with blank header".
This issue occurs when launching the task TS21500003 from the UWL of the manager trying to validate a leave request.
See these screenshots,
[http://s14.postimage.org/dponkbsoh/UWL_issue_1.jpg]
[http://s9.postimage.org/7si0vfa7j/UWL_issue_2.jpg]
From NWA and Log traces we can find, but it is not sure it is relevant (due to some other iview not set yet) :
error : "Item with external id :<000000005010> and system id: <SAP_UWL >: Problem in performing action <markAsLaunched>: Unknown action: <markAsLaunched>-"
warning : "com.sap.security.api.NoSuchUserException: The given id " "is not a unique id of a user!"
We tried to follow some recommandations :
- Tx SWFVISU / Task TS21500003
- DYNPARAM = LRF_REQUEST_ID=${item.REQUESTID}
- and from portal : "Universal Worklist - Administration" / "my system alias" / Re-Register
- and clear cache
=> without success.
we tried :
- role : SAP_MANAGER_MSS_NWBC and SAP_ALL
- we assigned this role or this profile at our user test
=> without success.
we find :
- Note 1600953 : Modifications to UWL configuration file in BP MSS Add-On 1.0
=> but we didn't setup this Add-On, so we think this note is not relevant for us.
to investigate :
We have also tried to copy and past the XML indicated in note 1600953 for task TS21500003 and it did not solve the issue. We then came back to our initial XML.
We have configured the SAP_WebDynpro_XSS as indicated but we still face he same issue :
- when trying to open the task in the UWL, a pop up with a blank header opens.
- when using the iview com.sap.pct.erp.mss.leave_request_approval, the system opens directly a leave request without showing the list of requests assigned to the manager.
Find step by step in this word document and the UWL information trace :
http://www.filedropper.com/issueuwl20120217
Thanks in advance for your help,
Regards,
Rodolphe

Hi,
thanks for your answer, we still have the issue.
We have tried to change the Web AS setting from ABAP to Java but same error message :
"ressource not found"
and error : "Item with external id :<000000005010> and system id: <SAP_UWL >: Problem in performing action <markAsLaunched>: Unknown action: <markAsLaunched>-"
warning : "com.sap.security.api.NoSuchUserException: The given id " "is not a unique id of a user!"
in the backend :
/nSWFVISU
TASK :TS21500003
DYNPARAM:
LRF_ARQ_MODE=A&LRF_REQUEST_ID=&LRF_SKIP_OVERVIEW_PAGE=X&LRF_WITEM_ID=
XML FILE configuration file Universal Worklist Configuration Content :
(concerning the Task)
<ItemType name="uwl.task.webflow.TS21500003.SAP_UWL" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
<ItemTypeCriteria systemId="SAP_UWL" externalType="TS21500003" connector="WebFlowConnector"/>
<Actions>
<Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproABAPLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
<Properties>
<Property name="display_order_priority" value="5"/>
<Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
<Property name="WebDynproApplication" value="hress_a_ptarq_leavreq_appl"/>
<Property name="WebDynproNamespace" value="sap"/>
<Property name="openInNewWindow" value="yes"/>
<Property name="System" value="SAP_UWL"/>
<Property name="DynamicParameter" value="LRF_ARQ_MODE=A&LRF_REQUEST_ID=&LRF_SKIP_OVERVIEW_PAGE=X&LRF_WITEM_ID="/>
</Properties>
<Descriptions default=""/>
</Action>
</Actions>
</ItemType>
Best regards,
Thomas

How to configure and test workflow for Creating a leave Request?

Hi,
When I select leave request iView I get an R/3 screen titled "Create Leave Request".And when I fill in the details for approver and press send I get this error message "You are not one of the possible agents of the task".
So help required to configure and test the workflow behind Create leave request iView.
Regards,
Pavanmeet.

Pavanmeet,
you have to set all activities in the workflow to "general task" as well, not only for WS12300111 itself (doubleclick on each symbol with the "triangle").
check the status of the sent leave request in transaction PTARQ (Display Documents). Here the "next agent" & the "pers. no" of the next agent is of interest.
logon with the user, that is saved in infotype 0105 of the above mentioned pers.no. there should be the approve request.
you can check the status of the workitems with SWI1 (i assume your system is prepared for workflows , check SWU3)
Message was edited by: Achim Hauck

ESS Leave Request Workflow Configuration

Hi Experts,
I Have ESS & MSS setup with mySAP ERP 2005 ECC 6.0, i have made the required configuration for absences, i assumed that leave requests should automatically be forwarded to the person with cheif position in the department, Now hwen an employee applies for a leave request i check the MSS UWL and nothing is appearing.
My question is do i have to maintain any configuration in terms of workflow or is it automatically configured if PA & Om integration is active ?
Points will be rewarded for any help..
Regards,
Ahmed Salah

Ok follow this path
Tools --> Business Workflow --> Development --> Tasks/Task Groups --> Change
Task type = Workflow template
Task = 12300111
Click on Change
Click on Workflow Builder.
Click on Process request by Employee.
Click on Task Properties (Agent assignment)
In Maintain Agent assignment,
See for Process Leave Request by Employee , add General Task.
Then click on the Update Index.
Hope this works for you.
Cheers!!!
Sanjay Sharma.

Leave Request - can't change the time of pending request

Hello,
We are trying to change the time of a pending leave request and when entering a new time in the duration field, the original time still shows up on the Review and Send screen. The leave request is for one day and for 5 hours - we are trying to change to 2 hours and 5 hours still shows up.
Is this an issue with the code or config? Any help is appreciated.
Thanks

is the note 1238028 implemented in your system?
have you done any modification
Depeding on your requirement you can decide how to use
PT_ARQ_REQUEST_CHECK ie hours field or the clock times.
That means you need to clear the time fields which are derived
from the work schedule and keep it empty since these fields
are hidden in your front end and no option for the pernr to modify
or correct the times.

What needs to be done to include the leave request type in the work flow

what needs to be done to include the leave request type in the work flow?
the present request for work flow includes the notificationto be sent to the approver
which doesnt include leave request type inthe description
to include this we need to maintain a container variable but what should be the method or abap dic object which has to be used for maintaining this leave request type container

Hi,
You can create and take where you pass leave type and get description of it and create an field in WF containr and fill it than you can use add that field when you are sending notification,.
Atul

What is the use of the FM PT_ARQ_REQUEST_EXECUTE--ESS Leave Request?

Hi,
Please let me know what is the functionality of the Function Module PT_ARQ_REQUEST_EXECUTE. The Documentation for this is not available.
We have an ESS Application to be developed where the employee needs to raise a leave request and the Manager has to approve it. We can make use of the two FM PT_ARQ_REUEST_CREATE and PT_ARQ_REUEST_PREPARE for raising the request.
I need to know how can we save a copy of the leave request before we send it for approval. what is the function module to be used?
Regards,
Aishwarya

Hi,
Approving Leave Requests Web application provides HR managers or other authorized persons with all the functions they require to check and approve leave requests.
This Web application is part of the Business Package for Employee Self-Service since it uses the same functions as the Employee Self-Service application, Leave Request and cannot be implemented on its own. However, it has been developed for use in Manager Self-Service.
More information you can get from following link its very usefull for U.
http://help.sap.com/saphelp_erp2005/helpdata/en/73/8eaf40a90c952ae10000000a155106/frameset.htm

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?

ESS Leave Request - Customer fields default function not working

Hi,
a. SAP version being discussed
SAP ECC6.0
EP7.0
ESS/MSS
b. Here is the scenario
1. We are using ESS Leave Request application for employees to request leave. We are using the standard web dynpro java leave request application delivered by SAP.
2. Lately there has been a need to provide a customer field on the request form which will have a calculated value showing up when the employee opens the request
3.We used one customer field called customer01 as per configuration steps.
4. This field appears on the request form when it is opened.
5. Our need is to display a value in that field when the form is opened.
6. SAP/s documentation states that we can use BADI PT_ABS_ARQ to default a value to this field on the form. This value is calculated during runtime dynamically.
7. We have used the method IF_EX_PT_ABS_REQ~SIMULATE_VIA_BLOP for this purpose
8. After activating and coding this implementation, the system does not default anything on the request form when it is opened up.
9. Once the employee hits the review button, this field gets its defaulted value but this is not what we want. We want the system to display this when the form is OPENED, that means at the prepare stage. For this field to appear after hitting the review button is meaningless as the employee needs to make a decision based on the value in this field before hitting the review button.
It almost seems like this BADI is called when the review button is hit and not when the form is opened up. We may be wrong and missing something obvious which one of you can immediately point out, Hence this post.
10. I did go thru the forum at great length and seen that there has been discusion surrounding the need to populate R3 from a value entered into this field. My problem is different wherein, I wish to populate this upfront as display information when the form is opened and then send it back to R3, once the employee submits the request.
Would be grateful if anybody on this forum could point me in the right direction.
Thank you,
Rajesh

Please, can I take this question a little further.
Is it possible to add more fields to the leave request form on the ESS portal. For example, our customer wants additional fields like reason for leave, contact residential and telephone number during leave, Require leave entitlements (Yes/No).
Would appreciate if a reply can be given on if it is possible or not and what to be done if it is possible.
Cheers

ESS Leave Request Workflow Issue

Hi Every one,
Our client is using ESS/Portal Leave Request workflow(ZWorkflow template which is configured to the portal) which is working fine up to the last month.Recently i developed 3 level Escalation functionaly which is working fine and we tested and finally transported to production in the last month .And recently i got an issue when the leave request is aproved after escallation is not setting the workflow status completed and keep on escalating to the next levels.
Note:When the 1st manager approves the leave request without escallation the workflow status is going to be completed which is fine and only there is an issue when escallated and approved the status of that specific leave request is approved but the workflow is not going to the status completed and keep on escalating to the next levels.
i checked the log and found there is condition based wait event step which have a condition when
Req.status = Approved&
Req.status = Withdrawn&
Req.status = Error.
must raise the event and complete the workflow only working fine when the escalation does'nt takes place and the direct manager reacted without escalating to another manager.
Please help e what might be the problem is.
Thanks,
Raja.

Hi,
Where is this event called? And more over is it an AND condition between those statements?
regards
Krishna

Leave request FPM

Hello,
Our users are complaing that they just have to go thru too many steps before they can approve a Leave Request in ess. So I have been asked to skip the review section while approving Leave Request.
After going thru various posting on this site, I learned that this can be possiable thru FPM configuration for leave approval ivew where I need to set the option "true" for skip review screen.
When I choose FPM applications under Leave Request I see it empty, there is nothing under FPM applications. Can anyone please suggest me what could be the reason? Any other configuration required for FPM? Please help.
Thank you,
Bobby

Thank you Shanti, I am able to see now Leave Request under FPM applications. But when I try to open Leave Request Approver under FPM, I am getting a dump . java.lang.NullPointerException.
Appreciate if you can please advise what could be the reason.
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
     at com.sap.xss.config.PcdNamingUtil.removePcdPrefixFromId(PcdNamingUtil.java:22)
     at com.sap.xss.cfg.edt.FPMApplicationEditor.doInit(FPMApplicationEditor.java:552)
     at com.sap.xss.cfg.edt.wdp.InternalFPMApplicationEditor.doInit(InternalFPMApplicationEditor.java:430)
     at com.sap.xss.cfg.edt.InconsistentObjectExceptionView.doInit(InconsistentObjectExceptionView.java:174)
     at com.sap.xss.cfg.edt.InconsistentObjectExceptionView.wdDoInit(InconsistentObjectExceptionView.java:100)
     at com.sap.xss.cfg.edt.wdp.InternalInconsistentObjectExceptionView.wdDoInit(InternalInconsistentObjectExceptionView.java:112)
     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.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.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.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:182)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:177)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     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.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     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)
A

Options for leave request work items in ECC6

We are upgrading our backend system from R/3 4.7 to ECC6. I am not very impressed with the leave request authorisation process and wondered if there are any other options open to us.
In 4.7, leave requests were workflowed to the requester's manager with a subject like this:
Process leave request from <fromdate> to <todate> submitted by <person>
When the manager selected it, they only see that request.
In ECC6 (using task 12300111 and the Webdynpro 'Leave Request: Approval') the subject in the inbox is;
<person>'s Leave Request
When the manager opens the item they see all leave request from all staff, despite this, they can only process one item at a time. Once completed, they are given an option to Approve Another Absence - but the link does not work. I can remove that link using ctrl-right-click, but was wondering;
1 Has anyone got the "Approve Another Absence" link working when the iView is launched from the UWL?
2 Has anyone managed to put the details of the request into the subject?
3 Has anyone managed to setup bulk authorisation of multiple requests in one step?
4 Has anyone managed to restrict the workitem to only display a single request?

Bharghava.K,
I've implemented a work around for this - I've added the following UWL configuration file as a high priority:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'>
<UWLConfiguration version="1.0">
<ItemTypes>
 <ItemType name="uwl.task.webflow.TS12300097" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchIView" executionMode="default">
 <ItemTypeCriteria externalType="TS12300097" connector="WebFlowConnector"/>
 <Actions>
 <Action name="launchIView" groupAction="" handler="IViewLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
 <Properties>
 <Property name="iview" value="pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.iviews/com.sap.pct.erp.ess.working_time/com.sap.pct.erp.ess.leaverequestapprover"/>
 </Properties>
 <Descriptions default="launchIView"/>
 </Action>
 </Actions>
 </ItemType>
</ItemTypes>
</UWLConfiguration>
Check the "Leave Request: Apporval" iView's ID if you try this - I don't know if ours is in the 'standard' place within the PCD.

ESS: UWL Leave request issue

Hi folks,
We are on EP 7.0 SP13 wit ESS/MSS 600 SP11 (for ERP2005) .
We configured ESS Leave request and facing the below issue.
When an employee takes leave with the leave request application and the manager rejects/approves this leave request,
a work item is send in the UWL Inbox of the employee. Processing this work item leads to the following error:
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequest' are not deployed on the server. Please check the used URL for typos.
Exception id: [0018FE28A06E006500000070000032B50004463FEC45E404]
I've checked the SWFVISU transaction and changed the package name of workflow task 'TS12300116' to 'sap.com/esslea', initially, it was 'com.sap/esslea'. Though i make this change and re-register the UWL system, i still get the error when opening the task from UWL Inbox
All ESS/MSS services/webdynpros are deployed without errors.
Does any body have an Idea ??
Thanks
Karthik

Hi Karthik,
The error is because in SWFVISU transaction, where the Workflow task is linked with the Leave request approver application ,the package name is wrong.
The task for approval process is TS12300097.
In SWFVISU,
Application name is : LeaveRequestApprover
Package : com.sap/ess~lea
If you notice,the package name mentioned here would be com.sap.xss.hr.lea.appl. Please correct it to com.sap/ess~lea.
You can also check out note 779075
Hope this solves it.
Regards
Reshma

Error when creating a leave request

Hi Experts,
I am setting up ESS (WDA) EHP5 on Portal 7.3. I and ERP6. I got this error when clicking on the calender to create a leave request:
No data for infotype 0001, personnel no. 00000000 in period 2012-01-24 - 2012-01-24. (Modifiers not found)
Got the same error on the portal as well as using PTARQ
I did customizing for Leave Request and there are also data for IT0001.
Is there anything else missing?
Please advise.
Thanks.

SInce you are getting a message recarding pernr 00000000, it looks like your user in portal may not be tied to an employee via infotype 0105?
/Kirsten

Configuring the attaching of documents to leave request

Similar Messages

Maybe you are looking for