SAP Management of Change: From a Start-Start to a Finish-Start way of working
Dear SAP Community,
complex changes in the industry require a well-thought Management of Change process to meet both regulatory and company-internal standards. The reliability, availability, maintainability, safety, and security of products and production facilities have become the key criteria for long term success of our customers.
A way to handle simple and complex changes affecting products and/or production facilities is SAP Management of Change.
When it comes to the review, approval, and implementation of a change process, SAP Management of Change uses a set of pre-defined activity templates. The dependency of those activity templates is delivered as a start-start dependency. A start-start dependency means that a predecessor activity must start before the succeeding activity can start.
However, the dependency can also be changed to a finish-start dependency by calling a re-calculation of the due dates of the succeeding activity. A finish-start dependency ensures that the predecessor activity must finish before starting the succeeding activity.
The main difference between both dependencies is the way the duration of the activities can be handled in the customizing. Using start-start dependency forces all tasks running in a sequence to have durations aggregated based on the successor activities. This calculation may cause some headaches and additional work when the duration of an early stage activity changes. Therefore, a finish-start dependency can be used so that only the duration of the current activity must be taken care of and the duration of any predecessor activities must not be taken care of.
The above concept makes configuration for SAP Management of Change quite a bit easier. I’m looking forward to hear your take on that and which dependencies you are using in your SAP Management of Change implementations.
With kind regards,
The link on the MoC webpage 'Solution Brief' is broken : this link doesn't work.