SRETIDLACS SAP (Index Category Language - Special Form for Administration) Structure details
Description: Index Category Language - Special Form for Administration
Structure field list including key, data, relationships and ABAP select examples
SRETIDLACS 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 "Index Category Language - Special Form for Administration" 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_SRETIDLACS TYPE SRETIDLACS.
The SRETIDLACS table consists of various fields, each holding specific information or linking keys about Index Category Language - Special Form for Administration data available in SAP. These include CLIENT (Client), CATID (Index category identification), LANGU (Language Key Acc. SAP Norm (1 character)), LAISO (2-Character SAP Language Code).. 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: Not classified
SAP SRETIDLACS 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 |
CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
CATID | Index category identification | SRET_CATID | CHAR | 32 | SRETIDCAT | SRET_CATID | H_SRETIDCAT | ||
LANGU | Language Key Acc. SAP Norm (1 character) | SRET_LANGU | CHAR | 1 | Assigned to domain | SRET_LANGU | |||
LAISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
NUMDOC | Planned No. of Documents for a Language | SRET_NUDOC | NUMC | 12 | SRET_NUDOC | ||||
AVGDOCSIZ | Average Document Size in KB | SRET_AVGDS | CHAR | 10 | SRET_AVGDS | ||||
IDXCOUNT | Counter for indexed/de-indexed documents | SRET_IDCNT | CHAR | 12 | SRET_IDCNT | ||||
CREA_USER | User who created the language for a category | SRET_CRELA | CHAR | 12 | SRET_USER | ||||
CRTIME | Language creation time (date - time) acc. to UTC | SRET_CRLTI | NUMC | 14 | SYTSTP | ||||
CHNG_USER | Language last changed by | SRET_CHGLA | CHAR | 12 | SRET_USER | ||||
CHTIME | Last time of change date - time (UTC) | SRET_CHLTI | NUMC | 14 | SYTSTP | ||||
TTIME | Transport (time stamp) | SRET_TTIME | NUMC | 14 | SYTSTP | ||||
TFLAG | Transport flag (import flag) | SRET_TFLAG | CHAR | 1 | SRET_FLAG1 | ||||
PYINS | Indicates whether a physical index is to be imported | SRET_PYINS | CHAR | 1 | SRET_FLAG1 | ||||
INDEXDEL | Indicates that the Index is To Be Deleted | SRET_IDXDE | CHAR | 1 | SRET_FLAG1 | ||||
HASINDEX | Indicates Whether a Physical Index Exists | SRET_HASIX | CHAR | 1 | SRET_FLAG | ||||
TRORDER | Transport request | SRET_TRORD | CHAR | 20 | SRET_TRORD | ||||
CTIME | Time stamp of export for checking against index | SRET_CTIME | NUMC | 14 | SYTSTP | ||||
ITIME | Time stamp for export of physical index | SRET_ITIME | NUMC | 14 | SYTSTP | ||||
IMPORT | Indicates whether the index was imported | SRET_IMPFL | CHAR | 1 | SRET_FLAG1 | ||||
NEEDCCPY | Shows if the Index is Copied to a Client Copy | SRET_NDCCP | CHAR | 3 | SRET_FLAG3 | ||||
SCLT | Special field of client for display and administration | SRET_SCLT | CHAR | 3 | SRET_SCLT |
Key field | Non-key field |
How do I retrieve data from SAP structure SRETIDLACS using ABAP code?
As SRETIDLACS 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 SRETIDLACS as there is no data to select.How to access SAP table SRETIDLACS
Within an ECC or HANA version of SAP you can also view further information about SRETIDLACS 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