A couple of questions on SRM BRF

[Former Member]

Dear all: we are quite new with the BRF approach and we have a couple of questions to be clarified to proceed further. Let us ask these questions and see if you, as experts, can bring some light.

1.- If we have a Shopping Cart with two items, the first one requires only one level of approval, and the second one, two levels. Both items will result in a different follow-on document. If the 1st item is fully approved. Will we have to wait till the second item is approved to get the follow-on document for the 1st item?

2.- The same case than above. The 1st item is fully approved and the second item is approved in the first level and rejected in the second level. If the requester changes the second item and sends if again for approval. Will be the first item sent again for approval?

Many thanks in advance for your anwers

Regards

Valentí

[Former Member · Accepted solution]

Hi,

1.- If we have a Shopping Cart with two items, the first one requires only one level of approval, and the second one, two levels. Both items will result in a different follow-on document. If the 1st item is fully approved. Will we have to wait till the second item is approved to get the follow-on document for the 1st item?

This is standard, you can't let create a PO for only first item while the second line item is awaiting for approval. you can only create the follow on document when whole SC is approved .

2.- The same case than above. The 1st item is fully approved and the second item is approved in the first level and rejected in the second level. If the requester changes the second item and sends if again for approval. Will be the first item sent again for approval?

Yes . when the system restart the workflow.

Saravanan

[Former Member · Accepted solution]

Hello: the answer to the first question is crystal clear to me. While at least one item in the SC has not been approved, the follow-on documen is not created. One additional question: if one item is rejected and the requester accepts the approver decision, the follow-on document is created for the approved items, isn't it?

But, regarding the second question: imagine the two items are to be approved by different approvers. If one of them approves his item and the other one rejects, when the requester modifies the rejected item and send it again for approval, why the item that was approved in the beginning must be approved again?. Is there any way to avoid it?

Thanks in advance

Regards

Valentí

[Former Member · Accepted solution]

Hi,

Hello: the answer to the first question is crystal clear to me. While at least one item in the SC has not been approved, the follow-on documen is not created. One additional question: if one item is rejected and the requester accepts the approver decision, the follow-on document is created for the approved items, isn't it?

yes - if you have line based approval, if the SC has two line items and one rejected and one approved then system will create a follow on document for the one got approved.

But, regarding the second question: imagine the two items are to be approved by different approvers. If one of them approves his item and the other one rejects, when the requester modifies the rejected item and send it again for approval, why the item that was approved in the beginning must be approved again?. Is there any way to avoid it?

this is standard.

Saravanan

[Former Member · Accepted solution]

Hello Saravanan

Thanks for your reply. I will try to explain what we did so far and the reason for our question.

We want to implement an item-basd approval WF. to do so, we created one area of responsibility per item with method GET_AREA_TO_ITEM_MAP.

For each level in the schema, we determine if the level will be executed or not depending on the value for the most expensive item. Maximum number of levels is 3.

Imagine we have 2 items. The first item will require 1 approval level. Second item will require 3 approval levels. So, for both items, the 3 levels in the process schema will be executed.

For the first item, requiring one level of approval, in the first level system will determine the correct approver, while in the second and third level, approval will be automatically done by the system. For the second item system will determine the three levels with the correct approvers in place.

First question: is it possible to avoid having the additional two levels with system approval for the first item?

Item 1

Level 1--> approver 1

Level 2 --> system

Level 3 --> system

Item 2

Level 1--> approver 1

Level 2 --> approver 2

Level 3 --> approver 3

If we can avoid the situation above, maybe if item 2 is rejected in level 3 while item 1 is fully approved, if requester edits the SC during the process of "Revise" SC, item 1 is not sent again for approval

Our problem is that we did not get to determine different number of levels for different items, because if a level is to be executed or not is determined for the whole SC not item by item. Or maybe we are wrong.

Thanks in advance for your reply

Best regards

Valentí

[Former Member · Accepted solution]

Hi,

This is standard, we can't build the logic to determine the level approver''s based on each line item. for example.

process level 100.

SC has 2 line item. you want the first item to be approved by only one approver, but the second you want to approve by 3 level of approvers. the system will send the second item to 2 and 3 level but the approval history shows for line 1 of level 2 and 3 as system in order to completed the process level.

Saravanan