There are a number of utility programs available in the Transport Expresso domain controller that enables you to report on the TE system. Each of these are described below.
A /BTI/TE menu is available giving access to the key ones.
|*Report Name / Transactio*n
|/BTI/TE_RTASK_STATUS_REPORT / /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
|/BTI/TE_RACTIVITY_EVENTS / /BTI/TE_RACT_EVENTS
| This report can be used to show an audit of Transport Expresso activities and events. This includes Imports (including import errors), Approvals, 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
|/BTI/TE_RIMPORT_AUDIT / /BTI/TE_RIMP_AUDIT
| This report provides an audit of transport imports allowing imports carried out in Transport Expresso 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 Transport Express
|/BTI/TE_RANALYSIS_RUN_HISTORY / /BTI/TE_RANAL_HIST
| When an analysis is performed the results of the analysis run are stored in the TE database. This 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)
| This report provides transport and location information as follows:
|/BTI/TE_RU001 / /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
|/BTI/TE_RTRANSPORT_IMPSTATUS / /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 TE view of the transport request (i.e. whether TE 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.
|/BTI/TE_RTRANSPORT_LOCATION / /BTI/TE_RTR_LOCATION
|The Transport Location report displays all transport forms belong to a particular Project or Transport path and where they current “sit” within the landscape.
|/BTI/TE_RMERGE_RECONCILIATION / /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.
|/BTI/TE_RTRANSPORT_MERGE / /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.
|/BTI/TE_RSYSTEM_COMPARISON / /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.
|/BTI/TE_RANALYSIS_CONFIG / /BTI/TE_RANAL_CONFIG
|The analysis configuration report provides a view of which analysis types are switched on for specific targets / locations in Transport Expresso. 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.
|This report provides an overview of the roles and users assigned to the selected tasks and an overview of the changes to both deployment and planning statuses
|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
| This report will give totals 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.
|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.
|This report shows the details of all active delegations in Transport Express
|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
|This new utility can be run to remove all of the Transport Forms over a certain age from any particular Control Point. Any Transport Forms that have been in the selected Control Point for more than the configured number of days are ‘completed’ and removed from the Path
|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
Thanks for your feedback.