Sorting cost element respective to the group

SORT_BY_KSTAR

* as of ProCED-Version 3.1.9 (expanded in 3.3.33)

In the standard case, the posting combinations determined by ProCED are only sorted according to the object number. Sorting is transferred on the level of the cost element /statistical key figure, as it is created when reading from the database.

Via this constant, the sorting for a cost element can be specified by an additional cost element group.

In the field Value from, enter a level for which the sorting should apply. Preferably, a 2, if sorting should still be carried out for objects at the highest level.

In the field Value to, enter the group: sorting will be carried out exactly as it appears in transaction KAH3. This group can not contain any subordinate hierarchies.

Note:

The cost element group should be complete and contain all cost elements relevant for ProCED/ If an entry in the group is missing, ProCED always enters the corresponding posting combinations at the end of the list, which is then transferred to Allevo (after all other combinations). With the original conception of this constant, the cost element group in KAH3 could only contain single values for cost elements. Since version 3.3.33, areas (cost element to / from) are also taken into account.

Note:

For reading functions valid for all objects (e.g. cost center with READ_ASSIGNED_OR), the constant SORT_BY_KSTAR must be saved to the leading object type (in this example, for the cost center). In this case, the constant MULTIPAGE_MODE must also be active, so that sorting according to the read objects can be achieved on the first level (i.e. in the chronological order of the orders).