cancel
Showing results for 
Search instead for 
Did you mean: 

FA approver changes should not lead the cart to buyer

Former Member
0 Kudos

Hi all,

FA(Financial approver) changes the Product category, cart should not go back to buyers and if there is the change in Purchase types then it should redetermine approvals based on new purchase types.

In our current scenario, if FA approver changes the product category then it leads the cart to buyer for sourcing.so now the requirement is if FA approver changes the product category it should not leads to buyer.

Please suggest your thoughts to proceed.

thanks,

sibi.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks

Former Member
0 Kudos

Thanks

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

Please check the BBP_WFL_SECURITY personalization key in personalization tab of PFCG or SU01 transaction.

BBP_WFL_SECUR_BADI is also available.

No authorization

Changes to the document are not allowed while it is being approved.

Low

Changes can be made to the document. The approval workflow is restarted after every change.

Medium

Changes can be made to the document. After every change, the approval workflow either continues or is restarted.

The system evaluates the start conditions and restarts the workflow if a new approval is required as a result of the change. If this is not the case, the approval workflow continues.

High

Changes can be made to the document. The current approval process always continues. A new approval workflow is not started when the document is changed.

Regards,

Masa

Former Member
0 Kudos

Hi,

Please check workflow restart condition.

Due to restart workflow restart condition at product category change, may be cart approval is flowing back to Buyers.

Now it would re-determine the new purchasers in new workflow.

-

Former Member
0 Kudos

Hi All,

the start condtion does not have product category change ,i beleive when there is change in product category, automatically Source of supply gets disappeared, was this a standard bug in SRM5.0?

Please post your views in this regard.

Thanks,

Prem