Error found when deleteing a leave request

Hi,
I am getting an error when I am deleting a leave request on ESS i.e.
Work item 000000000000 cannot be read
Please help me on the same.
With Regards
Gaurav Mittal

Hi,
No the thing is that I have to make it automatically for all the users, as all of them are facing the same problem. Please give a solution so that It will delete when the user want to delete his leave request from ESS automatically, not by going into R/3.
With Regards,
Gaurav

Similar Messages

Issue with ESS Leave request workflow - Deleting a leave request

Hi friends,
This is my scenario: An employee has created a leave request from ESS - Leave Request Workflow(Copy of WS12300111) gets triggered and work item gets created in manager's UWL. After that the employee realizes he has created a wrong leave request so he deletes that leave request from ESS. In this case the workflow instance which got triggered when he created the leave request is under process and the work item stays in the Manager's UWL( there is no terminating event or wait for event step in the approval step of workflow WS12300111), when the Manger opens that work item it shows a blank column, ideally speaking when the leave request is deleted by the employee the work item in the manger's UWL should be logically deleted and the workflow should complete, but this part is not handled in the standard workflow WS12300111as well. How to handle this case. I can put a wait for event or a condition to complete a work item at the approval step but i would like to know how the standard ESS leave request framework works in this case. Please advice.

Hi sapient
This is not handled in std. You have clear the next processor in your in method then only the work item will get vanished from the UWL. For clearting the next processor either you can create a method in your BOR and get the request id. For the request id get the max version and clear the next processor or in the BADI you have wirte your own logic when the change happens what you have to do. This logic has to be written in you BADI. I thing BADI will start with PT_ check with that name in se18
You cannot use wait for event or terminating event since its not R/3 workflow its ESS workflow you cannot use ternminating event or wait step.
Regards
vijay

An error occurred when processing the spool request. (Possibly due to memory problems)

Hi SAP,
My backgroud job is failing with log as shown below
Job started
Step 001 started (program ZMRS0065, variant SUS
Step 002 started (program ZDRS0090, variant SUS
Step 003 started (program ZFRS0305, variant SUS
Step 004 started (program ZFRS0300, variant SUS
Access error
Job cancelled after system exception ERROR_MESSAGE
An error occurred when processing the spool request. (Possibly due to memory problems)
Kindly help out in this issue
Regards
Mohammed

Hello Mohammed,
Have you seen any error in your SM21 system log and developer trace of spool work process
during that time?
The maximum size when create spool is 2GB.Pls also check if you are creating a spool
larger than it.
Best Regards
Jie Bai

'Error occurred when deleting master data (RSDMD118)'

Helo Gurus,
When I tried to delete master data prior to the reload, its giving an error message 'Error occurred when deleting master data'. RSDMD 118.
We are currently working in BW 3.1. We checked for SAP notes for the same. But not Able to find any. So please help me to sort it out the problem as early as possible.

Hi Mathew,
Are you sure that those master data are not used in any infoproviders? As far as I know you cannot delete master data if that is used in infocubes or DSOs.
You can also try transaction SLG1 with:
Object = RSDMD
Subobject = MD_DEL
and click on "Execute", this might give you the reason why data cannot be deleted.
Regards,
Csaba

Error occured when giving down payment request through Tcode F-47

Dear All,
Following error occured when giving down payment request through Tcode F-47 by
inserting purchase contract in Purch. Doc. field :
Purch. doc. 4600000442 neither a purch. order nor a schedul. agmt.
Message no. ME703
please suggests
Regards
Shailesh

Hi
As error message states, you should put PO number instead of Purchase Contract number in downpayment request.
You can create a PO for that Purchase contract if you want purchase contract should also be used in that process.
Brgds
Abdulla

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

Error in ESS while Accessing Leave Request

Dear All,
We are having the ESS in EP 7.0 and ECC 6.0, We have deployed the ESS components. Everything working fine for one User only,But for other users we are facing problem Leave Request. This is the error we are getting:::
com.sap.xss.config.FPMConfigurationException: Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest failed.
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)*
*     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)*
*     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)*
*     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)*
*     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)*
*     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)*
*     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)*
*     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)*
*     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)*
*     at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)*
*     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)*
*     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)*
*     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:172)*
*     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)*
*     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)*
*     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)*
*     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)*
*     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)*
*     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)*
*     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)*
*     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)*
*     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)*
*     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:879)*
*     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)*
*     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)*
*     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)*
*     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)*
*     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:596)*
*     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)*
*     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)*
*     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)*
*     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)*
*     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)*
*     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)*
*     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:683)*
*     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)*
*     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)*
*     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:390)*
*     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)*
*     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)*
*     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)*
*     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)*
*     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)*
*     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)*
*     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)*
*     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)*
*     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)*
*     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)*
*     at java.security.AccessController.doPrivileged(Native Method)*
*     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)*
*     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)*
Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest)
*     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:421)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1177)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1282)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1229)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:996)*
*     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)*
*     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:989)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)*
*     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)*
*     ... 69 more*
Please let me know what might be the problem, and y its not working for other ESS users.
Expecting solution and Ideas as soon as possible as its very are in crucial time.
Thanks
Ravi.S

This is a permission issue.
Please go to Content Admin> Portal C D> ...Provided by SAP> End User C> ESS> you will see the ESS object> Right click on it and select Permission and you will see the roles present on the right hand side.
Check it and save it.
Regards
Prashant

Errors found when running the example of "Five XSLT 2.0 Features ..."

Does anyone encounter the error "XSL-1015: (Error) Function 'current-group' not found" when running Oraxsl grouping_20.xsl?
Despite I followed exactly what memtioned in the article, it still did not work.
Thank you very much.

Before running the samples, I downloaded the Oracle XDK 10G via http://otn.oracle.com/tech/xml/xdkhome.html
just a week ago.
So, I believe I got the most up-to-dated version of XMLparserv2.jar.
I spent a day or 2, trying to execute some samples in the article, but things did not work out well. Whenever a stylesheet file (*.xsl) contains "current-group()" functions, it raises the above error.

Error 8 When deleting Report

I am using the save report.vi to save a Test result. When I start the test the first time, the file is deleted before saving. When I start it more often i receive and Error 8 at the delete file.
Because i ignore the error, save Report.vi opens a dialogue for replace or cancel. Replacing will overwrite the file.
When i stop the program and run it again, I do not receive the error or the dialog box for the fist saving action again.
I tried some application to delete the refnum but i couldn't. So what can i do to delete the file?
Attachments:
Report_save.zip ‏957 KB

Hi,
I've had a look at your application and the access denied error stopped when I closed the file.
Your application can't delete the file because it is still open. The first time, the file is not open so there is no problem but when you open it once, you're not allowed to delete it before closing the file.
To avoid this problem what you could do is go in the Save report to file vi (which is in your save report.vi) and close the file after writing into it.
See details on the picture attached.
Hope this helps !
Julien
Attachments:
Save_report_to_file.jpg ‏34 KB

I am receiving the following error message when deleting email messages

I am a new Apple Mac user and aside from converting me from the other useless PC operating system, I am still learning my way around MAC OS X Mavericks.
I am receiving the following error message when trying to delete an email message.
The Message "XXX XXXXXX XXXX XXXX by XXXXX XXXXXXX" could not be moved to the mailbox 'Trash" - veyron007(outlook)"
The IMAP command "UID COPY" (to deleted) failed for the mailbox "INBOX" with server error : Error 9.
Please try again later.
The error message above is exactly as it appears in the error box.
Does anybody know why I am receiving this message?
Does anybody know the correct procudure for loading email accounts with (OUTLOOK, OPTUSNET, etc)
Do I use IMAP or POP3 for OUTLOOK?
I look forward to receiving a reply.
Thanks

Having SSL turned on is supposed to be a lot safer (some require it), I wouldn't want a connection without.
SSL stands for Secure Socket Layer and using it means your connection to the server is encrypted.
Especially when using wifi your connection is prone to eavesdropping, I do not use wifi.
You can set a mail program like OSX's Mail.app to keep the POP mail on the server, but IMAP is my weapon of choice.
IMAP and POP3 are protocols. Mail.app (or Mail) is a client.
For the difference between POP and IMAP, look here:
http://www.geek.com/mobile/geek-101-pop-vs-imap-1536343/

Error message when i run a request on an InfoSet

Hi,
I' ve a this follow message when i run a request based on an InfoSet :
"System error in program SAPLRR12 and form SET_TCUR-02-(see long text)"
Do you know what's wrong ?
Thank you for your help
Jacques

The SAP note number is : 899572
I use BW 7.0
I don't have any access to OSS notes, could you help me please ?
Thnk you
Jacques

Delete Approved Leave Request

Hi all,
My understanding is the program RPTARQPOST posts the leave request documents to IT2001.
I am trying to find out what happens to a leave request that is approved and posted to infotype 2001 and then later gets cancelled/rejected/deleted. Does the initial approved record get removed from infotype 2001? If so how is this handled. Is the same program (RPTARQPOST) going to remove the records from IT2001?
Any suggestions and thoughts are appreciated.
Thanks
M

Hi,
I think removing the tick mark in the check box "Requests have to be approved" will cause that also the Request should not be approved by the Manager. But in our Case the Request should be approved and the deletion not.
Is there a possibility to control this apart?
Best Regards,
Nadin Schaa

Error found when upgrading from11.5.10.2 to R12.1.1 with the DB R 11.2.0.1

Hi All,
I have following the "Upgrade Advisor: E-Business Suite (EBS) Upgrade from 11.5.10.2 to 12.1.3 [ID 269.1]", and select the option 3 Configure --> Preform Upgrade on Test System --> Upgrade Test Environment 12.1.1 --> Perform Upgrade --> Apply AD 12.1.1 upgrade driver (required) (The steps before apply AD 12.1.1 have been done, the R12 rapid install have been done.)
According to their instructions, I need to merge 3 patches 9477107, 9179588, 7461070, and applied it to R12.1.1, it was successfully. (I have attached the adpatch file to metalink, they also confirmed that the patches have been applied successfully. ** Due to I have some warning messages found in the log, that's the reason I raised a SR to ask Oracle about it.)
After this step, the step 10. Run the American English upgrade patch driver (required) to be executed, but error found.
Accroding to this step, I need to apply 7303029:12.1.0 with preinstall mode and merge its with the American English drive which located in $AU_TOP/patch/115/driver/u6678700.drv.
As the patch readme file instructions, "adpatch options=nocopyportion,nogenerateportion" have been executed. After a while, the autopatch process was failed due to
AutoPatch error:
Missing prerequisite codelevel for entity 'ad'.
This patch requires the following codelevel or higher: 'R12.AD.B.1'.
The current on-site codelevel for the entity 'ad' is : 'R12.AD.A'.
In order to apply this patch you must first apply a patch that introduces
at least the minimum required codelevel.
You may merge this patch with a patch that introduces the required codelevel.
I was so wondering about it, how's come the ad codelevel doesn't match, the patch 7461070 should be the level 'R12.AD.B.1' (can be found in the patch's readme file.), how's come the current on-site code level is 'R12.AD.A'?
I was stuck in this point, can't process further.
Anyone was facing this issue too? If so, could you please let me know how to solve it. Or anythings I can do now? Do I need to re-apply the patch 7461070 again?
Thank you so much.
Amy

Amy,
As this an E-Business migration problem it would be better to ask the question in an E-Business forum.
Try here to begin with -
EBS General Discussion -
General EBS Discussion
and they should be able to help or direct you to the best forum to follow up.
Regards,
Mike

Error found when updating table

Dear all
i got an error message when executing the following update statement, any idea ?
Please help !!
SQL> UPDATE COMPRLMMR SET MMRLNM = MMRID;
UPDATE COMPRLMMR SET MMRLNM = MMRID;
ERROR ¦b¦æ 1:
ORA-01654: unable to extend index LIIL_SA.IDX_PRLMMR_MMRLNM by 128 in tablespace USERS
ORA-27059: skgfrsz: could not reduce file size
OSD-04005: SetFilePointer() failure, unable to read from file
O/S-Error: (OS 112) ºÏºÐªºªÅ¶¡¤£¨¬¡C

Looks like your USERS tablespace is full. You (or the DBA) will probably need to allocate additional space for the tablespace.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Error 00336 when deleting

I'm administrator and i try to delete some accounts, oportunities, etc and the system tell to me: "The record can not be deleted (SBL-ODS-00336)"
I'm administrator and i have all posible grants.
Any idea?

I can do a list of opportunities. Also i can invoke to a batch delete, but the problem persist because the batch process fail with the same error that manually delete (you can't delete the opportunity)
I'm thinking about one posible solution: With a webservice update the state of all oportunities and after that delete all with batch delete

Error found when deleteing a leave request

Similar Messages

Maybe you are looking for