Skip to Content

Embedded BW Problem : /ERP/GL_ACCT hierarchy is missing a node

Hi all,

we are using embedded BW over Simple Finance on ERP 6.0 EHP 7, and we are using the standard content query /ERP/SFIN_M01_Q2901 to do plan vs actuals reporting.

We have a problem with the display of a single GL account hierarchy node. This node does not display in the report unless I remove the restriction in the query on the financial statement version, so it seems as though the system does not recognize that node as a valid member of the financial statement version/GL account hierarchy.

When I check the financial statement version in OB58 I can see that the GL account is present in the financial statement version as expected.

Does anyone out there have any ideas about why the system might not be picking up that node in the hierarchy in embedded BW?

In embedded BW, there is no static hierarchy set up in the /ERP/GL_ACCT InfoObject. It is dynamically populated using a class, so it's not just a question of checking the hierarchy in the BW object like it was in the good old days.

All suggestions gratefully received.


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 18, 2017 at 09:36 AM


    I have the same problem. Have you solved it?

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Olha,

      yes we have got it resolved, but we had to go to SAP in the end to get a resolution.

      According to the notes they gave us, the problem is caused because the version of the hierarchy stored in the hierarchy buffer was not being refreshed as it should have been, so it was showing an outdated version of the hierarchy.

      They told us that they triggered a refresh of the hierarchy buffer in the query by debugging the query in RSRT and then triggering the refresh of the hierarchy buffer in the class


      in the debugger.

      They also said "this should not happen so please let us know if it happens again" so you may want to get a ticket raised with them even if you managed to get it fixed yourself.

      Good luck,