Skip to Content
avatar image
Former Member

PO change approval workflow not working !

Hi experts,

There is some problem with the PO change workflow we have ( SRM4.0 EBP 5.0 ) . This workflow has been customized. We find that after adding the added approvers the agents are being transferred to the concerned steps but once we again try to change the PO we find that the agents added are missing and it goes to the agent who had added the added approvers. What could be the possible reason for the same ? How can we troubleshoot the workflow in depth.

Plz reply !

With Regards,

Rajesh

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 25, 2007 at 02:25 PM

    hi,

    please let me know the following things.

    1. Is it classic Purchase order workflow (or) N-step Badi workflow? which one have you customized?

    have you copied standard to Z and making changes?

    2.How are you adding the agents ? manually?

    3. Are the system getting added from the org structure?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      We are using an extended classic workflow . The workflow which has been customized to have 8 step of approvers at the max.

      The agents are being identified based on the cost center assignment, for which the approvers have been maintained in a seperate HRMS system.( The cost center is linked to an org unit in HRMS where we derive the approvers).

      There are some approvers that come into play depending on special criterias like EB attribute of the user.

      Now the problem comes where there is an ad-hoc approval workflow also added to it which enables the user to add approvers manually but there is some problem in the agent transfer there. The step identified by the systm during runtime is not defined in the ad - hoc workflow also and hence the step shows no agent and it returns to the user who added the approver.

      Kindly help as to what is the reason for the same and what can be done to rectify this.

      With Regards,

      Rajesh