cancel
Showing results for 
Search instead for 
Did you mean: 

Why standard workflow WS12400007/WS12400005 not trigering?

former_member184119
Active Contributor
0 Kudos

we are implementing SAP Fiori for the first time, config and all are good in place in v_T554S_WEB,

For Leave request Creation and change standard workflow 12300111 is used.

For Leave request deletion we are using standard workflow 12400007 is used.

But some how this workflow is not working and throwing below error Unable to send the request HRTIM_ABS_REQ/022..

So I activating the BADI PT_REQ_GEN is this manditory to activate while WORKING with this workflows? any workarounds are highly appreciated.

former_member184119
Active Contributor
0 Kudos

No single answer so far 😞

ChrisSolomon
Active Contributor
0 Kudos

That's a VERY good way to get it NEVER answered.

bpawanchand
Active Contributor
0 Kudos

I am not sure if this is resolved or not. However, after gogin through your various comments . I would like to mention here few things:

1. If the workflow is not getting triggerred insert a break point in the BADI Implementation in Start Workflow. As these leave request based workflows will be started by using start workflow function modules. There are no events associated with these workflows.

2. Secondly, you mentieond that in pfct you are not able to view the workflow , make sure that you do not include the obecject ID 'WS" while you are trying to check the workflow definition.

3. If this workflow is made as general task make sure you update the indx of the workflow.

4. Make sure to use RE_RHMOVE30 transaction to trasnpor the attributes of the Workflow tasl.

5. Finally,. make use of buffer refresh SWU_OBUF trasnaction to refresh teh workflow buffer wheever you perfomr some changes.

Regards

Pavan

Accepted Solutions (0)

Answers (3)

Answers (3)

TheGokke
Active Participant

I don't think that you should be using this workflow. I have always used the same workflow (or a z copy based on the same template).

This being WS12300111 or the newer one 21500001.

The approve of a delete triggers the same workflow if the original request was already approved. If not the delete is automatic. So I would take a copy of the 21500001 workflow and if you never want approval when deleting a request you should handle this is the custom workflow.

anjan_paul
Active Contributor
0 Kudos

HI,

Please check SAP note 2536525.

Thanks


former_member463524
Contributor
0 Kudos

Hi,

It may raise because of authorization also repeat the error and run the tcode SU53 straight after you received this error message, the report will tell us which authorization is missing. The SAP note2478354 mentions that the only authorization object available for workflow is the object S_WF_WI which can also be checked by run SU56->F5->UserID and Authorization Obj. S_WF_WI.

Also share GBX01HR version also.

Regards,

Meera

former_member184119
Active Contributor
0 Kudos

I am trying to make workflow as general task but it is not identifying in PFTC !! any inputs on this ??

former_member184119
Active Contributor
0 Kudos

I changed the workflow from

  1. WS12400007 to WS12400005 still not trigerring, its only working fine for 12300111 for Trigerring the creation and change workflow not for withdrawn, any further inputs are welcome, thanks.Below is the screen shot of the configuration, appreciate your replies! thanks.