Entry per value set. A value set is defined by the type of subject
and the concrete key identifying the subject (or owner). Additionally
all value sets are associated to a destination, which is usually a
transaction.
The values (the contents of fields) are stored in the associated table
SVE.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Value Set Entry | Text | 8 | 1 | Edit | Yes | Public | ||
| NAM | Readable Name | Text | 40 | 1 | Edit | Yes | Public | ||
| DST | Destination Object (i.e. Transaction) | Text | 16 | 1 | Edit | Yes | Public | ||
| SUBTYP | Type of Subject | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| SUBKEY | Key of Subject | Text | 16 | 1 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| ETYEXTKEY | Entity owning Value Set | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| SVS_DST | DST, SUBTYP, SUBKEY | |
| SVS_ETYEXTKEY | ETYEXTKEY | |
| SVS_INR | INR | Unique |
| SVS_SUB | SUBTYP, SUBKEY |
/
INR
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter SVS. The field INR is used to maintain links from other tables into this table.
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
This field holds a readable ID to describe the value set in a user readable form. This is usually the long description of the destination.
This field holds a readable ID to describe the value set in a way that is readable to the user. This is usually the long description of the destination.
This field identifies the destination, where the value set is intended to be used. Usually this is the ID of an application transaction.
This field identifies the target/destination for the value set, i.e. where it is intended to be used. Usually this is the ID of an application transaction.
This field describes the type of subject the value set is associated to. A value set of type 'Session' keeps track of settings for the lifetime of a login session. The handling of session sets is implemented in SVSMOD in the rules SaveSsnLoad and SvsSssnSave. A value set of the type 'everybody' might be defined to hold system global settings for a transaction.
This field describes the type of subject the value set is associated to. A 'Session' value set traces the settings during a login session. An 'Everybody' value set can define global system settings for a transaction.
| Code | Text |
|---|---|
| U | User |
| J | Job |
| E | Everybody |
| S | Session |
| W | Workgroup of User |
Depending on the contents of SUBTYP, this field specifies the instance of the specific type. A session is identified by its INR.
Depending on the Type of Subject, this field specifies the instance of the type. A session is identified by its unique ID.
This field holds the version counter to keep track of the version history of an SVS entry. The individual versions are controlled by entries in the SLG table.
This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.
This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY of the owning entity to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.
This field holds the external key of the owning entity to identify the logical owner of this entry.
This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.