COM_SEARCH_TS_OBJECT_TYPE_CUST SAP (Structure with All Customizing Settings for Object Type) Structure details
Description: Structure with All Customizing Settings for Object Type
Related tables to COM_SEARCH_TS_OBJECT_TYPE_CUST
Access table COM_SEARCH_TS_OBJECT_TYPE_CUST
Structure field list including key, data, relationships and ABAP select examples
COM_SEARCH_TS_OBJECT_TYPE_CUST is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Structure with All Customizing Settings for Object Type" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_COM_SEARCH_TS_OBJECT_TYPE_CUST TYPE COM_SEARCH_TS_OBJECT_TYPE_CUST.
The COM_SEARCH_TS_OBJECT_TYPE_CUST table consists of various fields, each holding specific information or linking keys about Structure with All Customizing Settings for Object Type data available in SAP. These include MANDT (Client), BUSOBJ (Business Object for Search Engine Service (SES)), OBJECT_TYPE (Type of Business Object), INDEX_ACTIVE (Index is Active).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP COM_SEARCH_TS_OBJECT_TYPE_CUST structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| BUSOBJ | Business Object for Search Engine Service (SES) | COM_SEARCH_TV_BUSOBJ | CHAR | 10 | COM_SE_BUSOBJ | COM_SEARCH_BUSOBJ | |||
| OBJECT_TYPE | Type of Business Object | COM_SEARCH_TV_OBJECT_TYPE | CHAR | 10 | Assigned to domain | COM_SEARCH_OBJECT_TYPE | |||
| INDEX_ACTIVE | Index is Active | COM_SEARCH_TV_INDEX_ACTIVE | CHAR | 1 | BOOLE | ||||
| INDEX_ACTIVE_REL | Relation Index is Active | COM_SEARCH_TV_INDEX_ACTIVE_REL | CHAR | 1 | BOOLE | ||||
| INDEX_ID | Object Index ID in the Search Engine | COM_SEARCH_TV_INDEX_ID | CHAR | 64 | TREXD_INDEX_ID | ||||
| INDEX_PRIO | Priority at Indexing (Max = 0; Min = 999) | COM_SEARCH_TV_INDEX_PRIO | NUMC | 3 | |||||
| MAX_INDEXG_TASKS | Maximum Number of Parallel Tasks for Indexing | COM_SEARCH_TV_MAX_INDEXG_TASKS | INT4 | 10 | |||||
| UPD_PACK_SIZE | Maximum Number of Objects Per Index Update Package | COM_SEARCH_TV_UPD_PACK_SIZE | INT4 | 10 | |||||
| LOGLEVEL | Level of Detail of Spool List at Delta Indexing | COM_SEARCH_TV_LOGLEVEL | CHAR | 1 | COM_SEARCH_LOGLEVEL | ||||
| MULTILANGUAGE | Index Contains Multilingual Objects | COM_SEARCH_TV_MULTILANGUAGE | CHAR | 1 | BOOLE | ||||
| KEYMAPPING | Key Mapping is indexed | COM_SEARCH_TV_KEYMAPPING | CHAR | 1 | BOOLE | ||||
| RELATIONS | Indexing Relations | COM_SEARCH_TV_RELATIONS | CHAR | 1 | BOOLE | ||||
| INDEX_ID_REL | Relation Index ID in the Search Engine | COM_SEARCH_TV_INDEX_ID_REL | CHAR | 64 | TREXD_INDEX_ID | ||||
| INDEX_ID_JOIN | Join Index ID in the Search Engine | COM_SEARCH_TV_INDEX_ID_JOIN | CHAR | 64 | TREXD_INDEX_ID | ||||
| FAST_UPDATE | Flag: Fast Delta Update | COM_SEARCH_TV_FAST_UPDATE | CHAR | 1 | BOOLE | ||||
| COMMON_RUNTIME | Use Embedded Search | COM_SEARCH_TV_COMMON_RUNTIME | CHAR | 1 | BOOLE | ||||
| RFC_DESTINATION | Logical Destination (Specified in Function Call) | RFCDEST | CHAR | 32 | Assigned to domain | RFCDEST | RFC | F4_RFCDESTYPEALL | |
| OBJ_CLASS_NAME | Name of ABAP Class for Business Object | COM_SEARCH_TV_OBJ_CLASS_NAME | CHAR | 30 | SEOCLSNAME |
| Key field | Non-key field |
How do I retrieve data from SAP structure COM_SEARCH_TS_OBJECT_TYPE_CUST using ABAP code?
As COM_SEARCH_TS_OBJECT_TYPE_CUST is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on COM_SEARCH_TS_OBJECT_TYPE_CUST as there is no data to select.How to access SAP table COM_SEARCH_TS_OBJECT_TYPE_CUST
Within an ECC or HANA version of SAP you can also view further information about COM_SEARCH_TS_OBJECT_TYPE_CUST and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects