Essbase Accounts Hierarchy--- Design Issue

Hi All,Iam designing a P&L Cube & a Balance sheet Cube.I have a specific problem---Please read below1. In JDE, Account number is the combination of the BU , Object Account & Sub Account.Seems the unique number of accounts (with Account Numbers) are 1.5 million.Upto (Level 6 in JDE) , Accounts are standard across the Companies or business unitsOne company has several business units.Building hierarchy till level 6(level 6 means level 6 in JDE) may not be a problem in Essbase.The real challenge is after level 6,level 7 level 8 level 9 accounts are there & these are not standard for all business units. They differ for each business unit.For example,Bank Account ( suppose at level 6) for a BU 41100000 , BU 41000000 , BU 40000000Bankone (level 7 ) for the 4110000053 bank (level 7 ) for the 41100000Firstunion ( level 7) for 41000000FleetBank (level 7) for 41000000FleetBank (level 7) for 40000000So in this case how to achieve uniqueness vis-a-vis Essbase.Answer is : Account number which is the combination of the BU , object account & Sub accountBut what worries me is if we have 20,000 (suppose) Business units & we have level 7 accounts on an average 10 per BU, then which means we have to build 20,000 * 10 which is equivalent to 200,000.... if we think of level 8 , same logic continues....so when we build hierarchy.... for 1.5 million unique records we might end up having atleast 500,000 stored members, I think.My solution to this was not to go to level of detail after 6th level in JDE.What is your opinion?Did anyone come across such a situation. The Business people want to see the level of detail till level 9 of JDE & report also on that...What is the solution for this kind of problem??Notes : Levels in JDE are equivalent to generations in Essbase

I do something similar with JDE. I use short account id's in some cases to create uniqueness. I also have member names consisting of the full three tier account structure. My app is a read/write budgeting/forecasting application. Not sure what you are trying to do with your app. You can e-mail me if you havent't aleady figured out your [email protected]

Similar Messages

Essbase Accounts Hierarchy -- Design Help

Hi All,Iam designing a P&L Cube & a Balance sheet Cube.I have a specific problem---Please read below1. In JDE, Account number is the combination of the BU , Object Account & Sub Account.Seems the unique number of accounts (with Account Numbers) are 1.5 million.Upto (Level 6 in JDE) , Accounts are standard across the Companies or business unitsOne company has several business units.Building hierarchy till level 6(level 6 means level 6 in JDE) may not be a problem in Essbase.The real challenge is after level 6,level 7 level 8 level 9 accounts are there & these are not standard for all business units. They differ for each business unit.For example,Bank Account ( suppose at level 6) for a BU 41100000 , BU 41000000 , BU 40000000Bankone (level 7 ) for the 4110000053 bank (level 7 ) for the 41100000Firstunion ( level 7) for 41000000FleetBank (level 7) for 41000000FleetBank (level 7) for 40000000So in this case how to achieve uniqueness vis-a-vis Essbase.Answer is : Account number which is the combination of the BU , object account & Sub accountBut what worries me is if we have 20,000 (suppose) Business units & we have level 7 accounts on an average 10 per BU, then which means we have to build 20,000 * 10 which is equivalent to 200,000.... if we think of level 8 , same logic continues....so when we build hierarchy.... for 1.5 million unique records we might end up having atleast 500,000 stored members, I think.My solution to this was not to go to level of detail after 6th level in JDE.What is your opinion?Did anyone come across such a situation. The Business people want to see the level of detail till level 9 of JDE & report also on that...What is the solution for this kind of problem??Notes : Levels in JDE are equivalent to generations in Essbase

I do something similar with JDE. I use short account id's in some cases to create uniqueness. I also have member names consisting of the full three tier account structure. My app is a read/write budgeting/forecasting application. Not sure what you are trying to do with your app. You can e-mail me if you havent't aleady figured out your [email protected]

Accounts Hierarchy--Design Issue

Hi All,Iam designing a P&L Cube & a Balance sheet Cube.I have a specific problem---Please read below1. In JDE, Account number is the combination of the BU , Object Account & Sub Account.Seems the unique number of accounts (with Account Numbers) are 1.5 million.Upto (Level 6 in JDE) , Accounts are standard across the Companies or business unitsOne company has several business units.Building hierarchy till level 6(level 6 means level 6 in JDE) may not be a problem in Essbase.The real challenge is after level 6,level 7 level 8 level 9 accounts are there & these are not standard for all business units. They differ for each business unit.For example,Bank Account ( suppose at level 6) for a BU 41100000 , BU 41000000 , BU 40000000Bankone (level 7 ) for the 4110000053 bank (level 7 ) for the 41100000Firstunion ( level 7) for 41000000FleetBank (level 7) for 41000000FleetBank (level 7) for 40000000So in this case how to achieve uniqueness vis-a-vis Essbase.Answer is : Account number which is the combination of the BU , object account & Sub accountBut what worries me is if we have 20,000 (suppose) Business units & we have level 7 accounts on an average 10 per BU, then which means we have to build 20,000 * 10 which is equivalent to 200,000.... if we think of level 8 , same logic continues....so when we build hierarchy.... for 1.5 million unique records we might end up having atleast 500,000 stored members, I think.My solution to this was not to go to level of detail after 6th level in JDE.What is your opinion?Did anyone come across such a situation. The Business people want to see the level of detail till level 9 of JDE & report also on that...What is the solution for this kind of problem??Notes : Levels in JDE are equivalent to generations in Essbase

even though it might become a very sparsely populated cube, and I don't know if your business requirements would allow it, can you split the Accounts dimension across three dimensions: BU , Object Account & Sub Account?Or if you are using EIS to build the cube, to use Hybrid analysis to store levels in the hieracrhy relationally?

GL Account Hierarchy related issue

Hi BI gurus,
The Scenario is like this:-
We are doing reporting for Profit&Loss based on GL Account Hierarchy (0GL_ACCOUNT).
The GL Hierarchy have Asset & Liability nodes.
The problem is that, in BW, regardless of credit or debit values, it will just display the report the same values on both nodes. so certain GL accounts (e.g. Cash Loan) would appear both side of the hierarchy - Asset node and Liability node.
Is there a way to make it so when we do reporting based on Hierarchy, when the value's Credit, shows on "Asset Node", and Value's Debit will shows on "Liability node"?
Any advice is greatly appreciated.
Thanks,
Vince

Thanks for the info Yiannis, but I think I've found out the theory for this.
According to this [http://help.sap.com/saphelp_nw04s/helpdata/en/04/7b95fb42b0f94aba334c0890dbbda4/content.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/04/7b95fb42b0f94aba334c0890dbbda4/content.htm]
I have read through it, not fully understand how this works yet, but I think should be able to use the following:-
1. InfoObject 0GLACCEXT (instead of 0GL_ACCOUNT)
The exception aggregation (balance sheet aggregation) that is in effect here is only possible for the Financial Statement Item characteristic (technical name 0GLACCEXT). The hierarchy table for this characteristic contains a special attribute called Balance-Dependency of a Hierarchy Node (technical name 0BAL_DEPEND), which controls the balance sheet aggregation of the Financial Statement Item characteristic.
2. Virtual InfoCube 0FIGL_VC1 (will read data from 0FIGL_C01).
3. There is a balance sheet query available 0FIGL_VC1_Q0001, which displays the balance sheet data the same way as the R/3 report RFBILA00 does.
[http://help.sap.com/saphelp_sm32/helpdata/en/2d/955a73da4d6d41a0a6128caf274ce8/content.htm|http://help.sap.com/saphelp_sm32/helpdata/en/2d/955a73da4d6d41a0a6128caf274ce8/content.htm]
Rgds,
Vince

Essbase import - Accounts Hierarchy missing

Hi all,
well I have a weird one: I'm importing Essbase 9.3.1. cubes into 10.1.3.3.2. and 10.1.3.4. and can't get the "Accounts" hierarchy to be represented correctly in the physical layer.
Normally, Essbase dimensions of type "Accounts" are to be represented as hierarchy objects in OBI EE upon import. I looked at Oracles demo DB (Oracle2go) plus Marks example ([http://www.oracle.com/technology/pub/articles/rittman-essbase.html]) and Venkat ([http://oraclebizint.wordpress.com/2008/05/12/oracle-bi-ee-1013332-hyperion-essbase-connectivity-handling-measures-and-account-dimension/], [http://oraclebizint.wordpress.com/2008/05/08/hyperion-data-integration-management-931-loading-data-into-essbase-cubes-using-type1]) state the same.
What happens here is, that all the measures arrive flat after the import and I end up with my dimensions and hundreds of measures as physical columns.
As mentioned, I tried both 10.1.3.3.2. and 10.1.3.4. for the imports. Plus, I imported several different cubes, all containing Accounts dimensions. Everytime with the same results.
Anyone has got any thoughts on that?
Thanks in advance and cheers,
Christian
Edited by: Christian Berg on Sep 19, 2008 3:41 PM

Did you ever manage to solve this problem? I'm on the verge of starting on a similar initiative and from the info I gathered, it seems that this is as easy as just changing the dimension type of the "Account" dimension to "Other" on the cube itself within the Administrator - and define one of your other dimensions as a "Measures" dimension. I did a quick test and it seems to do the trick - maybe I'm missing something.

GL Account Hierarchy

Hi BW Experts,
Our's is a BW 3.0B system connected to ECC 6.0. In BW we have a hierarchy defined for GL Account which has GL accounts listed in both Assets & Liabilities. This hierarchy is coming from ECC as designed by functional team. The client requirement is : When the GL Account is active with the hierarchy, it should not display the accounts in both Assets & Liabilities. It should only display the accounts in Assets( if it is an Asset Account) & Liabilities ( if it is a liability account). We are reporting on a multiprovider which has the basic infocube.
Example:
GL Account: 10001 - Bank .
In the GL Account hierarchy, Account 10001 - Bank is under Assets & also Liabilities. Std. report in ECC for Balance Sheet and P/L statement, depending on the Net Amount, it goes under Assets or Liabilities group.
In BW, when the hierarchy is activated for the report, as the GL Account is manitained in both Assets & Liabilities: it would display the amounts under Assets -for Eg: 100001 - $1000.00
and also under Liabilities as: 100001 - $1000.00.
Is there a way to do this kind of reporting? Please let us know if anyone had came across a similar requirement or have a soultion for it.
Thanks,
Bala

Hi Bala,
I do understand you need. You cannot figure out the issue with GL Account. You definetly need to use 0GLACCEXT characteristic in a virtual infoprovider like 0FIGL_VC1. Then, you would have a chance to build your balance sheet report with hierarchy. This will prevent double assignment of GL account both in Assets and Liabilities.
Good luck,
MCA

Some hierarchy related issues, SQL Query is including unselected columns?

Hello Guys...
I have something strange happening in my report.. First of all, the RPD I have is built according to JDE model.
There is a schema which looks like this:
BU Dim ------->Fact<---------Account Dim <--------BU Account Dim (Indeed a copy of BU Dim)
A dim hierarchy is created as AccountDim with Account Desc at the lowest bottom level, the dimension key at that level is AcctID which is the unique identifier.
The issue comes when I created a report using Account, Account Desc, Fact Measures. The measures are not displayed as per account even if the joins and aggr levels are all defined correctly at the proper level..
I checked the sql that is generately, it is interested that whenever I include Account Desc column in the report, the SQL will include Actid column in the select and groupby part, which results in data being at the wrong level..
When I remove Actid from Account Hierarchy as the key, the report runs correctly and the SQL query won't include Actid column.. However, since the removal of the ACTid key from Account Hierarchy will cause other reports not running properly, I have to revert the change back to normal.. I'd like to know what to do in order to investigate more deeply as what's going on and as why the SQL will include columns fields that are not selected at answer levels..
Any suggestions will be greatly appreciately.. I'd like to provide the rpd file, but not sure how to..
Many Thanks

Hi, Vikeng,
Why use the salary table at all, if you're not ever getting any information from it?
Why not:
SELECT EmpName
,      DeptName
,      'N/A'          AS SalaryValue
FROM     Employee
,     Department
WHERE      Employee.EmployeeId     = Department.EmployeeId
Are you saying that somethimes there is a relationship, but not with this sample data?
If so, post some different sample data (CREATE TABLE and INSERT statements) that has a relationship for some rows, and not for others. Post the results you want from that data, and explain, with specific examples, how you get those results from that data.
You might just need an outer join.

CRMOD - Account Hierarchy (Relationship)

All ,
I am evaluating CRMOD - Account Hierarchy (Relationship) and I am having a few issue to identify the best practices to import and map the data according to the below scenario. I am not sure, if I am to use Portfolio Accounts / Books , PRM or just a Parent and Child Account relationship. Can someone provide guidance in regards to this requirement?
Scenario 1:
Parent Account (Distributor 1) has a 1:M Child Account(Partner 1) to which will have 1:M Sub Child Account(Customer 1)
Scenario 2:
Parent Account (Distributor 2) has a Child Account (Partner 2) to which will have Sub Child Account(Customer 1-same as the above)
Regards ,
Patrick

To create a parent child relationship in Accounts:
You create the account and then create the Sub-accounts accordingly. When you create the sub-account (b) to an account (a) the account b will have its parent account name defaulted with value of the parent account (a)
To import using import wizard:
1. Load all parent accounts with an External Unique Id
2. Then load the sub-accounts with External Unique Id and The parent account External Id (which is specified in step 1)
eg
parent account import
Account Name, Ext Id
ABC, 123
Sub-account import
Account Name, ext id, par account extid
def, 789, 123
ghi, 901, 123
Once you complete loading you can see parent account abc has 2 child accounts def and ghi - hope this helps

BPC Alternate hierarchy rollup issue - require help

Hi All,
We are seeing a rollup issue on Alternate Hierarchies. We had set-up alternate hierarchies on our Country Dimension (DC) to assist some managerial reporting that is only relevant to one of our Operating segments.
To show the problem, I am listing an example of our Country dimension member sheet. I have put "**" delimiter between the pertinent values to show which columns the values land under.
ID*DescriptionPARENTH1PARENTH2FORMULAH1*FORMULAH2
MAIN_HIER*Main Hier* ** ** ** **
D1*DC EuropeMAIN_HIER* ** ** **
A*Country AD1SG1* ** **
B*Country BD1SG1* ** **
C*Country CD1SG2* ** **
D*Country DD1SG3* ** **
D2--DC India*MAIN_HIER* ** ** **
E*Country ED2--ALT_HIER* ** **
C1*Calc Eur* ** *DC.H1.D1+DC.H1.E* **
ALT_HIER*Alt Hier* ** ** ** **
SG1*Sub Reg 1* *ALT_HIER* ** **
SG2*Sub Reg 2* *ALT_HIER* ** **
SG3*Sub Reg 3* *ALT_HIER* ** **
We have our main Country hierarchy that comes under the root parent MAIN_HIER. In addition to that on our main hierarchy we had a calculated node for Calc Europe (C1) which is supposed to be a summation of DC Europe (D1) + Country E (E). We had created an alternate hierarchy to represent a breakdown by more subregions (SG1, SG2, SG3 and Country E) within DC Europe so basically the root node of the alternate Hierarchy (ALT_HIER) should show the same amounts as the calculated node C1 on the main hierarchy.
If we take a higher level Account dimension member like NET_SALES the values tie out but if we take a base member in the Account Hierarchy (e.g one representing Customer Sales), the values don't match with the ALT_HIER values seem being the wrong ones. It almost seems like the rollups of the Alternate Hierarchy are not accurate.
Could you pls. shed some light on if the dimension member set-up above is wrong from any angle.
BTW, we are on BPC 7.0M SP04 Patch 2 and SQLServer version is SQLServer 2005 EE SP3.
Your insights would be greatly appreciated. Thanks in advance.
Regards,
Abhay Shanbhag

Abhay:
Please try below...
Add "RollupChildren(Account.Hx.CurrentMember,"+") to all non-base members who don't aggregate properly under FORMULAHx. For instance, I have below hierarchy PARENTH1 for Balance Sheet Total Asset
BALSHEET
TotalAsset
-CurrentAsset
-NonCurrentAsset
If CurrentAsset and NonCurrentAsset all roll up fine but TotalAsset doesn't add up. In your Dimension, put MDX formula RollupChildren(Account.H1.CurrentMember,"+") for TotalAsset and BALSHEET under FORMULAH1.
We have this issue when we created additional hierarchies, and it took us a while to debug before I got this hint from SAP Support. Ever since it works like a charm =)
Hope this helps
Brian

Restricted account hierarchy nodes

Hi BI Gurus,
I have a requirement to generate Profit and Loss statement in BI. I pulled up account hierarchy out of R/3 into BI.
The issue is client want to see some nodes of the account hierarchy restricted by specific Functional Area only.
Please suggest some solution.
Regards,
MV

Hi KK,
Can you please explain about manually restricting the nodes instead of using hierarchy? Should it be done at R/3 or BI level and how?
At R/3 level in Report Painter reports each node of the account hierarchy can be easily restricted to a particular Functional Area (at account node or set level) and client want to achieve the same in BI.
Also the account hierarchy should not be maintained at two places. Since well maintained account hierarchy is already there in R/3 which is why BI pulled it from there; now they are looking for ways to restrict some of the nodes by Functional Area.
Hope I have explained the situation with all the variables.
Please provide your valuable suggestions.
Thanks & Regards,
MV

SQL Load from Oracle into 64 bit Essbase 9.3.1 - issue

I have a sql load that works fine in 32 bit Essbase 7.1.5
Now I have setup the same sql load in a new 64 bit Essbase 9.3.1 environment. SQL runs. However when it retrieves it is not retrieving some fields "correctly". For example I have some extract functions in the SQL to extract the month or year from a date field. These are returning "0" now for the month or year. (the function syntax is correct as it works in the 7.1.5 environment. Plus for all my fields that are returning numeric dollar values, they are returning a value of "0" instead of the correct value (which it returns in the 7.1.5 environment).
The sql works correctly if run in SQLPlus. So Essbase is having the issue.
Any ideas?
Edited by: Sean V on Jun 5, 2009 7:48 AM

Hi Sean,
If you can do it yourself or someone else who can do it for you,
create a view in your db schema you are connected to and use a tool like Oracles SQLDeveloper (it's for free) or something similar to check your query result by select from your view.
This way you can hide your internal logic behind this view and no one has to worry about it.
From my POV this approach has no drawback but only advantage for you.
If it works as expected put the view into your rules file (I do assume you are using rules files)
Example (you need the CREATE VIEW privilege for you account(schema)):
CREATE v_dataload as
SELECT DIM_COL1 as year , DIM_COL2 as month, DIM_COL3 as market , DATA_COL1 as profit, DATA_COL2 as costs .... etc.,
In you rules file you then just put in the SELECT box: year,month, profit, costs ...
and in the table box: v_dataload
If you name you columns like the Dimension (Gen1) you have the comfort that essbase automatically maps the columns tho the appropriate dimension. (But remember a colum in Oracle can have only up to 30 Characters)
Back to you question:
If you get a correct result from you view when using SQLDeveloper but not in you rules file I would say it's very likely a ODBC driver problem.
If so, please check if you have installed the correct driver for your system. MERANT driver is the best choice as fare as I know.
In normal cases you never should have to cast anything into a VARCHAR, since exactly this is the job of the ODBC driver.
However, if everything fails and a cast (like Glen said) is the only way you can make it work put this cast into your view too.
CREATE v_dataload as
SELECT TO_CHAR(DIM_COL1) as year , TO_CHAR(DIM_COL2) as month, TO_CHAR(DIM_COL3) as market ,TO_CHAR( DATA_COL1) as profit, TO_CHAR(DATA_COL2) as costs .... etc.,
Regards
Andre
Edited by: andreml on Dec 16, 2009 12:52 PM

COST GL account when goods issue - enhancement or user exist

Hello SAP exports,
There is a requirement from F&A department for different COGS GL account based on Customer Account Assignment Group value when goods issues (GI) (goods movement). Customer Account Assignment Group field name is KNVV-KTGRD.   The solution is NOT possible for standard SAP SD (pricing procedure) / MM (T-Code:OBYC with GBB).    Therefore, I am searching solution for enhancement.
the requirement is like following:
KNVV-KTGRD                                   COGS GL account at goods issue
01                    Domestic                   818100
02                    Export                       818200
03                    Testing - sample         818300
04                    Testing - VOM            818400
05                    Franchise                   818500
Can you please let me know what and how this can be resolve by enhancement or user exist?
Thank you.
Kind Regards,
Sylvia Chen

Hello,
The requirement is to provide different COGS GL account based on the Customer Account Assignment Group value(KNVV-KTGRD) when SAP performs goods issue. for example, movement type 601,
This means, when company ships goods to differnt customers, then SAP should generate different COGS GL account.
for example, when company ships goods to customer account assignment group '01' (Domestic customers), then SAP should generate COGS GL account 818100.
when company ships goods to customer account assignment group '02' (export customes), then SAP should generate COGS GL account 818200.
when company ships goods to customer account assignment group '03' (Testing - sample customers), then SAP should generate COGS GL account 818300.
the logic is following:
KNVV-KTGRD              COGS GL account at goods issue
01 Domestic                 818100
02 Export                     818200
03 Testing - sample      818300
04 Testing - VOM         818400
05 Franchise                818500
I am not good at user exist.
Can you please provide solution with step-by-step guide?
Thank you.
Regards,
Sylvia Chen

Design issue with the multiprovider

Design issue with the multiprovider :
I have the following problem when using my multiprovider.
The data flow is like this. I have the info-objects IobjectA, IobjectB, IobjectCin my Cube.(Source for this data is s-systemA)
And from another s-system I am also loading the masterdata for IobjectA
Now I have created the multiprovider based on the cube and IobjectA.
However, surprisingly join in not workign in multiprovider correctly.
Scenario :
Record from the Cube.
IObjectA= 1AAA
IObjectB = 2BBB
IObjectC = 3CCC
Records from IobjectA =1AAA.
I expect the record should be like this :
IObjectA : IObjectB: IObjectC
1AAA       :2BBB       :3CCC
However, I am getting the record like this:
IObjectA : IObjectB: IObjectC
1AAA       :2BBB       :3CCC
1AAA         : #             :#
In the Identification section I have selected both the entries for IobjectA still I am getting this error.
My BW Version is 3.0B and the SP is 31.
Thanks in advance for your suggestion.

May be I was not clear enough in my first explanation, Let me try again to explain my scenario:
My Expectation from Multi Provider is :
IObjectA
1AAA
(From InfoObject)
Union
IObjectA     IObjectB     IObjectC
1AAA     2BBB     3CCC
(From Cube)
The record in the multiprovider should be :
IObjectA     IObjectB     IObjectC
1AAA     2BBB     3CCC
Because, this is what the Union says .. and the Definition of the multiprovider also says the same thing :
http://help.sap.com/saphelp_bw30b/helpdata/EN/ad/6b023b6069d22ee10000000a11402f/frameset.htm
Do you still think this is how the behaviour of the multiprovider.. if that is the case what would be the purpose of having an infoobject in the multiprovider.
Thank you very much in advance for your responses.
Best Regards.,
Praveen.

Data mart from two DSOs to one - Loosing values - Design issue

Dear BW experts,
I´m dealing with a design issue for which I would really appreciate any help and suggestions.
I will be as briefly as possible, and explain further based on the doubts , questions I received in order to make it easier go through this problem.
I have two standard DSOs (DSO #1 and #2) feeding a third DSO (DSO #3), also standard.
Each transformation DOES NOT include all fields, but only some of them.
One of the source DSO (let´s call it DSO #1) is uploaded with a datasource that allows reverse type of records (Record Mode = 'R'). Therefore some updates on DSO #1 comes with one entry with record mode 'R' and a 2nd entry with record mode = 'N' (new).
Both feeds are delta mode, and not the same entries are updated through each of them, but the entries that are updated can differ (means an specific entry (unique key values) could be update by one of the feeds, but no updates on the 2nd feed for that entry).
Issue we have: When a 'R' and 'N' entries happen in DSO #1 for any entry, that entry is also reversed and re created in the target DSO #3 (even being that not ALL fields are mapped in the transformation), and thefore we loose ALL the values that are exclusively updated through DSO #2, becoming blank.
I don´t know it we are missing something in our design, or how should we fix this issue we have.
Hope I was more or less clear with the description.
´d really appreciatted your feedback.
Thanks!!
Gustavo

Hi Gustavo
Two things I need to know.
1. Do you have any End Routine in your DSO? If yes, what is the setting under "Update behavior of End Routine Display"....Option available right side of Delete Button ater End Rouine.
2. Did you try with Full Load from DSO1 and DSO2 to DSO3? Do you face the same problem?
Regards
Anindya

Considerations should be taken into account when designing an RTF Template

What overall considerations should be taken into account when designing an RTF template?.
For example, how the tables should be set. When the report is running, I don't want to happen to the fields leaving the position defined during design.

Hi,
from my point of view, so general questions are not answered there...
One note,
I'm trying to get the data first, "load it" (for example) into Word and only then generate the tables using the wizards. This will give the effect.
Eldar A.

Essbase Accounts Hierarchy--- Design Issue

Similar Messages

Maybe you are looking for