Data dictionary :

➔​ Also known as abap dictionary - central repository to define/maintain

objects related to database.
◆​ Define - creation of objects
◆​ Maintain - changing/deleting objects.

Objects:

➔​ DATABASE TABLE
➔​ VIEW
➔​ DATA TYPE
◆​ DATA ELEMENT
◆​ STRUCTURE
◆​ TABLE TYPE
➔​ TYPE GROUP
➔​ DOMAIN
➔​ SEARCH HELP
➔​ LOCK OBJECT

DATABASE TABLE - stores data in the form of ‘rows’

and ‘columns’
◆​ Row - record
◆​ Column - field (to define a table , field should be defined first)
★​ To define the field
○​ data type, length - domain
○​ Description - data element

​ ​ FIELD = DATA ELEMENT + DOMAIN

❖​ DOMAIN - TECHNICAL INFORMATION FOR A FIELD ,such as data type and

length , also specifies
■​ Sign (checked- allows negative)
■​ Lower case (checked- accepts lowercase input)
■​ Conversion routine
●​ Used to convert data between display format (external) and
database format (internal).​

●​ Example: MATNR (Material Number)​

◆​ Display: M1001​

◆​ Stored as: 000000M1001​

 ●​ Routine used: CONVERSION_EXIT_MATN1_INPUT/OUTPUT​

●​
■​ Single values, intervals.
■​ Value table
❖​ DATA ELEMENT - SEMANTIC INFORMATION FOR A FIELD ,such as field
description , field labels (short, medium,long and heading)

Advantages:

Reusablity - instead of creating , same data element and domain can be reused in
multiple table fields

Used in foreign key relationship, search help, ALE-IDOC.

METHODS TO CREATE FIELDS :

●​ CREATE DOMAIN AND DATA ELEMENT SEPERATELY

○​ DOMAIN
■​ SE11>>DOMAIN >> NAME(STARTSWITH Z OR Y with naming
conventions)>>CREATE >>SHORT DESCRIPTION
●​ PROPERTIES → info about package , date , language
used
●​ DEFINITION → info of the field characteristics
○​ Format
■​ Data type
■​ No of characters
■​ Decimal places
○​ Output characteristics
■​ Output length
■​ Convers. Routine

Conversion Routine (also called Conversion Exit) is used to convert values

between internal (DB) format and display (external) format.
Naming Convention:​
Always starts with CONVERSION_EXIT_​
Structure:

CONVERSION_EXIT_<NAME>_INPUT – Converts from external to internal

CONVERSION_EXIT_<NAME>_OUTPUT – Converts from internal to external

Example:​
Domain MATNR (Material Number) uses conversion exit:​
CONVERSION_EXIT_MATN1

INPUT: Strips leading zeros from user input

OUTPUT: Adds leading zeros for DB format

Function Modules:

CONVERSION_EXIT_MATN1_INPUT – Used before saving to DB

CONVERSION_EXIT_MATN1_OUTPUT – Used before displaying to user

Why It’s Important:​

Ensures consistent format handling for:

Material numbers

Customer/vendor numbers

Dates

Units, etc.

■​ Sign
■​ Lower case
●​ VALUE RANGE →
○​ Single vals
○​ Intervals
○​ Value table

After filling the necessary fields >> ctrl+s(save) >>ctrl+f2(check)>>

ctrl+f3(activate)
 ○​ DATA ELEMENT
■​ SE11(TCODE)>>DATATYPE>> DATA ELEMENT >>
NAMING(STARTING WITH Z OR Y)

>>CREATE >>CONTINUE >> SHORT DESCRIPTION

●​ ATTRIBUTES - INFO ABOUT USER , DATE(LAST

CHANGED), PACKAGE, LANGUAGE USED
●​ DATA TYPE
○​ ELEMENTARY TYPE
■​ DOMAIN
■​ DATA TYPE
■​ LENGTH (HERE WE NEED TO GIVE THE NAME OF
THE DOMAIN WE CREATED AND ENTER TO VIEW )
○​ BUILT-IN TYPE
■​ DATA TYPE
■​ LENGTH
○​ REFERENCE TYPE
■​ REFERENCED TYPE
■​ REFERENCE TO BUILT-IN TYPE
●​ DATA TYPE
●​ LENGTH
●​ FURTHER CHARACTERISTICS
○​ SEARCH HELP
■​ NAME
■​ PARAMETERS
○​ PARAMETER ID
○​ DEFAULT COMPONENT NAME
○​ NO CHANGE DOCUMENT
○​ NO INPUT HISTORY
○​ BIDIRECTIONAL OPTIONS
■​ BASIC DIRECTION IS SET TO LTR
■​ NO BIDI FILTERING
●​ FIELD LABEL
○​ SHORT, MEDIUM,LONG,HEADING

[ AFTER FILLING REQUIRED DETAILS OF THE FIELD , SAVE ,CHECK AND

ACTIVATE]

●​ CREATE DOMAIN WITHIN A DATA ELEMENT

○​ SE11>>DATA TYPE >> DATA ELEMENT>> NAMING,
CREATE,CONTINUE>> SHORT DESCRIPTION>> FIELD LABEL

>> CLICK ON DATA TYPE >> IN DOMAIN - GIVE NAME AND DOUBLE
CLICK>> SYSTEM ASKS - TO CREATE , CONTINUE AND DO THE
DOMAIN CREATION PROCESS , AT LAST ACTIVATE IT .

●​ CREATE DOMAIN AND DATA ELEMENT IN A TABLE

○​ INSIDE THE TABLE >> TYPE THE NAME OF THE DATA ELEMENT
INSIDE THE DATA ELEMENT FIELD >> DOUBLE CLICK ON THE
FIELD >> CREATE DATA ELEMENT >> CREATE DOMAIN INSIDE THE
DATA ELEMENT , SAVE AND ACTIVATE.

DATABASE TABLE CREATION:

❖​ SE11>> DATABASE TABLE>>NAME(STARTING WITH Z OR Y(NAMING

CONVENTION) >> CREATE>> SHORT DESCRIPTION.
❖​ TABS INSIDE THE DATABASE TABLE
➢​ ATTRIBUTES - INFO ABOUT USER , DATE(LAST CHANGED),
PACKAGE, LANGUAGE USED
➢​ DELIVERY AND MAINTANENCE
■​ DELIVERY CLASS
●​ A - APPLICATION TABLE (MASTER AND TRANSACTION
DATA)
●​ C- CUSTOMIZING TABLE, MAINTANENCE ONLY BY
CUSTOMER , NOT SAP IMPORT
●​ L- TABLE FOR STORING TEMPORARY DATA ,
DELIVERY REPORT.
●​ G,E,S,W - SYSTEM DATA.
■​ DATA BROWSER/TABLE VIEW MAINTENANCE
 SE11 SE16 SE16N SM30

Display/Maintenance Display Yes Yes Yes Yes

allowed
Maintenance Yes Yes Yes Yes

Display/Maintenance Display No No No No
not allowed
Maintenance No No No No

Display/Maintenance Display Yes Yes Yes Yes

allowed with
restrictions Maintenance No No No No

Only Display Display Yes Yes Yes Yes

allowed
Maintenance Yes No No No

➢​ FIELDS
➢​ ENTRY HELP/CHECK
➢​ CURRENCY/QUANTITY FIELDS

TECHNICAL SETTINGS:

➔​ GENERAL PROPERTIES
◆​ LOGICAL MEMORY PARAMETERS
●​ DATA CLASS - IT SPECIFIES THE PHYSICAL AREA OF THE
TABLE INSIDE THE DATABASE
○​ APPL0 - MASTER DATA, TRANSPARENT TABLES
○​ APPL1 - TRANSACTION DATA, TRANSPARENT TABLES
○​ APPL2 - ORGANIZATION AND CUSTOMIZING
◆​ MASTER DATA - DATA WHICH NEVER
CHANGES/CHANGES VERY RARELY .
◆​ TRANSACTION DATA - DAY TO DAY BUSINESS
DATA WHICH CHANGES EVERY DAY .
◆​ ORGANIZATION DATA - RELATED TO
ORGANIZATION OR COMPANY LIKE HOW MANY
COMPANY CODES,PLANTS,SALES
ORGANIZATION ETC,
○​ Size category is used to define the expected space
required for the table in the database. It defines the
amount of the records that the memory segment
 can hold. We can choose a size category from 0 to 4
for your table.
○​ When you create a table, the system reserves initial
space (an initial extent) in the database. If more
space is required at a later time due to data entries,
additional memory is added depending on the
selected size category.

◆​ TABLE SHARING
●​ SHARING TYPE
◆​ BUFFERING - TEMPORARY MEMORY TO STORE THE DATA. ITS
MAINLY USED TO INCREASE THE SYSTEM PERFORMANCE.
●​ BUFFERING NOT ALLOWED - DATA IS NOT STORED IN
BUFFER (DEFAULT)
●​ BUFFERING ALLOWED BUT SWITCHED OFF - USED BY SAP
●​ BUFFERING SWITCHED ON - DATA STORED IN BUFFER
◆​ BUFFERING TYPE
●​ SINGLE RECORD BUFF- ONLY FIRST RECORD OR RECORDS
WHICH ARE READ WILL BE STORED IN THE BUFFER.
●​ GENERIC AREA BUFFERED - THE KEY FIELD’S DATA IS
CALLED GENERIC AREA . ONLY GENERIC AREA DATA i.e,
KEY FIELDS DATA WILL BE STORED IN BUFFER
●​ FULLY BUFFERED - ALL RECORDS WILL BE STORED IN
BUFFER.
●​ (NUMBER OF KEY FIELDS)
◆​ DATA CHANGES
●​ LOG CHANGES - THIS CHECKBOX WOULD DEFINE WHETHER
CHANGES TO THE DATA RECORDS OF THE TABLE ARE TO
BE LOGGED OR NOT
○​ IF CHECKBOX IS SELECTED , THEN EVERY CHANGE
 (UPDATE/ DELETE) TO AN EXISTING DATA RECORD IS
RECORDED IN THE STANDARD DATABASE LOG TABLE
DBTABLOG.

CHECK AND ACTIVATE , GO BACK TO TABLE>> CHECK AND ACTIVATE.

➔​ DB- SPECIFIC PROPERTIES

◆​ STORAGE TYPE
●​ COLUMN STORE
●​ ROW STORE
●​ UNDEFINED
◆​ LOAD UNIT
●​ COLUMN PREFERRED
●​ PAGE PREFERRED
●​ COLUMN ENFORCED
●​ PAGE PREFERRED

ENHANCEMENT CATEGORY FOR STRUCTURE :

​ WHEN THERE IS NO ACTIVE UNICODE CHECK , ENHANCEMENTS TO

TABLES AND STRUCTURES CAN CAUSE SYNTAX AND RUNTIME ERRORS
DURING TYPE CHECKS AND PARTICULARLY IN COMBINATION WITH DEEP
STRUCTURES.

GO TO EXTRAS → ENHANCEMENT CATEGORY (DEPENDING ON STRUCTURE

DEFINITION , THE RADIOBUTTON ALLOWED IN THE DIALOG BOX ARE READY
FOR INPUT .CHOOSE ONE OF THE POSSIBLE ENHANCEMENT CATEGORY.

●​ CAN BE ENHANCED (DEEP)

●​ CAN BE ENHANCED (CHARACTER-TYPE/ NUMERIC)
●​ CAN BE ENHANCED (CHARACTER TYPE)
●​ CANNOT BE ENHANCED
●​ NOT CLASSIFIED

RECORD CREATION INTO TABLE :

SE11>>TABLE NAME >> CHANGE >> UTILITIES >> TABLE OF CONTENTS >>
CREATE ENTRIES

​ ​ ​ ​ ​ (OR)

SE16>> TABLE NAME> CREATE ENTRIES(F5) >> ENTER INPUT VALUES >>
SAVE.
DISPLAYING TABLE CONTENTS:

IN DATABASE TABLE >> UTILITIES>> TABLE CONTENTS>> DISPLAY

>>EXECUTE BUTTON.

POINT TO REMEMBER :

SOMETIMES WE WILL GET UNAVOIDABLE ERRORS DURING ADDING OR

DELETING EXISTING RECORD, TO SOLVE THOSE ERROR , WE SHOULD NEED
TO USE DATABASE UTILITY (SE14)

SE14>> TABLE NAME>> EDIT>> ACTIVATE AND ADJUST DATABASE TABLE.

TABLE MAINTANENCE GENERATOR:

Table maintenance generator is a tool which generate table maintenance
program. Through table maintenance program we can maintain our custom
table. That means through this tool we can edit, add and delete the entries
from the custom table.

MAINTANENCE MEANS - CREATION,DELETION AND MODIFICATION.

(OR)
TO GIVE SM30 ACCESS FOR USERS FOR ENTERING THE MULTIPLE
VALUES AT A TIME.

STEPS:
●​ CREATE A DATABASE TABLE( MENTIONED IN CREATION OF TABLE)
●​ SAVE AND ACTIVATE
●​ ON TOP OF THE MENU BAR >> UTILITIES>> TABLE MAINTANENCE
GENERATOR.
●​ TABS INSIDE TMG:
○​ TECHNICAL DIALOG DETAILS
■​ AUTHORIZATION GROUP
■​ AUTHORIZATION OBJECT
■​ FUNCTION GROUP
■​ PACKAGE
○​ MAINTANENCE SCREEN
■​ MAINTANENCE TYPE
●​ ONE STEP
●​ TWO STEP
 ■​ MAINT. SCREEN NO
●​ OVERVIEW SCREEN
●​ SINGLE SCREEN
○​ DIALOG DATA TRANSPORT DETAILS:
■​ RECORDING ROUTINE
●​ STANDARD RECORDING ROUTINE
●​ NO ,OR USER , RECORDING ROUTINE
■​ COMPARE FLAG
●​ AUTOMATICALLY ADJUSTABLE
FOR THIS , SOME OF THE DETAILS SHOULD BE PROVIDED
MANDATORILY TO ACTIVATE TMG FOR OUR TABLE
​AUTHORIZATION GROUP - &NC&
​FUNCTION GROUP - TABLE NAME
​MAINTANENCE TYPE - ‘ONE STEP’
​CLICK ON ‘FIND SCREEN NUMBERS’ AT TOP TO DECLARE THE
SCREEN NUMBER.
​THUS THE SCREEN NUMBER WILL BE AUTOMATICALLY PROPOSED
​THEN CLICK ON CREATE ICON
​TMG WILL BE CREATED.

UNIT TESTING:
GOTO >> SM30>> TABLE NAME >>
MAINTAIN (IF AND ONLY IF YOU GIVEN IN TABLE AS MAINTANENCE
ALLOWED WITH SOME RESTRICTION IN DATA BROWSER/TABLE VIEW
MAINTANENCE)>>CLICK NEW ENTRIES>> SAVE.

POINTS TO REMEMBER:
➔​ DATABASE TABLE CAN BE TRANSPORTED TO NEXT LEVEL
WITHOUT THE ENTRIES (EMPTY TABLE).
➔​ IF WE WANT TO ADD ONE OR MORE FIELD TO THE TABLE >>
CHANGE>>ACTIVATE AND SAVE.
➔​ BUT IT DOES NOT EXIST IN THE TMG, SO REGENERATE TMG BY
DELETING AND SAVE AND ACTIVATE NEW TMG.

STRUCTURES:
➔​ Container of reusable fields
➔​ Structure holds empty fields
➔​ It holds data at run time only , but after execution it holds empty data.
➔​ Structure will not have technical attributes like table
 ➔​ Once the structure is created we must include them in table , there
are two ways of inserting structure in the table , they are:
◆​ Include structure
●​ Used only for customized table
●​ Reusable by multiple tables
●​ Field name = ‘.include’ and data element as structure
name.
◆​ Append structure
●​ Used in standard sap tables
●​ Not reusable
●​ Click on append structure in the table.

CREATION OF STRUCTURE:

SE11>> DATA TYPE >> STRUCTURE >> NAME >> CREATE , CONTINUE >>
SHORT DESCRIPTION.

TABS INSIDE STRUCTURE:

❖​ ATTRIBUTES
❖​ COMPONENTS
➢​ COMPONENT
➢​ TYPING METHOD
➢​ COMPONENT TYPE
➢​ DATA TYPE
➢​ LENGTH
➢​ DECIMAL
➢​ COORDINATE
➢​ SHORT DESCRIPTION
❖​ INPUT HELP/CHECK
➢​ COMPONENT
➢​ COMPONENT TYPE
➢​ DATA TYPE
➢​ FOREIGN KEYS
➢​ CHECK TABLE
➢​ ORIGIN OF INPUT HELP
➢​ SRCH HELP
➢​ FIXED VALUES
➢​ DOMAIN
❖​ CURRENCY/QUANTITY FIELDS
➢​ COMPONENT
➢​ TYPING METHOD
 ➢​ COMPONENT TYPE
➢​ DATA TYPE
➢​ REFERENCE TABLE
➢​ REFERENCE FIELD
➢​ SHORT DESCRIPTION

FOREIGN KEY RELATIONSHIP:

➔​ RELATIONSHIP BETWEEN TWO TABLES FOR VALIDATING THE

DATA IS CALLED FOREIGN KEY RELATION.
➔​ VALIDATION - CHECKING WHETHER THE VALUE IS CORRECT/NOT.
◆​ CHECK TABLE - STORES MASTER DATA IS CALLED A CHECK
TABLE
◆​ FOREIGN KEY TABLE - A TABLE LINKED WITH CHECK TABLE
FOR VALIDATING ITS OWN DATA IS CALLED FOREIGN KEY
TABLE.

STEPS :
●​ CREATION OF FOREIGN KEY FOR 2 TABLES WITH A COMMON
KEY FIELD :
●​ IN FOREIGN KEY TABLE >> CLICK THE FIELD AND CLICK ON
FOREIGN KEY ICON .
●​ PROVIDE THE CHECK TABLE AS THE MASTER DATA TABLE
●​ CLICK ON GENERATE PROPOSAL BUTTON
●​ CLICK ON COPY BUTTON SAVE AND ACTIVATE.

UNIT TESTING
●​ UTILITIES>> TABLE CONTENTS >> CREATE >> ENTER INVALID
CUSTOMER NUMBER >> SAVE.
●​ ERROR MESSAGE WILL BE DISPLAYED.

TABS IN FOREIGN KEY TABLE

Definition:​
Cardinality defines the relationship between two tables—how many
records in one table relate to records in another.

Format:​
<min..max>

●​ min: Minimum number of related records required.​

●​ max: Maximum number of related records possible.

VALUE TABLE:

●​ A TABLE NAME DEFINED AT THE DOMAIN LEVEL , SO THAT ALL

THE TABLE FIELDS WILL BE REFERRING TO THE DOMAIN WILL BE
CHECKED OR VALIDATED WITH A SINGLE TABLE CALLED AS
VALUE TABLE.
●​ It is a table which contains all valid entries of a domain, this domain can be
reused in multiple tables.
●​ ADVANTAGE - TO AUTOMATE THE SYSTEM FOR FOREIGN KEY
RELATION (system will automatically display check table name to
generate foreign key proposal)

Steps for creating value table:

➔​ After the creation of a table with some records, define the check table
(in foreign key ) name at domain level.

Difference between check table and value table :

●​ The check table will carry out the check for input values for the table field
being entered in any application and value table will provide values on F4
help for that table field.
●​ The check table defines the foreign keys and is part of the table definition.
●​ The value table is part of the domain definition.
●​ Check table is validation at field level.
●​ Value table provides value at the domain level.
●​ Value table is defined at the domain level and is used to provide F4 help for
all the fields which refer to that domain.
 ●​ Also while defining a check table SAP proposes the value table as check
table by default. Referring to the previous example if you tried to define a
check table for the MATNR field SAP would propose MARA as the check
table.

Indexes:

➔​ Improves the performance of the table and report.

➔​ types of Index
◆​ Primary Index -> Primary Key Will act as a Primary Index.
◆​ Secondary Index -> Based upon the requirement , We will
create secondary Indexes.
◆​ Disadvantage -> Index will occupy space on the database
Layer.
➔​ An Index name is 3 characters long.
➔​ Index will store like this - Table name~Index name( Example -
ZEMPTABLE~ABC , Where ZEMPTABLE is table name , ABC is Index
name).
➔​ Index for all database systems-> Index will be created on all the
databases.
➔​ Index for Selected database systems-> We can choose database,
where we want to create the index.
➔​ No database Index-> Index will remove from the database, It's
definition will be there.

Steps for creating index:

●​ se11>> database table>> table name>>display>> index tab>>
●​ Create index>> give table name, index name >> continue>>a popup
will be shown to ask about the language,
○​ maint.in origin lang
○​ maint.in logon lang
●​ Click maint.in logon lang .
●​ Short description>>click table fields>>
●​ Provide required fields,save and activate.

Points to remember:
We can able to edit the standard index , in old versions, we have to create
index at table level and database level
New version , the system itself able to create the indexes in database.
Types of tables:

Feature Transparent Pooled Table Cluster Table

Table

Definition 1:1 mapping Many small tables Multiple tables

with DB table stored together in a stored together in
single table pool a single table
cluster

Storage in Individual Stored logically in Stored logically in

DB physical table one pooled table one clustered table

Data Direct via Open Indirect (must use Indirect (must use
Access SQL SAP Open SQL) SAP Open SQL)

Performanc High for large Lower for large Efficient for

e data volumes volumes related, joined
reads

Used For Master & Customizing or Tables with

transactional system tables with dependent,
data (e.g., few entries (e.g., hierarchical data
MARA, EKKO) TST01) (e.g., BSEG)

Database Independent of SAP-specific, SAP-specific,

Dependenc DB platform DB-independent DB-independent
y implementation implementation

Can be Yes Yes Yes

Buffered

Example MARA, EKKO TST01, A018 BSEG, KOCLU

VIEWS:

●​ A DDIC view is a grouping of columns in one or more DDIC database

tables in accordance with an application-specific view
●​ View -> A view is virtual table.
●​ A view is a logical database.
●​ It does not have any data.
●​ Difference b/w table and View -> Table has data. View does not have
any data.
○​ Database view
■​ view is created by extracting the data from 2 or more
tables.
■​ Tables must have relationship between them.
■​ It is used for READ ONLY purpose.
■​ When database view is created using single table, we can
UPDATE the data in it. (Similar to Projection View)
■​ STEPS
●​ SE11>> VIEW>>NAME &CREATE>>DATABASE
VIEW OPTION>>COPY>>SHORT DESCRIPTION>> IN
TABLE/JOIN CONDITION TAB ENTER THE TABLES
TO BE VIEWED>>CLICK RELATIONSHIP>>SELECT
REQUIRED JOIN CONDITIONS>> CLICK COPY>> IN
VIEW FIELDS TAB CLICK TABLE FIELDS
●​ DOUBLE CLICK ANY TABLE , SELECT REQUIRED
FIELDS TO VIEW>> CLICK COPY
●​ IN SELECTION CONDITIONS TAB , ENTER THE
CONDITIONS IF REQUIRED.
●​ SAVE AND ACTIVATE.
●​ TMG WILL NOT BE POSSIBLE IN DATBASE VIEW ,
IF WE WANT TO VIEW THE DATA , CLICK
CONTENTS /SE16.
○​ Projection view – this view is created by extracting the data
from the same table.
■​ Give the name of the table in BASE TABLE. And specify
the TABLE FIELDS.
■​ This is used for READ ONLY and READ and CHANGE
(Adding the data) purpose.
○​ Maintenance view – to maintain 1 or more tables. Tables must
be related.
■​ If we want to maintain 4 or 5 tables, we normally generate
TMG for those tables individually and do the maintenance
separately.
■​ But through the Maintenance view, those tables can be
taken together to do the maintenance. Meaning, READ,
CHANGE, DELETE and INSERT are possible.
■​ Note: MANDT field has to be included on the Maintenance
view. And the relationship between the tables must be 1
 to 1.
○​ Help view – it is used in search helps.
■​ Tables must be related.
■​ Similar to Maintenance view, the relationship between the
tables must be 1 to 1.
■​ The contents tab will not be displayed in HELP VIEW. This
is done for READ ONLY purpose.
SEARCH HELP:
➔​ OBJECTS USED TO PROVIDE INPUT HELP(F4) FOR SCREEN FIELDS
◆​ TYPES
●​ ELEMENTARY SEARCH HELP
○​ Create the search help in SE11 and you can use it in
SE38 using the addition MATCH CODE OBJECT in
PARAMETERS
○​ Create a DOMAIN & DATA ELEMENT and attach the
search help to it. And give this data element name
as TYPE in the PARAMETERS.
●​ COLLECTIVE SEARCH HELP
○​ It can be created by combining elementary search
helps.
○​ Give the name of the search helps one by one.
These search helps are added as tabs in the F4 help
in the program.
○​ Hot Key- used to access the different tabs by using
the HOT KEY. For example, if the 1st search help has
the HOT KEY value as A and the 2nd as B and so on.
Meaning, the HOT KEY is used to prioritize the
displaying of the TAB ORDER.
○​ FOR eg.,Typing =B in the PARAMETERS field in the
program will show the 2nd TAB directly

●​ STEPS : SE11>> SEARCH HELP>> NAME &

CREATE>>ELEMENTARY SEARCH
HELP>>CONTINUE>>SHORT DESCRIPTION>> ENTER
TABLE/VIEW NAME INSIDE ‘SELECTION
METHOD’>>ENTER REQUIRED FIELDS.
○​ IMPORT - TO DISPLAY FIELDS IN THE SCREEN
○​ EXPORT - TO DISPLAY FIELD VALUES AT OUTPUT.
○​ LPOS &SPOS - POSITION OF SEARCH FIELDS.
 ○​ SAVE AND ACTIVATE.
●​ AFTER CREATION WE CAN ADD THEM IN DATA
ELEMENT OR IN THE PROGRAM USING MATCHCODE
OBJECT.

LOCK OBJECTS:

➔​ If the same data is accessed by multiple users at the same time, we

need to lock the data in order to maintain synchronization.
➔​ For example, if 2 users trying to access the same record/data, who
has got the access first, the lock is done for that user. The other user
will get access only after the first user releases the lock.
➔​ SM12 is the TCODEà to display the lock entries.
➔​ start with ‘E’. So the lock object must be of ‘EZ…..’ or ‘EY…..’
➔​ types of lock modes
◆​ Read lock (Shared lock)
●​ Its default value is ‘S’. Read is possible but not Write by
other users.
◆​ Write lock (Exclusive lock)
●​ Its default value is ‘E’. Read and Write not possible by
other users. Write access will be grant to the user who
keeps trying to access the record several times when the
object is on LOCK condition.
◆​ Enhanced write lock (Exclusive but not cumulative) -
●​ Its default value is ‘X’. Read and Write not possible. It
prevents the further access from the same transaction.
When we create a lock object, 2 function modules are created by SAP;
1. ENQUEUE →ENQUEUE_lockobjectname →locking the object
2. DEQUEUE→DEQUEUE_lockobjectname→release or unlock the object

STEPS:

SE38>> CALL THE FUNCTION MODULES

➔​ ENQUEUE - TO LOCK THE OBJECT

➔​ DEQUEUE - TO UNLOCK THE OBJECT

LOCK OTHER DEFAULT READ WRITE

NAME VALUE
READ LOCK SHARED S YES NO
LOCK

WRITE LOCK EXCLUSIVE E NO NO

LOCK

ENHANCED EXCLUSIVE X NO NO
LOCK BUT NOT
CUMILATIVE

SUMMARY:
​ ​ 1) Read Lock( Shared Lock , S) - Others user can view the data,
but can not changed the data.
​ 2) Write Lock( Exclusive lock , E) - Others user can not view the
data and can not changed the data.
​ 3) Enhanced Write Lock( Exclusive lock without cumulation,X) -
Others user can not view the data and can not changed the data + It protect
the further access for the same transaction.

TYPE GROUP:
●​ A type group, also known as a type pool, is a way to
define reusable data types, constants, and macros
in a single, centrally managed location.
●​ These definitions, created using the TYPE-POOL
statement, can then be included in multiple ABAP
programs using the TYPE-POOLS statement,
promoting code reuse and consistency.