Release strategy value check

[charnockl]

We have a value based release strategy for Purchase Requisitions e.g. first release > 20000, second release >50000, third release >100000 etc.

It is a new requirement from our cost accounting department that they check items over a certain value. They want this value to be variable in that, over time, they would start checking all items over 10000, but once the process is embedded they would only be interested in items over 40000 and so on.

I could meet their requirement [10000] by having a zero level release of >10000 in the example I provided, but this would mean reconfiguring the release strategy every time the "variable" value changes. If they decided they wanted to change the check to the 40000 threshold, I would then need to remove the 10000 check and insert a step between the 20000 and 50000 release levels [codes].

Has anyone encountered a requirement like this and, if so, how have you catered for it?

Thanks and regards, Lara

[charnockl]

Hi Dominik

Thanks so much for following up. Apologies for the delay in my response, I was out of town.

The current procedure is that all approvers must approve i.e. all prerequisites must be met.

thanks, Lara

[DominikTylczyn]

Hello charnockl

I think your requirement is easier to implement than you presume. Notice, that when you define release strategies you don't insert steps for release levels / values. You just define release strategies with one or multiple steps / release codes. Then you classify each release strategy (not a release strategy step!) with e.g. value. So when there is a purchase requisition that exceeds value threshold, the release strategy is triggered. Release strategies, release codes are configuration settings. Whereas classification is just master data and you can change it directly in production system.

I'd suggest first to agree with your cost accounting department on number of release strategies and number of steps in each strategy. The easiest approach here would be to stick to one-step strategies. If you go this way and value thresholds are to be changed, you'll just need to adjust release strategy classification.

Best regards

Dominik Tylczynski

[charnockl]

Hi 3a9e4ce873a94034b33dc62b0ce600ee

If it is easier to implement I'd be delighted!! I'm not sure that I'm understanding you, though. I'd really be grateful if you could share your insights, I will provide a real example from our system. Please note that our release strategy is by cost center, purchasing group and value, but for purposes of this example I'll just illustrate the values.

Group Code Value Approval AA 01 - Procurement AA 02 >2500 Approver 1 AA 03 2500.01-20000 Approver 2 AA 04 20000.01 - 50000.00 Approver 3 AA 05 50000.01 - 100000.00 Approver 4 AA 06 100000.01 - 200000.00 Approver 5 AA 07 200000.01 - 500000.00 Approver 6 AA 08 > 500000.00 Approver 7

In this example release group AA is for the cost center AA. The approvers (1, 2 and 3) are specifically prescribed in the authority matrix as the approvers for only that cost center. Cost center BB would have it's own release strategy [AB] where the approvers are different users. Procurement are the 01 release for all cost centers, then approvers 1-3 are specific for that cost centre. Approvers 4-7 are Management users who approve company-wide.

How would you set this up differently to meet the cost accountant requirement?

I really appreciate your time and input.

regards, Lara

[DominikTylczyn]

Hi charnockl

I'm trying to understand your requirement, hence a question. Are we talking here of one step or multiple step approvals?

E.g. your case of AA 08 > 500000.00 Approver 7 is it to be approved by Approver 7 only or by all seven approvers i.e. Approver 1, then Approver 2, then Approver 3 etc.?

Regards

Dominik