|
|
SELECT_TURBO
* from Allevo version 2.9.36 (extended in 3.4)
With its row- and column structure, the Allevo Master has almost unlimited possibilities to display planning relevant data. Basically, each line in the Master can possess its own characteristics. Consequently, the related contents (data) with single selections must be read from the SAP database. This can lead to losses in performance.
The constant SELECT_TURBO may serve to accelerate reading by grouping Excel cells of similar row and column features in blocks before reading, and reading them first in a common buffer. Such features can be e.g.: similar row definitions, same year/version, same planned/actual indicator.
The constant SELECT_TURBO is activated via X in column Value from.
From version 3.3, the constant is already active as presetting. To deactivate it, enter N in Value from.
Behavior depending on row definitions:
· The constant is available for annual planning (not for periods). Row definitions A, B, C, D, F, G, H, I, J and L are supported (as well as K, if NO activity type dependent planning is used, from Allevo 3.0.8 also P). Consequently, the constant currently offers no advantage for row definitions Q, R, M and N: Allevo checks these row definitions and possibly switches back to the standard reading mode (thus, the appropriate data are read, just not accelerated).
· Row definition T generally uses the accelerated reading via constant SELECT_TURBO.
|
Important: |
Determined by the system, the constant must not be active for rolling and overall fiscal year reading (e.g. from period 4 to period 3 of the following year). This situation may provoke false results and is automatically recognized only from version 3.4! On the other hand, reading restricted to particular periods within a fiscal year (e.g. from period 3 till period 10) is possible, as well as the overall fiscal year reading of complete years (i.e. e.g. from period 1 year 2000 till period 12 year 2010). The constant must not be active if the elimination of internal business volume from total is applied (see also the constant IBV_ELIM). |
Other optimization functions can be activated by an entry in column Value to. Each of these functions is activated via 1 (in all other cases it is off, e.g. if 0 is entered). That results in a scheme with the total of 9 characters: the relevant position in the scheme defines the related function:
1. If the position is set in Value to, no restriction to cost elements is made in SELECT of primary costs. The actual select statement for COSP is thus relatively small, so that a further acceleration can often be achieved. However, depending on the situation, it may appear that too many cost elements are selected, which can undermine the performance gain: in this case, the first position should be set with 0.
2. If set, no restriction to cost elements/partner objects is applied in SELECT of secondary costs (table COSS, otherwise the same explanation as for the position 1 applies).
3. Allevo internally
uses a table with all column definitions: multiplied by the key rows
from Excel, it can result in several thousand rows that need to be monitored regularly for the sorting of
data.
If the third position is set in Value to,
(a) each column definition will be processed individually (reduction of
simultaneously processed rows), and
(b) each row will be searched through with the previous sorting (BINARY
SEARCH).
4. If set, reading in blocks is active also for distribution keys (COKP).
5. Activates block-wise reading of prices (COST).
6. Activates block-wise reading of the previous planned values for primary costs before planning (e.g. when using NO_ZERO_DELTA).
7. Activates block-wise reading of the distribution key for primary costs before planning.
8. Activates block-wise reading of values for secondary costs before planning.
9. Activates block-wise reading of the distribution key for secondary costs before planning
To activate all additional options, 111111111 should be entered in column Value to. These additional options have no effects when reading profit center data.
|
Note: |
There are many conditions that determine whether the constant achieves a significant runtime improvement during reading. These are e.g. the structure of the Master, or also the user’s technical environment. Only one test under real conditions can lead to a definitive statement (both with activated and deactivated option respectively); in specific cases an option can even lead to deteriorations. |
* New from version 3.3
The constant is now active as presetting.
* New from version 3.4
To deactivate the constant, N must obligatorily be entered in Value from (before, a blank entry was sufficient).