10-25-2013 4:01 PM
Hello All,
Just trying to understand if SE14 can cause clearing out only few fields when it was run depending on changes made in table ??
I have added secondary index in a table & new field in between two existing fields. (no chagnes in primary keys). After creation of secondary index, it's recommanded to run SE14 - "Activate & Adjust database - using Save Data opiton". So I ran that.
But after running this we found that data from field newly added onwards was cleared out. Accroding to my knowledge it should not happend when SAVE data option is used in SE14.
Anybody else faced similar issue ? or knows what can possibly cause this ?
neo
10-26-2013 9:37 AM
SE14 - "Activate & Adjust database - using Save Data opiton".
Its required when you change the type of your existing field. I think in your case(adding new fields) its not at all required. May be you have changed something else also. Even i tried same thing no. of time and every time no data loss.
10-26-2013 7:29 AM
10-26-2013 9:37 AM
SE14 - "Activate & Adjust database - using Save Data opiton".
Its required when you change the type of your existing field. I think in your case(adding new fields) its not at all required. May be you have changed something else also. Even i tried same thing no. of time and every time no data loss.
10-26-2013 9:55 AM
are you saving data through some transaction? If it is custom transaction, may be you should check your code, if you have appended those fields.
Regards,
KS
10-27-2013 11:03 AM
10-27-2013 4:10 PM
No. SE14, adjust table saving data, will not result in loss of records. If you're sure that's what has happened you should report it to SAP via the support channels as a serious software issue.
10-28-2013 3:10 PM
thanks you all for your replies.
we are in process of removing options which could have cleared data, so we can narrow down the list & identify actual process which caused this.
I think I'm going to put se14 out of that list.