Can we change the fully approved SC?

[Former Member]

Dear SAP experts,

We are in SRM 7.01 with backend ECC 6.05. I have a simple question, can we change a SC that is already fully approved? As in ECC, though the PR are already fully released, we can change the PR and as the result the PR release strategy can be restarted.

Can we have the same functionality for SC in SRM?

Best regards,

Josh

[robin_janke]

Hi,

I think that in the sourcing cockpit you can change the shopping cart, however I don't think you can achieve editing while there are valid follow-on documents.

Regards,

Robin

[ricardo_cavedini]

Hello,

It is not possible to change the cart after fully approved.

In SRM 7.0 there is the edit button for approved carts, but this is intended to enable the delete button at item level and not to change the document itself.

Regards,

Ricardo

[Former Member]

For SRM 7,another obesrevtaion regarding the change of carts after fully approved...The cart can be edited for the field "SOURCE OF SUPPLY" also.

[Former Member]

Hi,

Whether the SC requester can change the SC or not is determined by the parameter "BBP_WFL_SECURITY" under the personlization tab in trascn PFCG for the SC creator role(e.g. EMPLOYEE role).

To change the SC,the SC creator will be able to see a CHANGE button on the Screen to make the changes and resend the SC for approval.in order to get the change button, the parameter setting level should be atleast "Low".

See the foll details on security level:

Security Levels

Each user in the SRM system can have a Security Level.

The Security Level predicts how a workflow will react when a change has been made to a business docuement. I.e. A Shopping Cart, Purchase Order etc.

There are 5 different values for the BBP_WFL_SECURITY and there are several ways to check the security levels.

Checking the Security Level of a user

Here I discuss two ways to check the BBP_WFL_SECURITY of a user. The first is by using the Business Object Builder and the second is by using User Maintenance.

1) Business Object Builder: SWO1

Logon with a user who is authorized to access transaction SWO1 Business Object Builder.

Enter the Business Object for a SRM User BUS4101 and press 'Test'. Now press the 'Instance' button to give us the ability to examine the user. Enter the user name of the user and execute. Now we can see many of the attributes that are associated with this user. The Security level of the user is available here. The value is the BBP_WFL_SECURITY for the instanced user.

2) User Maintenance: SU01

Logon with a user who is authorized to access transaction SU01 User Maintenance.

Enter the 'Username' of the user. You can now see much of the data that is associated with this user. To check the users security level we must navigate to the 'Personalization Tab'. Now Double-Click on the object key 'BBP_WFL_SECURITY'.

Security Level Definition

As mentioned above, there are 5 different Security Level values that can be assigned to a user, each of which will have a different effect on a workflow when the associated business document has been changed. These range from 0-4 and they can be maintained for each user in User Maintenance (SU01 -> Personalization Tab -> BBP_WFL_SECURITY), provided the user you have logged on with has the ability to make changes to these settings.

Please note that if the customer has an active implementation of the BBP_WFL_SECUR_BADI, it is possible that the BBP_WFL_SECURITY settings in the database can be overridden.

BBP_WFL_SECURITY = 4 High

If the user who changes the purchasing document has their security level set to 'High', the workflow will never restart after the change has taken place. No restart flag has been set in BBP_PDH_WFL_CHECK_RESTART. Again, as mentioned above, the BADI can override these settings.

BBP_WFL_SECURITY = 3 Medium

If the user who changes the purchasing document has their security level set to 'Medium', the workflow will re-evaluate the starting conditions of the workflow. If the change made to the document means that the starting conditions of a new workflow are satisfied, then the new workflow will be called and replace the old workflow. The existing workflow will be terminated.

If, however, no other starting conditions have been satisfied, then the workflow will continue. Again, as mentioned above, the BADI can override these settings.

BBP_WFL_SECURITY = 2 Low

If the user who changes the purchasing document has their security level set to 'Low', then the workflow will always restart after the change has been made. The restart flag in function module BBP_PDH_WFL_CHECK_RESTART will be flagged. Again, as mentioned above, the BADI can override these settings.

BBP_WFL_SECURITY = 1 None

Here the user does not have a security setting and changes to the document at not possible. Again, as mentioned above, the BADI can override these settings.

BBP_WFL_SECURITY = 0 Not Defined

When the setting is '0', however, the value is INITIAL. Again, as mentioned above, the BADI can override these settings.

It is wise to note that depending on the business document there are differences in how changes will effect a workflow! Please see the function module BBP_PDH_WFL_CHECK_RESTART to see these exactly!

RBEI SRM/Snehal

[former_member208675]

Hi,

No. There is no way you can change/update approved SC. If you want to change SC; it is to be done in approval stage.

I hope it resolves your doubt.

Regards,

[Former Member]

Hi Josh,

I am not sure the shopping cart can be changed after fully approved.

The changes can be possible when status "Save" and "waiting for approval".

In ERP system the business process(procurement process) is entirely different forexample if we take your case as example the PR has to be converted into PO by purchaser manually even PR got fully released.So during that time the changes can be possible and workflow can be regenerated and as it is internal document.

But in SAP SRM system the follow on document creates immediately when shopping cart gets approved fully. So here no changes are allowed.

Hope you can understand the difference procurement process in ERP and SRM.

Regards,

RBEI/SRM Naga.