- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
44 Indexes on DB tables and TYPE GROUP
In the SAP ABAP Dictionary (DDIC), database indexes are dedicated sorted data structures that act as a copy of selected table fields to drastically reduce query processing times during SELECT operations. Instead of performing a sequential, full-table scan, the database utilizes binary searches via the index to pinpoint physical pointers to the actual table entries.
Types of Database Indexes
Primary Index: Automatically created by the system when a table is activated. It contains all the primary key fields of the table, ensures data uniqueness, and cannot be deleted.
Secondary Index: Created manually by developers or partners to optimize queries based on non-primary key fields (e.g., searching sales orders by creation date rather than order number).
Extension Index: A secondary index created by customers or partners on standard SAP-delivered tables without modifying the original SAP definition.
Specialized Indexes (SAP HANA): Modern SAP HANA architectures utilize default Inverted Value indexes for column store tables, and support specialized Full-Text or Fuzzy Search indexes for advanced text mining capabilities.
Creating and Managing Indexes in SE11.
You can manage indexes centrally via the ABAP Dictionary using transaction code SE11.
Enter your table name in SE11 and choose Display.
Click the Indexes... button on the application toolbar.
Choose Create and assign a 3-character Index ID.
Provide a descriptive short text.
Click Table Fields to select and transfer the columns you wish to index.
Specify whether the index is Unique or Non-Unique.
Save, check, and Activate the index to physically build it on the underlying database system.
Naming Conventions and Namespaces
Index identifiers in SAP are always 3 characters long. At the database layer, they are formatted as DBTAB~ID (e.g., VBAK~KUN for a customer index on sales orders).
Customer Indexes: IDs must start with Y or Z when added to standard SAP tables.
Partner Indexes: IDs must start with J.
Extension Indexes: Created when adding secondary indexes to delivered SAP tables without modifying the original object.
Видео 44 Indexes on DB tables and TYPE GROUP канала Ranjit V
Types of Database Indexes
Primary Index: Automatically created by the system when a table is activated. It contains all the primary key fields of the table, ensures data uniqueness, and cannot be deleted.
Secondary Index: Created manually by developers or partners to optimize queries based on non-primary key fields (e.g., searching sales orders by creation date rather than order number).
Extension Index: A secondary index created by customers or partners on standard SAP-delivered tables without modifying the original SAP definition.
Specialized Indexes (SAP HANA): Modern SAP HANA architectures utilize default Inverted Value indexes for column store tables, and support specialized Full-Text or Fuzzy Search indexes for advanced text mining capabilities.
Creating and Managing Indexes in SE11.
You can manage indexes centrally via the ABAP Dictionary using transaction code SE11.
Enter your table name in SE11 and choose Display.
Click the Indexes... button on the application toolbar.
Choose Create and assign a 3-character Index ID.
Provide a descriptive short text.
Click Table Fields to select and transfer the columns you wish to index.
Specify whether the index is Unique or Non-Unique.
Save, check, and Activate the index to physically build it on the underlying database system.
Naming Conventions and Namespaces
Index identifiers in SAP are always 3 characters long. At the database layer, they are formatted as DBTAB~ID (e.g., VBAK~KUN for a customer index on sales orders).
Customer Indexes: IDs must start with Y or Z when added to standard SAP tables.
Partner Indexes: IDs must start with J.
Extension Indexes: Created when adding secondary indexes to delivered SAP tables without modifying the original object.
Видео 44 Indexes on DB tables and TYPE GROUP канала Ranjit V
Комментарии отсутствуют
Информация о видео
Вчера, 9:00:34
00:46:50
Другие видео канала




















