ChaRM on implementation Projects
I have a conceptual question regarding the use of ChaRM on Implementation projects.
We are using ChaRM and have ensured that CTS is driven from Solution Manager i.e transport requests can only be created from corrections (SDMI). To date all SDMI's have been created as follow on documents to Change Transactions (SDCR). Going forward we would like to differentiate genuine changes (Changes to scope after blueprint sign off) from implementation activities driven from blueprinted requirements.
Whilst we see benefit from approval workflows for genuine changes, it is quite a chore to create SDCR's for all regular implementation work which is implicitly approved by signed off blueprint.
It is also difficult for us to then differentiate Changes from Implementation SDCR's.
Can anyone see a problem with all implementation tasks being generated directly as SDMI's with no preceding SDCR whilst leaving genuine changes as SDCR generated corrections?
The only one I can think of so far is that there is workflow that sets the status on an SDCR when the SDMI has been through it's lifecycle although I'm not sure how the system would behave if there is no SDCR.