TM1 Forum

You can move actuals to budget by rules alone. Start month/start year may be stored in a parameter cube and read out by the rule. You don't have to write a rule for every month. Take a look at the DIMNM/DIMIX-example in the rules manual. Since you have only one time dimension it is easy to apply in ...

welcome to the forum! some thoughts: - you probably need to duplicate your dim_store to be able to display it on two axis. - this leads you to the "many-to-many dimension" concept in SSAS. Search for examples on the web if this fits your need. - defining dim_store as "role playing&quo...

Hi Jennifer, what is written in the ASCIIOUTPUT-file eMediaOutput.cma? You may keep programming simpler in the development stage. Take only some source rows as input and no errorhandling. If you run on an error, TI gives you the error and you know where to search. Always use ASCIIOUTPUT to check ele...

Hi Stanislav, since you are transfering Actuals, you could as well transfer the values with TI and store them physically in cube B. Assuming you have no end user interactivity for Actuals. Write a process that runs after you have loaded your Actuals in cube A. Another point is the summation SAP3000 ...

well, read out your parameter from your parameter cube and put it in subset. Then assign subset to your view: like: # (3) Subset for month #Monat auslesen mon = CellGetS('z_param', 'Ben Allg', 'Para102', 'pardat_s2'); SubsetDestroy('Monat', 'z_mon'); SubsetCreate('Monat', 'z_mon'); SubsetElementInse...

Hi,
late answer but maybe useful for others.
The message appeared in my case when there were restrictions applied for the SAP cube in TI. Search for "addInfoCubeRestriction(...)" in your process and if existent check if the attributes in brackets fit to the cube in question.

HTH,

Marcus

Paul, if you are working in a Microsoft environment, why are you using TM1 for pure reporting? For Reporting you can use Analysis Services alone. I suppose IBM will not invest much effort in the Reporting Services connection because there is Cognos Connection , Report Studio, Analysis Studio etc alr...

Hi, I would convert it in the TI script. If I will have to change the sign while loading the data into TM1 (using TI process) then I will have to change the signs again when offloading the data from TM1 to the backend database. Yes, there's work in sight either for you or someone on the backend side...

Hi Bane, if you are referring to the mondrian example, don't ignore the already existing parent levels (e.g. "All Marital Status"): your statement is: select {[Measures].[Unit Sales]} ON COLUMNS, {Crossjoin([Gender].[Gender].Members, [Marital Status].Members)} ON ROWS from [Sales] Try out ...

Harry, check your TI script for the CellPutN section. For a 4 dim cube it should be something like #****Begin: Generated Statements*** CellPutN(Value,'cubex',Dim1,Dim2,Dim3,Dim4); #****End: Generated Statements**** You need to specify the element for the "measure dimension" as well. Your &...

I would not give users control to edit dimensions. The process has to be controlled by an administrator. There could be a template where users enter the elements in a structured way (leaf element, according parent element). The admin would integrate this template as a meta data source into the dimen...

Hi, you may set the default memeber for each dimension in the cube "}HierarchyProperties". The according dimension "}HierarchyProperties" contains an element "defaultMember". This might help you in creating reports, if many of them have some default members in common. s...

to check if data are in the cube did you export your TM1 cube data into a flat file and see if something is written into the file?

I found no way to let control cubes show up in FM. A workaround would be to create a new normal cube with the same dimensions that build your control cube. Not nice of course. For view stats you would need to populate it with rules probably.

Kaveenga,

from an MDX query point of view you can't put members of one dimension on more than one axis. So I wonder how you did with SSAS/SSRS. -> You may have used "role playing dimensions". You may show us an example. The MDX for the Cockpit query would be interesting, too.

You need Cognos 8.4 BI to connect to existing TM1 cubes. In Framework Manager 8.4 you can select TM1 as a data source and create a package. Make sure to set the measure dimension before in TM1. Then you may use Analysis Studio or Report Studio to create ad hoc- or standard reports. I don't know if t...

did you test it? Changes not saved to disk are retrieved by Server2?

Good luck - they will always come back!

Marcus

PS: Of course I'm passionate to OLAP, but I didn't succeed in extending it to my family members and friends. It's so far away for them, I could as well talk of craters on the moon. Don't know how you are approaching this issue...

it works with

DimensionElementPrincipalName

and an ; after your endif

Regards,

M.

The trend I have been seing in the market the last few years is rather the reverse though. I have seen large companies (finally) make inventories of all the different BI software packages that somehow got implemented at this or that department with one goal: reduce the number of different software ...