Test Impact Radar (0043) analysis can be used to highlight what top level SAP objects (e.g. Transactions, programs, etc.) are impacted by the selected transport(s). For example, if a database table structure was changed it could be used to identify all transactions and programs that use that table to help target testing effort.

It can also indicate what Test Scripts are impacted by the changes in the transports if these have been uploaded into ActiveControl. I.e. identify what test scripts should be executed at a minimum as a result of the changes contained in the transports.

Note that there is some pre-requisite setup that needs to be performed for the Test Impact Radar analysis check to run correctly. Please refer to ‘Test Impact Radar’ section of this Administration Guide for details of this setup.


Parameter Description
CHECK_LINKS Check if the link creation is up to date.
MAX_LEVEL Maximum recursion level for analyser (Default = 10).
MAX_OBJ_TIME Maximum time to analyse an object (Default = 60 seconds).
TARGET Target ID where the dependencies will be checked.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment