cancel
Showing results for 
Search instead for 
Did you mean: 

Role with Approval limits. - urgent

Former Member
0 Kudos

Hi,

Ver : ECC 6

Workflow : Contract workflow (n-step)

I have to replace the agent determination logic for this workflow. Approvers are going have different roles (PFCG) with approval limit.

Based on the value of contract, it should pick up the right apprver(s). i have no clue how to implement this. cud anyone of you please help me on this to achieve the solution??

Thanks

Jayanthi.K

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I am on ECC 5.0 and I can't see WS14000148, but sample WS on 5.0 is 20000079. This is based on 'ReleaseStepCreated' event.

You configure the number of release steps in spro -> MM -> Pur -> Contracts -> Release procedure.

Than a new workflow is started for each release step. This seems to fit quite well to your requirement.

I guess it must be similar concept in this new WS.

Regards,

Michal

Former Member
0 Kudos

I m sorry, it is an SRM workflow. u will find it only in SRM server. workflow for Contract approval.

Thanks

JAyanthi.K

Former Member
0 Kudos

Appropriate release strategy must be customised first of all. Than the problem is reduced to release codes.

Regards,

Michal

Former Member
0 Kudos

Hi Jayanthi K,

which workflow number do you mean?

Generally within a workflow to a task you can assign roles in the following 2 ways:

- Worklow - node - agent (responsible agents) - you can put role here (from PFCG)

- PFTC - TS... - agent allocation (possible agents) - you can put role here as well (from PFCG)

Regards

Tibor

Former Member
0 Kudos

Hi Tibor,

I have to copy the n-step workflow for contract WS14000148.

I have to validate against the total value of the contract with the approval limit defined in the personalisation tab in PFCG.

I have to implement the n-step BADI for this requirement. will the n-step BADI works for bespoke template????

cheers

jayanthi.K

Former Member
0 Kudos

Hi Jayanthi,

Well, if the Agent determination is based on any Org Unit, you can go for RULES Using Responsibilities.But as it deals with ROLES, we have to rule out this option.

May be, you can define one custom method which recieves the WF Initiator and Contract total value, where you get the required ROLE & Approval Limit and get the required Agent and send it back to Workflow.

Regards

<i><b>Raja Sekhar</b></i>

Former Member
0 Kudos

Hi Raja,

I should not write any custom methods or rules.

I have to activate the n-step BADI in this case. when we have BADI's, we should implement that instead of writing any bespoke objects..

thanks

jayanthi.K

Former Member
0 Kudos

Hi Jayanthi,

Then check the BADI's Parameter interface. Check if this BADI has any relation to the workflow, I mean check if the parameter interface is connected to Workflow Container elements(May be to the Agents Container element). If so, then based on the Import parameters, get the role and it's personalized parameter(Approval Limit), based on the condition, you must be able to populate the appropiate agent and send it back to the workflow.

BTW,Howz the Agent determination done actually for that standard task? I mean is it through Expression or Rules ? If it is through rules, then I should really doubt the usage of BADI in your scenario.

Am sorry, we dont have SRM implemented in our current site, Else, I must have found you a way out.

Regards

<i><b>Raja Sekhar</b></i>