Preselection in Allevo Reading Function

PRE_SELECT

* from Allevo version 2.9.36 (extended in 3.3)

The Allevo Master offers, with its row- and column structure, offers almost unlimited possibilities to display data relevant for planning. Basically each cell in the Master can possess its own individual properties. Consequently, the corresponding contents must also be read from the SAP data base individually; this in turn may affect the performance.

The constant PRE_SELECT functions similarly to the Allevo module ProCED. Before the individual data records are read, the system checks for which cost elements entries exist in the data base. Here, the tables COSS, COSP and, if required, COKS, COKP and /KERN/IPPCOMMENT are checked (in Allevo 3.0.8 and later also when reading the data for the profit center). The following complex reading functions are executed only if postings exist in the selected time period.

The constant is activated via a corresponding entry in column Value from:

§ Y = preselection active

§ N = preselection not active

If the constant is not activated (empty column Value from), the following specifications are applied (Allevo version 3.0 and later):

§ Allevo Single and MultiPage: preselection active

§ Allevo MultiObject (MO): preselection is not performed since an equivalent function is often performed by ProCED.

The constant has an impact on row definitions A, B, C, D, E, F, H, I, J and K (from Allevo 3.0.8 also on row definition P): in version 3.1.6 the preselection is also performed for period values (in earlier versions only for years).

In exceptional cases, it may be useful to exclude one or several row definitions from the preselection. For this purpose, an N must be entered in column Value from of the constant. The row definition(s) to be excluded must be specified in column Value to.

Note:

The constant induces performance optimization primarily if a big number of cost elements and cost element groups are stored in the Master, since otherwise Allevo has to fetch the data from each single row-/column definition from the data base. For prevention of the large-scale selection conditions, the constant SELECT_SEQ_COUNT can be additionally used (from Allevo version 3.1; see documentation there).

* new from Allevo version 3.3

From version 3.3 onward, the function of PRE_SELECT may also be used to adjust cost elements stored in the Allevo Master to real postings in the system when executing the planning (see the additional constant CHECK_KSTAR_GRP for this application).

* new from Allevo version 3.4

The constant may now be used also in combination with Allevo own tables (see functions for constant  USE_ALLEVO_TABLES or object type KX).