Consolidated Amt not computing

[beek]

Hi there,

This is the first time I'm posting question here, hope I will be able to get some help
Here is my problem. Sometimes, the user will report that the Consolidated value is not computing, for example, in the month dimension, Q1 consists of child Jan, Feb and Mar. In Jan, value = 100, Feb value = 200, Mar value = 300. Q1 should be reflecting 600, by consolidating these figures, but the Q1 is only reflecting 300. When I click on the Check Calculated Calculation, I can see the row Mar value is showing 0. When I double-click on Mar(Mar is a computed field), then I can see 300.
After we did a server reset (due to other reason), this issue is auto fixed. The consolidated figure is now computed correctly.
This issue had been haunting us. We are using IBM Cognos Express Xcelerator Version 9.0, Windows server 2003, 8Gb RAM.
What could have cause the consolidated amt not consolidating (sometimes)?

Please share with me your views on this.

Thank you

Cheers.

[qml]

Typical answer would be - you're using SKIPCHECK in your rules, but are not feeding all calculated N-level values correctly. Can you post your rules and feeders here?

[beek]

Hi Kamil,

Thank you for your reply. Sorry for replying this so late (as I thought there will be email alert to notify me whenever there's someone replied to my post, so I just wait for the email.. )
So far, from then till now, there are only 2 occurrence of the field showing not fed, but it was fed correctly after the TM1 server is restarted. I suspect it could due to our server RAM is too low to support the model(the PF size is >25Gb, yet server RAM is only at 8Gb).
Anyway, since we already have plan to upgrade our server soon, I will rest my case here. I will monitor again if this happen after the server upgrade.

Cheers.

[Alan Kirk]

Thank you for your reply. Sorry for replying this so late (as I thought there will be email alert to notify me whenever there's someone replied to my post, so I just wait for the email.. )

Since you've decided to leave the matter in abeyance I won't address your main question, but I'll address this one.

On this type of forum software you can either subscribe to an entire forum (you get an e-mail whenever any post is made in the forum), or subscribe to individual topics (you're notified only when a post is made to a subscribed topic). In both cases the option is down near the foot of the page. The Subscribe Topic (or Unsubscribe Topic) link is shown when you have a topic open, and the Subscribe Forum (or Unsubscribe Forum) link is shown when you're looking at the list of topics page of any forum.

If you decide not to subscribe to the forum but still want to be notified when there's a reply to your post, simply choose Subscribe Topic.

If you want to save yourself the trouble of doing that every time you post, go to the User Control Panel link up near the top left of the page, Board Preferences tab, Edit Posting Defaults group, and set Notify me upon replies by default to Yes.

[asutcliffe]

So far, from then till now, there are only 2 occurrence of the field showing not fed, but it was fed correctly after the TM1 server is restarted. I suspect it could due to our server RAM is too low to support the model(the PF size is >25Gb, yet server RAM is only at 8Gb).
Anyway, since we already have plan to upgrade our server soon, I will rest my case here. I will monitor again if this happen after the server upgrade.

Cheers.

Are you using conditional feeders? If you post the feeder statements it would help people understand.

Conditional feeders aren't re-processed when data they're predicated upon changes. So if the condition wasn't true when the feeders were last processed (possibly last startup time), the cells won't be fed even if that condition is now true.

All feeders are processed when the server starts though which would explain why the cells are fed after a restart. Of course, you can selectively re-process a cube's feeders by creating a simple TI process or by re-saving the rules for that cube rather than restarting the whole server.

[beek]

Thank you for replies.
Below is my rules. Field AAA Total Inventory is the field that I'm had problem with but ok after server restarts. Is this consider Conditional formating? As it is derived from other fields.

[{ 'ISM Closing Stock', 'DDD Inventory' , 'CCC Inventory' , 'AAA Total Inventory' , 'SCM_InvProgress_Inventory'}
,'Actual'] =N:STET ; C: IF (LONG(ATTRS('Week','Week',!Week))=4 % LONG(!Week)=8
, DB('Forecast_SCM',!Year,!Scenario
, ELCOMP ( 'Week' ,!Week , ELCOMPN('Week', !Week ) )
,!Country,!Product_SCM,!Forecast_SCM_Measure)
, STET
) ;
['AAA Total Inventory'] = N: IF (DB('SettingByWeek_SCM',!Year,!Scenario,!Week,'fActual') = 1
% DIMIX('Week',!Week) <= DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'N Week') )
% DIMIX('Week',!Week) > DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'Scenario Week End') ) , STET
, DB('Forecast_SCM',!Year,!Scenario , ATTRS('Week', !Week ,'Previous'),!Country,!Product_SCM, !Forecast_SCM_Measure)
+ ['Total Receiving'] -['AAA Sales']-['ITR']-['B Stk'] ) ;
C: IF (LONG(ATTRS('Week','Week',!Week))=4 % LONG(!Week)=8
, DB('Forecast_SCM',!Year,!Scenario
, ELCOMP ( 'Week' ,!Week , ELCOMPN('Week', !Week ) )
,!Country,!Product_SCM,!Forecast_SCM_Measure)
, STET
) ;


Feeders;

['AAA Total Inventory']=>DB('Forecast_SCM',!Year,!Scenario
, IF ( DIMIX('Week',!Week) < DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'N Week') )
% DIMIX('Week',!Week) > DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'Scenario Week End') ) , ''
, ATTRS('Week', !Week ,'Next') )
,!Country,!Product_SCM, !Forecast_SCM_Measure) ;


['GIT'] => ['AAA Total Inventory'] ;
['AAA Sales'] => ['AAA Total Inventory'] ;
['ITR'] => ['AAA Total Inventory'] ;
['B Stk'] => ['AAA Total Inventory'] ;
['AAA Total Inventory'] =>['BBB Inventory'] , ['AAA DOS'] ;

[tomok]

['AAA Total Inventory']=>DB('Forecast_SCM',!Year,!Scenario
, IF ( DIMIX('Week',!Week) < DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'N Week') )
% DIMIX('Week',!Week) > DIMIX ('Week' , DB('SettingByScenario_SCM',!Year,!Scenario,'Scenario Week End') ) , ''
, ATTRS('Week', !Week ,'Next') )
,!Country,!Product_SCM, !Forecast_SCM_Measure) ;

This is a conditional feeder. You are feeding only when the week is inside some defined range. The fed cells are NOT going to change automatically whenever you change the value in 'N Week' or 'Scenario Week End'. You have to either 1) re-save the rule file or 2) recycle the TM1 service to re-process the conditional check.

[beek]

Hi Tomok,

Can you advise me how do I recycle the TM1 service to re-process the conditional check ?

[Alan Kirk]

Hi Tomok,

Can you advise me how do I recycle the TM1 service to re-process the conditional check ?

It's another way of saying "shut down the TM1 server and restart it".

[beek]

ic.. Thanks

[rmackenzie]

either 1) re-save the rule file or 2) recycle the TM1 service to re-process the conditional check.

Or, there is option 3.