SAP DDIC

 Transparent Table :   It is used to store application data such as Master and Transactional data. We always create transparent tables only. There is one to one relationship for the table in DDIC another table with the same structure and the same name and the same fields will be created in the original data base. Pooled Tables:  It should be exclusively for the storing internal control information ( Screen Sequences, program parameters, temporary data, continuous texts such as documentation ). The data from the several different pooled tables can be stored in one table pool. This is many to one relationship for many pooled tables in DDIC only on data base table will be created in the database. Cluster Tables: It should be used exclusively for storing internal control information ( Screen Sequences, program parameters, temporary data, continuous texts such as documentation ). The data from the several different cluster tables can be stored in one table clusters. This is ma...

Foreign Key : Is a field in one table  ( Foreign Key Table ) that is connected to another table ( Check table ) field via foreign key relation ship and the purpose is to validate the data being entered in foreign key table with a valid set of values from the check table. Technical requirements(rules) to define a foreign key: Foreign key definition is only possible for fields with data elements. Foreign key field should be refer a data element always. The domain names of the foreign key field and check table field should be same and it is to make sure that at least the data type and length of the field to check table is same. Triggering Foreign key : This will be triggered through the GUI only the data will be validated for the input provided through screens only. It will not validated the foreign key relation when you insert the data into foreign key table through open SQL that is the reason SAP always suggest to update the data base tables only through t...

Handling currency (Amount) and Quantity fields in Table or Structure Creation: In any table, a Quantity   Field requires another field Unit of measurement as a reference field either from the same table or from another table and similarly a Currency Key Field   should be provided as a reference field for the Currency Field(Amount) because Quantity field make sense along with the unit of measurement field and similarly currency field along with the currency key. The meaning of the field in the table can be identified by the system, based on it's data type.    We will create a table with Currency and Quantity fields along with other fields. Since we knew how to create a table, here we are not repeating the process of creating table, data elements, domains etc.. Field details of the custom table.   Create the table ZPURCHASE_1 with all the above fields and make sure that PONO and LIFNR are the Key Fields. Step 1 :  Execute SE11 Transaction t...

The ABAP Dictionary centrally describes and manages all the data definitions used in the system. The ABAP Dictionary is completely integrated in the ABAP Workbench. All the other components of the Workbench can actively access the definitions stored ill the ABAP dictionary ABAP dictionary supports the definitions of user-defined types (data elements, structures and table types). You can also define the structure of database objects (tables, indexes and views) in the ABAP Dictionary. These objects can be automatically created in the database with this definition. The most important object types in the ABAP Dictionary are tables, views, types (data elements, structures, and table types), domains, search helps and lock objects. Purpose  Data definitions (metadata) are created and managed in the ABAP Dictionary. The ABAP Dictionary permits a central description of all the data used in the system without redundancies. New or modified information is automatically prov...