0FIGL_V10_Q0001 unassigned node "0COA/0BSRESULT"

[Former Member]

Dear all,

when executing query 0FIGL_V10_Q0001 on Virtual Cube 0FIGL_V10 there is displayed a node "0COA/0BSRESULT" under unassigned nodes. The amount shown for this node should normally be displayed under Activa. It seems that the underlying function module of cube 0FIGL_V10 assigns certain data to this dummy account "0COA/0BSRESULT"

Can anybody tell me why an amount appears there and how to fix this? Maybe there is an error in the sourcesystem with certain accounts? Or is it a bug in SAP BI? We have BI Content Release 703 and support package SAPKIBIIQ3.

Many thanks in advance!

[Former Member]

That query will arrange those nodes based on how the financial statement version is defined.

What accounts are falling under that node? Bring in GL account and see what they are. Then check the financial statement version to see where they are defined there. You can use tcode FSE2 to see how they are created on the ECC side.

Hope it helps,

Justin

[Former Member]

Thanks for your reply but this was not the solution since this node is a dummy node created by the underlying function module when executing the query. The node is not present in the source system. However I debugged the function module and found out that when executing the query the function module adds the balances of all balance sheet accounts into this dummy account. So it simply displays the sum of all balance sheet accounts - at the end a 0 should appear if everything is balanced which is currently not the case.

Anyway, the problem is solved and it was no error in the Query. Thanks for your support.

[vikram_bagade5]

Hello Matthias Völz,

We are facing a sililar issue of nodes not assigned. Can you please let me know how did u solve this issue. Did you make any changes in the function module code?

Awaiting your helpful reply.

Thanks and Regards,

Vikram

[vikram_bagade5]

Hello Matthias Völz,

We are facing a sililar issue of nodes not assigned. Can you please let me know how did u solve this issue. Did you make any changes in the function module code?

Awaiting your helpful reply.

Thanks and Regards,

Vikram

[Former Member]

Dear Vikram,

no you dont need to change anything in the function module. I was just debugging it to find out where the node 0COA/0BSRESULT comes from. As I wrote above, this node is created by the function module and contains the sum of all debit/credit balance sheet accounts, i.e. the total balance (which should normally be zero).

It might happen that some balance sheet accounts are not assigned to hierarchy nodes - that was the main problem I was facing.Please check first those accounts in the source system, with transaction FSE3. There you see the assignment in the source system. If the accounts are correctly assigned in the source system, make a double click on the account in transaction FSE3 to check if the checkboxes for "D" and "C" are checked. These have the function that the account can appear under debits or credits depending if the balance is positive or negative. If not both checkboxes are checked (which is not neccessarily an error) then those accounts appear as unassigned in BI system because when loading the hierarchy the system cannot determine under which hierarchy node the account should appear (it depends on the balance of the account).

To solve this problem there is a special feature in infoobject 0GLACCEXT called balance dependency. You have to maintain the hierarchies of the infoobject, go to the relevant account and set the balance dependency indicator with 1 and 2. Normally the account should appear 2 times in the hierarchy (debit and credit) and the indicator is set to 2 for debit and 1 for debit side.

Unfortuantely I cant provide screenshots but I hope you will find it in the system.

Regards,

Matthias

[vikram_bagade5]

Hello Matthias,

Thank you so much for your comprehensive reply. The issue is resolved with the help of the note 663945.

In my case there were no gl accounts unassigned in FSE3 and it was all fine. The issue was the transfer rules of object 0GLACCEXT were missing proper mapping. I used the note 663945 and mapped accordingly and the issue is resolved.

Thanks again for your reply.

Regards,

Vikram

[Former Member]

I'm having the same issue and followed all the things mentioned here but still no luck.

[vikram_bagade5]

Hello PrabhuG

Can you elaborate your issue and the current status of your query design and data model.

REgards,

Vikram

[Former Member]

I m facing same issues.

Please suggest any ideas