Costing Structures for Data Basis

Question

We are trying to create a strucutre in SEM - BW compoent
But we are getting errors from message class FINB_CONFIG.
Want to understand what is this message class and what does it mean?
Thanks and regards

Answer 1

Hi Eugene,
Thanks for the response.  My answers are below. 
1. May I know in more details about the columns structure. What's in it, and how restricted?
The following characteristics are in each column of the structure:
a. Controlling Area - variable selection (1000 = budget, 2000 = actuals)
b. Version - variable selection (300 = budget, 900 = actuals at GAAP rate, 950 = actuals at management rate (different currency translation method)
c. Fiscal Year - variable selection
d. Posting Period - variable selection
e. Cons Group - node selected from cons. group hierarchy that corresponds to business region (domestic, europe, corporate, etc.)
Key figure: Periodic value in Group Currency
So the structure is supposed to show Actual GAAP values, Management values, and Budget values for each business region.
2. ConsGroup hier is used in the columns structure -- how, exactly... and in the filter area -- how restricted, exactly?
Even though Cons. Group is restricted in the column structure as described above, the customer wanted the flexibility to still select a specific Cons. Group as filter criteria, so a variable selection from hierarchy was added to the filter area.  Most of the time the report will be executed leaving this blank.  They understand that selecting a value here will limit the data that is available in the column structure. 
Additional info:
Originally the report pulled data directly from the transactional cube.  All columns of the structure were populated upon report execution, but I wanted to switch to the virtual cube and use Cons. Group instead of simply aggregating Cons. Units (per original query design) so that interunit eliminations would be properly reported.  The virtual cube was added to the multiprovider so I am now restricting the Infoprovider characteristic in the query's filter area to the virtual cube but am now encountering this error message upon execution.
Thanks again,
Samir