Symptom
You want to identify the ledger group to which documents have been posted to via Manage Journal Entries.
The ledger group is not filled as you might be used to before the CE2105 upgrade for asset accounting postings in the entry page of Manage Journal Entries.
Moreover, when filtering for a ledger group, also items with ledger group “blank” are displayed.
Example – Manage Journal Entries
Currently, no other apps with this behavior have been identified. In Verify General Journal Entries for Requester, the ledger group is also available as a selection criterion, however, when filtering for the ledger group, only the journal entries specifically posted in this ledger group are selected.
Image/data in this document is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP S/4HANA Cloud
Cause
The filtering logic in Manage Journal Entries works in a way that it selects the entries for the ledger group selected (e.g. 2L) and the ones for ledger group “blank” since technically, the entries with ledger group “blank” are posted to all ledgers and thus ledger groups. That is why they are included as well.
Furthermore, due to changes in the context of Universal Parallel Accounting, the posting logic in asset accounting has been simplified in a way that the values are posted directly to the respective ledger without using the technical vehicle of a ledger group which was necessary before. This is part of harmonizing and simplifying the posting logic across the different subledgers. For details about the functional background, please check the What’s New Information for Asset Postings.
Resolution
In general, we recommend to focus your reporting on the ledger instead of the ledger group. In the analytical apps in General Ledger accounting and Asset Accounting it is already possible to select data based on a ledger. Examples for these apps are Display Line Items in General Ledger, Asset Balances, Asset History Sheet etc.
However, Manage Journal Entries (entry page) is technically based on the accounting document header. This does not include the ledger, but only the ledger group. That’s why reporting via ledger is currently not supported when entering Manage Journal Entries.
As an alternative you can use the search in Display Line Items in General Ledger to identify e.g. the documents for depreciation posting for a certain ledger (see screenshots below).
If you do want to stick to using Manage Journal Entries for the specific use case mentioned above, you can use the document number ranges or header text as an indication to which ledger the entry has been posted and/or navigate to the document detail to identify the ledger group.
Keywords
Ledger Group, Accounting , KBA , FI-FIO-GL-TRA , Transaction Apps , FI-FIO-GL-TRA-2CL , Transaction Apps (Public Cloud) , Problem