on 03-07-2017 3:58 PM
Dear All,
I'm facing an issue with contract release strategy; coudl you please help ?
We have release strategies of contract based on target value of contract (depending on amount, contract belong to a specific strategy).
At some point in time, the number of strategies has been changed and the target amount as well.
Let's say for example, before change, contract with amount 10 000€ where part of S1, after change they should be part of strategy S2.
For new contract, no impact, they are assigned to appropriate strategy.
For old contract we do have issues.
Example :
contract 460000001 has target amount 10 000, it is created before the customizing change, it is assigned to strategy S1.
The release procedure is completed.
After customizing change, I change the target valuer of 460000001, instead of 10000, I set 11 000.
11000 with new customizing correspond to Strategy S2 but system :
- do not reassign 460000001 to new strategy S2
- do not initialize the status of release procedure, despite the change in amount, the contract remain consider as released.
IS there a best practice to handle that situation ?
Thank you for kind help
best regards
Morgan
In that note, they say that the solutiojn is "to explicitly trigger the determination of a new release strategy for the document concerned."
Do you know what it meaned by that and how to do so ?
Obviously it is not just about changing an information in the document because, we did that several time without a new strategy to be assigned to the document, like nothing happened at all.
To answer to the first question, most of the document concerned have a release indicator with changeable status "4 - changeable, new release in case of new Strat. or val. Change".
And, even changing the value does not have an impact.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I admit it is late Jürgen but ... I was not working for that company when that change as been implemented.
Now, I have to maintain it and face the result.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Asking for best practice after the fact is a little late. As the best practice is to avoid changing release strategies
The KBA 1635346 has this sentence "You must absolutely avoid changes to release strategy customizing once the release strategy is in use. Please read question 6 of note 365604 about this"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you checked the release indicator for your release strategy ?
Be confirmed that you are using correct changeable for release indicator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.