on 2022 Apr 08 9:19 PM
Hello Team,
we are on 2021 BRIM version and I am seeing the behavior in the system that once a calloff order has been created from master agreement , VC configuration on the item on the master agreement become non editable. What is the rational for SAP in providing this behavior on the master agreement? why not allow VC configuration change so new call offs can reflect this update? Trying to understand why this is designed this way. Thanks.
Hi Chetan,
Master agreement attributes cannot be edited as soon as the item is released irrespective of whether Call Off documents have been created or not. Of course, you cannot set the status back to In process if subsequent documents exist. The purpose of master agreement is to define attributes (like billing cycle, CCM version, prices, configuration etc.) which must be held true when subscription orders/ solution quotations are created from its reference.
With configuration, it is also possible to set the configuration status in master agreement item. If the status is "Fixed" then the configuration values are copied to the subsequent subscription order/ solution quote and they cannot be changed there. If the status is "Not Fixed" then the copied configuration values can be changed in subsequent subscription order/ solution quote.
If certain attributes are required to be changed in master agreement then you can create successor item in master agreement which delimits the old item and new item can have desired attributes. New Call Off documents can be then created with reference to existing item or successor item based on validity of that item.
I do not understand the requirement of changing the attributes of an existing master agreement item after creating subsequent Call Off documents. Can you elaborate please? Thanks.
Regards
Deepak
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Deepak,
the purpose of the master agreement that we are using is not only to capture common attributes but also to treat it like true master contract document. We do have BP hierarchies and we create subscription contracts at a lower level BP in the hierarchy as our usage is at that level+ few other reasons. Given this background, we do get some changes from time to time for attributes like minimum commitment amounts, commitment period etc which are captured as VC. So now when change happens for these parameters, we want to be able to update them and see the new call offs getting this updated VC values.
Based on your explanation, looks like SAP has not designed the master agreement this way and you need expire the line and re enter it with new VC.
However if I am having a sharing contract scenario on top of above situation, would I be able to transfer the sharing contract to new line item? Not sure how this will effect CC side calculation. Do you have any input that you can share here? Thanks.
User | Count |
---|---|
10 | |
5 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.