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...