Allevo Planning Data for Free Costing

USE_ALLEVO_TABLES

* from Allevo version 3.2.23 (extended in 3.4)

During transfer of Allevo planning data to SAP, the functions that are provided by SAP for such applications are normally used (BAPIs). Allevo postings are therefore equivalent to those postings that have been entered by SAP via the original planning transactions.

In special cases however, it may be useful to include planning data that purposely do not follow the SAP planning transactions (e.g. to simulate planning for objects that do not even exist yet in the system). In this case, planning data are adopted in Allevo own tables (/KERN/ACOSx, i.e. e.g. /KERN/ACOSS instead of COSS).

Constant USE_ALLEVO_TABLES acts as superordinate button and activates the use of the Allevo own tables in the current layout (an X in column Value from). The corresponding functions during reading and writing are described in the Allevo SAP manual (see section “Planning data in Allevo own tables”).

You may individually decide per row and column definition when to access the Allevo own tables.

· Column Value to of the constant may contain row definitions to address the Allevo own tables: multiple row definitions are to be entered as comma-separated list (e.g. “A,B,G1”). With no entry in Value to, all row definitions are switched to Allevo own tables except for rows in the dynamic range: here, SAP tables remain serve as basis.  Row definitions in the dynamic range therefore must be explicitly named in the constant (see also notes in the Allevo SAP manual on “FI Dynamic“).

· With row definitions, activation is performed via button „Allevo tables (summarization)“ in the master record of the column definitions (without such entry, the normal Read/Write functions apply).

Only exception from these rules: with the Allevo own object type KX, all ACOSx tables are generally addressed (same behavior as if activation had been performed for all row/ column definitions in combination with the constant).

Note:

When using the Allevo own tables, some planning functions of Allevo are not available, such as: - The functions for constant PRE_SELECT are switched off as soon as  USE_ALLEVO_TABLES is active. - No LAP rule planning - Posting via FP is only realized in a following version of Allevo.

* new from Allevo version 3.4

In the first program version, write definitions did not have a flag for the individual activation of Allevo tables. In these versions, all write columns were automatically set to Allevo tables if the constant was active. From 3.4, the corresponding button must be set in the master record also with write columns.