Thursday, April 11, 2013

Transactional Reporting in TM1 – Some Guidelines


Can TM1 report transactional data?
Yes but further questions need to be asked on business process, volumes and dimensionality

What Volume limitations are there?
You will always be limited by the amount of physical RAM within the box but a key consideration will always be the dimensionality required. Does a table field become a measure or a dimension will need to be carefully thought through. Does that field become a prompt in a report or a filter? Does it have multi-level hierarchies on it?

How can I reduce Volume?
Think about only storing a certain time period of transactional data e.g. a rolling 12 months or maybe just the current financial year.
Does the transactional data need to be physically stored in TM1. Can you instead do drill through to transactions from balance. Always question the business process and whether they can do exception inquiries vs data dumps
Transactional cubes should hopefully not contain any rules.

What Dimensionality limitations are there?
You can build a 256 dimension cube in TM1 but why would you if you can never find the data you want.
Cubes within TM1 should always be built to a business purpose. Mega cubes are never an answer. Think about the prompts and filters that users require.
If the cubes requires multiple date dimensions (date created, date sold, date invoiced etc) then your sparsity in the cube will naturally increase. In memory cubes will struggle to compete with ROLAP cubes in this regard.

How can I reduce dimensionality?
Can a dimension become a measure.
Can you merge 2 or 3 dimension into 1 by concatenation e.g. CostCentre-Project-Employee

What is the appropriate tool to display the results in?
TM1 Active Forms – Easiest and most flexible since you can report from multiple cubes, pass MDX queries etc. Issue is acceptance in BI deployment
Report Studio – Possible but long time to get right. Need to remember cross tabs don’t do strings only lists. Querying multiple cubes will require prompt macros
Analysis Studio – Will struggle with  multiple dimensions on rows and wont display strings
Don’t forget strings will only appear typically at the lowest level of the cube i.e. all N levels

Saturday, December 15, 2012

952 FP3

952 FP3 has now been released.
Details can be found here:

http://www-01.ibm.com/support/docview.wss?uid=swg27036833&myns=swgimgmt&mynp=OCSS9RXT&mync=E

Sunday, December 02, 2012

TM1Web Skinning


To adjust the banner in tm1web to be visibly different between environments i.e. DEV/UAT/PRD

Go to this location:

C:\inetpub\wwwroot\TM1Web\images\banner\

Edit the file banner-background.png in paint and then rename  banner-swoosh.png to be banner-swoosh - Old.png so it doesn’t appear.

TM1 10 and Congos configuration – The Good, The Bad and The Ugly

My blog post on the Tridant website about TM1 10 and Congos configuration – The Good, The Bad and The Ugly:

http://www.tridant.com.au/blog/tm1-10-and-congos-configuration-the-good-the-bad-and-the-ugly-james-wakefield/

Remove TM1 Portlets

Interesting article here on how to properly remove TM1 portlets from cognos:

http://www-01.ibm.com/support/docview.wss?uid=swg21619034&myns=swgimgmt&mynp=OCSS9RXT&mync=E

Thursday, October 25, 2012

Saturday, October 13, 2012

Cognos BI and Salesforce

As of Cognos BI 10.2 you can report of Salesforce direct without the need for Virtual View Manager:

http://www-01.ibm.com/support/docview.wss?uid=swg21614133&myns=swgimgmt&mynp=OCSSEP7J&mync=R

Friday, October 12, 2012

IBM Cognos Fix Packs

You can find a list of upcoming Cognos Fix Packs here:

http://www-01.ibm.com/software/data/cognos/support/fixpacks.html

Note that 952 FP3 is coming out probably before the end of the year

Thursday, September 20, 2012

Run-time error '53':File not found: tm1xl.ocx

If you are installing TM1 10.1 or TM1 10.1.1 the you will probably be asking your IT department to make sure they install the pre-requisites on the server.

You will find them here:

http://pic.dhe.ibm.com/infocenter/ctm1/v10r1m0/topic/com.ibm.swg.ba.cognos.tm1_inst.10.1.1.doc/c_tm1_inst_requiredsoftwareconfiguration.html

Note how it asks for "Microsoft Visual C++ 2005 SP1 Redistributable Package"

The IT department seeing TM1 is 64 bit will probably only install the 64 bit version of the package. I have even seen them install not the SP1 version. The problem will come that if they don't install the x86 version and TM1 perspectives gets installed you will receive the error Run-time error '53':File not found: tm1xl.ocx when you open perspectives.

Obviously the fix is to install the x86 version of the C++ but hopefully this post will stop many back and forth emails between you and IT