Earlier in 2020, a customer reported a scenario whereby Deep Impact Analysis (0060) was reporting missing dependent objects against a Development system when running DIA between QA and Production, when in fact those missing objects were actually always only intended to remain in the Development system and never be transported to QA and Production.
As such, the Customer requested a solution whereby you can specific the Reference target where the dependency needs to be checked. This would therefore allow them to run the Deep Impact Analysis (0060) between their QA system and Production, and not get ‘spurious missing dependancies for objects that were only ever meant to remain in Development SAP system.
ActiveControl 8.3 introduces the capability to define the Reference Target to check for Dependencies.
Optional new Parameter EXISTS_IN_REF_TARGET should be set to the Reference Target system number in which the Dependency needs to be checked again.
As an example, if your landscape is DEV > QA > PROD – and you are running Analyser between QA and Production, if the analyser finds some missing object dependency in Production, if you have set EXISTS_IN_REF_TARGET as the QA system, then it will look to see if the object exists in QA. If it does not, then the Analyser will exclude that object depedency from the Analyser results.
Figure: New Parameter has been added to the 0060 Deep Impact Analysis (New) analyser.
More information can be found in this online Change Note.
Post your comment on this topic.