Reporting upon transports
ABAP transports are store for each managed system in its own config store called ABAP_TRANSPORTS.
Change Reporting showing config store ABAP_TRANSPORTS. All config stores containing software level related config items are store in config store group ABAP-SOFTWARE
Configuration Validation offers via Reporting Directory several reports upon transports such as:
- Production backlog
The goal of this report is to find the transports which are released in Development system (DEV) but not yet imported into Production system (PROD). For this purpose a Target System will be generated and filled with the actual transport requests that have been created in the provided Development system (DEV) and have the TRSTATUS different to "D".
- Development backlog
The goal of this report is to find the transports which are created in DEV but not yet released in DEV.
- Failed transports
The goal of this report is to find the transports which are failed (RETCOD > 4).
- Local transports
The goal of this report is to find the transports which are created in the provided system.
Reporting Directory using "Display SAP reports": Shows all reports with predefined rules to get a specific reporting immediately.
Reporting of Production Backlog:
Transports that are parked in the import buffer of QAS and PRD cause inconsistencies within the transport landscape. Changes should be quickly forwarded from DEV to QAS and PRD in order to keep the transport landscape consistent.
Execution of the predefined report 0PRDBLG in the Report Directory shows which transports were released in a selected development system (SD7) but not yet imported into a selected production system (SI7).
Please refere to the 0PRDBLG Report in the Report Directory section for a detailed description of this report.
Reporting of Development Backlog:
The number of open transport requests in the development system indicate the number of ongoing changes.
The development backlog should be kept small. That means transport requests must be released in a timely manner. Open transport requests which are not updated for a certain time should be analyzed. If they are still needed they should be released. If they are not needed any more, the changes should be backed out. Open transport requests in the development system cause inconsistencies with the production system.
Reporting of local transports:
The amount of transports which created directly in production (emergency changes) identifies to what degree SAP best practice procedures for software development are followed.
The predefined report 0LOCTRA from the Report Directory support customer for the following activities
- Make sure that all changes are performed in the development system and deployed to production after sufficient testing
- Provide worklist to analyze the root causes of the emergency changes
- Introduce methods and procedures to minimize the ad-hoc change
Reporting on failed transports:
The amount of failed changes identifies problems in production due to software changes. It is an indicator for the quality of the software change management processes. In addition it provides worklists with currently existing problems in production.
The predefined report 0BADTRA from the Report Directory support customer for the following activities
- Control the quality of the software change management processes and take corrective measures if needed
- Provide worklist to analyze the root causes of the failed changes
- Provide guidelines to remove old object versions in production due to wrong transport sequences