We have 0FISCVARNT hardcoded with K4 in the update rules as of 3.0b and the queries based on this version with OFISCVARNT again restricted by K4 in the query. The queries were running correctly without any error message in 3.0b. However, after the upgrade to 2004S, the queries fail saying that 0FISCVARNT is not available in the cube. The query designer does not have this object in the time dimension. The cube is populated with K4 for all rows. Is it necessary to remove this object from the query? I think because it is hard coded with K4 in the update rules and populated in the cube with values, it is not necessary to restrict this characteristic again in the query as per 2004S. Has anyone come across this problem? It seems to be a big maintenance issue.