Creating CBTA test configurations in productive SAP Solution Manager 7.2 instances
Customers using a two-tier or three-tier SAP Solution Manager 7.2 landscape normally do not allow any changes in their productive Solution Manager instance without using transports. Any changes must be orchestrated by the SAP Transport Organizer. This is a best practice and a recommended setup. Some workarounds are possible, but all have some disadvantages. For more details please have a look at SAP note 1987155 (How To Create eCATT Objects on Productive systems).
In general, when using test automation tools like CBTA (Component Based Test Automation) the transport approach might become a hassle. CBTA test configurations are eCATT objects in disguise and so they are subject to rules about the changeability of development objects in an SAP ABAP system.
This means that CBTA test configurations need to be developed in a development Solution Manager instance. Then they must be transported and tested in a QA Solution Manager instance, eventually. Finally, they must be transported to the productive Solution Manager instance where they are executed in regular test phases, e.g. during regression tests.
With SAP Solution Manager 7.2 SP08 there is a new option available to avoid the transportation of CBTA test configurations from the development system, then to the QA system and finally to the productive Solution Manager system.
By implementing SAP note 2653468 (eCATT – using local objects without registration in object directory) you will be able to create and execute CBTA test configurations in your productive SAP Solution Manager instance directly, without interfering with the SAP Transport Organizer.
After implementing SAP note 2653468 you must maintain a namespace (e.g. “ZCBTA”).
As of SAP_BASIS 7.40 SP20 there will be an entry in the customizing implementation guide (transaction SPRO) at the following menu path:
“SAP Referenz-IMG -> SAP NetWeaver -> Application Server -> Test Workbench -> Extended Computer Aided Test Tool (eCATT) -> Expert Settings -> Configure CTS/TADIR Handling”
If you are on SAP_BASIS 7.40 SP19 (after the implementation of the SAP Note 2653468, including related notes) you may use transaction SM30 and maintain the table ECCUST_LOCAL_OBJ as outlined above.
This namespace is used as a prefix for your newly created CBTA test configurations and assigned to a local package (e.g. $TMP).
Now you can create and execute CBTA test configurations in your productive SAP Solution Manager directly.