Aggregation of cost element groups

NODE_AGGREGATION

In Allevo it is possible to plan for cost element groups or for the saved representative cost element. In this case, the posting combinations provided by ProCED should also be aggregated by cost element group.

All groups that are to be aggregated must be combined as sub-groups within a group. These superior groups are then entered in Value from for the constant NODE_AGGREGATION.

The aggregation is done for the sub-groups for which a cost element is directly assigned.

The aggregation has an impact on the following fields in mapping:

· FD_INFOOBJ contains the ID code of the cost element group

· FD_INFOOBJ_TXT contains the text description of the cost element group

· FD_KATYP contains “99”

· SOURCETAB is empty

If a cost element is not found to belong to any group, then it is displayed as a single row in the results list.

Usually, ProCED sorts the results list according to the entry for the cost element (in this case, according to the group). The entry of an X in Value to prevents this type of sorting. It will be output in the order that was previously read from the database. This should be the preferred way to sort, if reading is to be done across objects (e.g. with READ_ASSIGNED_OR).

Note:

The group entered in the constant NODE_AGGREGATION only functions to aggregate available posting rows: it is therefore NOT a filter for selection (to achieve this you still need to make an entry at the button |Restr. KoA Group| in the ProCED start screen). For rows with aggregation by cost element group, not all ProCED mapping fields will contain meaningful data: the contents are usually transferred from the first cost element.