Features & Enhancements

1) Impact on Fiori applications and OData services

UI5 based Fiori applications and OData services are now top-level objects in ActiveDiscover. They are considered entry points to the system and are reported just like other application types (SAP GUI transactions, RFCs, etc.).

Figure AD130-01: UI5 objects as top-level objects.

1.1) UI5 application impact from an OData service

Relationships between UI5 applications and OData services are now detected by ActiveDiscover, so if an OData service is modified and is declared to be used by an UI5 application, the impact on the UI5 application is reported. Both classic (SEGW based) and CDS view based OData services are supported.

Figure AD130-02: Object relation details

1.2) UI5 application impact from a role change (through a Fiori Tile Catalog)

If a role containing a Fiori Tile Catalog has changed, the UI5 applications in the relevant catalog are reported as being impacted.

1.3) Embedded and standalone front-end server

ActiveDiscover supports both the embedded and the standalone front-end server setup for the Fiori Launchpad.

The standalone front-end server can be linked to the source and target systems in the landscape configuration section. When a UI5 application is found to be impacted, it is indicated in the object list that it resides on the standalone front-end server.

Figure AD130-03: Standalone front-end server

1.4) CDS view relationships

The tool can now recognize relationships and changes around CDS views which helps extending the impact analysis for OData services in particular.

ActiveDiscover is able to find relationships between CDS views through associations or JOINs, relationships between CDS views and transparent tables, and relationships between DCLs (Data Control Language) objects and CDS views.

2) Analysis schedules

During the analysis setup, now it is possible to set up the analysis to run periodically with the same settings.

Figure AD130-04a: Schedule periodic analysis runs

This step creates an analysis schedule. Analysis schedules can be managed in the new Analysis Schedules tab on the Analysis Runs page.

Figure AD130-04b: Analysis schedules tab

3) Run an analysis on a set of transport based on selection criteria

During the analysis setup, in addition to selecting individual transports in the system as a source, now it is also possible to define selection criteria, based on which the matching transports will be picked up and analyzed automatically. (This is especially useful together with analysis schedules.)

Figure AD130-05: Analysis transport selection criteria

4) Impact on security roles

ActiveDiscover can now report impact on security roles and has dedicated sections on the dashboard to report this. It is highlighted if a direct change has been made to a role, and the tool can also detect if a composite role has been impacted via changing a related single role.

Impacted roles are also prioritized based on the number of assigned users.

Figure AD130-06: Impacted roles

5) Impact categories

The list of impacted objects now features a new Impact Category field. The purpose of this is to give the user a quick way to assess the reason why a top-level object got identified as being impacted (eg. Dictionary Change, Repository Change, Security Role Change, Customizing Change etc.).

Figure AD130-07: Impact category

6) Improvements to the accuracy of Key Difference Identification (previously called Failure Prediction)

In ActiveDiscover version 1.20 and lower, the Key Difference Identification module (previously called Failure Prediction) carried out all checks for every impacted top level that has been found. This sometimes led to noisy results as differences unrelated to the change being analyzed were also identified.

Now only those checks are performed that are related to the current change, removing the irrelevant messages.

7) Impact analysis for SAP Extended Warehouse Management

If the source system of the change being analyzed has the Extended Warehouse Management module installed, ActiveDiscover can now identify impacted logical transactions in the RF framework, helping with narrowing down the scope of the change in an EWM context more accurately.

Figure AD130-08: Impact analysis on SAP EWM

8) Option to ignore customizing changes in impact analysis

Customizing entries in a transport (object types CDAT, VDAT, TDAT, TABU) related certain core tables can result in a huge number of impacted objects, rendering the results hard to interpret.

The analysis setup page now features an option to ignore these objects during the run.

Figure AD130-09: Option to include or exclude customizing changes