ActiveControl 8.2 introduces the ability to report on customising transports as part of ‘Top Level Object’ reporting as part of Test Impact Radar (0043), to enable a complete view of all functions impacted by a release that contains both customising and repository objects.

Example. Program 1 code refers to Table 1. If you analyse a transport containing a change to Table 1, Program 1 will now be reported by Test Impact Radar.

Note that the enhanced analyser does not analyse the contents of a customising entry change, it only indicates that a customising change has been made.


The object types to check for must be configured in /BTI/TE_TR_TABTY.

If you leave this table entry, you will get error described in this Knowledge Article.


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