3756036 - Balance sheet/income statement - Multidimensional (W0161): debit/credit mapping from manage global hierarchies not applied when using alternative g/l account dimension – SAP s/4hana cloud public edition

• Mapping rules defined in a financial statement version hierarchy in the manage global hierarchies app (F2918) are not reflected in the balance sheet/income statement – multidimensional app (W0161) when viewing by alternative G/L account.
• An alternative account with a credit balance is shown under the node intended for debit balances instead of the node intended for credit balances.
• No error message or error code is displayed.

• SAP S/4HANA Cloud Public Edition

1. In the manage global hierarchies app (F2918), create a financial statement version hierarchy.
2. For a given alternative G/L account, define rules so that:  a) debit balances map to a specific node (example asset) and b) credit balances map to a different node (example liability).
3. In the balance sheet/income statement – multidimensional app (W0161), select the hierarchy ID created above and the relevant organizational filters.
4. Switch the report to display by alternative G/L account and run the report.
5. Observe that an account with a credit balance appears under the node configured for debit balances, not under the node configured for credit balances.

In app Balance sheet/income statement - Multidimensional W0161, debit/credit-dependent node assignment applies only when using the “Financial Statement Leaf Item” dimension. When the report dimension is switched to “Alternative G/L account” (and an account-based hierarchy is used), the debit/credit shift logic is not applied; the display uses only the debit-side assignment from the hierarchy. 

The backend logic for this dimension only impacts the 'Financial statement leaf item' (updating the 0A/1A/2A suffixes based on balance). Although the logic triggers when using the 'Alternative GL Account' dimension, it does not modify those values. Consequently, the output for 'Alternative GL Account' remains unaffected by this logic." 

1. Use the “Financial Statement Leaf Item” dimension in app W0161 when you require debit/credit-dependent node assignment as defined in the financial statement version hierarchy.
2. Avoid switching the report dimension to “Alternative G/L account” for scenarios that rely on debit/credit split logic, since this overrides the debit/credit mapping.
3. If analysis by alternative G/L account is necessary, be aware that only the debit-side assignment from the hierarchy is used for display; validate results by cross-checking with the “Financial Statement Leaf Item” view when debit/credit-dependent presentation is required.

• Refer to: 3064950 - Financial Statement Version versus Hierarchy ID at Fiori reporting apps for Balance Sheet
• Refer to: Balance Sheet/Income Statement – Multidimensional (W0161) documentation
• Refer to: 3569200 - FSV cannot be selected in "Balance Sheet/Income Statement - Multidimensional" app - SAP S/4HANA Cloud Public Edition
• Refer to: 3283852 - Limitations of the app Balance Sheet/Income Statement – Multidimensional (W0161, F3084)

w0161, f2918, manage global hierarchies, financial statement version, hierarchy id, debit credit mapping, dr/cr, alternative g/l account, financial statement leaf item, mapping override, node assignment, balance sheet income statement, multidimensional report, hierarchy rules, reporting apps public cloud , KBA , FI-FIO-GL-IS-2CL , Reporting Apps (Public Cloud) , FI-GL-GL-D-2CL , Reporting/Analysis/Display (Public Cloud) , Problem