Effect of Inactive Sources on Operations

Save

Saves the object in an inactive version without a syntax check. Enters the object in your inactive object list.

Activate

Creates an active version from the existing inactive version. If an object contains components (like classes in ABAP Objects), you can activate individual components. Before activating the object, the system checks the syntax of the entire object, then creates an active version, generates a runtime version, and deletes the corresponding entry from your inactive object list.

Generate

Creates a new runtime version from the existing active version. Unlike the 'Activate' function, this function only generates a new load version.

Display Active/Inactive Sources

If an object exists in both active and inactive versions, you can switch between the versions in the ABAP Workbench tools.

Delete

Both active and inactive versions are deleted.

Note that when you delete components of a global class in the Class Builder, they reappear in your inactive object list with the "Delete" icon. They are not finally deleted or removed from your inactive object list until you activate the relevant objects.

Copy

The system uses the active version of the source object, except in the Function Builder, where it asks you which version you want to copy if both an active and an inactive version exist). The new copy is always inactive.

Rename

Applies to both the active and inactive versions of an object.

Syntax check

Uses your inactive object list.

Execute

A runtime object can only be generated from a syntactically-correct active version. The inactive version of an executable program can be run from the ABAP Editor. If you execute a program from the object list, there must be an active version.

Transport

Only active objects can be transported. You cannot release a transport request until all objects have been activated.