Question Re: No approval workflow found. Inform system administrator SC SRM 7.0 in Spend Management Q&A

No approval workflow found. Inform system administrator SC SRM 7.0

S0016576034 — Thu, 25 Sep 2014 16:09:28 GMT

Hi Gurus,

I need your support with the next Workflow issue:

After restart the SRM server there is an issue with WF (Application Controlled Workflow)

When a SC was check appear error "No approval workflow found. Inform system administrator", this issue only apply for one backend and others backend works ok.

When i check this message in table T100 have area BBP_WFL and number 012.

I followed the next steps to check WF conditions in SRM:

1-. Template WS14500015 for BUS2121 in tcode swetypv

2-. Tcode SWU3 for check automatic conditions, only show error from HR Control Tables.

3-. in PFTC check active template

4-. This themplate is for BADI BBP_WFL_APPROV_BADI, in SE18 Implementation is called:

5-. RFC for backend were test in SM59, and its ok.

The Component version is SAP SRM 7.0 and SRM Server SAPKIBKV13, please consider that is extended classic scenario.

Thanks for your help!

Re: No approval workflow found. Inform system administrator SC SRM 7.0

konstantin_anikeev — Sat, 27 Sep 2014 13:00:54 GMT

Hi,

Please check the transaction SWB_COND or SWB_PROCUREMENT for start parameters of the workflows.

This message normally occurs, if the conditions are wrong.

Please also check if you have redefined the standard business object BUS2121 (assignment in the transaction SWO6, Object itself SWO1 - try to test it for the shopping cart).

Regards

Konstantin

Re: No approval workflow found. Inform system administrator SC SRM 7.0

hugo_amo — Sat, 27 Sep 2014 13:23:30 GMT

Hi Jorge,

Review Note 322526 - Analysis for workflow problems.

http://service.sap.com/sap/support/notes/322526

Regards,

Hugo

Re: No approval workflow found. Inform system administrator SC SRM 7.0

S0016576034 — Mon, 29 Sep 2014 23:56:06 GMT

We applied the note 322526 and all parameters looks ok (equal to PRO), despite this we still have the issue.

I think the next step is to debug BADI BBP_WFL_APPROV_BADI.

Thanks for the help, If you have another idea is welcome.