Function documentationConsolidation-Group-Specific Entries

 

You can use posting level 35 to make group-specific manual postings that relate to management consolidation only and are not included in external consolidation.

Prerequisites

You have activated the FIN_ACC_GC_BCOMB business function.

Features

In Customizing for document types, you can create document types that post to posting level 35 (Posting Specific to Consolidation Group). This is only supported for manual document types (manual posting, upload, and copying of documents).

Postings made to posting level 35 are handled in the same way as postings to posting level 30 – the only difference being that there is a special reporting logic for postings to posting level 35. This reporting logic enables you to make manual postings explicitly for specific consolidation groups.

The following table shows an example of postings and reporting for posting levels 30 and 35 in a consolidation group hierarchy:

Consolidation Group Hierarchy

Posting (30)

Posting (35)

Reporting (30)

Reporting (35)

Higher-level group

50

50

150

50

Lower-level group

100

100

100

100

In the lower-level group, you post the value 100 to level 30 and again to level 35. The values are displayed accordingly in reporting.

If you now post the value 50 to level 30 in the higher-level group, the value displayed for level 30 in reporting is 150. This is because values from lower-level groups are inherited implicitly by higher-level groups.

However, if you post the value 50 to level 35 in the higher-level group, the value displayed for level 35 of the higher-level group when reporting is run is 50, which is the value that you posted explicitly for this group.

To achieve the behavior described above in reporting, the system's reporting logic performs a virtual revocation of data posted on level 35 from lower-level consolidation groups. The system only revokes this data in the working memory used to display data with reporting logic; the data is not revoked persistently from the database.