Dictionary objects (se11)

1. Tables

2. Views

3. Data elements

4. Domains

5. Type Groups

6. Search Helps

7. Table Types

8. Lock objects

9. Structures

Table can be used to store the data permanently.

Data  master data / Transaction data

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 account holder
name, material data, vendor data.
Transaction data:

Day to day business data is called transaction data.

Example:-Emp attendance details, emp salaries, customer orders, bank transactions.

Business Document's- are used for data exchange

Enquiry form, quotation, purchase order document, sales order document, billing document,
delivery schedule document.

 Every business document contains 1 header record and one or more item record's.

 Header records data will be stored in header tables.

 Item records data will be stored in item tables.

Example for Header and item tables:

VBRK  Billing document header data

 Key fields  mandt(client), vbeln(billing document no)

Eg: vbeln  0090005178

VBRP  Billing document item data

Key fields  mandt (client), vbeln (billing document no), posnr (item no)

Eg: vbeln  0090005178  contains 4 items

Other header and item tables: - Sales Documents (VBAK and VBAP),
Purchase Documents (EKKO and EKPO)

 As part of database tables we can directly use the standard tables, enhance the
standard table (adding fields).

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

To create dictionary objects, we use t-code -> se11.

Primary key:

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.

Combination of primary key fields is called as composite key.

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 client 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 will not
available in other client.

Eg: KNA1, MARA, LFA1, VBAK, VBAP, EKKO, EKPO, VBRK, VBRP
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.

Eg: TFDIR, TADIR

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 field can be created in two ways:-

i. By using direct data types.

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

Procedure for creating custom database 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 custom 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 application table.

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 allowed with restriction.

Note:

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

2. Display Maintenance allowed.

It supports all the operations i.e 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:

It specifies the schema (partition) in which the table as to be stored. As an ABAP Consultant we
will use only Master Schema (APPL0) and Transaction schema (APPL1).
Size category:

It 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 automatically to the
amount of initial size.

 In size category the range of number of data records depends upon "structure of the
table".
Enhancement category:

It specifies the type of enhancement that can be made to the table.

Enhancement is a process of adding the additional fields in the standard tables.

Limitations of table fields' creation using direct data types:

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

 We cannot impose validations on table data.

 It doesn't support reusability

  Cannot maintain field labels
Table maintenance:

After creating every database table, ABAP consultants must generate Table Maintenance, so
that an interface will be generated through which the end users can maintain the table.

 The table maintenance allows the end user to maintain the table for performing the
operations like insertion, deletion, Modification and view the data (display).

 For generating table maintenance, we require a function group.

 A function group is an object which stores objects related to table maintenance.

I.e. dependent objects (screens, subroutines, f.m's) related to table maintenance are
stored inside function group.

 For creating Function group, we use se80

 As part of generating table maintenance, we need to specify maintenance type which

is of two types.

 Maintenance type is of two types:-

i. One step:

In one step only one screen is generated called as overview screen in which all the CRUD
(create, read, update and delete) operations are performed.

ii. Two step:

 In two step, Two screens will be generated, overview screen and single screen.

 In overview screen we can only 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)->z830fgroup

2. In SE11, navigate to the table, choose the menu 'utilities table maintenance
generator'

Authorization group  &nc&

Note: Authorization group is an object created by BASIS consultant which is associated

with set of users who are authorized to maintain a particular object (table).

Function group  z830fgroup (existing function group)

Maintenance type one step (select the radiobutton)

 Propose 'overview screen' no by choosing 'find scr numbers' propose
screen no. on appl.toolbar

3. Click on create button (appl.toolbar)

 Once a table maintenance is generated, we can maintain the table using the T-
code
"SM30".

 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 (ZTEMP), create  provide short text( … }, choose the
radiobutton 'Transaction with parameters' Provide Transaction (SM30), select the
checkbox 'skip initial screen' , in gui support select the checkbox 'sap gui for
windows' and provide default values for the skipped screen at the end

Name of screen field value

Viewname z830emp

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 code (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).
Table creation using data elements and domains:

Data element: is a reusable dictionary object which provides description for the field.
I.e. the description (labels) maintained at data element level will automatically
appear on the screen wherever the data element is referred. It can be created by
referring to a direct data type / referring to a domain. We can also associate a
search help (f4 help) as part of data element.

Domain: is a reusable dictionary object which stores technical properties of the field like
data
type, size, fixed values, value table….
Note:

If it is client dependent table we have to give minimum two primary key fields otherwise if
only
'mandt' is primary key field then we can maintain maximum of single

record. Collection of Primary key fields is called as Composite key.