In some cases, the policy described above will not be sufficiently flexible. For example, it may be necessary to make changes to some business objects directly on the production system, where the danger of issues arising is low, and where the overhead of creating business objects on a different system, and then transporting them, is considered too high.
In this case, the recommendation is that a clear distinction is made between business object types are going to be managed locally, and those that will be managed using standard development lifecycle practices, leveraging CTM as detailed above. CTM should then only be used with business objects where the business object type is being managed using standard development lifecycle practices. It should not be used to transport business objects where the business object type is being managed locally on the production system.