You have either created a BSP extension or processed one that already exists.
Activation does not take place for the individual BSP elements alone, but is always done for the entire extension.
You use this standard function of the Workbench in order to put the entire BSP extension, including its elements, into the active version. If necessary, the system will generate the basis class ( CLG_* or ZCLG_*) again upon activation. This renewed generation always takes place during activation in the following cases:
If generation-relevant element data has been changed because, for example, you have created, deleted, or changed element attributes.
If a basis class for a particular element does not exist at all because, for example, it was deleted manually, or was not transported by mistake.
When you activate, you create a runtime version of the BSP extension. If necessary, the system will also regenerate the element handler classes and your basis classes. Newly-created classes are automatically written to the same transport request as the BSP extension.
Now the active version of the BSP extension appears in the Tag Browser under the entry BSP Extensions. There it is assigned to the selection Transportable or Local, depending on the object catalog entry.
Note that activating the extension can invalidate all the BSP pages that use this extension. Calling the respective BSP pages again means they will be regenerated if changes have been made.