Planning Object according to User Authorization

 

USER_ELEMENTS

* from Allevo version 3.0 (modified in 3.4)

The F4 value help normally displays the list of all the plannable objects once Allevo is started (using the SAP standard selection for the respective object).

Constant USER_ELEMENTS may serve to limit the list of elements to objects that the user is authorized for (reduces the amount of entries). Activation is performed by a 6-digit code in field Value from according to the structure listed in the table below. The position in this character string determines which check of the restriction should be performed (see the list below).

A value of X or Y is possible for each position: if the space is left empty, the corresponding check will not be performed.

The list of possible restrictions:

Pos.

Content of Authorization Check

1

Status verification:
for X, status > 0 is checked;
for Y, in addition status < 4 is checked

2

According to the indication in the master record, the user is responsible for cost center or Allevo object:
for X: search via SAP user name in field VERAK
for Y: search via user last name in field VERAK
for U: search via SAP user name in the master record (e.g. field VERAK_USER)

3

Verification of cost center validity in the current plan year

4

Check reading authorizations for respective cost centers

5

Check for planning authorization for respective cost centers

6

The object list is compared with the Allevo own authorization check (function is possible from Allevo 3.3).

Example: Entry „XU“ checks for valid status and displays only objects (cost centers) where the current user is assigned in the master record..

With an allocation of a position in Value from, the usual F4 value documentation on the object (e.g. cost center) is automatically replaced by an Allevo own list).

As an alternative or in addition, it is possible to use a Badi in order to make customer-specific restrictions. This is useful e.g. if assignment to the cost center is made in the HR organization management.

Note:

Depending on the characteristic of existing authorizations, the constant may lead to a delay in calling the F4 value list (check runtime in particular cases).

* new from version 3.1

Integration of Badi via enhancement spot /KERN/IPP_BADI_OBJECTLIST.

* new from version 3.4

Reference via SAP user name in the master record.