Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi,

You might try creating a TI using "CubeProcessFeeders" on the middle cube or even all three cubes in order (Source, Helper, Result).  If the feeders for the helper cube were reprocessed before the source cube, it is possible that the feeders were not passed on to the result cube.  However, using the inbuilt tools it will look for everything is fed correctly.

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi,

You might try creating a TI using "CubeProcessFeeders" on the middle cube or even all three cubes in order (Source, Helper, Result).  If the feeders for the helper cube were reprocessed before the source cube, it is possible that the feeders were not passed on to the result cube.  However, using the inbuilt tools it will look for everything is fed correctly.

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Scott,

Unfortunately, the TI didn't change anything in the values.

If you have more ideas, please let me know!

BR;

Hi,

You might try creating a TI using "CubeProcessFeeders" on the middle cube or even all three cubes in order (Source, Helper, Result).  If the feeders for the helper cube were reprocessed before the source cube, it is possible that the feeders were not passed on to the result cube.  However, using the inbuilt tools it will look for everything is fed correctly.

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hello !

Did you try a TI with 

CubeProcessFeeders(CubeName) for your three cubes ?

Other, when I see your rules, I don't succed to Math Rules (in helper) and feeders in (Source).

Your Measure "Flow_Source" is affected by rule only if :

 Country is the same as Costcenter

Currency is the same as Costcenter

Company is the same as Deprtement's CostCenter

And then you take the value of Db (..........)

The feeders must be the correlation of Your DB formula.

Your feed formula use 'A' as second dimension, are you sure that 

is the same thing ?

regards,

Philippe

------------------------------
Philippe CHAMPLEBOUX+NEXT+DECISION

Original Message:
Sent: Tue November 14, 2023 07:53 AM
From: Vedrana Tomic
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Hi Scott,

Unfortunately, the TI didn't change anything in the values.

If you have more ideas, please let me know!

BR;

Hi,

You might try creating a TI using "CubeProcessFeeders" on the middle cube or even all three cubes in order (Source, Helper, Result).  If the feeders for the helper cube were reprocessed before the source cube, it is possible that the feeders were not passed on to the result cube.  However, using the inbuilt tools it will look for everything is fed correctly.

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana, since you mentioned the problem is with the unfed values in your "Result Cube", we need to look at the feeders in the "Helper Cube".

I have conditional feeders which make checks based on certain string values.

You have a normal feeder in the "Source Cube". Conditional feeders use IF statements

What role do string values play here?

String-based conditional feeders Those feeders may not re-fire automatically and may require to run CubeProcessFeeders as Scott suggested for the cubes containing the feeders (Source, Cube and Helper Cube). You can add CubeProcessFeeders to the Epilog of the process updating the attributes.

You can also look at ForceReevaluationOfFeedersForFedCellsOnDataChange parameter, but it may have some performance impact.

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna
------------------------------

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Vedrana,

I believe the issue seems to be in the department to cost center mapping in the feeders from the source cube to target cube. I see a reference to !department, but does a department element name correspond to a cost center element name? Considering the manipulation that you do to retrieve the company in your helper cube (using Costcenter_Code attribute in your department dimension) it seems this is not a 1-on-1 element name mapping. Please be aware that with this approach you need to recalculate the feeders when the Currency, Country and Company attributes change. This is certainly not a bug.

Kind regards,

Luc

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Luc,

I appreciate your input.

The mapping is sound - I have tested this multiple times and again - everything works as expected between Source and Helper. 

It is only in the Result Cube that the aggregations don't work.

However, I managed to get them to work by writing Feeders for the Result Cube in my Source Cubes. 

This has also made my architecture a lot more complex and more difficult to maintain.

Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Vedrana,

I believe the issue seems to be in the department to cost center mapping in the feeders from the source cube to target cube. I see a reference to !department, but does a department element name correspond to a cost center element name? Considering the manipulation that you do to retrieve the company in your helper cube (using Costcenter_Code attribute in your department dimension) it seems this is not a 1-on-1 element name mapping. Please be aware that with this approach you need to recalculate the feeders when the Currency, Country and Company attributes change. This is certainly not a bug.

Kind regards,

Luc

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana,

It should be enough to feed from the helper cube as long as the cells in the helper cube as fed correctly. However, the best choice of where to put the feeders depends on the dimensionality of the cubes. I also don't understand why you need a helper cube, if you only need to make adjustments and some calculations. Why not include this functionality in the design of source cube?

Kind regards,

Luc

Dear Luc,

I appreciate your input.

The mapping is sound - I have tested this multiple times and again - everything works as expected between Source and Helper. 

It is only in the Result Cube that the aggregations don't work.

However, I managed to get them to work by writing Feeders for the Result Cube in my Source Cubes. 

This has also made my architecture a lot more complex and more difficult to maintain.

Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Vedrana,

I believe the issue seems to be in the department to cost center mapping in the feeders from the source cube to target cube. I see a reference to !department, but does a department element name correspond to a cost center element name? Considering the manipulation that you do to retrieve the company in your helper cube (using Costcenter_Code attribute in your department dimension) it seems this is not a 1-on-1 element name mapping. Please be aware that with this approach you need to recalculate the feeders when the Currency, Country and Company attributes change. This is certainly not a bug.

Kind regards,

Luc

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Luc,

Thank you for your quick reply.

"However, the best choice of where to put the feeders depends on the dimensionality of the cubes"

Would you be so kind as to elaborate on this part?

"If you only need to make adjustments and some calculations. Why not include this functionality in the design of source cube?"

The dimensions between the Source and the Result cube vary a lot - the structure of the two cubes is quite different and the Helper Cube serves as a matching structure for them.

To include the functionality in the Source Cube, I'd have to rebuild it from Scratch and change ALL the reports that are based on it (not feasible). Additionally, it would have a performance impact on my Source Cube, which I'm also trying to avoid as performance is the reason I've started this whole exercise.

I appreciate your help.

BR; 

Hi Vedrana,

It should be enough to feed from the helper cube as long as the cells in the helper cube as fed correctly. However, the best choice of where to put the feeders depends on the dimensionality of the cubes. I also don't understand why you need a helper cube, if you only need to make adjustments and some calculations. Why not include this functionality in the design of source cube?

Kind regards,

Luc

Dear Luc,

I appreciate your input.

The mapping is sound - I have tested this multiple times and again - everything works as expected between Source and Helper. 

It is only in the Result Cube that the aggregations don't work.

However, I managed to get them to work by writing Feeders for the Result Cube in my Source Cubes. 

This has also made my architecture a lot more complex and more difficult to maintain.

Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Vedrana,

I believe the issue seems to be in the department to cost center mapping in the feeders from the source cube to target cube. I see a reference to !department, but does a department element name correspond to a cost center element name? Considering the manipulation that you do to retrieve the company in your helper cube (using Costcenter_Code attribute in your department dimension) it seems this is not a 1-on-1 element name mapping. Please be aware that with this approach you need to recalculate the feeders when the Currency, Country and Company attributes change. This is certainly not a bug.

Kind regards,

Luc

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana,

I've just reviewed your feeders again from the helper cube to the result cube, but to me it seems strange that you include a reference to the cost center dimension twice. This would mean that you have a duplicate of the cost center dimension in your Result cube where if you select a cost center on one dimension, you need to select the same cost center in the other dimension to encounter a value. I guess one of the references to the cost center dimension needs to be "Total CostCenter".

Setting up a design where the dimensions between source and target cube differ a lot always comes with an "overfeeding" penalty impacting the performance if you try to set it up with rules and feeders. Have you also considered a Turbo Integrator based approach?

Kind regards,

Luc

Dear Luc,

Thank you for your quick reply.

"However, the best choice of where to put the feeders depends on the dimensionality of the cubes"

Would you be so kind as to elaborate on this part?

"If you only need to make adjustments and some calculations. Why not include this functionality in the design of source cube?"

The dimensions between the Source and the Result cube vary a lot - the structure of the two cubes is quite different and the Helper Cube serves as a matching structure for them.

To include the functionality in the Source Cube, I'd have to rebuild it from Scratch and change ALL the reports that are based on it (not feasible). Additionally, it would have a performance impact on my Source Cube, which I'm also trying to avoid as performance is the reason I've started this whole exercise.

I appreciate your help.

BR; 

Hi Vedrana,

It should be enough to feed from the helper cube as long as the cells in the helper cube as fed correctly. However, the best choice of where to put the feeders depends on the dimensionality of the cubes. I also don't understand why you need a helper cube, if you only need to make adjustments and some calculations. Why not include this functionality in the design of source cube?

Kind regards,

Luc

Dear Luc,

I appreciate your input.

The mapping is sound - I have tested this multiple times and again - everything works as expected between Source and Helper. 

It is only in the Result Cube that the aggregations don't work.

However, I managed to get them to work by writing Feeders for the Result Cube in my Source Cubes. 

This has also made my architecture a lot more complex and more difficult to maintain.

Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Vedrana,

I believe the issue seems to be in the department to cost center mapping in the feeders from the source cube to target cube. I see a reference to !department, but does a department element name correspond to a cost center element name? Considering the manipulation that you do to retrieve the company in your helper cube (using Costcenter_Code attribute in your department dimension) it seems this is not a 1-on-1 element name mapping. Please be aware that with this approach you need to recalculate the feeders when the Currency, Country and Company attributes change. This is certainly not a bug.

Kind regards,

Luc

Dear Vlad,

I have conditional feeders which make checks based on certain string values.

In my Helper Cube the Rules look something like this:

While the Feeder in the Source Cube looks like this:

What role do string values play here?

Thank you and best regards!

------------------------------
------------------------------
Vedrana Tomic
Business Partner
PM Factory Consulting
Vienna

Original Message:
Sent: Mon November 13, 2023 11:42 AM
From: Vlad Didenko
Subject: Possible reasons why cube cells are not being aggregated, even though they are fed?

Do you have any string-based conditional feeders in your Helper Cube?

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana,

Couple of things make me think its a dimension element vs dimension alias that causes the feeder to not work between those dimensions not shared. eg. costcentre and department.

eg.

Costcentre:CC1 (alias London)  >>>  Department:London   (The rule will work but the feeder will not)

You'd have to add an ATTRS('Costcentre', !Costcentre, 'Alias') to the feeder.

Cheers

Karl Blackler<o:p></o:p>

Head of Product Development<o:p></o:p>

Cortell Australia Pty Limited<o:p></o:p>

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Jose,

I appreciate your input and agree with you - as straightforward as possible is the best approach.

The structures of the three Cubes look like this:

Source_Cube
- Department
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Planningmeasure_Department

Helper_Cube
- Measure
- Area
- Currency
- Year
- Month
- Country
- Company
- Measuremapping
- Costcenter

Result_Cube
- Costcenter
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Country
- Company
- CM_Structure_Costcenter
- Planningmeasure

Let me know if you come up with some other advice/ideas that could result in this behaviour.

Thank you and have a nice day!

BR; 

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana

Thanks for posting the structure. I do have one question with regards to the measures in Helper and Results cubes. Helper has a "Flow_x_Share" measure - is this a leaf element or a consolidated element? Result PlanningMeasure also has a "Flow_x_Share" measure which is clearly a leaf element. 

If the Helper Measure is a consolidation and not a leaf, then the leaves would be triggered at leaf level, and would thus not find a valid measure in the Result cube. Does that help?

Guessing a bit at the dimension structures, but this is one reason why your feeders might not work. 

Cheers

Johann

Dear Jose,

I appreciate your input and agree with you - as straightforward as possible is the best approach.

The structures of the three Cubes look like this:

Source_Cube
- Department
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Planningmeasure_Department

Helper_Cube
- Measure
- Area
- Currency
- Year
- Month
- Country
- Company
- Measuremapping
- Costcenter

Result_Cube
- Costcenter
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Country
- Company
- CM_Structure_Costcenter
- Planningmeasure

Let me know if you come up with some other advice/ideas that could result in this behaviour.

Thank you and have a nice day!

BR; 

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Hi Vedrana

Thanks for posting the structure. I do have one question with regards to the measures in Helper and Results cubes. Helper has a "Flow_x_Share" measure - is this a leaf element or a consolidated element? Result PlanningMeasure also has a "Flow_x_Share" measure which is clearly a leaf element. 

If the Helper Measure is a consolidation and not a leaf, then the leaves would be triggered at leaf level, and would thus not find a valid measure in the Result cube. Does that help?

Guessing a bit at the dimension structures, but this is one reason why your feeders might not work. 

Cheers

Johann

Dear Jose,

I appreciate your input and agree with you - as straightforward as possible is the best approach.

The structures of the three Cubes look like this:

Source_Cube
- Department
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Planningmeasure_Department

Helper_Cube
- Measure
- Area
- Currency
- Year
- Month
- Country
- Company
- Measuremapping
- Costcenter

Result_Cube
- Costcenter
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Country
- Company
- CM_Structure_Costcenter
- Planningmeasure

Let me know if you come up with some other advice/ideas that could result in this behaviour.

Thank you and have a nice day!

BR; 

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Johannes,

I appreciate your input.

"Unfortunately", the Flow_x_Share measure is a leaf measure, so that can't be the culprit.

However, you made me think - I am matching the elements of Planningmeasure Dimension with the elements in the Measuremapping Dimension. In the Planningmeasure Dimensions the elements are Leaf elements, but in the Measuremapping Dimensions they are Consolidated elements.

Could this also have an effect? I did not expect this to be an issue.

Thank you so much for your feedback!

BR; 

Hi Vedrana

Thanks for posting the structure. I do have one question with regards to the measures in Helper and Results cubes. Helper has a "Flow_x_Share" measure - is this a leaf element or a consolidated element? Result PlanningMeasure also has a "Flow_x_Share" measure which is clearly a leaf element. 

If the Helper Measure is a consolidation and not a leaf, then the leaves would be triggered at leaf level, and would thus not find a valid measure in the Result cube. Does that help?

Guessing a bit at the dimension structures, but this is one reason why your feeders might not work. 

Cheers

Johann

Dear Jose,

I appreciate your input and agree with you - as straightforward as possible is the best approach.

The structures of the three Cubes look like this:

Source_Cube
- Department
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Planningmeasure_Department

Helper_Cube
- Measure
- Area
- Currency
- Year
- Month
- Country
- Company
- Measuremapping
- Costcenter

Result_Cube
- Costcenter
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Country
- Company
- CM_Structure_Costcenter
- Planningmeasure

Let me know if you come up with some other advice/ideas that could result in this behaviour.

Thank you and have a nice day!

BR; 

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Yes that will have an impact. Feeders are triggered at leaf level. Assume the following elements in your dimensions:
Measure Mapping:
C My Total

  Leaf 1

  Leaf 2

Then in Planning measure we have a leaf called "My Total".
If you try feed from My Total, the feeders are triggered for the leaves under "my Total" consolidation, and will thus try to feed Planning Measures "Leaf 1" and "leaf 2". 
If there aren't many measures (and the dimension is static), add specific feeders from "My Total" to "My Total" (code it into both sides of the feeder). If there are many measures, add an attribute to the MappingMeasures dimension that shows the "My Total" and feed to that Attribute. 

Hope that makes sense?

Johann

Dear Johannes,

I appreciate your input.

"Unfortunately", the Flow_x_Share measure is a leaf measure, so that can't be the culprit.

However, you made me think - I am matching the elements of Planningmeasure Dimension with the elements in the Measuremapping Dimension. In the Planningmeasure Dimensions the elements are Leaf elements, but in the Measuremapping Dimensions they are Consolidated elements.

Could this also have an effect? I did not expect this to be an issue.

Thank you so much for your feedback!

BR; 

Hi Vedrana

Thanks for posting the structure. I do have one question with regards to the measures in Helper and Results cubes. Helper has a "Flow_x_Share" measure - is this a leaf element or a consolidated element? Result PlanningMeasure also has a "Flow_x_Share" measure which is clearly a leaf element. 

If the Helper Measure is a consolidation and not a leaf, then the leaves would be triggered at leaf level, and would thus not find a valid measure in the Result cube. Does that help?

Guessing a bit at the dimension structures, but this is one reason why your feeders might not work. 

Cheers

Johann

Dear Jose,

I appreciate your input and agree with you - as straightforward as possible is the best approach.

The structures of the three Cubes look like this:

Source_Cube
- Department
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Planningmeasure_Department

Helper_Cube
- Measure
- Area
- Currency
- Year
- Month
- Country
- Company
- Measuremapping
- Costcenter

Result_Cube
- Costcenter
- Planningcycle
- Currency
- Datatype
- Year
- Month
- Country
- Company
- CM_Structure_Costcenter
- Planningmeasure

Let me know if you come up with some other advice/ideas that could result in this behaviour.

Thank you and have a nice day!

BR; 

Dear Jose,

After everything else failed, I ended up writing Feeders in my Source Cubes, which has indeed solved the aggregation issue. 

Thank you for your input on this!

However, it has also made my architecture a lot more complex and more difficult to maintain.
Do you know if this TM1 behaviour is by design? I would expect that the Feeders in the Helper Cube are sufficient as I'm only directly feeding from this cube and only indirectly from the Source Cube.

BR;

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,

Dear Planning Analytics community,

I have encountered a situation that I could only describe as a bug, but maybe some of you have also seen such behaviour and know more.

Concretely, this is my architecture:

Source Cube

Helper Cube

Result Cube

I have rules that feed values from the Source Cube to the Helper Cube, where I perform some adjustments and calculations on the data. Then I want to feed my Result Cube with the data, for which I also have rules.

The first step Source Cube → Helper Cube works like a charm and as expected.

But when trying to feed the data from my Helper Cube to my Result Cube, the aggregations are not working, leaving me with wrong (empty) values on the consolidated levels. Leaf element values are all correct.

When I disable SKIPCHECK, the aggregations work as expected, which is an indicator that this is a Feeder issue.

However, when I check the cells I can see that they are properly fed.

Have any of your encountered this behaviour or any suggestions on how I might go on about solving it?

Any tries to explicitely calculate the aggregations by rule have failed.

I'm happy about any info and if you need further information or have questions/remarks, don't hesitate to contact me!

Thank you and best regards,