MBT Transport Request is using an enhancement spot to derive icons and descriptions from a list of objects. The tool provides several enhancement spot implementations out of the box. The enhancement spot can also be used to further extend the tool and support more standard or even customer or partner object types.
Implementations Included with Tool
Each enhancement spot implementation covers a group of object types:
|Enhancement Spot Implementation
|Object types for SAP Basis
|Object types for Business Document Service
|Object types for SAP BW
|Object types for Change & Transport System
|Object types for Gateway
|Object types for SAP Notes
|Object types for ABAP Workbench
|Object types for Web Dynpro
Customer or Partner Implementation
To extend the solution, implement enhancement spot
/MBTOOLS/BC_CTS_REQ_DISPLAY in transactions
|Enhancement spot provided by the tool
|BAdI provided by the tool
|The interface provided by the tool
|Mandatory implementation: Method to return the description for objects in a transport. Importing parameters correspond to the content of the transport i.e. tables
E071K (table keys) and
E071K_STR (table keys in string format). Descriptions and icons for all imported entries shall be returned via changing parameter
|Optional implementation: Method to return an icon for object types supported by the implementation.
|Optional implementation: Range to contain all object types supported by the implementation.
To familiarize yourself with the implementation requirements, have a look at the implementation
/MBTOOLS/BC_CTS_REQ_DISP_NOTE and the corresponding class
For details, see the SAP documentation on How to Implement a BAdI.
The system will call all implementations of the enhancement spot no matter which object types are supported by an individual implementation. In other words, the importing parameters
IT_E071* for method
get_object_descriptions contain all entries relevant to the current output of the transport tools.
Therefore, it is essential that each implementation performs in an optional way and only processes entries that are handled by the implementation. This can be easily accomplished by filtering the
IT_E071* entries when looping over them using a where-condition on the object type. See the class
/MBTOOLS/CL_CTS_REQ_DISP_NOTE for example.