Leave Request through ESS

[Former Member]

Hi,

The workflow is not Triggering when a new leave request had been created from ESS. I am using Standard workflow WS12300111. The document has been created but the WF is not getting triggered.

When I am testing from R/3 side using T-Code PTARQ. Here when I am trying to create a leave request it is giving the following Error 'HRTIM_ABS_REQ 022 Unable to send the request CL_PT_REQ_WF_PROCESSOR'. When I see the list of documents created, I can find all the documents created from ESS but the Workflow is not getting Triggered. The Workflow is also working fine when I run it using the document number created it is working fine.

Is there any thing that should be maintained to Trigger the Workflow.

Regards,

Ramu N.

Can

[Former Member · Accepted solution]

Hi Ramu,

First check the event linkage for the workflow using transaction SWETYPV. The goto transaction SWUD, enter the workflow template and click 'Test Environment'. In the next screen click 'Simulate Event'. You will then be shown a list of what occurs when the event is triggered and by checking the error codes, should be able to work this one out.

Thanks

Gareth

[Former Member · Accepted solution]

Hi Gareth/Raja,

Gareth,

When I have Tested using SWUD it is giving an Information message as 'No start events or start transactions/forms'. In SWETYPV there is no linkage for the Workflow Template or the Tasks, the workflow task is using ABAP Class as Object Category and CL_PT_REQ_WF_ATTRIBS as Object Type and DUMMY as method for ABAP Class how can I give Events in SWETYPV.

Raja,

I have checked SPRO the Workflow template is there, when I have checked from R/3 side the program is picking the workflow template mentioned in SPRO but it is unable to trigger the workflow.

Regards,

Ramu N.

[Former Member · Accepted solution]

Hey,

Can you check if there is any dump in ST22?

Regards

Raja Sekhar

[Former Member · Accepted solution]

Hi Raja,

There is Dump, I am analyzing the Dump. Let u know what is the problem after checking the Dump. Is this a problem regarding configuration or any other thing.

Regards,

Ramu N.

[Former Member · Accepted solution]

Hi Ramu and Raja,

Please post the title of the dump and the code sample section as well if it takes too long to analyse. This may seem a little obvious so apologies but has the workflow system been fully configured (use SWU3 to check). Secondly, have you created a delegate business object and does the dump relate to some new coding?

Regards

Gareth

[Former Member · Accepted solution]

Hi Gareth,

I am not using any customized BO, WF etc. I am using the standard SAP BO,WF etc. for ESS leave form, I have checked SWU3 it has been configured.

Should I give entries in SWUVISU to trigger the workflow.

I am unable to trace the problem why the Dump had came.

Dump I am getting :-

Runtime Error DYNPRO_SEND_IN_BACKGROUND

ShrtText

Screen output without connection to user.

What happened?

Error in ABAP application program.

The current ABAP program "SAPMP50A" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPMP50A " 1000.

Regards,

Ramu N.

[Former Member · Accepted solution]

Hi Ramu,

This shouldn't be to much of an issue. What is happening is that the background program is calling PA30 but as this is a dialog, but is a background operation, it is failing.

This is happening BEFORE the event manager is invoked. So, are you using a custom program to create the Leave Request in ESS and if so, is it updating the leave infotype using CALL TRANSACTION?

The answers should tell us what we need to do.

Regards

Gareth

[Former Member · Accepted solution]

Hi Gareth,

You are Right, custom developed Leave Form has been used where they are using CALL TRANSACTION.

Regards,

Ramu N.

[Former Member · Accepted solution]

Hi Ramu,

The custom leave form is where the problem lies. Either redevelop using BAPI HR_INFOTYPE_OPERATION or use the command CALL TRANSACTION and SKIP FIRST SCREEN after setting the correct parameters. The BAPI is recommended as this will mean easier programming and maintenance.

Regards

Gareth

[Former Member]

Hi Ramu,

Make sure that you have maintained the workflow template number in SPRO - Personnel Management - Employee Self Service - Service Specific Settings - Working Time - Leave Request - Processing Processes - Specify Processing Processes for Types of Leave - Define Absences / Processing Processes. Chose the appropiate RULE GROUP and enable the PROCESS REQUEST USING WORKFLOW,then you can mention the Workflow template number for New Request / Cancellation Request / Change Request.

Hope this helps.

Regards

<i><b>Raja Sekhar</b></i>