07-26-2016 10:01 PM
hello Gurus, please help be to understand below: Transaction SE11 can be used to verify the consistency of tables............... the system checks whether the tables or view definitions in the ABAP Dictionary (DDIC) agree with the runtime object or database object. The data in the database is accessed via the runtime object of the active NAMETAB. Changes to the ABAP Dictionary are not written (and therefore are not effective) until they are activated in the NAMETAB.................. COuld any one explain what is ACTIVE NAMETAB
07-26-2016 10:07 PM
07-26-2016 10:07 PM
07-26-2016 10:12 PM
any layman explanation that you could give would be so much helpful. thanks in advance
07-26-2016 10:23 PM
Excerpt from sap Library (first paragraph):
The name table (nametab) contains the table and field definitions that are activated in the SAP System. An entry is made in the Repository buffer when a mass activator or a user (using the ABAP Dictionary, Transaction SE11) requests to activate a table. The corresponding name table is then generated from the information that is managed in the Repository.
Isn't it clear?
I don't understand what is the "active" nametab, but it's clear that the nametab is updated when you activate a table. I think "active" is meaningless with nametab, probably it means "current nametab" in the context of your sentence.
07-27-2016 8:49 PM
As objects in the data dictionary can be active or inactive, there is an active and an inactive nametab, as well as special steps "move nametab" to move the inactive to the active nametab.
At some places, the nametab is called "runtime object" in the ABAP help and in the data dictionary. This is because it is read by the kernel in all places when Information about data dictionary objects is requested.
On a more technical level, the nametab is a set of database tables (not defined in the data dictionary :-)) and a kernel API to read them, as well a special buffering ("Nametab buffer") and an ABAP API to read the kernel API. The database tables contain all necessary Information about DDIC objects (like columns of tables, datatypes and so on).
But all of this should not bother the ABAP developer much.
Best regards,
Kilian.