Leave request workflow WS12300111

[devrajsinghr]

Hi Friends;

I am working on a leave request worklfow WS90000XXX which was customized using WS12300111; This workflow is getting started when a leave request is getting raised at portal; but There is not any event linkage in WF Basic data --> triggering event tab;

I doubting that there must be some BADI or configuration at Back end (ECC end).

Please provide your inputs so that I can trace it further.

Regards

Dev

[Former Member · Accepted solution]

Hi,

The workflow is not triggered using event, its triggered from HR leave customization.

check this view V_T554S_WEB ( in SM30) each rule group and leave type will have workflow which needs to be triggered.

regards,

sabari prabhu.

[devrajsinghr · Accepted solution]

Hi Sabari;

Thanks for you & Pawan inputs;

I have checked the table view and by loookin at it I understood that in this table we can maintain WF number which we need to trigger for a specific leave type;

But Here the problem come that we have maintained a custom WF 9000XXX number in this configuration but when user deleting the leave request for the employee it is calling the standard WF 12300111.

Could you provide information that which can be the reason for it.

Regards

Dev

[former_member190818 · Accepted solution]

Hi Dev,

Did you gave in all the 3 WF ID request ?

Regards,

JMB

[devrajsinghr · Accepted solution]

HI JMB;

I didn't get about which 3 ID you are asking ; could your please elaborate..

Regards

Dev

[former_member190818 · Accepted solution]

Hi Dev,

If you go in that Table Maintenance and choose any one entry. You will have for workflow no. settings. There will be option for WF ID of New Request, WF Id of Cancellation Request and WF ID of Change Request. Give the same custom workflow no. in all these 3 fields

Regards,

JMB

[devrajsinghr · Accepted solution]

Hi JmB;

Thanks for your reply;

But here we have maintained only for WF ID of New Request wid WF number 90XXXXXX

and rest two are = 0;

Even then it is executing the WF on deletion;

Regards

Dev

[devrajsinghr · Accepted solution]

Hi All;

Is there any other configuration which is required to be done by functional ppl to integrate leave request WF with Portal?

Regards

Dev

[Former Member · Accepted solution]

Hi,

The leave request configuration is done in SPRO. I cannot now remember the path, but there is a button "Customization" in transaction PTARQ. Press that and you are brought into the correct place in SPRO (or there you still need to open some path, but you should be able to find "Leave requests" easily, since there are not that many options). There you will find a functionality to configure each absence type and define different workflows for different situations (creating, changing and deleting) - and this is exactly where you can configure your thing.

This is documented in SAP library and the functional people should know what I am talking about. This is where you should configure all the leave request workflow related things (you can even find the BADI stuff here). It is unnecesary to try to configure all this directly in some table.

Regards,

Karri

[bpawanchand · Accepted solution]

Yes you have do the settings in working time configuration in SPRO txn...

Follow the below steps...

1. Execute transaction PTARQ, and click on determine Rule Group, now in the next screen enter the pernr for which the standard workflow is getting triggered while trying to delete the leave request.

2. ONce you know the rule group click F3 and Again come back to main screen of the PTARQ txn..

3. Now click on Customizing button which is available on the main scren of the PTARQ.

4.Expan Service Specific Settings ---> Working Time -

---

> Leave Request ---> Processing Processes ---> Specify Processing Processes for Types of Leave -

---

> Define Absences/Processing Processes execute and select the rule group which you found in the 1st point found and check Workflow taskid for Cancellation...

[devrajsinghr · Accepted solution]

Hi Pawan;

Thanks For your reply..

But it will take me to table view V_T554S_WEB only which is already discussed above..

Is there any other setting which needs to be done to make the scenario working..

Actually I am observing a strange thing that

I have created the LR on behalf of a employee and it is triggering the WF (which is copied from WS12300111) attached by the help of the BADI..As the manager has applied for the leave so it is not going for approval ..

But it is not getting complete .. It is getting stacked at wait step.

Is there any reason or time frame in which wf ll complete caz I have checked in PRD for some of the completed old WF instances which has completed that time only ?

Could you please provide some inputs on this?

Regards

Dev

[bpawanchand · Accepted solution]

Yes it is the standard behaviour of the leave workflow, If at all there are no errors in the approved leave and the approver has not rejected then it will wait for posting, I mean you need to post the approved documents by either using the txn PTARQ or By executing the program RPTARQPOST, this posting raises a event posted, which will iform the workflow that the respective leave request is approved and posted in the respective infotypes....

[devrajsinghr · Accepted solution]

Hi Pawan;

I have tried what you have suggested.. and reach on the following conclusion.

*We are having two WF one is standard WS 1230011 & WS900XXXX

We have configured our all leave type for WS9000XXX in SPRO config or view V_T554S_WEB & I am checking for Leave type VACATION for which *

- Rule group is 00000001which seems name as SAP Standard;

- Retroactive processing permitted for 4 weeks.

- WF ID of New Request is 900XXXXX for rest two option WF id is 0.

=====================

Every thing is working fine;

=====================

1 - When any employee raised leave then it go for the approval and if the manager do it for an employee then it automatically get approved.

2 - Then as it was stacked in wait step I hope there must be some job running in PRD environment as it was a test environment I have run the Trsn PTARQ and done the Posting and WF get completed.

but ; Problem occurs here

Now If I delete the leave which is not yet posted then there won't be any problem..

But if I try to delete a leave which Doc status is Posted then it is throughing the following errors;

1 - * Unable to send the request*

2 - *You are not one of the possible agents of task 'WS12300111' *

SO here the Point comes that from where it is PICKING UP WS12300111?

Please put some input so that I can try further.

Regards

Dev

[bpawanchand · Accepted solution]

SO here the Point comes that from where it is PICKING UP WS12300111?

As i said in my previous post that you need to check in the rule group with respect to the leave type,what is the workflow taskid configured for LEAVE CANCELLATION. I strongly feel that the workflow task mentioned for cancellation of leave is WS12300111, so please change the task ID from standard to the customized workflow taskid.

You are not one of the possible agents of task 'WS12300111' *

If it is ok that on cancellation the standard workflow temaplte should handle then make sure that the agent assignment for the standrad workflow task id is made as general for this you have to follow the below steps,

1. Execute PFTC Txn, select the task type as workflow tempalte and mention the standworkflow ID as 12300111 with out WS,

open in display mode and on menu clcik addtional Assignment ---> agent Assignemnt ---> maintian ---> click on the Attributes -

---

> and select General save ina customizing request* and then run the txn *SWUOBUF and click SHIFT+F1 once it is executed the time which is dispalyed on the screen will be updated.....

[devrajsinghr · Accepted solution]

Hi Pawan;

Yes I have checked the WF ID for cancellation id maintained as 0 as I have told in my previous post, They have maintained only for WF ID of New Request as custom WF number.

and as you have suggested to make it as general task that I have done initially but then it is starting the WS12300111 and sending the approval WI to manager itself but when he is checking the WI in UWL and clicking on the WI ,

then there is no content is available in WI also no button for approval and other which is generally there .

and caz of that we cant take any action on the WI.

Regards

Dev

[bpawanchand · Accepted solution]

So try to debug and check why the standard workflow is getiing picked by insertinga break point in the folloing badi and its respective implementaiton

the BADI is PT_ABS_REQ and if you have implemented it then put a break point in the class CL_PT_ARQ_REQ Enhancement for Leave Request method name is IF_EX_PT_ABS_REQ~GET_WORKFLOW_ATTRIBS Gets Customizing for Workflow

It will pick all your respective leave customizing in the above method... IF the implemention is missing it will throughan error saying Customization is missing

[devrajsinghr · Accepted solution]

Hi All;

Thanks for your reply and quick support.. Let me brief the sol.

There is a class CL_PT_ARQ_PROCESSOR method IF_PT_REQ_PROCESSOR~GET_WF_MAIN_TASK which returns the WF ID by reading the WF configuration.

As I have mentioned that we have maintained 0 as WF ID for modify & Deletion so in this method it is mentioned that if WF ID is initial then it is putting Standard WF ID and passing it forward.

• IF NOT wf_attribs-workflow_taskdel IS INITIAL.

CONCATENATE 'WS' wf_attribs-workflow_taskdel INTO ex_wf_main_task_del.

ELSE.

ex_wf_main_task_del = cl_pt_req_const=>c_workflow_task. "standard workflow *

Thanks specially Pawan;

It was a good learning.

Regards

Dev.

[Former Member · Accepted solution]

Hi, can you please tell me how did you enhance this class ? I need to make custom changes under method Convert_Request_into_Attabs().

[Former Member · Accepted solution]

I found out how to enhance it.

Do you know that's the method that calculates the leave days and deduction for leave quota?

[bpawanchand]

For leave workflow you don't have any start events the workflow is started by using the standard SAP FM SAP_WAPI_START_WORKFLOW and the BADi which is responsible to start workflow is PT_GEN_REQ and the implementation method will be START_WF ....

[devrajsinghr]

Thanks Pawan;

For your inputs but as I have mentioned standard workflow is getting trigger;

Is there any config where we maintain which wf should trigger instead of the table V_T554S_WEB.

Regards

Dev