SAP DATA DICTIONARY
 
 
 
 
 
 
 
 
 
 

  SAP REPORTS
 
 
 
 
 
 

SAP DDIC Technical Settings & Others

The technical settings of a table is use to define how the table will be handled when it is created in the database. That is whether the table will be buffered or not, what type of buffering can be done, or if changes to table data records will be logged or not.

There are different parameters that you can set:

1. Data class - The data class defines the physical area of the database (tablespace) in which the table should be created.

2. Size category - The size category defines the size of the extents created for the table. When the table is created in the database, the required information about the memory area to be selected and the extent size is determined from the technical settings.

3. Buffering permission - The buffering permission defines whether the table may be buffered or not. There are three different types of buffering permission. They are - 'Buffering not permitted', 'Buffering permitted but not activated', and 'Buffering activated'. The buffering type is used to define how we want to buffer the table and which table records should be loaded into the application server buffer when a record from the table is retrieved.

4. Buffering type - If the table may be buffered, you must define a buffering type (full, single-record, generic). The buffering type defines how many table records are loaded into the buffer when a table entry is accessed.

5. Logging - This parameter defines whether changes to the table entries should be logged. If logging is switched on, each change to a table record is recorded in a log table.


Q. What is delivery class?
A. The delivery class controls the transport of table data for installation, upgrade, client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance.

Q. What is database utility?
A. The database utility is the interface between the SAP Data Dictionary and the relational database (Like SQL, Oracle etc) underlying the SAP System. You can go to database utility using transaction code - SE14 or using SE11. The database utility allows you to edit (create, delete and adjust to changes to their definition in the ABAP Dictionary) all the database objects that has been derived from objects of the ABAP Dictionary.


Foreign Keys

Q. What are the different kinds of foreign key in SAP?
A. There are four types of foreign keys in SAP. They are:
1. Compound foreign key
2. Generic foreign key
3. Constant foreign key
4. Adapted foreign key

Q. What are the technical requirements for creating a foreign key?
A. There are following two technical requirements for creating a foreign key-
1. The check must occur against a field within the primary key of the check table, and
2. The domain names for the foreign key field and the check field must be the same, i.e. the data element for the foreign key should be similar.

Q. What types of foreign keys field describe?
A. It describes what the foreign key fields mean in the foreign key table. Wether it contains key fields or/and candidate fields.

Q. What are the three types of foreign key fields can be defined?
A. The following three types of foreign key fields can be defined:
1. No key fields/candidates
2. Key fields/candidates
3. Key fields of a text table

Q. What is text table?
A. Table T1 is a text table of table T2 if the key of T1 comprises the key of T2 and an additional language key field . The key of check table has an additional language key field, in respect what foreign key fields has.

Q. What is an aggregate object in DDIC?
A. An aggregate object is composed of more than one table. For example 'View' is an aggregate object. To include the table in an aggregate object you must specify the cardinality while creating foreign key, else you won't be able to include.

 
 

  

  

  

  

  

  



                                                      Copyright © 2011 SAPApplication.com. All rights reserved.
Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /home/psarv/public_html/dbanalyticsconnect.php:2 Stack trace: #0 /home/psarv/public_html/st-page-counter.php(1): include() #1 /home/psarv/public_html/footer.php(32): include('/home/psarv/pub...') #2 /home/psarv/public_html/sap-ddic-others.php(153): include('/home/psarv/pub...') #3 {main} thrown in /home/psarv/public_html/dbanalyticsconnect.php on line 2