|
Flexible Access to Planning Year |
|
FLEX_YEAR
* Allevo version 3.2 and later
Normally the Allevo planning transaction is started with the main planning year stored in column definition CX_WW.
In exceptional cases it may, however, make sense to start the transaction with another year and/or offer the user a list of available years to select from. The constant FLEX_YEAR controls therefore the representation and the function of the “planning year” 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 year” field is hidden when starting the planning transaction.
2 Any entry of a planning year is possible without review of the content. The given value is copied to CX_WW.
3 The planning year can be selected through Combobox. The content is to be entered in column Value from. The given value is copied to CX_WW.
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 planning year from CX_WW with no possibility of modification.
In modes 3, 5 and 7 a list of years that are to be offered for selection can be entered, separated by comma. No check is made on the validity of years. The value entered in CX_WW must be also included in this list.
|
Note: |
When using this constant, the planning year is usually set in other column definitions (by means of relative references). See also the constant FLEX_VERSION for flexible selection of the planning version with appropriate BADI extensions to version access. |