Flexible Access to Planning Version

FLEX_VERSION

* Allevo version 3.2 and later

Normally the Allevo planning transaction is started with the planning version stored in the column definition CX_WW.

In exceptional cases it may, however, make sense to start the transaction with another planning version and/or offer the user a list of possible versions to select from. The constant FLEX_VERSION controls therefore the representation and the function of the “planning version” field on the initial screen of the Allevo planning transaction (e.g. /KERN/IPPKS).

To activate the constant a number with one of the following meanings is to be entered in column Value from:

1 The “planning version” field is hidden when starting the planning.

2 All the stored versions related to a particular planning year are listed for selection. The given value is copied to CX_WW.

3 The version can be selected through Combobox. The selection is either to be done from all active versions in SAP or through the entries of column Value to.

4 Like 2, but the given value is copied to CX_RR

5 Like 3, but the given value is copied to CX_RR

6 Like 2, but the given value is copied to CX_WW and CX_RR

7 Like 3, but the given value is copied to CX_WW and CX_RR

An empty entry in column Value from shows, as by default, the version from CX_WW with no possibility of modification.

In modes 3, 5 and 7 a list of versions that are to be offered for selection can be entered, separated by comma. No check is made on the validity of a version. The value entered in CX_WW must be also included in this list.

Note:

A flexible access by year/version with regard to customer requirements can be individually directed via BADI (e.g. when year/version should be dependent on additional customer specific logic). The related BADI is executed continuously; in this case the constant does not need to be set (Event EXIT_INIT).

Note:

When using this constant, the planning year is usually set in other column definitions (by means of relative references). With BADI a customer specific solution is also available for this purpose (event START_PLAN). See also the constant FLEX_YEAR for flexible selection of the planning year.