You are able to see Data for the Account mentioned , so its not an issue with the TB property you mentioned . As I see , in the last column you are trying to fetch YTD data.
Just make sure if your cube is set for YTD aggregation. For that , Open outline go to period property and check its properties. Also if there are any formulas concerned with these retrievals , make sure they work for YTD . Else no way you can expect the data to roll up for Y-T-D.
If work with Dynamic Calc members try this solution
-> use TwoPass calculation option on member properties.
Had already tried the Two pass calc. Its not working.
You can use the MDX formula using Openingperiod () function to achieve the tbfirst value for account "nf400210020".The OpeningPeriod() function fetches a FirstDescendant and it can be applied and works on any dimension.
WHEN IsGeneration ( [Account].CurrentMember,3 ) THEN
I took a look at Sample.Basic and see that TBFirst works just fine with Dynamic Time Series:
Market Actual Product Opening Inventory Jan 117405 Opening Inventory Feb 116434 Opening Inventory Mar 115558 Opening Inventory Qtr1 117405 Opening Inventory Qtr2 119143 Opening Inventory Jul 143458 Opening Inventory Aug 142587 Opening Inventory Sep 142215 Opening Inventory Qtr3 143458 Opening Inventory Qtr4 141850
Opening Inventory Year 117405
Opening Inventory H-T-D(Jan) 117405
Opening Inventory H-T-D(Feb) 117405
Opening Inventory H-T-D(Mar) 117405
Opening Inventory H-T-D(Apr) 117405
Opening Inventory H-T-D(Sep) 117405
Opening Inventory H-T-D(Dec) 117405
If you go to that application, can you get the same results?
What happens with a non-TBFirst member in your database? Does it add up?
I'm wondering if your Y-T-D DTS is maybe not pointing to the right generation.
Can you show doxumentation when aso stat support dts.?
Who's talking about ASO?
Per the OP:
>>The cube i am working on is BSO.
Is your "Y-T-D(09)" a dyn-calc member with a member formula by any chance?
>>Is your "Y-T-D(09)" a dyn-calc member with a member formula by any chance?
^^^Pretty sure any time you see a Y-T-D(periodname) you're looking at Dynamic Time Series. And yes, that is a dynamic calc, but one that is supported natively in BSO Essbase and handles time balance automatically.
I don't recall why it was setup this way originally, but we actually do not use the native Dynamic Time Series functionality in our BSO cubes. We use a member formula instead ("@PTD (Jan:Dec)" for YTD-Dec, etc.). If that's how the OP has his YTD implemented, then he might want to check his member formula for the YTD members..