Data in the Cube not getting aggregated

Question

Hi Friends
We have Cube 1 and Cube 2.
The data flow is represented below:
R/3 DataSource>Cube1>Cube2
In Cube1 data is Stored according to the Calender Day.
Cube2 has Calweek.
In Transformations of Cube 1 and Cube 2 Calday of Cube 1 is mapped to Calweek of Cube 2.
In the CUBE2 when i upload data from Cube1.Keyfigure Values are not getting summed.
EXAMPLE: Data in Cube 1
MatNo CustNo qty calday
10001  xyz     100  01.01.2010
10001  xyz      100  02.01.2010
10001  xyz      100   03.01.2010
10001  xyz     100  04.01.2010
10001  xyz      100  05.01.2010
10001  xyz      100   06.01.2010
10001  xyz      100   07.01.2010
Data in Cube 2:
MatNo CustNo qty calweek
10001  xyz     100  01.2010
10001  xyz      100  01.2010
10001  xyz      100   01.2010
10001  xyz     100   01.2010
10001  xyz      100   01.2010
10001  xyz      100   01.2010
10001  xyz      100   01.2010
But Expected Output Should be:
MatNo CustNo qty calweek
10001  xyz     700  01.2010
How to acheive this?
I checked in the transformations all keyfigures are maintained in aggregation summation
regards
Preetam

Answer 1

Just now i performed consisyency check for the cube:
I a getting following warnings:
Time characteristic 0CALWEEK value 200915 does not fit with time char 0CALMONTH val 0
Consistency of time dimension of InfoCube &1
Description
This test checks whether or not the time characteristics of the InfoCube used in the time dimension are consistent. The consistency of time characteristics is extremely important for non-cumulative Cubes and partitioned InfoCubes.
Values that do not fit together in the time dimension of an InfoCube result in incorrect results for non-cumulative cubes and InfoCubes that are partitioned according to time characteristics.
For InfoCubes that have been partitioned according to time characteristics, conditions for the partitioning characteristic are derived from restrictions for the time characteristic.
Errors
When an error arises the InfoCube is marked as a Cube with an non-consistent time dimension. This has the following consequences:
The derivation of conditions for partitioning criteria is deactivated on account of the non-fitting time characteristics. This usually has a negative effect on performance.
When the InfoCube contains non-cumulatives, the system generates a warning for each query indicating that the displayed data may be incorrect.
Repair Options
Caution
No action is required if the InfoCube does not contain non-cumulatives or is not partitioned.
If the Infocube is partitioned, an action is only required if the read performance has gotten worse.
You cannot automatically repair the entries of the time dimension table. However, you are able to delete entries that are no longer in use from the time dimension table.
The system displays whether the incorrect dimension entries are still being used in the fact table.
If these entries are no longer being used, you can carry out an automatic repair. In this case, all time dimension entries not being used in the fact table are removed.
After the repair, the system checks whether or not the dimension is correct. If the time dimension is correct again, the InfoCube is marked as an InfoCube with a correct time dimension once again.
If the entries are still being used, use transaction Listcube to check which data packages are affected.  You may be able to delete the data packages and then use the repair to remove the time dimension entries no longer being used. You can then reload the deleted data packages. Otherwise the InfoCube has to be built again.