Dear all,
A question from a newcomer in TM1. I would appreciate your inputs/pointers.
In a TI process which is used for Data copy between say cube to cube or csv file to cube,
1. Should the Parameters in this TurboIntegrator process should always be on the dimensions of the Source cube/Source? Or should it be on the dimensions of the target Cube ?
Thanks in advance!
Parameter in TI process
- Steve Rowe
- Site Admin
- Posts: 2417
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Parameter in TI process
Hi Pluto, welcome,
(This assumes you mean parameters rather than variables as defined in a TI process)
The short answer they should be whatever you need them to be...
Typically for the scenario you describe they will be some of the dimensions of the source cube, i.e. time and version
(This assumes you mean parameters rather than variables as defined in a TI process)
The short answer they should be whatever you need them to be...
Typically for the scenario you describe they will be some of the dimensions of the source cube, i.e. time and version
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- MVP
- Posts: 3119
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Parameter in TI process
True. Usually you have these parameters:
pSourceYear
pSourcePeriod
pSourceScenario
pSourceVersion
pTargetYear
pTargetPeriod
pTargetScenario
pTargetVersion
If data comes from a csv file, typically the first 4 parameters drop.
pSourceYear
pSourcePeriod
pSourceScenario
pSourceVersion
pTargetYear
pTargetPeriod
pTargetScenario
pTargetVersion
If data comes from a csv file, typically the first 4 parameters drop.
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 10
- Joined: Wed Dec 13, 2017 4:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: 2016
Re: Parameter in TI process
Thanks Steve for the welcome and the reply, thanks Wim as well.
So, Parameters can be taken anything based on the individual requirement.
Some more fundamental questions please. I would appreciate your inputs.
For such a Data copy TI process between say cube to cube or csv file to cube, sequence of steps and respective questions are:
1. Set the parameters.
2. Prolog:
We have to create a VIEW based on the SOurce cube. Each of the Dimensions of this view has to be created from the Source cube dimensions.
Then ZeroOut of the Target is done.
Que.
In this tab, if we have to change the dimension of the source cube, then it is done here. Is this correct ?
I am not able to understand clearly what is the function of the Metadata tab.
4. DATA Tab:
In this tab, whatever lines of code is written, it will be applied on each row of record in the Source cube. Is this right?
While writing the data in to the Target, in the CEllPUTN or like wise command,
Should we use Variables imported from Source like vScenario, vYear etc..
or
Should we use Parameters created like pScenrio, pYear etc.. ?
What is the difference between the above cases?
Thanks again in advance! Greatly appreciate your help!
Best,
Pluto
So, Parameters can be taken anything based on the individual requirement.
Some more fundamental questions please. I would appreciate your inputs.
For such a Data copy TI process between say cube to cube or csv file to cube, sequence of steps and respective questions are:
1. Set the parameters.
2. Prolog:
We have to create a VIEW based on the SOurce cube. Each of the Dimensions of this view has to be created from the Source cube dimensions.
Then ZeroOut of the Target is done.
Que.
- Is it complusory to create every dimensions of the Source cube in the VIEW ?
- Why is this VIEW necessary in the first place?
- Should the dimensions of the View be created in same order as the order in which dimensions are present in the Target cube?
- Why ZeroOut is necessary ? Won't the TI process overwrite the existing data when it runs successdully?
In this tab, if we have to change the dimension of the source cube, then it is done here. Is this correct ?
I am not able to understand clearly what is the function of the Metadata tab.
4. DATA Tab:
In this tab, whatever lines of code is written, it will be applied on each row of record in the Source cube. Is this right?
While writing the data in to the Target, in the CEllPUTN or like wise command,
Should we use Variables imported from Source like vScenario, vYear etc..
or
Should we use Parameters created like pScenrio, pYear etc.. ?
What is the difference between the above cases?
Thanks again in advance! Greatly appreciate your help!
Best,
Pluto
-
- MVP
- Posts: 3119
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Parameter in TI process
Pluto,
You ask a lot of questions, but they are all pertinent. Typically such questions are treated in (custom or standard) Turbo Integrator courses.
But here's an answer to the questions.
Is it complusory to create every dimensions of the Source cube in the VIEW ?
==> Not needed. If you do not limit a certain dimension, then all elements will be taken by TM1 for that dimension. Very often in the view source we skip consolidated cells, and cells that are 0, and cells that are calculated with rules. Therefore, very often, only the leaf level elements remain when you do not set a filter on a dimension.
Why is this VIEW necessary in the first place?
==> to grab the cells of which the values need to be transferred to the target...
Should the dimensions of the View be created in same order as the order in which dimensions are present in the Target cube?
==> not needed
Why ZeroOut is necessary ? Won't the TI process overwrite the existing data when it runs successdully?
==> If you use CellPutN and the source changes (like a value going from 100 to 0) then the 100 that was in the target cube since the last run of the process, will not be cleared automatically. You have to do that yourself with a ViewZeroOut function (or similar functions like CubeClearData, CellPutProportionalSpread, a.s.o.).
In this tab, if we have to change the dimension of the source cube, then it is done here. Is this correct ?
==> Most likely, dimensions in the target cube. For example, you copy data for employees, and a new employee should be created in the respective dimension in the target cube such that in the Data tab of the process you are able to load data on that employee.
In this tab, whatever lines of code is written, it will be applied on each row of record in the Source cube. Is this right?
==> Yes, every cell that survives your settings of yes or no skipping consolidations, zeroes, rules cells
While writing the data in to the Target, in the CEllPUTN or like wise command,
Should we use Variables imported from Source like vScenario, vYear etc..
or
Should we use Parameters created like pScenrio, pYear etc.. ?
==> Depends. For example, if you copy all data for all employees onto a dummy employee in the target cube, it will probably be pEmployee (pEmployee could be set to 'No employee' or similar). If you copy data employee by employee, it will probably be vEmployee (vEmployee being the variable for the dimension elements of your source). Or vEmployee could be the result of a lookup (like an account could have an attribute with an employee name, then you could have: vEmployee = Attrs( 'Account', vAccount, 'Employee') and you know what employee to use.
So it's important to understand what you are doing and adapt your coding to meet the requirements of the process. The variations are endless.
You ask a lot of questions, but they are all pertinent. Typically such questions are treated in (custom or standard) Turbo Integrator courses.
But here's an answer to the questions.
Is it complusory to create every dimensions of the Source cube in the VIEW ?
==> Not needed. If you do not limit a certain dimension, then all elements will be taken by TM1 for that dimension. Very often in the view source we skip consolidated cells, and cells that are 0, and cells that are calculated with rules. Therefore, very often, only the leaf level elements remain when you do not set a filter on a dimension.
Why is this VIEW necessary in the first place?
==> to grab the cells of which the values need to be transferred to the target...
Should the dimensions of the View be created in same order as the order in which dimensions are present in the Target cube?
==> not needed
Why ZeroOut is necessary ? Won't the TI process overwrite the existing data when it runs successdully?
==> If you use CellPutN and the source changes (like a value going from 100 to 0) then the 100 that was in the target cube since the last run of the process, will not be cleared automatically. You have to do that yourself with a ViewZeroOut function (or similar functions like CubeClearData, CellPutProportionalSpread, a.s.o.).
In this tab, if we have to change the dimension of the source cube, then it is done here. Is this correct ?
==> Most likely, dimensions in the target cube. For example, you copy data for employees, and a new employee should be created in the respective dimension in the target cube such that in the Data tab of the process you are able to load data on that employee.
In this tab, whatever lines of code is written, it will be applied on each row of record in the Source cube. Is this right?
==> Yes, every cell that survives your settings of yes or no skipping consolidations, zeroes, rules cells
While writing the data in to the Target, in the CEllPUTN or like wise command,
Should we use Variables imported from Source like vScenario, vYear etc..
or
Should we use Parameters created like pScenrio, pYear etc.. ?
==> Depends. For example, if you copy all data for all employees onto a dummy employee in the target cube, it will probably be pEmployee (pEmployee could be set to 'No employee' or similar). If you copy data employee by employee, it will probably be vEmployee (vEmployee being the variable for the dimension elements of your source). Or vEmployee could be the result of a lookup (like an account could have an attribute with an employee name, then you could have: vEmployee = Attrs( 'Account', vAccount, 'Employee') and you know what employee to use.
So it's important to understand what you are doing and adapt your coding to meet the requirements of the process. The variations are endless.
Last edited by Wim Gielis on Sun Jul 08, 2018 12:18 pm, edited 1 time in total.
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- MVP
- Posts: 3119
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Parameter in TI process
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 10
- Joined: Wed Dec 13, 2017 4:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: 2016
Re: Parameter in TI process
Thanks so much Wim for the detailed reply! It helps a lot.
Being a totally newcomer to TM1, all these questions are coming up
Being a totally newcomer to TM1, all these questions are coming up
- orlando
- Community Contributor
- Posts: 167
- Joined: Fri Aug 04, 2017 8:27 am
- OLAP Product: TM1
- Version: PAL 2.0.8
- Excel Version: Office 365
Re: Parameter in TI process
Hi Pluto,
for a TM1 newcomer the several guides (with examples and exercises) are very helpful.
http://www-01.ibm.com/support/docview.w ... wg27049091
Best regards,
orlando
-
- Posts: 10
- Joined: Wed Dec 13, 2017 4:57 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: 2016
Re: Parameter in TI process
Thanks much for the link, Orlando!
Regards,
Pluto
Regards,
Pluto