No ChaRM? You Can Still Easily Track Transports
- by Narendra Agrawal, Manager, Accenture
- January 20, 2011
A weekend of ABAP work can lead to better organization, tracking, and monitoring of your SAP ERP Central Component (SAP ECC) transports and change requests. Standard functionality within SAP ECC does not provide an easy way to list and track all transports associated with a work package or change request. With some quick ABAP coding, you can build your own application that allows you not only to rapidly produce a list of transports for a work package, but also monitor their import and export statuses as they migrate through the system landscape.
The simple transport application creates a centralized registry for all released SAP ERP Central Component (SAP ECC) transports and their assignments to a work package or change request. You can query the registry to produce a comprehensive list of transports in the correct sequence for a given work package.
Standard SAP ERP Central Component (SAP ECC) does not provide an easy way to identify and track all transports related to a given work package such as Reports, Interfaces, Conversions, Extensions, Forms, and Workflow (RICEFW) objects, configuration designs, security changes, change requests, or testing issues. An accurate list of transports in the correct sequence is required whenever a work package is ready for migration from development to test and production. If not done correctly, the outcome may be a missing transport or an out-of-sequence transport.
Many projects work around this problem by using methods such as maintaining the transport list for each work package (key object or change request) in a Microsoft Excel spreadsheet. However, with no reliable way to enforce compliance for updating this spreadsheet each time a new transport is released, it is often out of date and inaccurate. Furthermore, it becomes even more difficult to produce a comprehensive list of transports that includes all corresponding transports from all work streams (such as functional and security) in the correct release order.
SAP’s solution to this problem is to implement Change Request Management (ChaRM). However, if your project is not yet ready to commit time and resources to a full ChaRM implementation, then your ABAP developer can build a lightweight alternative to ChaRM, a simple transport management system, in as little as one weekend. This alternative enables you not only to clearly identify all SAP ECC transports associated with a particular change request or work package, it also helps you monitor their collective import and export status as those transports race toward the production system.
I show you, step by step, how to build and implement this solution, which involves creating a couple of tables, a table maintenance generator, some quick ABAP, and implementation of two Business Add-Ins (BAdIs).
Would you like to see this full item?