ESS Document Error

[Former Member]

Hi Friends,

We are using standard Leave workflow WS12300111.

It is working Fine. Some cases Workflow status showing as STARTED. but if i check RPTARQDBVIEW program i am getting some ERROR documents. After approve of Leave request still the workflow status is same(STARTED) i think because it is not posted.

How can i find why Document is going to ERROR status.

And how can i post only that particular Documents.

Thanks in Advance.

Kumar.

[vijy_mukunthan]

HI kumar

Goto> t-code PTARQ There is a button called process error. Type your employee number and execute you will find the list of request id's with error. Copy the document id and goto>se11 t-code table name is PTREQ_HEADER give the document number at request_id field execute it you can find the list. In the list last column will be workitem id copy that workitem id. Goto-->SWIA T-CODE give the workitem id and double click on it. Inside goto log and go to technical settings on the below part go to history tab u can find the error of the workite.

Regards

vijay

[Former Member]

Hi,

I don' think that the workflow is in error (since it is in status started). The leave request itself is in error. The posting program hasn't been able to post it correctly. A time specialist should take a look to the error (details can be found for example in the job log, if the posting program has been scheduled as a batch job). After the error has been corrected, the workflow should also end. Once again, I don't think that this is in any sense a workflow problem. Just correct the leave request and post it again.

Regards,

Karri

[Former Member]

Hi Karri,

Yes you are correct.

I already mention that my workflow status is STARTED and NO ERRORs inside. My workflow working perfect.

And i checked the Document in table PTREQ_HEADER latest status is APPROVED. And job log showing as below.

Collision with another time entry

Change in correction phase for Controlling area 00

Personal payroll past not reached

Can anybody tel why these errors/messages raise. I need to explain my end user.

Thanks,

Kumar.