TM1 Forum

Hello people, how are you?

I need to do a Turbo Integrator process to establish some records to "Declined" status according to a Data Element. If you see the attachment excel file to a better explanation of my lines...

I have a cube with 2 views:

1- In the first view, I can set the records to "Approved" or "Declined", then
2- In the second one, I have an TI process to receive all those "Declined" records...

...until here, everything is good...

...but, in the "Adjustment" view there is one column that identify the records groups (Control), so I need decline too, all those records that have the same "Control" number like those were declined, in this way:

The TI Process must take of "Declined" view the first "Control" number ("1"), by the "CellGetN()" statement and compare it with each record in the "Adjustment" view, line by line, to change in that same view to "Declined" those whom meet the same "Control" number.

Later, this TI Process, must take the following "Control" number of the "Declined" view to compare it in the "Adjustment" view and apply the declined status.

After that, in the "Declined" view, I must see all rejected records, the first ones manually declined and the automatically declined, distinguished with the letter "D" of "Declined". Please see the attachment file to better understanding.

I hope I have explained well.

Thank you for your guidance...

Jose.Mong
jmong@mstech-inc.com
Panama

I'm guessing that FC_BALANCE is a dimension containing elements STATUS, ACCT_NUM, CONTROL, DEBIT, CREDIT, ELEMENT_6, ELEMENT_7. If so, then you can create a TI process like this:

* data source set to a view of the cube that we see in your example
* parameter that takes a control group value as parameter e.g. 1 or 3 per your example
* restrict the view of the cube to at least the CONTROL element of the FC_BALANCE dimension - it is not clear from your examples what other dimensions you would restrict on
* for each row of the data check (CellGetS) the STATUS value. If it is not 'Declined' then write 'd' into the STATUS measure where the intersection is defined by the same elements as in your data source, i.e. same ROW_NUMBER, same ENTITY

A couple of other points:

* it would be helpful to supply the dimensionality of the cube - the attachment is great but it is missing this information
* there is some questionable design - you have a ROW_NUMBER dimension - cube design that includes transactions is sometimes/ often not a good idea
* maybe you have a fourth dimension that has ADJUSTMENT and DECLINED in it - this is also a bit weird as this is being handled by the STATUS measure... or did I get that wrong?
* generally, it looks like you should investigate the alternative of building this application in a relational database as it may be easier to build and a better user experience