Dictionary objects(se11)

Master data:-

The data which doesn’t change frequently is known as master data.

Example :-

Empno, ename ,customer no,customer name ,bank account no, bank

Transaction data:-

Day to day business data is called transaction data.

Example:-

Emp attendance details, emp salaries, customer orders, bank transactions.

Document’s:- are used for data exchange

Enquiry form, quotation, purchase order document, sales order document ,

 Every business document contains 1 header record and one or more

 Header records data will be stored in header tables.

 Item records data will be stored in item tables.

 As part of database tables we can directly use the standard tables,

 We can also create the tables for storing the customer specific data.

To create dictionary object, we have t-code -> se11.

A field declared as primary key can’t accept the duplicate values.

In SAP, every table must contain minimum 1 key field and max. 16 primary
fields. Primary key fields must be at the beginning of the table.

 Based on the client concept, the database tables are classified into
two types.

i. Client dependent tables.

ii. Client independent tables.

Client dependent tables:-

The tables which contains MANDT as first field is called dependent.

MANDT field will hold the client no.

The records in these tables are specific to the client i.e. the record inserted
in one client and will not available in other client.

Client independent tables:-

This table doesn’t contain MANDT field.

The record’s in this tables are not specific to any client’s i.e. they are
available across the client’s .
Table creation:-
A table is dictionary object which is a collection of rows
(records) and columns (fields)
 Tables are used for storing the data permanently.

In ABAP a table can be created in two ways:-

ii. By using data elements and domains (recommended).

Procedure for creating custom tables:-

i. Analyze the fields and the corresponding data types.

ii. Create and activate the table.

iii. Generate table maintenance.

iv. Declare and define events (if required) at the table maintenance
level.

v. Create the t-code for the table maintenance.

Minimum settings required for creating database tables:

Delivery and maintenance settings:

1. Delivery class .

2. Data browser / table view maintenance .

Delivery class:
It is used for controlling the transporting of table data.

The possible value’s are “A” or “C”.

A -> application table used for storing master and transaction data.

Generally it is recommended to create the client dependent table as

C -> customizing table used for storing customers specific data.

Data browser / table view maintenance :-

It can contain the following 3 possible values.

In dialog box:

1. Display / Maintenance are allowed with restriction.

Note:

In this we can only view the data but we can’t perform the operatons
like insertion, deletion and modification.

2. Display Maintenance allowed.

It supports all the operations we can view, insert , delete and modify.

3. Display maintenance not allowed.

It doesn’t support any of the operations.

Technical settings:-

1. Data class.

2. Size category.
 Data class:-

Its specifies the schema (partition) in which the table as to be stored.

Example:-

As an ABAP Consultant we will use only Master Schema (APPL0) and

Size category:

Its specifies the initial amount of memory that needs to be allocated for the
database table.

 When the initial memory is utilized, the memory gets extended

 In size category the range of number of data records depends upon “

Enhancement category:-

Its specifies the type of enhancement i.e. that can be made to the table.

Later on enhancement is a process of adding the additional fields in the

Limitations of table creation using direct data types:-

Disadvantages:

 Always the character field values are captured in upper case.

 We cannot impose validations on table data.

 It doesn’t support reusability

Table maintenance :-
After creating every database table, ABAP consultant must
generate Table Maintenance.
The table maintenance allows end user to maintain the table
for performing the operations like insertion, deletion,
Modification and view.
For generating table maintenance we require function group.
A function group is an object which stores the objects related
to table maintenance. i.e. dependent objects (screens,
subroutines,f.m’s) related to table maintenance are stored
inside function group.
As part of generating table maintenance, we need to specify
maintenance type which is of two types.
Maintenance type is of two types:-
i. Step 1:
In one step only one screen is generated called as overview
screen in which all the CRUD operations are performed.
ii. Step 2 :
In two step, Two screens will be generated, overview screen
and single screen.
 In overview screen we can view the data, delete the data
and modify the data.
In single screen we can insert the data.
Procedure for generating Table maintenance:
1. Create /Consider a function group (se80)
2. In SE11, navigate to the table, choose the menu ‘utilities
table maintenance generator’
Authorization group  &nc&
Function group  z930fgroup (existing function group)
Maintenance type one step (select)
Propose ‘overview screen’ no by choosing find scr
numbers on appl.toolbar
3. Click on create button (appl.toolbar)
 T-code “SM30” is used for maintaining the database tables.
To minimize the process of table maintenance, we need to
create custom t-code for every table maintenance
Custom t-code creation SE93
Creating T-code for table maintenance:
SE93 .provide custom t-code (z930), create  provide
short text( … ), choose the radiobutton ‘Transaction with
parameters’ Transaction (SM30), select the checkboxes
‘skip initial screen’ and provide default values for the skipped
screen at the end
Name of screen field value
Viewname z930emp
Update X
Note: For collecting screen field names, goto sm30 initial
screen, press f1 in table/view field and collect the screen
field name, similarly put focus on ‘maintain’ button, press f1
and collect the function (upd) (equal to update)
Note: Whenever we create t-code for any object, select the
check box ‘SAP GUI for windows’ ,otherwise t-code cannot
be used(incomplete).
Note :-

If it is client dependent table we have to give minimum two primary

Collection of Primary key fields is called as Composite key.