Allevo own Authorization Control

AUTHORIZATION

// from Allevo version 3.0 (extended in version 3.4)

The Allevo own access checks are available for all object types supported by Allevo (cost centers, orders, WBS elements). It is a redundant authorization check since Allevo meets all SAP authorizations anyway.  Consequently, application is only useful if no organizational aspect for authorizations shall or can be implemented on the side of SAP, as for example with the Allevo own objects.

Constant AUTHORIZATION is set up as follows:

§ Entry X in column Value from activates the constant. This entry is equivalent to a number 3. As an alternative, you may also enter 2 in a previous version of the authorization check (see note below).

§ Enter the table containing the authorization rules in column Value to: this may be the Allevo standard table /KERN/IPPAUTHSMP or a table in the customer-specific naming environment if special requirements shall be met (see examples in the manual “Allevo & SAP“).

If the constant is active, the function “Authorization concept“ may be called in the Allevo settings in order to set up an appropriate field assignment for the access checks. When using the Allevo standard table /KERN/IPPAUTHSMP, Allevo may also work with default assignments (see details in the manual).

Constant OWN_AUTH_TRACE furthermore gives an overview of all authorization checks to go through.

NOTE: The authorization module was revised in major parts for Allevo version 3.0, especially with regard to the use of placeholders such as * and ?. This allows to, for example, release an entire project or all subordinate WBS elements according to the shares in the name. A detailed description can be found in the Allevo manual. The revised authorization check is not compatible with all functions of previous versions. To continue working with a previous version, enter 2 in Value from.

New from Allevo version 3.3.4: Extension for Profit Center

The access control is now available also for the profit center.

New from Allevo version 3.4: Standard table for authorization check available

A standard table /KERN/IPPAUTHSMP containing predefined field names and assignments is now available. A customized table for the authorization check is therefore no longer necessary.

In addition, the authorization check has been extended to all object types supported by Allevo (including object and business process).

The constant and field assignments may also be used for the * layout.

A table containing the access rules may be used for different object types simultaneously (FIELD_OBART must then be assigned).

New from Allevo version 3.4.22: Authorization check upon planning completion

The authorization check is now performed also with “Complete planning“.