‎2010 Feb 04 1:59 PM
Hello experts,
could you please give me some examples of usage the t-code SE14?
What is the difference between Runtime Object and Database Object in this transaction?
Thanks,
Radek
‎2010 Feb 04 4:37 PM
Hi,
SE14 is use to Convert Data Dictionary tables on Database Level, this transaction is used to activate and adjust the database table and delete database table.
When you do some changes in database table, like added additional fields or removed fields for a table in se11, then you need to adjust using SE14.
Analysis option is available for database views using: Extras->Database object->Check or Display and Extras->Runtime object-> Check or Display the definitions of the view in the database in runtime object and SE11 can be checked with one another or checked.
There is a user-friendly option for tables to compare definitions in the database, in the runtime object and in the Dictionary maintenance with one another. These these analysis functions using Extras -> Database object -> Check or Display and Extras -> Runtime object -> Check or Display. In this way, the differences that have been found (Check) or the definitions themselves (Display) can be displayed.
Regards,
Moqeeth.
‎2010 Feb 04 2:11 PM
T code SE14 is used to delete the table entries and used to adjust the databased table when we try to add fields to the existing table
‎2010 Feb 04 2:35 PM
Hi,
Please refer the below link. Hope it helps.
http://help.sap.com/saphelp_nw70/helpdata/en/cf/21f0e3446011d189700000e8322d00/frameset.htm
‎2010 Feb 04 3:41 PM
After you change the table structure in SE11, changes will not updated at database level, to do that you need to use SE14 so that both DD and DB will be in synch.
‎2010 Feb 04 4:37 PM
Hi,
SE14 is use to Convert Data Dictionary tables on Database Level, this transaction is used to activate and adjust the database table and delete database table.
When you do some changes in database table, like added additional fields or removed fields for a table in se11, then you need to adjust using SE14.
Analysis option is available for database views using: Extras->Database object->Check or Display and Extras->Runtime object-> Check or Display the definitions of the view in the database in runtime object and SE11 can be checked with one another or checked.
There is a user-friendly option for tables to compare definitions in the database, in the runtime object and in the Dictionary maintenance with one another. These these analysis functions using Extras -> Database object -> Check or Display and Extras -> Runtime object -> Check or Display. In this way, the differences that have been found (Check) or the definitions themselves (Display) can be displayed.
Regards,
Moqeeth.
‎2010 Feb 05 8:10 AM
Hello,
when do I have to do this adjustings with se14? I have never done it and my programs work fine although I changer table structure many times and activate only in SE11.
And I see nothing if I choose Database Object-Check(only an empty window).
Thanks,
Radek
Edited by: Radomir Vanicek on Feb 5, 2010 9:13 AM
‎2010 Feb 05 2:30 PM
Hi,
Usually when you change something and active the table then if there is some problem a pop-up will show all the all the errors and messages and at the bottom it will ask you to Run SE14 and adjust the table.
But care must be taken will doing this adjustment since there are two radio buttons in SE14
1. Save Data
2. Delete Data
If you just want to adjust the table then radio button 'Save Data' must be used.
Secondly if you want to delete data from the table use must use the appropriate options in SE14.
Hope it helps you,
Regards,
Abhijit G. Borkar
‎2011 Sep 22 2:30 PM
hi ,
se14 for delete the records and update the records then what is the difference between table maintenance generator and se14 .
‎2011 Sep 22 2:51 PM
deletion and update of records is not in the sense you understand .se14 have the ability to delete all the records in a table ( that is drop the table) and adjust the records which is applicable when you add a new field or change a field's type .
So se14 is a transaction which is used by basis consultants whereas table maintenance (sm30) is a transaction which is used by end-users and work-analysts etc.