The new Deep Impact Analysis function is available to highlight the lower level dependencies between the objects contained within transports being analysed and other transports existing in the landscape. It checks the objects included in the analysed transports and determines whether any of the objects referenced within those are either part of the group of changes being approved/imported or have already been imported beforehand.
For example, if a database table is being imported into a QA system, a check would be made to ensure that all referenced data elements are not missing in the system. The same would apply to a program being transported to ensure that any referenced data dictionary objects, function modules, classes, methods, etc. are all present. This can then reduce the number of import failures due to hidden dependencies between changes and transports.
Even small development teams suffer from the issue whereby one developer uses objects created by another in different change. For distributed and off-shore teams this becomes more of an issue. The Deep Impact Inspector can be used to significantly reduce the issues caused by this.
Note that there is some pre-requisite software and configuration setup that needs to be performed for the Deep Impact Inspector analysis check to run correctly. Please refer to the Administration Guide for details of this setup.
Post your comment on this topic.