Issue when few fields were added to a custom table

Question

Hi,
We have added some new fields to the existing database table(Customize). One of the fields is POD_date (data element- sydatum).
When we look for entries in table with condition POD_DATE EQ '00/00/0000' or space it gives fewer entries. In place it has to give 18k old entries with 00/00/0000 which it doesnt. Ideally it should have done '00/00/0000'  for all older records as there wasnt field at that time. When fetch without above condition it gives 18k records with field in POD (00/00/0000) but when same thing is given in selectioon criterion it gives fewer.
Regards
Mohinder
Edited by: Mohinder Singh Chauhan on Dec 14, 2009 1:26 PM

Answer 1

Dear all,
I encounter quite the same problem :
We added an include to the table EKKO containing several fields such as ZZTYPC.
The initialization flag was not set at creation time so the new fields were populated with the NULL value.
We would like now to initialize the value for all the records of the field ZZTYPC to avoid problems when we use this field as a selection criteria in Tx SE16.
As suggested in the previous post, I checked the initilization flag for this field at the structure level (Dictionary : Display structure), save & activate but the modification is not carried over the table EKKO : the "initial values" check box stays unchecked for the field ZZTYPC thus the adaptation of EKKO is useless.
We use DB2 as database.
You help would be appreciated.
Best Regards,
Olivier