Display Period Data, 1st Year and Mix

YEAR1_PERIOD

The constant controls the combined display of actual and planning data as it is common with forecast periods. The importance of this constant depends on the method used for the display of period planning.

A) Period Planning in the “Compact“ method

With the “compact” method of period planning, it is possible to plan 12 or 24 periods to exact months.

By entering X in column Value from of the constant YEAR1_PERIOD, processing by period is activated for the first year. The activation applies both to reading and planning of the data, which results in the following effect:

· Planning follows the settings in column definition CX_WW (no longer relevant for the balloon variant, see note below).

· The reading function may be flexibly controlled. It is, for example, also possible to mix actual and planning data: here, actual values are always read according to column definition CX_RR (year, period, version); i.e. not based on characteristics of the period column CM_R1. Mixing is also considered during reading after planning (see constant READ_ON_OPEN).

The numbers 1, 2 or 3 specified in column Value to determine which system is used for reading the data:  

1 Only the actual values of the current year (column definition CX_RR) are entered in the monthly planning table according to the characteristics of column definition CX_RR. Here, you may also enter To-period, all other periods remain empty.

2 Current plan values are entered in the monthly planning table (from period 1 to 12). Data are read with year, version and period as stored in column definition CM_R1 (same function as without constant).

3 Mixing actual and planned values: actual values of the current year are entered up to the selected To-period (specifications on the selection according to parameters in CX_RR). From the To-period (of CX_RR), (plan) values are entered according to the parameters in column definition CM_R1 up to the last period. Normally, these values are read up to period 12 (depends however on the specification on the To-period in CM_R1).

Note:

Allevo additionally knows the function for reading from a different column definitions if status 3 (already planned) was achieved. It is useful, for example, if only the state of the already planned values shall be read from this status on. For this purpose, the reference to another column definition must be entered in CM_R1: this is usually a reference to CX_WW (or also CM_W1). With such a reference to a different column definitions from status 3, the original combination named above ((YEAR1_PERIOD is ignored).

With this method, the planning data can be exchanged between Excel and SAP for 12 periods only. During the reading, data from period 13 till 16 will be automatically added to period 12, in case this period is specified in column definition (the function is only available in Allevo 3.2 and later, in earlier versions the additional periods have been ignored).

Annual columns have already always contained the sum of all periods of a column definition.  

B) Period Planning with the „Balloon“ Variant (new from version 3.0)

With this option, any number of periods over any number of years can be planned. The balloon variant may also read actual special periods (13-16) individually.

In this case, the Value from of the constant YEAR1_PERIOD is no longer of relevance.  The entry in column Value to, however, still defines whether the actual and planning data are mixed (with regard to the entry in column definition CM_R1).

* new from version 3.4

Special periods are now available also for reading and writing plan data (see also SAP manual for the section on column definitions).

The planning function for special periods may be useful especially when storing planning data in /KERN/ACOSx tables (e.g. with Allevo objects). For standard planning (e.g. on cost centers), the SAP Customizing must be set up appropriately: a corresponding message from BAPI may point to this.