Sap Abap Ddic Se11
Sap Abap Ddic Se11
Abap
DDIC (Data
Dictionary-
SE11)
Sonu Jangir Abap Developer
[Date]
Table of Contents
Data Dictionary
Database Tables
Domain
Data Types
Currency and Quantity Fields
Table Maintenance Generator
Primary and Foreign Key Relationship
Technical Properties of a Table
Structures
Predefined Types
Include and Append Structure
Search Help
Views
Lock Objects
[Date]
They are the small data storage components in the data base.
Tables are the collection of fields which contain the physical
data.
The tables are made up of rows by columns.
[Date]
[Date]
Pooled tables:
The cluster tables also have many to one relationship with the
database tables, that means one table in the data dictionary is
stored with another set of tables called cluster pool.
Key field names are same in DDIC and cluster Pool
[Date]
2. Bottom up approach:
Note: In the real time the top down approach is advisable since
the bottom up approach take more time and difficult to remember
to create a data element and domains.
Domain
Introduction:
[Date]
Data Elements:
Mandatory fields:
The tables which have the field name will have MANDT (client
[Date]
Key fields:
Key fields are used to maintain the unique data by avoiding the
duplicate data.
In SAP the key field check boxes are checked to make the fields
as primary key fields.
Note: If there are more than one field the data will be checked
row level.
It is checked to take the default field values of the key fields for
the first time.
Example: integer :0
Character : space…………..etc.
Note:
Press F4 function key to see all the system provided data
types in the search help.
The decimal places should be filled for the decimal data types
such are currency, quantity………..etc.
The field output length is used to restrict the data output
length.
The check box sign is checked to return sign of the number.
The check box lower case is checked to make the character
fields as a case sensitive to accept both upper and lower case
letters. Since the system takes the character data as
uppercase letters by default.
Example: Data type : (NUMC)
No of characters : (10)
Decimal places : ( )
…………………………………………
Note:
Check the check boxes key and initial value to make the fields
of the table as key field.
Follow the similar steps to create any number of required
data elements and domains.
(Refer ‘creation of data elements’ and ‘creation of domains’ )
Note:
The transaction codes SE16or SE16N can also be used.
The button number of entries is used to know the total
number of recordings in the table.
Note:
Check is to add input fields and uncheck is to hide input fields.
An icon find (ctrl + f) can be used to find the required fields.
(Find icon enter a field name or field label in the find string
press enter)
An icon select all (F9) is used to select all the fields.
An icon deselect all (shift + F2) is used to deselect all the
fields.
Once the table is displayed either in ALV list format or ALV grid
format.
Click on an icon local file (ctrl + shift + F9).
Select the required file format such as ‘spread sheet’ or ‘rich
text’ or ‘html format’……etc.
Click on yes button.
Select the required directory by pressing the function key ‘F4’
or search help icon.
Enter the file name (download_excell.xls).
Click on back icon.
[Date]
In SAP the currency and quality fields are required currency key
and quantity unit. Hence, the reference table and the reference
field must be specified for currency and quantity fields.
The data type for the currency field is ‘CURR’ and the data type
for the currency key is ‘CUKY’.
The data type for the quantity is ‘QUAN’ and the data type for
quantity key is ‘UNIT’.
Note:
The reference table could be any table which has the currency
key and quantity unit fields.
The same table can also be used as a reference table if it has
the currency key or quantity unit fields.
Once the currency and quantity fields are inserted in the table
or structures.
Click on the tab currency or quantity fields.
Note: The columns reference table and reference fields are enabled
for the currency and quantity fields only.
100.50 pieces/kgs/grams……..
Note: In the real time the custom tables and the maintenance
views are maintained using the transaction code SM30 only.
EMP_NO :
_______________
EMP_NAME :
_______________
|
|
|
SINGLE SCREEN
Overview screen – 1
Document Prepared By Sonu Jangir Sap Abap Developer
In the real time the option one step maintenance is
preferable. Since, the multiple entries can be maintained at a
time.
Note: Select an entry and click on delete (shift + F2) icon to delete
the table / view entries.
Click on save icon.
Click on back icon.
inserted.
Deletion of TMG:
Table Adjustment:
Note:
The TMG is not copied while copying the table.
The data of an existing table is not copied while copying the
table.
UPDATE X
Click on save icon.
Click on local object button.
Execute the above created transaction code to maintain the
[Date]
table.
Document Prepared By Sonu Jangir Sap Abap Developer
Indexes:
Primary Index:
Secondary Index:
Note: In the real time the secondary indexes are not advisable since
the data is filtered at database level for all the users.
The indexes are represented as below.
Note:
Here domain name of EMP_NO and EMPNO should be similar.
It is not possible to join pooled and cluster tables, since they
are already set of tables.
A search help is displayed to see the possible entries of a
check table field on the foreign key field when the foreign key
table or child table are executed.
|
|
|
Key fields / candidates
There are two ways to check the relationship between the tables:
[Date]
Note:
Follow the similar steps to insert any number of transparent
tables.
The button delete table is used to remove the tables from the
join.
Note: If the system given an error message as ‘entry xxxx does not
exists in the check table’, the relationship is working fine.
Value table:
Intervals:
Lower Limit Upper Limit Short Text
A S
[Date]
T X
Document Prepared By Sonu Jangir Sap Abap Developer
(or) Value table (ZCUST_TABLE2)
Standard Tables:
Example:
Most of the FICO tables start with BS*, PR* and CS*
Note:
In fico some of the tables are cluster tables which start with
BSE*
Example: BSEG – Accounting Document Segment.
BSEC – Accounting Data Document Segment.
BSET – Tax Data Document.
…….
Vendor Tables:
Customer tables:
[Date]
In case of linear search the search criteria is started for the first
record and stopped once the required record is found.
Example: 1, 2, 3,……75,……100.
Linear search
In case of binary search total number of records are split in to
two equal parts (n/2) then the search criteria is started in the
second half.
[Date]
Note: in case of delivery class ‘A’ the table or maintenance view can
be maintained in any system (Development Quality
Production) using SM30.
Master data:
Transaction data:
Note: If the user tries to enter a record over that the selected
range, the system will increase the size category in to a next
category (0 to 1).
e.) Buffering:
Fully buffer:
Structures:
[Date]
Introduction:
Document Prepared By Sonu Jangir Sap Abap Developer
It is almost similar to a table but only the difference is the
structures do not have any physical data. Whereas, tables have
physical data.
The structure is filled with a single record at runtime only.
The structure can be referred across the system.
Example: EMP_CITY
Creation of domain:
Pre-defined types:
Steps to make use of the predefined types while creating the table
or structure:
Note: Follow the similar steps to make use of pre-defined types for
any number of fields.
[Date]
Example:
Document Prepared By Sonu Jangir Sap Abap Developer
Component Component type Data Length Short
type description
EMP_CITY <ZCUST_EMP_CITY> CHAR 30 Employee
city
EMP_COUNTRY CHAR 25
Employee
country
Include structure:
Append structure:
Note: Fields for include and append structure are in blue color.
INCLUDE APPEND
[Date]
These are used to display all the possible entries in the search
help window.
The function key (F4) or search help icon () is pressed to display
the search help window.
The DDIC search helps are of two types.
o Elementary search help.
o Collective search help.
Example:
Search help IMP EXP LPOS SPOS
parameter
NAME1 * * 2 2
NOTE:
The checkboxes IMP and EXP must be check to import all the
possible entries from the specified table or help view and
export the selected entry to the screen fields.
The position numbers LPOS and SPOS must be filled with the
same number to position the search help window on a screen
field.
The search help exit is used to control the possible entries of a
search help.
KUNNR * * KUNNR
Click on the tab included search helps.
Enter the required elementary search helps.
Place the cursor on the 1st search help name.
Click on the button parameters assignment.
Click on yes button.
Click on copy button.
Note: Follow the similar steps to assign the parameters for any
number of search helps.
Click on activate icon.
Click on local object button.
Click on yes button.
Click on test icon.
Press F4 function key.
Click on an appropriate tabs to see the possible entries.
Cancel the search help window.
Click on back.
4. Hot key:
5.VIEWS
Introduction:
1. Database view:
2. Maintenance view:
3. Help view:
4. Projection view:
Note: The transaction code SQVI can also be used to know the join
conditions.
Example:
Note:
Follow the similar steps for any number of base tables.
The field names should not be duplicate in the tables or
structures or views.
Note:
Follow the similar steps to create the help view by selecting a
radio button help view.
Help views cannot be executed.
Note: Follow the similar steps to select the fields for any number of
tables by clicking on ‘Table Fields’ button.
[Date]
6.LOCK OBJECTS
Introduction:
They are used to control the parallel access for the same data
by the multiple users. i.e., the synchronous access to the same
data is provided using lock objects.
The lock object name should start with ‘E’ followed by the table
name.
Example:
E<ZCUST_DBNAME> EVBAP
Custom table standard table
Following are different types of lock modes:-
1. Write lock.
2. Read lock.
3. Exclusive not cumulative.
1. Write lock:
2. Read lock:
Note: All other write locks are rejected but read locks are accepted.
Note: The system generated two function modules one starts with
ENQUEUE* and another one with DEQUEUE* once the lock object is
activated.
The transaction code SM12 is used to list out the locked objects
and to delete locked objects.