Purchase order workflow. Levels of approval

Question

Good morning
We are designing a workflow for the Purchase Order approval and have some doubts. We will create a workflow that will have multiple parallel approvers for each stage, based on the values of the items.
The multiple approvers will be required to approve depending on cost centre and on projects. The cost centre approver will be the user responsible assigned in the cost centre master record.
For instance if we have 2 cost centres, 2 different approvers would be required and if for example the total price on the Purchase order for the items of one of these cost centres is high enough, this cost centre will require a second step of approval.
In this last case, we need to know if it is possible to determine in an standard way, the “boss” or responsible for the first approver that is the one linked in the cost centre master record.
Thank you very much in advance and regards,
Alejandra

Answer 1

Thank you Kjetil
We are still only designing the workflow, we haven begin to customize it.
I am planning to create a customized workflow for cases with more than one approver at the same level. If we use some table to register if all the approvers have approved and only at that point we marke the Purchase Order as released, I think we could accomplish with the requirement.
Please let me know if you think this is possible.
Thank you very much and regards,
Alejandra
> I don't know how far you have gotten in your
> customizing yet. A similar scenario have just been
> set up by myself here for requisition release, where
> the responsible person's manager would receive the
> workflow if the responsible person himself (or
> herself) had registered the requisition.
>
> However, the standard workflow for requisitions does
> not support more than one approver per release code.
> You can send the workflow to multiple people, but as
> soon as one releases the release is effective. In our
> case this was solved by sending the workflow to the
> person responsible for the largest share when the
> account assignment is distributed.
>
> Since you are not using standard responsibilities you
> have to implement the enhancement to determine
> agents, and in this enhancement you can use function
> module SWX_GET_MANAGER to find the manager of a
> person.
>
> Note that the authorization control is only via roles
> in the release solution. So you need to define
> separate roles for the different release codes if you
> want to prevent people from being able to release at
> several levels.
>
> One additional tip: the flag WFLOW VAPOS should be
> set to X in table T77S0. You can use SM30 to add an
> entry if it isn't already there. When this flag is
> set vacant positions will be handled as if there is
> no manager position.