Read Objects without Valid Allevo Status

STATUS_READ_ALL

* from Allevo version 2.9.20 (extended in 3.2.8)

This constant allows to edit objects without any valid entry on the Allevo status. This requirement initially originated from the work with (MO) with the following background: ProCED reads postings for orders or WBS elements regardless of the status in the corresponding Allevo planning transaction. These objects all appear in the Master of MultiObject and should then of course always be equipped with data.  

Using constant STATUS_READ_ALL, you may determine how to handle these planning objects without status. Activation is performed by a number in column Value from. The following options are available for the case that a status is not maintained:

1. Read reference data for objects without status with message output (text: “Plan objects not released for planning”).
Transfer of plan data to SAP is not possible (only for objects with status).

2. Read reference data as in (1), however without any not for the user;
Transfer of plan data as in (1).

3. Reference data are read without note for the user.  
During planning, an entry with status 3 is automatically created in the Allevo status management (also without message for the user).

Without specification in column “Value from“, only objects with a valid Allevo status are read (corresponds to Allevo standard behavior).

Initially, the constant was intended mostly for the MultiObject mode in order to simplify status maintenance for a great number of objects within one Master. In current Allevo versions, STATUS_READ_ALL may also be applied to the start object (see versions of the extensions below).  This is controlled via column Value to. With an S (= Start screen) entered here, the constant does NOT apply to the current start object or the start objects: here, the usual release via the status management is necessary.

In the MultiObject mode, different object types may be processed in the Allevo Master simultaneously: for status request and also for setting the status (to 3 = planned), Allevo uses the same layout ID as during the start of the planning transaction (e.g. required for the license check on deviating object types). It is today no longer necessary to create a layout with the same ID for all addressed object types beforehand; this might however still be useful in single cases.

The planner may close planning simultaneously for all relevant objects; again, only plannable objects are included (if constant STATUS_READ_ALL is set). For special applications in MO where the start object is representative, please observe constant CLOSE_OBJECT_MO.

Note:

When using this constant, you need to make sure that enough licenses are available for the relevant objects (otherwise, the ongoing planning might interrupt). Before calling the planning screen, Allevo usually shows a list of objects included in the current selection; constant NO_MULTILIST changes this behavior if desired. Constant MULTI_WITHCLOSED may also be useful especially for displaying objects that are already closed.

* New from Allevo version 3.2.8

The constant now applies to the Allevo main object as well. Also in this case, the update for the entry in the status management is performed when transferring plan data: in this way, the planning progress is documented.

The constant is also included in transactions for offline planning, offline files may therefore be generated regardless of the status. During importing, the status is then automatically increased.

* New from Allevo version 3.4.30

The expansion to the start object is not in all cases useful. An individual setting for this is now available via “Value to” (for S, the constant is ignored for start objects).

* New from Allevo version 3.5

If the constant is active, all objects of a hierarchy are adopted to the Allevo Tree (before, this application sometimes required release via status table).