ActiveControl includes a number of out-of-the-box Reports aimed at cutting out the need for spreadsheets and manual analysis performed within many organisations as part of the delivery of SAP change.

Most of these Reports are available in the Windows GUI and Web UI. All of them are available via transactions in the SAP GUI of the Domain Controller.

Report Name Transaction Description
Task Status Report /n//BTI/TE_RTASK_STATUS This operational report gives detailed project and task level status information. It provide a snap shot of the status of projects giving both detailed and summary information about the status of all items relating to the projects.
Some of the key data that can be reported upon is:
• Project/Task/Transport reporting showing the current deployment status (e.g. In development, In test, Awaiting production, etc.)
• Project/Task reporting showing the current planning status
• The full details of all items returned (Projects/Tasks/Transports) for the selected criteria are available along with a high level summary of the number of items in each status
Transport & Task Activity & Events Audit /n/BTI/TE_RACT_EVENTS This report can be used to show an audit of ActiveControl activities and events. This includes Imports (including import errors), Inbox/Outbox approvals and rejections, Test Signoff approvals or rejections, Mark as Imported, Mark as Manually Applied, Added to Import Queue, Added to Control Point, etc.
The data can be reported at transport level or task and project level as required
Import Audit Report (AC / SAP comparison) /n/BTI/TE_RIMP_AUDIT This report provides an audit of transport imports allowing imports carried out in ActiveControl to be compared to those performed in SAP / STMS so differences can be highlighted.
It can be used find transports imported via SMTS that need to be updated in ActiveControl.
Change Analysis History Report /n/BTI/TE_RANAL_HIST When an analysis is performed the results of the analysis run are stored in the ActiveControl database. This Report provides a history of analysis issues along with the action taken by the user.
The change analysis history report allows this history to be reported upon. It gives the full details of the analysis issues along with the action taken by the user (e.g. Approve anyway)
Transport Locn by Date/Obj/Proj/Ownr /n/BTI/TE_RTRAN_LOCN This report provides transport and location information as follows:
  • Retention: For a selected period, the transports with import date/time and duration of “retention” in all relevant systems in the selected transport path
  • Object: For one or more objects, the transports imported in selected systems
  • Project: For a project, where the relevant transports are located
  • Owner: For one or more transport owners, where the relevant transports are located
Transport Request Conflict Analysis /n/BTI/TE_RCONFLCT_ANL The conflict analysis report is used to report on conflict analysis issues during the merge process. It can be executed for a specific merge target and all conflicting transports are reported. Each transport can be double-clicked to view the object details
Transport Import Progress by Path /n/BTI/TE_RTR_IMPSTAT The Import Status report displays all transport requests for a given transport path and into which systems the transport has been imported. The report allows for you to specify whether you want the ActiveControl view of the transport request (i.e. whether ActiveControl believes the transport was imported) or via the TMS view which examines the transport logs to determine whether the transport was imported. Alternatively, both views can be combined. Each system in the transport path is displayed dynamically, and whether the transport has or hasn’t been imported into that given target is displayed.
Transport Locn by Date/Obj/Proj/Ownr /n/BTI/TE_RTRAN_LOCN The Transport Location report displays all Transport Forms belonging to a particular Project or Transport path and where they current “sit” within the landscape.
Transport & Merge Recon. Report /n/BTI/TE_RMERGE_RECON The transport and merge reconciliation report is used to provide reconciliation from the original transport to all related merge transports along with an import status to show which systems the transport has been imported into. It provides a linkage into all merged systems so the progress of the original transport can be fully tracked.
Transport Merge Report /n/BTI/TE_RTR_MERGE The Transport Merge report should be run during and just prior to the release of a project (or upgrade project) that is currently using the “Merge” process.
During the merge process, Production Support transport requests are merged into the future release / project and this is either done manually or automatically. In either case, this report displays all Production Support transport requests and the corresponding merge request that they were merged into the project/release on.
This report should be run during and just prior to the project/release to ensure that the Production Support transports have all been fully merged and that no regression will occur when the project is set live.
Merge & Conflict Manager /n/BTI/TE_RMERGE_CONF Used to manage merges and conflicts in dual track landscapes.
System Change Comparison Report /n/BTI/TE_RSYSTEM_COMP The System Comparison report allows you to compare two target systems to determine what differences exist between what has been imported into each. A break-down of the missing transport requests (and Tasks) is provided enabling you to take appropriate steps.
Analysis Config Report /n/BTI/TE_RANAL_CONFIG The analysis configuration report provides a view of which analysis types are switched on for specific targets / locations in ActiveControl. The yellow icon shows where the analysis is switched on for the location and the green icon indicates where it’s mandatory. Clicking on the items will show a popup if there are any parameters entered.
Open Transports by System & Chg Date /n/BTI/TE_ROPEN_TRANS This report can be used to identify old/orphan unreleased transports that are present in development systems and haven’t been changed since a specified date. This is useful to aid in the clean-up activity of unrequired transports
Change Metrics Report /n/BTI/TE_RCHG_METRICS This report will give total number of transport imports (and associated tasks) into selected systems for a date / time range.
It can be used to report metrics for systems and projects by priority, group, type, etc.
Test Results Entry Report /n/BTI/TE_RTEST_RESULT This report can be used to give visibility to all test results entered for multiple Business Tasks or even a whole project. It will show negative and positive entries for each Business Task and any comments entered.
Delegations Report /n/BTI/TE_RDELEGATIONS This report shows the details of all active delegations in ActiveControl.
Transport Import Status across Paths /n/BTI/TE_RTR_IMPPATHS This report is an extension of the Import Status Report, but allows you to view transports over multiple paths. For the report to format the data properly, the Roles assigned to each Target must be consistent across the paths
Build List Report /n/BTI/TE_BUILD_LIST This report allows you to sequence all Transports and manual activities for a group of transports in a control point and to give estimated timings using previous import history. This report allows you to create an always up-to-date build list for project cut-overs
Risk Analysis Report /n/BTI/TE_RRISK_ANLSIS This report is used to identify transports containing objects contained in a specific set of risk groups.
This can be useful for enabling a retrospective analysis on changes made to critical objects / blacklists etc.
It is based on current Risk Guard group / template locking functionality.
Change Documents Report /n/BTI/TE_RCHANGE_DOCS Audit Report to be able to track what configuration level changes have been done within ActiveControl. This includes config to (i) Targets , (ii) Approvers, (iii) Paths, (iv) Control points, (v) Groups, (vi) Admins, (vii) Analysers and (viii) User Roles.
System Rebuild Report /n/BTI/TE_USYS_REBUILD Basis / Administrator report that can be run in the backend to help with system refreshes and copybacks. The report identifies missing transports after a rebuild/refresh based on a specific date – ie to reapply transports that were previously applied in the refreshed system that had not yet reached the source system of the refresh (eg Production). When not run in test mode this can also be used to add transports back into the relevant import queue as well.

Feedback

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