WS14000133 Issues

[Former Member]

We derive the FIRST approver from the SLA approver levels i.e. the first approver is dependent on the value of the SC . The second and third are pretty much constant for Finance Approval and Purchasing Approval respectively.

So the structure looks like

Index Branch Approver

1 1 Approver1

2 1 Finance Approver

3 1 Purchasing Approver

Issue 1:

In our case when the requester has saved the SC the requester can still change the SC and increase/decrease the value of the SC even though the SC has been routed for approval or already been approved by certain approvers.

The approval structure shown above should change with the index 1 should be re-calculated if the SC has not been approved by Approver 1.

If the SC has already been approved by Approver 1 and the requester changes the SC, then we would like to insert a new approver depending on the value change and then have it rerouted it for Finance and Purchasing approvals(Index 2 and 3 above).

Issue 2:

Now in our case the approvers can change the value of the SC.When the Approvers do change the value of the SC , it is routed back to the requester to accept changes. Now I am not sure what happens at this point. Let's say Approver 1 approved without any changes. It goes to Finance Approver(Index 2) for approval and he does change the value of the SC. Now the SC comes back to the requester for accepting changes. Does the index for the requester now change to 3 or is it 0 ZERO again.

What we want to do is that we want to save the approval history that is already complete and insert new approvals in the hierarchy if the requester a/o approver make changes . We want to maintain a history of all approvals that have been completed. Can somebody advise if they have experienced this and how did they proceed with this.

Any help shall be appreciated.

Yogi.

[khan_voyalpadusman]

Issue 1 :

-

---

Since the requestor is allowed to change the shopping cart

1) when it has been routed to approver and he has not approved the cart.

2) when it has been already approved by approver.

then in both the cases workflow restart will happen and so the approver

determination will always happen according to the newly changed value.

for this to happen , you have to maintain security level of the requestor

to 'Low'.

transaction ---> SU01 ---> display ---> personalization tab --->

personalization object key ---> BBP_WFL_SECURITY ---> maintain value fot

this key

Issue 2 :

-

---

when the approver changes the shopping cart and the workitem comes to

the inbox of the requestor.

when the requestor ---> has not made any changes to the shopping cart

and accepts the changes.

In such case , shopping cart will go to the next level of the approval

chain.

No restart will happen here because no changes have been made to the

document.