0Calmonth empty in Infocube?

[darryl_goveas3]

Hi Gurus,

We have a curious situation in one of our cubes. We are bringing in external data, and in the transformation to the cube we use the transation data field (dats type) to load into the 0CALMONTH char using a time coversion routine.

However, for any dates beginning in 2009 the 0CALMONTH field is empty it seems, and any queries return null results if it is used.

Is there an update process we need to run somewhere, or any other causes for this?

Thanks!

Darryl

[Former Member · Accepted solution]

Hi,

Did you check if the data is available in the cube via listcube transaction or the via display data. Please check if the data exists in the cube for the selections used to execute the query.

Also If possible check the data in the PSA to make sure that the data is extracted properly. Still teh update might have failed if the data was extracted in a wrong fromat.

Please check

Regards,

Adarsh Mhatre

[darryl_goveas3 · Accepted solution]

hi,

I am looking at the cube directly via display data. I also store the original date value in the cube, and the format of those values has not changed. The only difference is that the time conversion is not working to populate either 0calday or 0calmonth anymore. fyi, I checked in our dev and qa systems, and the same code is working fine there...

thx,

Darryl

[former_member185181 · Accepted solution]

can you post the routine you are using?

[Former Member · Accepted solution]

Hi ,

Please check if the year is still maintained in the T00* tables.

-Vikram

[darryl_goveas3 · Accepted solution]

Hi.

I checked several of the T00 tables that pertained to time values (mainly T009 and associated ones) - all the tables are the same in our qa and prod systems. In both, there are no specific entries for each year, just some entries from when the system was first set up several years ago.

It is curious since I just ran a new load in QA a few days ago and it populates 0calday and 0calmonth correctly still, but in prod the last one that worked was for the load for 2008 data.

[darryl_goveas3 · Accepted solution]

Hi,

The routine is just a standard one. In the transformation from the DSO to the cube, I am using the dso date field (type DATS) as an input to both the 0calday and 0calmonth fields in the cube. the routine shows rule type 'Time Char' direct update for 0calday (type dats, len 😎 and rule type 'Time Char' Time Conversion for 0Calmonth (type numc, len 6, conv routine peri6)

[Former Member · Accepted solution]

Hi,

Is this problem occurring for only one info cube or many?

If its just, try doing RSRV Checks on the cube and 0CALMONTH.

Also reactivate the transformation. Sometimes the generated program of the transformation gets corrupted, hence the issue.

-Vikram

[former_member185181 · Accepted solution]

try assigning the calmonth manually through routine so that you can check debugging the code and find exactly where you are missing it.

[darryl_goveas3 · Accepted solution]

Hi all,

Problem solved - thanks for everyones time and suggestions. SAP's feedback via OSS was that they felt that the factview was corrupt.

They suggested to "recreate the factview with report SAP_FACTVIEWS_RECREATE. Attached Note 499820 has details on this report." Unfortunately, that didn't solve the issue.

In the end, I had some other updates planned for this cube anyways, so transported a revised cube and tranformation / DTP to Production. After reload, the issue was resolved. I suspect Vikram's analysis was probably correct and the transformation code was corrupted.

Thanks,

Darryl

[Former Member]

Hi,

Can u please let me know from where you are doing time conversion for 0calday and 0calmonth....

Thanks,

Kamal

[darryl_goveas3]

Hi,

I am doing the conversion in a transformation that is feeding the cube from a staging dso. the field from the dso is a date field from the external source system, but it is loaded into a DATS type field in BW. There is valid data in the dso.