Shoppig cart triggers Approvers hierachy from the begining

[Former Member]

Hi,

There is one issue... when shopping cart value changed by the user ....then it starts approval process from the beginning.. we want that it should not start from the beginning.

Suppose a shopping cart is being created on 25th Feb 2008 with a value 200USD. On 1st March 2008 the value of shopping cart is changed due to change in taxes. Then it is going for approval from the beginning. But I want it should not start from the beginning, it should start from the level it is being approved and onwards.

I also want to know whether this is standard flow of SAP. Please reply me as soon as possible.

Regards

Praveen Kumar Ghosh

[Former Member]

Thanks Imthiaz,

Your solution worked. I wrote to SAP and what they have updated I m pasting here

Authorization to Change During Approval

You can use the Business Add-In (BAdI) BBP_WFL_SECUR_BADI to determine

whether

A shopping cart can be changed during the approval process

The approval workflow restarts when changes are made to the document

A reviewer/approver can be added or changed

These are the call scenarios (see import parameter SCENARIO).

You use this BAdI to overwrite the settings for the authorization level

of approver. The BAdI is called each time the shopping cart screen is

opened and whenever a purchase order is ordered and held.

For more information, see the SAP Note 502952.

Example

You use this BAdI to prevent the approval workflow from starting again

if the manager changes only the cost center of a shopping cart during

the approval process.

Standard settings

Rejection of a shopping cart item causes the approval process to be

restarted (dependent on workflow start conditions and authorization

level). SAP supplies a BAdI-Implementation that prevents a restart if

you set the authorization level of the approver to "not defined".

The standard system features the following authorization levels, which

you can set in user maintenance (transaction SU01) or role maintenance

(transaction PFCG) on the Personalization tab. Note that user settings

override role settings:

Not defined Initial setting: Authorization level on delivery.

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.

Note: if the approver is assigned several roles, the system uses the

highest authorization level.

Activities

The following parameters are provided in the SET_SECURITY_LEVEL method:

Import

ACTUAL_USER (user whose authorization level is overridden)

OBJECT_ID (transaction number of the document

OBJECT_TYPE (business process type)

GUID (unique document key)

SCENARIO (scenarios in which the BAdI is called).

Export

NEW_SEC_LEVEL (determined authorization level)

[imthiaz_ahmed]

Questions related to SRM will be better answered in SRM forum, Still here is the answer to your question. SRM has this std functionality. Based on the user's WF security level which can be set at the role level or the user level personalization tab, the WF 4 -never restarts, 2 - always restarts, 3 - restarts conditionally, 0 -no changes allowed.

Regards,

Imthiaz