Category - Data Dictionary - SAP TECH CONCEPTS

12/23/2017 Category: Data Dictionary - SAP TECH CONCEPTS
SAP TECH CONCEPTS (/)

Home (/) About (/about.html) Contact (/contact.html)
What is Domain in DDIC of SAP ? Author

(http://saptechconcepts.weebly.com/home/what-is-domain- Vamsi Bodda.
data-element)
6/12/2014 1 Comment (http://saptechconcepts.weebly.com/home/what-is-domain-data-element#comments) Archives
November 2016
Domain : Domain defines the technical attributes of a field such as data type,no.of characters,decimal
(/home/archives/11-2016)
places.
January 2015
It also describes the output length,conversion routine,sign,upper/lower case,values possible for the
field that is using this domain.
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
RSS Feed (/1/feed)
Data Type : This describes the type of the data like

CURR,QUAN,CHAR,NUMC,RAW,STRING,TIMS,DATS etc.
No. of characters : Number of valid positions of a field without editing characters (e.g. commas or
points).
Decimal Places : Number of decimal places allowed for a value.
Decimal places are only meaningful for the data types CURR, DEC, FLTP, QUAN, DF16_DEC, and
DF34_DEC.
Output Length : Maximum field length including editing characters (e.g. commas or periods) for inputting
and outputting values.
This value is computed automatically from the specifications for the data type, number of places and
possibly the number of decimal places. It can be overwritten.
Conversion Routine : Conversion takes place when converting the contents of a screen field from
display format to SAP-internal format and vice versa and when outputting with the ABAP statement
WRITE, depending on the data type of the field.
A conversion routine is identified by its five-place name and is stored as a group of two function modules.
https://saptechconcepts.weebly.com/home/category/data-dictionary 1/11
The function modules have a fixed naming convention. The following function modules are assigned to
conversion routine xxxxx: Categories
CONVERSION_EXIT_xxxxx_INPUT All (/home/category/all)
CONVERSION_EXIT_xxxxx_OUTPUT BDC
The INPUT module performs the conversion from display format to internal format. The OUTPUT module (/home/category/bdc)
performs the conversion from internal format to display format. Data Dictionary
If a screen field refers to a domain with a conversion routine, this conversion routine is executed (/home/category/data-
automatically each time an entry is made in this screen field or when values are displayed with this dictionary)
screen field. Enhancements
Sign : If fields referring to this domain can contain negative values, this flag must be set. (/home/category/enhanc
When the field contents are output on the screen, the first position of the output is reserved for a ements)
plus/minus sign. Function Modules
Lower Case : If this indicator is set, upper case and lower case are distinguished when you enter values (/home/category/functio
with screen masks. n-modules)
Otherwise all the letters entered will be converted to upper case when you enter values with a screen Generic ABAP
mask. (/home/category/generic
Value Range : Here you can specify Fixed single values,Intervals or a Value Table. -abap)
So that the values present in the Fixed values/Intervals defined / values present in the associated Value OOPS
table will be accepted as inputs for the fields having this domain. (/home/category/oops)
You can only define fixed values for domains of data types CHAR, NUMC, DEC, INT1, INT2 and INT4. Performance Tuning
(/home/category/perfor
Like 1 Tweet mance-tuning)
SAP Query & LDB
1 Comment (http://saptechconcepts.weebly.com/home/what-is-domain-data-element#comments)
(/home/category/sap
query ldbc350e11eb0)
SAP R/3 Architecture
What is Data element in SAP ? (/home/category/sap-r3-
architecture)
(http://saptechconcepts.weebly.com/home/what-is-data- Tips And Tricks
element-in-sap) (/home/category/tips-
and-tricks)
6/12/2014 0 Comments (http://saptechconcepts.weebly.com/home/what-is-data-element-in-sap#comments)
Tricky Interview Q's
Data Element : Data element describes the functional attributes of a field. (/home/category/tricky-
The below screenshots depicts the properties associated with a data element. interview-qs)
Name : The name of the Search help that can be assigned to the data elememt.
Parameters : The parameter should be a both importing and exporting parameter of search help.
Parameter ID : A field using this data element can be filled with proposed values from SAP memory
using a parameter ID.
Default Component Name : You can assign an English default name to the data element in this field.
Components in BAPI structures that use the data element should have this default name. Using default
names unifies the assignment of component names.
Change Document : This flag is used to create change documents for business objects.
Logging only takes place if the fields whose contents were changed refer to a data element that was
flagged as relevant for the change document.
No Input History : If this indicator is set, the mechanism that the SAP GUI uses to handle the input
history of a screen input field is switched off.(you can use this property for fields that hold sensitive data
like account numbers,pin numbers etc.)
Basic direction is set to LTR : If this flag is set, the field content is always displayed in the basic writing
direction LTR (left to right), even if the write direction of the window is RTL (right to left) - for example,
when logging on in Hebrew or Arabic.
No BIDI Filtering : This flag is required only in connection with bi-directional (BIDI) scripts such as
Hebrew or Arabic, and only in special cases. It should not be set for normal situations.
Field Label : The Short,Medium,Long text is used for screen field texts and Header text is used as
heading to output the field values in the lists.
Like 1 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/what-is-data-element-in-sap#comments)
Types of DDIC Database tables in SAP

(http://saptechconcepts.weebly.com/home/types-of-ddic-
database-tables-in-sap)
6/10/2014
0 Comments (http://saptechconcepts.weebly.com/home/types-of-ddic-database-tables-in-sap#comments)
There are three types of database tables :

1. Transparent tables
2. Pooled tables
3. Cluster tables
Transparent tables :
1. It has one-to-one relationship with the table in the database i.e. table in the database has the same
name as in the dictionary.The database table has the same name, the same number of fields, and the
fields have the same names as the R/3 table definition.
2. We can use either Native SQL or Open SQL to access these tables.
3. Secondary indexes can be created and buffering can be done on transparent tables.
Use : Data of commercial relevance is usually stored in transparent tables.All application and user data is
stored in transparent tables.
Pooled Tables / Table Pool : Several pooled tables can be combined to form a table pool.The table pool
corresponds to a physical table on the database in which all the records of the allocated pooled tables are
stored.Each Pooled table must be assigned to a Table Pool.
1. It has many-to-one relationship with the table definition in the database i.e. many pooled tables are
stored in a single table in the database called a table pool.
2. Table Pools are used to hold large number of small tables.They need not have key in common.
3. Pooled table can be accessed only using Open SQL.
4. Secondary indexes cannot be created on Pooled tables and can be buffered..
5. The definition of a pool consists essentially of two key fields (Tabname type CHAR(10) and Varkey
type CHAR(n) ) and a long argument field (Vardata type RAW(n) ).
6. The name of the pooled table is written to the field Tabname.
The contents of all key fields of the pooled table are written as a string to field Varkey and the contents of
all data fields as a string to field Vardata.
The length of the string stored in Vardata is entered in field Dataln by the database interface.
Example of Pooled tables: A004, A005
Example of Table Pool : KAPOL
Cluster tables / Table Cluster : Several cluster tables can be combined to form a table cluster.Several
cluster tables are stored in one corresponding table on the database.Each Cluster table must be
assigned to a Table Cluster.
1. It has many-to-one relationship with the table definition in the database i.e. many cluster tables are
stored in a single table in the database called a table cluster.
2. Table Clusters are used to hold few number of large tables that have common primary key fields.
Several logical data records from different cluster tables can be stored together in one physical record in
a table cluster.
3. Cluster table can be accessed only using Open SQL.
4. Secondary indexes cannot be created on Cluster tables and cannot be buffered.
5. A cluster key consists of a series of freely definable key fields and a field (Pageno) for distinguishing
continuation records. A cluster also contains a long field (Vardata) that contains the contents of the data
fields of the cluster tables for this key.
Use : A cluster is useful in the case where data is accessed from multiple tables simultaneously and
those tables have at least one of their primary key fields in common. Cluster tables reduce the number of
database reads and thereby improves performance.
Example of Cluster tables: BSEC, BSEG , EDID4
Example of Table Cluster : RFBLG ,EDI40
Additional Info on Pooled and Cluster tables :

1. Table pools (pools) and Table clusters (clusters) are special table types in ABAP dictionary which
stores the data from several different tables.They should be used exclusively for storing internal control
information (screen sequences, program parameters, temporary data, continuous texts such as
documentation).
2. Pooled and cluster tables are generally created only by SAP and not by developers, due to proprietary
format of these tables within the database and technical constraints to use within ABAP/4 programs.
3. In pooled table both INDEX and APPEND STRUCTURE is disabled while in cluster only INDEX is
disabled.
4. Cluster tables must have one key common to assign to a Table Cluster but this is not the case for
pooled table.
Like 0 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/types-of-ddic-database-tables-in-sap#comments)
Technical settings of a database table in SAP

(http://saptechconcepts.weebly.com/home/technical-settings-of-
a-database-table-in-sap)
6/9/2014
0 Comments (http://saptechconcepts.weebly.com/home/technical-settings-of-a-database-table-in-sap#comments)
Data Class : The data class defines the physical area of the database in which the table is logically
stored.
The most commonly used data classes are :
APPL0 Master data

APPL1 Transaction data
APPL2 Organizational and customizing data
The data class has an effect on table storage only for the database systems ORACLE and
INFORMIX.
Size Category : The size category value specifies the probable space required for a table in the
database.
The category value ranges from 0 to 14 with each category having some fixed storage area value
in the database.
When you create a table, initial space is saved for it in the database. If more space is required
later as a result of data that has been entered, the storage space is increased in accordance with
the category selected.
Buffering : The buffering status specifies whether a table can be buffered or not.
Buffering a table improves the performance when accessing the data records contained in the
table.
For buffering status we have the following options :
Buffering not allowed
Buffering allowed but switched off
Buffering switched on
If Buffering is switched on we need to specify the type of buffering :
Single records buffering : Only the records of a table which are actually accessed are loaded into the
buffer.
This buffering is preferable for large tables where there are frequent single-record accesses (using
SELECT SINGLE ...)
Fully buffered : If a read access is made to a record, all records of the table are transferred to the buffer.
This buffering is preferable for comparatively small tables for which the access range is large.Tables best
suited to full buffering are small, frequently read, and rarely updated.
Generic Area buffered : When one record of the table is accessed, all the records whose left justified part
of the key (generic key area) match this record are loaded . The generic key is a part of the primary key
of the table that is left-justified.
The number of key fields to be entered must lie between 1 and the number of key fields -1.
The individual generic areas are treated like independent tables that are fully buffered.
Log data changes : The logging flag defines whether changes to the data records of a table should be
logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user
or an application program is recorded in a log table in the database.
The logs can be displayed with Transaction table history - SCU3 .
Write access only with Java : If this indicator is checked , the contents of the table may only be
changed from within Java.
Like 0 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/technical-settings-of-a-database-table-in-sap#comments)
Delivery Class of a database table in SAP

(http://saptechconcepts.weebly.com/home/delivery-class-of-a-
database-table-in-sap)
6/9/2014
0 Comments (http://saptechconcepts.weebly.com/home/delivery-class-of-a-database-table-in-sap#comments)
Delivery Class : The delivery class controls the transport of table data when installing or upgrading, in a
client copy and when transporting between customer systems.The delivery class is also used in the
extended table maintenance.
Following are the delivery classes:

A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table, SAP may insert new data records, but may not overwrite or delete existing
data records. The customer namespace must be defined in table TRESC.
E: System table with its own namespaces for customer entries. The customer namespace must
be defined in table TRESC.
S: System table, data changes have the same status as program changes.
W: System table whose data is transported with its own transport objects (e.g. R3TR PROG,
R3TR TABL, etc.).
Like 0 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/delivery-class-of-a-database-table-in-sap#comments)
Views in DDIC of SAP

(http://saptechconcepts.weebly.com/home/views-in-ddic-of-sap)
6/8/2014 0 Comments (http://saptechconcepts.weebly.com/home/views-in-ddic-of-sap#comments)
View : A View is a logical view defined on one or more tables i.e. view is not actually physically stored but
will be derived from one or more other tables.
Types of views :
There are four different types of views :
1. Database view (type D)
2. Projection view (type P)
3. Help views (type H)
4. Maintenance view (type C)
Other view types Structure view (type S) , Entity view (type E) are no longer supported as of Release
3.0.
Database view :
Data about an application object is often distributed on several database tables. A database view
provides an application-specific view on such distributed data.
The view defined in the ABAP Dictionary is reproduced in the underlying database and you can
only define them using transparent tables.
You can use both OPEN SQL and NATIVE SQL to access database views from ABAP programs.
If you define a database view using only one table, you can make changes to the view. For
database views containing several tables, however, only read accesses are allowed.
Database views implement Inner join .
Significance :
Database views should be created if want to select logically connected data from different tables
simultaneously. Selection with a database view is generally faster than access to individual tables.
Since the join operation is executed in the database in this case, you can minimize the number of
database accesses in this way.
Projection view :
Projection views are used to suppress certain fields from a table.
A projection view contains exactly one table. You cannot define selection conditions for projection
views.
Unlike database view ,there is no restriction on type of the table. It is possible to access
transparent/pooled tables/cluster tables with a projection view.
Significance :
When you access the database, you only read and write the field contents actually needed by using a
projection view.
Help View :
Help view can be used as a selection method in search help.
The first table to be inserted in the help view is called as the primary table of the help view. The
tables added to this primary table with foreign keys are called secondary tables.
A help view implements an Outer join, i.e. all the contents of the primary table of the help view
are always displayed. You therefore should not formulate a selection condition for fields in one of
the secondary tables of the help view.
Significance :
The selection method of a search help is either a table or a view. If you have to select data from several
tables for the search help, you should generally use a database view as selection method. However, a
database view always implements an inner join. If you need a view with outer join for the data selection,
you have to use a help view as selection method.
Maintenance View :
Maintenance views are used to maintain complex application objects in an easy way.
It implements Outer join
All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for
maintenance views are always derived from the foreign key.
You can maintain the data from the base tables of a maintenance view together using table views
maintenance transaction SM30.
Significance :
You can display, modify and create the data of a complex application object together.
Normally the user is not interested in the technical implementation of the application object, that is in the
distribution of the data on several tables.So in this case the maintenance view is helpful for easy
maintenance of data.
Restrictions for selecting the secondary tables for Maintenance and Help Views :
There are some restrictions for selecting the secondary tables of a maintenance view or help view. The
secondary tables have to be in an N:1 dependency to the primary table or directly preceding secondary
table.
This ensures that there is at most one dependent record in each of the secondary tables for a data record
in the primary table.
Like 0 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/views-in-ddic-of-sap#comments)
Type Group in DDIC of SAP

(http://saptechconcepts.weebly.com/home/type-group-in-ddic-
of-sap)
6/7/2014 0 Comments (http://saptechconcepts.weebly.com/home/type-group-in-ddic-of-sap#comments)
Type Group :
Type group is used to declare different type declarations under a single group in data dictionary.
This enables us to globally declare a custom type and use it in multiple programs using TYPE-
POOLS statement.
In addition to Types,Constants can also be created in it.
Some of the commonly used SAP standard type groups are SLIS, ABAP etc.
We can also create our custom type groups.
The restriction for creating the types/constants in it is all the type names and constant names
should begin with the type group name.
Example ; for SLIS type group...the namming convention is SLIS_<type/constant name>.
By using this site you consent to the use of cookies. Cookies can be managed in your browser or device settings. ✕
Like 0 Tweet
0 Comments (http://saptechconcepts.weebly.com/home/type-group-in-ddic-of-sap#comments)
Lock object in DDIC of SAP

(http://saptechconcepts.weebly.com/home/lock-object-in-ddic-
of-sap)
6/6/2014 6 Comments (http://saptechconcepts.weebly.com/home/lock-object-in-ddic-of-sap#comments)
Lock object : The name of the lock object should begin with E.The purpose of the lock mechanism is to
prevent two transactions from changing the same data in the database simultaneously.
In a lock object we define the tables in which data records must be locked with a lock request, and the
key fields of these tables as Lock parameters.
When we activate the lock object, the two function modules ENQUEUE_<lockobjectname> and
DEQUEUE_<lockobjectname> are generated from its definition to set and release locks respectively.
When tables are selected, one table is selected as Primary table.

If you want to lock records in more than one table with the lock object,further tables (secondary tables)
can also be added using foreign key relationships.(the foreign key fields must be key fields of the foreign
key table).
Types of Lock modes :

Exclusive lock/Write lock : The locked data can be read or processed by one user only. A request for
another exclusive lock or for a shared lock is rejected.
Shared lock/Read Lock : Several users can read the same data at the same time, but as soon as a user
edits the data, a second user can no longer access this data. Requests for further shared locks are
accepted, even if they are issued by different users, but exclusive locks are rejected.
Exclusive but not cumulative lock : Exclusive locks can be requested by the same transaction more
than once and handled successively, but an exclusive but not cumulative lock can only be requested once
by a given transaction. All other lock requests are rejected.
Like 0 Tweet

Category - Data Dictionary - SAP TECH CONCEPTS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Category - Data Dictionary - SAP TECH CONCEPTS

Uploaded by

Copyright:

Available Formats

12/23/2017 Category: Data Dictionary - SAP TECH CONCEPTS

SAP TECH CONCEPTS (/)

What is Domain in DDIC of SAP ? Author

RSS Feed (/1/feed)

Data Type : This describes the type of the data like

Types of DDIC Database tables in SAP

There are three types of database tables :

Additional Info on Pooled and Cluster tables :

Technical settings of a database table in SAP

APPL0 Master data

Delivery Class of a database table in SAP

Following are the delivery classes:

Views in DDIC of SAP

Type Group in DDIC of SAP

Lock object in DDIC of SAP

When tables are selected, one table is selected as Primary table.

Types of Lock modes :

You might also like