Get Example source ABAP code based on a different SAP table
ABAP Test Cockpit
ABAP_BACKGROUND ABAP Test Cockpit (ATC>) is a framework for internal SAP use that is integrated into ABAP Workbench; it simplifies considerably the handling of the tests required during development. ATC> makes it possible to execute and display results for various tests on development objects, for example:
Extended program checks
Static performance tests
Module tests with ABAP Unit
Static usability tests
Package checks Whereas Code Inspector is only integrated into the development environment by way of the standard check > and can otherwise only be used by calling a separate transaction, ATC> is completely integrated into Object Navigator and Transport Organizer>, and is available there for tests during development. ATC> allows quality managers to perform mass tests.
ABAP_RULE Configuring and Using ABAP Test Cockpit Correctly> If ABAP Test Cockpit is available in your system, make sure that an ATC> run is performed on all involved development objects and that no messages are displayed before you release the objects for transport. The ATC> check should be integrated directly into the transport release.
ABAP_DETAILS The ATC> is a tool that, for the first time, can be used both by SAP developers and as part of central quality assurance management. For example, if a developer checks all development objects of a package in the development system using the same ATC> configuration used by a quality manager as part of a mass run in a consolidation system, he can go ahead and correct all messages without having to wait for feedback from the quality manager. If ATC> is configured correctly, the above rule includes the previous rules for syntax warnings>, extended program checks>, and Code Inspector>>.