TXI_OIHSLO SAP (TDP (excise duty) special ledger object table) Structure details
Description: TDP (excise duty) special ledger object table
Structure field list including key, data, relationships and ABAP select examples
TXI_OIHSLO 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 "TDP (excise duty) special ledger object table" 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_OIHSLO TYPE TXI_OIHSLO.
The TXI_OIHSLO table consists of various fields, each holding specific information or linking keys about TDP (excise duty) special ledger object table data available in SAP. These include MANDT (Client), OBJNR (Object number for FI-SL tables), DATIV (Posting date frm which the objct is valid for act.postings), DATIB (Posting date up to which the object is valid for act.postngs).. 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: Can be enhanced (character-type)
SAP TXI_OIHSLO 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 | T000 | MANDT | |||
| OBJNR | Object number for FI-SL tables | GOBJNR | CHAR | 18 | OBJNR | ||||
| DATIV | Posting date frm which the objct is valid for act.postings | DAT_0_VON | DATS | 8 | DATUM | ||||
| DATIB | Posting date up to which the object is valid for act.postngs | DAT_0_BIS | DATS | 8 | DATUM | ||||
| DATPV | Posting date frm which the objct is valid for plan postings | DAT_1_VON | DATS | 8 | DATUM | ||||
| DATPB | Posting date up to which the objct is valid for plan postngs | DAT_1_BIS | DATS | 8 | DATUM | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
| BWTAR | Valuation Type | BWTAR_D | CHAR | 10 | T149D | BWTAR | BWT | ||
| OITAXGRP | Excise Duty Group | OIH_TAXGRP | CHAR | 2 | OIH2 | OIH_TAXGRP | |||
| OIHANTYP | Excise Duty Handling Type | OIH_HANTYP | CHAR | 2 | OIH5 | OIH_HANTYP | |||
| OITAXFRO | Excise duty tax key for 'from' location | OIH_TAXFRO | CHAR | 2 | OIH4 | OIH_TAXKEY | |||
| OITAXTO | Excise duty tax key for 'to' location | OIH_TAXTO | CHAR | 2 | OIH4 | OIH_TAXKEY | |||
| ACCT | Account Number | RACCT | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ACC | |
| BUSA | Business Area | GSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
| CNTR | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS |
| Key field | Non-key field |
How do I retrieve data from SAP structure TXI_OIHSLO using ABAP code?
As TXI_OIHSLO 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_OIHSLO as there is no data to select.How to access SAP table TXI_OIHSLO
Within an ECC or HANA version of SAP you can also view further information about TXI_OIHSLO 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