Chapter 07 abap dictionary changes1

Editor's Notes

• #4: An object must be fully activated in the SAP system in order to be used by other objects (e.g., a domain must be activated prior to being used by a data element, tables must be activated prior to being used in an ABAP program, etc.). ABAP Dictionary objects are activated either: Individually (immediately after each object is saved with the activation icon) or Mass (several objects grouped together for later activation after each one has been saved) Two steps are required to perform a mass activation: 1. Enter the object types and names in a table named TACOB. Use the menu path: System  Services  Table Maintenance  Extended Table Maintenance or transaction SM30 to access this table. Enter TACOB for the table name and click the maintain pushbutton. Some of the object types are: DOMA (domains) DATA ELEMENTS (data elements) TABL (tables) 2. Execute the mass activation program RDDMASG0 via transaction SE38, or use the menu path: System  Services  Reporting (transaction SA38). Enter TACOB for the external table name and click the Execute pushbutton.
• #5: The mass activation program RDDMASG0 can either be run online or scheduled as a background job. Greater efficiency is gained when objects are activated online due to the links that can occur between subcomponents of objects. (i.e., links between data elements and various tables). For example, if several tables attempt to use the same data elements, failures can occur when the tables are activated because the data elements are waiting on a background job to run in order to be activated.
• #6: ABAP programs and Screen Painter screens always use the current version of a table activated in the Dictionary. Entries are made in a log file to keep track of each occurrence when a table has been activated. When an object is changed and re-activated, all other objects currently linked to the changed object are automatically updated, (i.e., when a domain is changed and activated, all data elements, tables, report programs, module pool programs reflect the change, they do not need to be reactivated as well). As you can see, changing and reactivating objects can greatly affect a large number of associated objects. If appropriate, a data object is automatically checked for consistency (among data types) when the object has been changed.
• #7: The Database (DB) Utility is a tool used in SAP to serve as an interface between the database management software (i.e., ORACLE™, INFORMIX™, DB2™, INGRES™, etc) and the ABAP Dictionary. It is used to: Convert data (i.e., change field lengths and data types, etc.) Activate objects in the ABAP Dictionary Create tables and indices Perform all standard table operations in the database that were entered in the ABAP Dictionary The DB Utility automatically writes the SQL commands necessary to create, change and delete tables and indexes in the physical database, and records the tables in the ABAP Dictionary. As the DB Utility is operating, a log file gets created which contains information on whether or not the conversion was successful and the point of failure during the conversion if it was not successful. The DB Utility can be run either online or in the background. You can also manually run the DB Utility from any ABAP Dictionary screen under the UTILITIES menu or transaction SE14.
• #8: Changing the primary key of a value table that is being used by a domain, requires a lengthy process because of the embedded links between the domain and the value table. It is not a simple process to change and reactivate a value table. Changing the table is step 3 and reactivating the table is step 5 in an 8 step process that is necessary in order in change the key fields of a value table being used by a domain. The 8 steps are: Delete “old” value table from domain Activate domain without value table Change primary key Maintain all dependent tables (remove check table) Activate dependent tables Reactivate value table Type value table in affected domain: Activate domain Maintain dependent tables if required: (Define foreign keys)
• #9: An object in the ABAP Dictionary can exist in various versions and a listing of them can be viewed within the object’s dictionary maintenance screen via the menu path Utilities  Version management. There are two VERSIONS of an object that can exist in the ABAP Dictionary: Active: valid in the dictionary and in any development objects (i.e., programs) in which it is used. Revised: a modified version. A lock is taken. You can switch between the two versions. Once an object is activated, you can change it and save a modified (revised) version. This can be viewed from Utilities  Version management. If you activate this new revised version, it overwrites the original activated object. In the Version Manager, objects which are saved appear with the notation “mod.” Objects which are activated appear with the notation “act.” (Continued on next page)
• #10: Versions (continued): Temporary versions (under the heading “Version(s) in the version database”): During the development process while a change request is open, several temporary versions of an active object can be stored. Even after the object has been activated, it can be reset to the previous status. Store versions in the maintenance screen of objects via the leftmost menu (i.e., Table, Data Element, Program)®Store version. Temporary versions act as backup versions prior to the change request being released. When a change request is released, all temporary versions are deleted. Historical versions: If an object has been changed and activated, when the corresponding change request for the object is released for transport, the active version is stored as an historical version in a versions database. These versions are created every time a change request is released after an object has been changed. From the object maintenance screen, use the menu path Utilities®Version management to see an overview of all versions that exist for an object. Versions of non-dictionary objects (i.e., programs) can be stored. However, only active, temporary and historical versions are possible (modified versions).
• #11: Display: List all defined attributes of object. Compare: Differences between this version and previous versions are highlighted. Retrieve: Retrieve stored version of object. Version is located in the ABAP Dictionary and takes the form of a revised version. Remote compare: Comparison with versions from other systems.
• #14: When you activate an object any locks on the object are automatically released. Other users can see the revised version in the Dictionary but can only access the active version.
• #15: Versions of modified (repaired) SAP standard objects can be compared with new SAP standard objects by using the transaction SPDD. SPDD compares an inactive SAP standard version with the active modified (repaired) version and displays the results of the comparison in tabular form. All modifications to SAP objects made by clients are incorporated for review and considered by SAP during a system upgrade for a new release of SAP.