Allevo License Number

LIC_KEY

Allevo licensing is performed via a multi-digit license key, which is to be stored in the constant LIC_KEY (column Value from). This key is furthermore dependent on the installation number of the SAP system on which Allevo was installed.

Note:

Constant LIC_KEY must always be entered in the so-called * layout. Entries in named layouts of Allevo will be ignored. With export/import functions of Allevo, the constant may optionally be transferred (rather unsuitable for importing standard constants, since a different license key is usually valid in the target system).

The license key comprises the release for the purchased number of objects (e.g. cost centers, orders…) and possible additional modules per controlling area. Only the absolute number of objects is included. The allocation of cost centers (orders, WBS elements) to controlling areas is unimportant.

An object (cost center, order, WBS element) will only be counted regarding the license if it has reached status 3 within the framework of the status administration.

You may also create a license in a way that it applies to a single controlling area respectively. This is useful if the number of planning objects shall be treated separately per organizational unit. The rule (separated or general) must be the same for all controlling areas; you may therefore possibly need to create an individual license key for each controlling area. Entry in the constant:

· A license key must be specified in column Value from.

· The Allevo license model was revised in Allevo version 3.3. Working with satellites is now performed using side calculations. The corresponding satellites are released via an individual license key that must be specified in column Value to. From Allevo 3.4, the new global constant LIC_KEY_SUBJECTS should be used for this purpose.

New from version 3.3

A license key for the new licensing system contains the ID of the object type (e.g. “KS:xxxx”) in the first two digits in order to better recognize the application case of a key.

Only objects with status 3 will be counted. An individual key per controlling area is now possible.

Satellites are now being released using so-called “side calculations“. The corresponding key with the allocation of side calculations and satellites functions via an individual license key that must be entered in “Value to”.

If Allevo is run in a test system for the customer, a so-called “workshop license” may be assigned by entering “WORKSHOP” in column Value from. The entry is generated automatically when calling an Allevo planning transaction provided that no license entry is stored yet (outside a productive environment).

New from version 3.4

The side calculations are now managed centrally via an individual Customizing table allocating side calculations to satellites. The belonging license key is stored for all object types in the constant LIC_KEY_SUBJECTS (for details see Allevo SAP manual).