TM1 Forum

Apologize in advance but search is not working for me.

Running a TI process and not all values are being updating as expected. After reconciling, ran TI process for a small subset where this was the case adding ASCIOUTPUT line to verify data being properly obtained.

Sample ascioutput:
"2019","2019-06","03/16/2019","R","43899728 1X 002-V Multi","1X","002","0","0","0","0","1","0","0","0"
"2019","2019-06","03/16/2019","R","43899729 2X 002-V Multi","2X","002","0","0","0","0","4","0","0","0"
"2019","2019-07","03/23/2019","R","43899722 L 002-V Multi","L","002","0","0","0","0","1","0","0","0"
"2019","2019-05","03/09/2019","R","43899723 XL 002-V Multi","XL","002","1","0","0","0","0","1","6.8575","17.99"
"2019","2019-23","07/13/2019","R","43899727 NS 749-V Gold","NS","749","1","0","0","0","1","1","1.0259","5.99"
"2019","2019-06","03/16/2019","R","43899721 M 002-V Multi","M","002","0","4","0","71.96","0","0","0","0"
"2019","2019-04","03/02/2019","R","43899723 XL 002-V Multi","XL","002","1","0","0","0","2","1","6.8575","17.99"
"2019","2019-05","03/09/2019","R","43899722 L 002-V Multi","L","002","1","0","0","0","0","1","6.8575","14.39"

Cube view shows no values.

Did you navigate to the exact cells that should have received the values ?
Do you check a consolidated value whether children have a weight of 0 ?
What about the settings for the decimal separator and similar ?

Thanks for the response. We have over a hundred thousand sku elements and all children that I checked have a weight of 1. Only a small percentage are not updating. Consolidated values follow same pattern.

Did you navigate to the exact cells that should have received the values ? Yes and all zero.
What about the settings for the decimal separator and similar ? Not totally sure what you are referring to but all elements checked are same.

What is the data source ?
Is it possible that 1 specific cell is being written to from multiple 'records' in the data source ?
About the decimal separator: you are sure that values are 0 instead of 0.00001 for example - due to formatting that hides the small values ?

ODBC to Oracle EBS.
I would say no as we consolidate at the SKU level which is our lowest element.
We should have no .00001 type values.

Currently creating a new TI process test using a flat file to see if I get same issue.

Limit the ODBC query to 1 record (that does not work).
Navigate to the exact cell. If it works, there will be something else that puts the cell again to 0. Like another record to the same cell.
If it does not work, you can investigate further.

So you used ASCIIOutput to get a text file containing the variable values as defined by your code. Did you zero in on a few of the exact records that represent cells in the cube that you say are not updating? Did you check each of the columns from those records in the ASCIOutput to make sure they represented valid elements in the respective dimensions? What I would do is take one of those rows that did not update and paste it into Excel. Then write a DBS formula that mimics what you are trying to do with your CellPutN in the TI process. That should give you a clue. Possibly there is a rule on that intersection in TM1 that is keeping it from updating.

Will try now sir. Appreciate suggestions.

A rule was the culprit. Owner of rule stated should not be impact but not the case. Thanks for leading me in that direction!

rfielden wrote: ↑Fri Sep 06, 2019 6:01 pm A rule was the culprit. Owner of rule stated should not be impact but not the case. Thanks for leading me in that direction!

If indeed it was a rule stopping the update you should have gotten an error log message which would have told you that you were attempting to write to a rule valued cell. However, had you encapsulated the CellPutN inside an ISUPDATEABLE function then you wouldn't have. This is why I'm not a big fan of ISUPDATEABLE. I only use it when I absolutely have to.