Deep Impact Analysis (0023) can be used to highlight the lower level dependencies between the repository objects contained within the transport(s) being analysed and other transports existing in the landscape. This can be used to avoid deployment errors where transports are imported without the necessary dependent objects being present in the target SAP system.
The process 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 transported, a check would be made to ensure that all referenced data elements are not missing. The same would apply to a program being transported to ensure that any referenced data dictionary objects, function modules, classes, methods, etc. are not missing. This can then reduce the number of import failures due to hidden dependencies between changes and transports.
Deep Impact Analysis is used to perform technical / repository checks so therefore doesn’t include configuration objects in its analysis.
Note that there is some pre-requisite Diffuser configuration setup that needs to be performed for Deep Impact Analysis (0023) to run correctly. This is detailed in this FAQ.
|GROUP_IMPORT_METHODS||Fast import/Import All methods to ignore transport sequence. Default is methods 2 and 5.|
|IGNORE_SEQUENCE||Ignore the transport sequence when calculating missing dependencies (transports with missing dependent objects that are contained in transports later in the import sequence will not be reported) . If not set then Fast import/Import All methods specified in GROUP_IMPORT_METHODS will ignore the transport sequence anyway. It’s good practice to set IGNORE_SEQUENCE = ‘X’ on non-Import Queue.|
|LEVELS||Specify the number of levels to go down in object hierarchy.|
|MAX_OBJ_TIME||Maximum time to analyse an object. Default = 60 seconds.|