VDSK1 (Organizational Key) (SAP Library - Personnel Administration (PA-PA))

VDSK1 (Organizational Key)

Definition

Field in authorization objects that is used to run diverse authorization checks by organizational assignment (using the P_ORGIN authorization object). The content of the organizational key is either derived by the system from the fields of the Organizational Assignment infotype (0001) or entered manually by the user.

Structure

Controlling the Creation and Validation of the Organizational Key

The VDSK1 feature (Organizational Key) and the T527 (Organizational Key: Control), T527A (Organizational Key: Rules for Creating Organizational Keys), and T527O (Organizational Key: Validation) tables control the creation and validation of the organizational key.

A variable key, VARKY, is determined for this purpose using the VDSK1 feature. This key is used according to the T527 table to determine how the VDSK1 (Organizational Key) should be created or validated. The OFLAG (Default/Validation) and RULID (Rule for Creating Organizational Keys) fields are evaluated for this. The OFLAG (Default/Validation) field can have the following specifications:

1: optional entry without validation

2: optional entry with validation

3: required entry with validation

4: default that cannot be overwritten without validation

5: default that can be overwritten without validation

6: default that can be overwritten with validation

7: default that cannot be overwritten with validation

If you make an entry in the OFLAG field (Default/Validation) which causes a default value to be created (specifications 4, 5, 6 or 7), you must also maintain the RULID field (Rule for Creating Organizational Key). This entry is then used to determine the corresponding rule for the organizational key in the T527A table (Organizational Key: Rule for Creating Organizational Key).

If you make an entry in the OFLAG field (Default/Validation) which causes the organizational key to be validated, you must enter the values that should be recognized by the system as permitted in the T527O table (Organizational Key Validation).

Note

If an entry for OFLAG (Default/Validation) is not permitted (that is, the number is not between 1-7), the system always responds as if 1 had been entered in the field.

Example

Example of an entry in table T527:

VARKY	OFLAG	RULID
TEST	6	XY

If the VDSK1 feature returns the TEST key, the organizational key is created according to the entries in table T527A that belong to XY. In addition, the organizational key is validated against the entries in table T527O.

Creating the Organizational Key

The T527A table (Organizational Key: Rule for Creating Organizational Keys) controls the creation of the organizational key.

You can create one or several rows for each rule. The rows are always sorted according to SEQNO (sequence number). SNAME (Field Name) specifies the field of the Organizational Assignment infotype (0001) from which data should be included in the organizational key. Using the LNGTH (Length) and OFFST (Offset) fields, you can also specify that only data from certain places in the specified fields should be transported. OFFST defines the number of places that should be skipped (from the left). LNGTH specifies the number of places that should be included. The fields, or parts of fields, that have been determined for each row are placed after each other in the organizational key.

Example

Example of entries in table T527A:

RULID	SEQNO	SNAME	LNGTH	OFFST
01	10	P0001-KOSTL	5	0
XY	01	P0001-KOSTL	1	0
XY	04	P0001-PERNR	2	3
XY	05	P0001-KOSTL	1	9
ZZ	01	P0001-KOSTL	5	5

If the organizational key should be created according to RULID (Rule) 01, the first 5 places of the cost center are always entered in the organizational key, for example, 12345 is entered in the organizational key for cost center 1234567890.

If the organizational key should be created according to RULID (Rule) XY, the first place is the first number of the cost center, the fourth and fifth places are the fourth and fifth numbers of the personnel number, and the tenth place is the tenth number of the cost center. For example, 1450 is entered in the organizational key for cost center 1234567890 and personnel number 12345678.

If the organizational key should be created according to RULID (Rule) ZZ, the last five places of the cost center are entered in the organizational key. For example, 67890 is entered in the organizational key for the cost center 1234567890.

Validating the Organizational Key

The T527O table (Organizational Key: Validation) contains a list of the permitted entries for the VDSK1 field (Organizational Key). Only entries with HIRAR (Hierarchy) = 1 are relevant for validations. All other entries are ignored when validating the organizational key.

The ORGKY column (Organizational Key) contains the organizational key that should be permitted during the validation. All other columns are irrelevant for the validation.

In the TEXT1 (Short Name) and TEXT2 (Name) columns, you can store a short text or a description for each organizational key. The texts appear when you press the input help for the Organizational Key field. The texts are irrelevant for the actual validations.

The NODTY column (Organizational Element) is no longer of significance. The column is still included in the T527O table for reasons of downward compatibility but is no longer displayed in the table view.

Example

Example of entries in table T527O:

HIRAR	ORGKY	NODTY	TEXT1	TEXT2
1	ADM		Adm.	Administration
1	PRO		Prod.	Production
2	PRO		TEST	Test
2	TEST		Test	Test

The organizational keys PRO and ADM are permitted organizational keys due to the first two rows of the table. The entries with the text Test are all irrelevant because they have an entry unequal to 1 in the HIRAR field. If there are no more entries in the T527O table, TEST, in particular, is not a permitted organizational key.