Planning Analytics Local - SAP BW data source using Cognos Integration server (CIS)

[gabi]

Hello,

I wonder if someone use CIS for loading BW data to TM1 and can advise on a problem.
As TM1 ignore spaces and considers 'Act Vs Bud' to be equivalent to 'ActVsBud', I have problem to load BW metadata where there are elements with spaces which TM1 ignore so we have 2 identical elements in the dimension.
(Example 'Sample 1' & 'Sample1').
Customer insist to have direct connection from TM1 to BW without use of text files (can be generated from CIS).

Any idea how to avoid duplicates elements (when space ignored) when loading BW metadata from BW using CIS?

Thank you,
Gabi

[tomok]

As TM1 ignore spaces and considers 'Act Vs Bud' to be equivalent to 'ActVsBud', I have problem to load BW metadata where there are elements with spaces which TM1 ignore so we have 2 identical elements in the dimension.

I don't see how it is possible to have 2 identical elements in TM1. If you have 'Act Vs Bud' in the dimension and try to add 'ActVsBud' then TM1 will not add the 'ActVsBud' because it thinks it already exists. I just confirmed this by creating a dummy dimension myself , adding 'Act Vs Bud', saving, and then trying to add 'ActVsBud'. It wouldn't let me add 'ActVsBud'.

[gabi]

No, It's not possible to have 2 identical elements in the same dimension.
My question is for the CIS selection to load dimension from BW as CIS fail to load the dimension.
I'm looking for a way to bypass this limitation by an option to rename one of the elements and allowing to load the data to the correct intersection afterwords.

[Wim Gielis]

I have not used CIS before. Does it bypass Turbo Integrator ? If not, and there is still a TI process: what I tend to do in similar situations, is have the TI wizard generate code. Then copy/paste the generated statements below and turn off these sections (simply: If(1=0) kind of test). Then below you can add whatever logic is needed to have the dimensions/ data loaded correctly. Hope this applies to your situation.

[gabi]

Hello Tomok,

Thank you for your reply.
All process is running from CIS on TM1 so there is no option to add manipulations to the process.
I found that during CIS process execution, pro file is created and deleted afterwards - This is just for the attributes phase.
I didn't see any (temp) pro files for dimensions and cube loading.

There is an option in CIS to load metadata and data to csv files (create csv in TM1 model folder) and also create the process in TM1 in order to be able to load from the csv file.

Thank you,
Gabi

[gtonkin]

I have had a similar problem in the past where I received elements from a source system like Sample 1 and Sample1 and they meant different things in the source system.
I was forced to substitute spaces with another character e.g. tilde (Sample~1, Sample1), in all subsequent processes the dealt with metadata/imports.
On export I would do the reverse. Looks a bit silly but solved my issue - YMMV