
- •Icons in Body Text
- •Introduction to the Dictionary
- •Overview of the functions
- •Data objects in the ABAP Dictionary
- •Data types
- •Exercise 1: Basic Data Types
- •Exercise 2: Simple and Nested Structures
- •Exercise 4: Deep Structures
- •Tables
- •Summary
- •Exercise 5: Tables in the ABAP Dictionary
- •Pooled and cluster tables
- •Performance During Table Access
- •Improved Performance through Access per Index
- •Improving the Performance through Table Buffering
- •Exercise 6: Performance Aspects with Table Access
- •Task 1:
- •Input Checks
- •Input check via the technical domains
- •Object Dependencies
- •Activation and Where-Used List
- •Changes to Tables
- •Database Changes to Transparent Tables
- •Enhancement of SAP Standard Tables
- •Exercise 9: Changes to Database Tables
- •Views and Maintenance Views
- •Restricted or Enhanced Views on Database Tables
- •Exercise 11: Views
- •Creating Maintenance Views
- •Exercise 12: Maintenance Views
- •Search Helps
- •Input helps
- •Exercise 13: Search Helps
- •Table ZEMPLOY##
- •Table ZDEPMENT##
- •Table ZEMPLOY##
- •Table ZEMPLOY##
- •Table ZDEPMENT##
- •Table ZDEPMENT##
- •Check table T000
- •Check table SCARR
- •Check table ZDEPMENT##
- •Check table SCURX
- •Check table STRAVELAG
- •Check table ZDEPMENT##
- •Check table T002

BC430 |
Lesson: Tables in the ABAP Dictionary |
Summary
•All the business-oriented data is administered in the form of tables whose definition is stored in the ABAP Dictionary.
•A two-level domain concept is used for defining the tables. The semantic definition is implemented with data elements and the technical definition with domains.
•The fields of include structures can be included in tables.
•The technical settings of a table define how the table should be stored in the database (tablespace, extent size) and whether changes to the data records should be logged.
2006/Q2 |
© 2007 SAP AG. All rights reserved. |
55 |

Unit 2: Data objects in the ABAP Dictionary |
BC430 |
56 |
© 2007 SAP AG. All rights reserved. |
2006/Q2 |

BC430 |
Lesson: Tables in the ABAP Dictionary |
Exercise 5: Tables in the ABAP Dictionary
Exercise Objectives
After completing this exercise, you will be able to:
•Create tables and use the two-level domain concept
•Define the technical settings sensibly
•Document fields
•Create and use include structures
Business Example
In these exercises, the tables of the flight model will be enhanced with employee management. This employee management enables the airlines to enter and evaluate data about their employees (for example, name, personnel number, salary, department, etc.) and about assignments within the organization (airline departments).
In this exercise, two tables will be created for the employee data and the airline departments.
The data for the employees is maintained in the ZEMPLOY## table. The names and addresses of the employees and their salaries are stored in the ZEMPLOY## table. The ZDEPMENT## table contains the departments of the airline. Each department can be reached with a telephone and fax number. These tables will be enhanced step-by-step in the following exercises.
Task 1:
Create the two transparent tables ZEMPLOY## and ZDEPMENT##. Define their key fields.
Note: Before you can activate the tables, you still have to define their technical settings. The procedure is described in the last tasks for the exercises. The first tasks can also be solved without activating the table.
Data is maintained for three airlines. An airline has 20,000 employees and between 10 and 30 departments. Do not buffer or log the data. Buffering will be discussed in the exercises for the next unit.
1.Create table ZEMPLOY##.
Via the path Tools → ABAP Workbench → Development → ABAP Dictionary, you come to the overview screen of the ABAP Dictionary.
Continued on next page
2006/Q2 |
© 2007 SAP AG. All rights reserved. |
57 |