abasubsystems (ap_sub)

This table holds the current versions of all subsystems that are included in a database, and thus defines the subsystem configuration for the database.

Note that a removed subsystem still remains in the table, but has a non-NULL value in the deregdate column.

Normally you add rows to this table by running DBBUILD, but there are some situations
where you want to add a subsystem manually:
* You have added the ABAPERLS subsystem to an existing database, and want to enter the existing subsystems.
* You have split a subsystem into two in version-control.
When you add a subsystem manually, you leave inhid NULL, but you should still provide a value for ss_label, so that the next update script can perform the normal checking procedures. (See the page for DBUPDGEN.)

To add a subsystem manually, you can first use ap_sub_insert_sp to insert the subsystem and get a sortorder, and then ap_sub_update_sp to provide an ss_label and mark the system as complete.

If you want to rename a subsystem, use ap_sub_rename_sp.

Current label of the subsystem in version-control. This should be not be NULL for a properly maintained subsystem. (But it would be NULL if you install the subsystem without specifying -label to DBBUILD or likewise run an update script which was generated with specifying -to to DBUPDGEN.) This is always a label on the format LetterMajor.Middle.Minor.

Pointer to the entry in abainstallhistory that performed the last update of ss_label for the subsystem. That entry must have the same ss_label, and this is enforced by a trigger.

inhid is only NULL if you added the subsystem manually.

When a new subsystem is added, it's sortorder is set to 50 + the highest current sortorder. You can however change it if you like. The column does not serve as a purpose for AbaPerls as such, but exists to make it possible to view the table with the subsystems in the same order as in the config-file.

The sortorder must be a positive number.

When DBBUILD start building a subsystem, it writes a row into abasubsystems and sets this bit to 1. Once DBBUILD has completed, it sets the bit to 0, and the bit is to remain that way.

If DBBUILD for some reason does not complete, and you let the subsystem remain in this state, AbaPerls will regard the subsystem as non-existing. If you restart DBBUILD to build the subsystem, DBBUILD will start from the beginning.

If non-NULL, the subsystem is no longer part of the database.