TXI_TIV39 SAP (Reason for notice) Structure details
Description: Reason for notice
Structure field list including key, data, relationships and ABAP select examples
TXI_TIV39 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 "Reason for notice" 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_TXI_TIV39 TYPE TXI_TIV39.
The TXI_TIV39 table consists of various fields, each holding specific information or linking keys about Reason for notice data available in SAP. These include MANDT (Client), RKUEGRU (Reason for notice), SKUEART (Notice Type).. 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 TXI_TIV39 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 | |||
RKUEGRU | Reason for notice | RKUEGRU | NUMC | 2 | Assigned to domain | RKUEGRU | |||
SKUEART | Notice Type | SKUAR | CHAR | 1 | SKUAR |
Key field | Non-key field |
How do I retrieve data from SAP structure TXI_TIV39 using ABAP code?
As TXI_TIV39 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 TXI_TIV39 as there is no data to select.How to access SAP table TXI_TIV39
Within an ECC or HANA version of SAP you can also view further information about TXI_TIV39 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