Authorization Check for Allevo Start Transaction

AUTH_PLAN_START

// For Allevo  3.3 and later

The constant AUTH_PLAN_START controls the authorizations for the initial object when MultiObject is started.

Background: When a planning transaction is started, Allevo verifies whether the user has the required authorization for planning the relevant objects. In the MultiObject mode, though, the initial object sometimes only has a presentational character: the real planning is done through the objects of another object type allocated, for example, the planning of all internal orders for a cost center without directly planning the cost center itself. In this specific case, the planner may not have the planning authorization for the initial object.

Individual authorization checks are controlled by the entries in the constant’s column Value from. The following options are available:

§ D automatically switches Allevo to a reporting mode if no planning right is available for the current object (i.e. entry X). This option is available for all types of transaction, provided they are started through an individual object (i.e. not only for MultiObject).

§ N is only effective in MultiObject; the authorization check is completely skipped for the initial object here (even when uploading the offline file).

§ R, too, is only effective in MultiObject – this entry only verifies the reading authorization and NOT the planning authorization for the initial object. Reading authorization is sufficient to open the planning for any allocated objects.

The options N and R are also valid when using MultiObject Reporting.

NOTE: When plan data is written to SAP, Allevo explicitly verifies a second time for each object and cost element, whether a planning authorization is available (otherwise the post is not accepted). The above described options therefore ONLY apply for the verification of the initial object!