Bex Report Displaying #

[former_member212746]

Hi Gurus,

We have recently added few new fields to the DSO and then to the Cube.

We are loading daily delta to the DSO and then to Cube and data gets compressed in the cube.

Now in order to populate the values of these new fields we did a full load to DSO for one period and then we are pushing the data to Cube thru delta.

But when we run the bex report we get the value for new fields but another line also comes with #.

My doubt is doesn't the delta from dso takes care of the replacing the old record with new one.

As in cube all chars are key so this issue is coming? One with old record and one with new one.

If we do compression this issue will get resolved?

Thanks and Regards,

Monalisa Mohanty

[cornelia_lezoch · Accepted solution]

Hi Monalisa,

Compression in cubes compresses only several records with exactly the same char values into one record (which came out of several loading requests).

In your case you have to make sure, that the DSO ist creating the reverse of the original record and the new record.

The reverse of the old record plus the original old record will then be compressed in the cube into one record with value 0 - so you need to do compression with 0-deletion in the cube to get rid of those records.

regards

Cornelia

[Former Member]

Hi,

if your newly added fields are part of DSO -Key fields , then DSO data wont get overwritten, this will treated as a new record -->0recordmode will be N , eventually your DSO will have two records in active table. And when you load the same data to cube, you will see two records, one with existing old record and another with newly loaded (full) record with new field.

Please check the DSO first.

[Former Member]

Hi Monalisa,

Did you check in the Cube level how the records are getting displayed?.

Before loading delta in to your cube you checked for the dso Data as well .. and it is correct right ?

Also can you send the screenshot of the report with the # value together with couple of keyfigures.

You can fix this straight by selectively deleting the data from the cube based on period and then

performing full load with selections  from Source DSO.

Regards

Vivek