What is the maximum number of characteristic values a characteristic
can hold?
As of Release 4.6C, the maximum number of characteristic values of a characteristic is limited to 9999. When using
change numbers, the number of maximum entries is less, because it is necessary to store several change states
(e.g. when the position of a value changes, or a value is deleted). Therefore, the maximum number of values a characteristic
can hold when assigned directly in the transaction CT04 is 9999, minus the number of values changed with a change
number. For example, if 1000 values have been changed with a change number for a characteristic, the maximum number
of values that can be assigned directly after the change is (9999 - 1000) = 8999 . In case the same value has been changed
with two separate change numbers, the number of changed values will also be double. For example, if 1000 values are
changed with the change number 'CHANGE_1' and the same 1000 values are then changed with the change number
'CHANGE_2', then it will count as 1000*2 values and the maximum number of values that can be assigned directly after
the changes is (9999 - 1000 - 1000) = 7999 .
For performance reasons, it is not advised to use a large number of values within a characteristic. If a high number of values
must be assigned or it is not possible to foresee the maximum number of values, a check table should be used to hold all values.
If the maximum number of 9999 is reached, an overflow occurs, which triggers error message C1034 in the characteristics
maintenance.
When the maximum number of entries is reached, the following options are available:
Working without change number
1.) A new characteristic must be created with a check table and the values may be copied or added directly.
Working with change number
1.) A new characteristic may be created which replaces the old characteristic at a certain date and contains the characteristic
values of the first characteristic (on this date). Therefore the new characteristic should be copied from the old one.
2.) The old characteristic can be set to 'no display'.
3.) The new characteristic could have the same characteristic description (because most of the users are working with the
characteristic description).
Why does the external value check via function module not return values?
In the function module for the value check it is necessary to fill the export parameter VALUE_EX which will return the
language-neutral value.
Apart from the value check function module a function module must be created to provide input help (F4 help). This
module must have the same name followed by "_F4".
In addition, another module can provide language-independent value descriptions. The name of this module must be
the same, followed by "_DC".
Please have a look at following notes dealing with this issue:
588283 - Error in the external value check via function module
1085134 - Values entered for characteristic disappear
1155969 - Function module for value check