Need to make a change in existing TM1 application

[alia]

Sorry for very open question. I come across a senario where i have to make modification to an existing TM1 application and can not understand where to start it. Here is the current situation

I have a volume cube with followig dimension
Airline,
workstation,
version,
month

Currently the workstation dimension has attribute license or common and it does not change. so far we do not have any issue to load the data in above cube

Now the requirment has change the workstaion attribute license and common change every month. I need to know how i can maintain the list of workstation monthly basis and load the data in volume cube based on monthly workstation list Any help is really appreciated

[winsonlee]

Has the changes for license and common attribute been updated on the workstation dimension ? or you are looking for solution on how to update the attribute on the workstation dimension ?

[TrailRunnerMark]

Hi,

That is pretty open ended! I didn't understand from your post if the attributes of the workstation elements changed or if you get new workstation elements each month. You will have to give a bit more information.

If the elements in the workstation dimension are changing each month (i.e. new workstations), then you will need to add new workstations to that dimension so you have somewhere to load the data. That is a dimension maintenance issue.

If only the attributes of each workstation are changing, that shouldn't affect the ability to load data.

[alia]

First thank for responses. Current application has workstation dimension and that dimension has all the workstation with attribute license or common.

Now the requirment has change the same workstation can be license in one month and common in another month because the rate are diffrent for license and common, i have to maintain the list of workstation (license or common) by month. Now my issue is how i can load the data in volume cube for each workstation and properly aggregated for licnese and common workstation in volume cube

For example

XYZ123 workstation in Jan is license but in Feb it is common
In Jan it has 200 value but in Feb it is 300

when i load the data in volume cube we like to see

------------------------------- ----- Jan-----Feb
All workstation -------------------200-----300
common workstation-------------200
XYZ123 ----------------------------200
License workstation------------------------ 300
XYZ123---------------------------------------300

Now issue is how i can maintaian the monthly list of workstation for license and common and than load the volume cube for workstaion list based on month. Hope i make scense here. I am looking some hint or guidance how to start.

My idea is to craete another cube for workstation with elements (workstation, month, license) and the license element has value yYor N. Every month I load the cube for license or common workstation value Y OR N. What i do not understand undertand is how i can load the volume cube based on new workstaion cube and maintain the list of workstation in volume cube as deined in workstation cube for each month

[winsonlee]

when you mention common, what is it referring to ? From the hierarchy, common and license looks like a consolidation element instead of an attribute. The number that you are providing is a count of how many work station there are ?

I presume your source data looks something like the following ?

workstation name Month common license
XYZ123 Jan Y N
XYZ123 Feb N Y


If that is the case you can write code in metadata to insert the workstation name
if ( common = 'Y')
DimensionElementComponentAdd( dimname, 'common workstation', workstationname);
else if (license = 'Y')
DimensionElementComponentAdd( dimname, 'license workstation', workstationname);

in the data tab

if( common = 'Y')
CellPutN(1, cubename, 'common workstation', workstationname, monthname)
else if ( license = 'Y'
CellPutN(1, cubename, 'license workstation', workstationname, monthname)


of course if it is a total refresh of data to the cube, you have to empty the cube data and repopulate.. and for the dimension you can break all the child and parent relationship and reattach when you run the process.

[tomok]

For example

XYZ123 workstation in Jan is license but in Feb it is common
In Jan it has 200 value but in Feb it is 300

when i load the data in volume cube we like to see

------------------------------- ----- Jan-----Feb
All workstation -------------------200-----300
common workstation-------------200
XYZ123 ----------------------------200
License workstation------------------------ 300
XYZ123---------------------------------------300

This is not an example of an attribute, it's an example of a hierarchy. The problem with making Common and License nodes in the workstation hierarchy is they can't vary with time. This is a common issue with TM1. It's quite difficult and/or convoluted to have a solution where the hierarchy is supposed to vary with time yet you want to maintain the history. Your best answer would be to add another dimension to the cube, call it WS_Type and it would look like this:

All Types
.....Common
.....LIcense

This way you can load the data for each workstation into the appropriate type for each month and maintain the proper history.

[alia]

Thanks you guys. Tom you are right on spot. This is what i am trying to achive to maintain the history of workstation by month for history data. For example if workstation xyz123 in Jan has 200 as common license but same workstation in Feb has 300 as license than i want to see both in hierarchy.

Currently workstation dimension has attribute for each workstation as license Y or N and it never change and when i load the data in volume cube whcih has (workstation, month, airline) elements than no issue because workstation history is not changing

Now i need to maintain this change in volume cube. Can you please advise how to set the herarchy of volume cube for license workstation and common workstation. From volume cube i need to consolidated all license workstation in license total with the detail of each workstation and same as common workstations in common total and than consoliadted everything to one as all workstation. Consilidation is important for us because rest of the application base on consoliated data only volume cube needs the detail data and we have to submit detail data to client.

I got what you said to add one more dimension in volumen cube for common and license only thing i need to understand now how it can cosolidate it with detail workstation as i showed in by previous entry. But thanks you guys, i need to make sure how i am going to achieve this as you know wrong start will lead to disaster

current application

Volume cube has (airline, workstation, months,value) members
Workstation dimension has attribute License and Common as Y OR N
Based on workstation attribute hirarchy in volume cube is build whcih is statics at this time
The input come in (AA, XYZ123, Jan, 200)

Now i need to maintain workstation list by month for historical data which is goign forward will not static. So i can not use attribute for worksattion any more. To manitisan history as Tom said i need time dimension with workstation

[tomok]

To manitisan history as Tom said i need time dimension with workstation

No, you don't. I gave you the solution, don't know why you are ignoring it. Yes, I will admit it is not "ideal" because the Common and License nodes are not rollups in the workstation hierarchy but that's just the way it is. This is a common problem with TM1 and if you can figure out a way to do what you want, exactly as you want it, on this then you'll be breaking new ground and will have solved something that those of us with years of experience haven not been able to do.

To see the consolidated amounts for Common or License you have to pick the Common or License node from the Type dimension and then all workstations, with the view zero-suppressed. This way workstations that don't have values for the one selected are not shown.

[alia]

Thank you TOM. I am not ignoring your advise and will follow to add new dimension in volume for license and common workstation. This is only solution i can pull in short time.

But I also like to understand for knowledge purpose only some more options such as slow changing dimension or attaching attribute to time dimension can be worked in my scenario and TM1 has this concept. TOM this more inquiry is for knowledge purpose only. I already accept your solution and will go for it

Thank you