Skip to Content

Custom Hierarchy

Hello,

We have a requirement to build a custom hierarchy based on the combination of two fields in the S/4HANA code block (Account + Custom Dimension) to be consumed for reporting by AO in an embedded consolidation BPC solution.

At the higher levels of the hierarchy it will represent the FSV but at the lower levels it will represent Account + Custom Dimension. How might this be achieved in the Real Time Consolidation Model? Is it better to configure this in S/4HANA using a custom CDS view or perhaps in BW as a custom characteristic, and what would be the benefits of either approach? Any insight would be much appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • May 02, 2017 at 12:48 AM

    Hi Kevin, we have a requirement to build a CDS view that uses the FSV hierarchy in a 1610 system. Were you able to achieve this? If so, would you share an example of your CDS code?

    Add comment
    10|10000 characters needed characters exceeded

  • May 05, 2017 at 02:23 AM

    Hi,

    The default hierarchy in standard /ERP/GL_ACCT info object is driven from FSV. This is built via abap class: CL_FCOM_IP_HRY_READER_GLACCT.

    Now, two things to bear in mind:

    1- If you change this class, you would automatically affect all other reports in your system

    2- Even though you'll have a different hierarchy - remember that you'll no be able to save data in the consolidation journal with accounts that don't exist in the account master

    What's the requirement here? Do you wish to select the node (Account + custom) and use both as filters in account and custom characteristic
    ?

    Cheers

    Add comment
    10|10000 characters needed characters exceeded