LEINT_LTBK SAP (Planning interface to TR header) Structure details
Description: Planning interface to TR header
Structure field list including key, data, relationships and ABAP select examples
LEINT_LTBK 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 "Planning interface to TR header" 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_LEINT_LTBK TYPE LEINT_LTBK.
The LEINT_LTBK table consists of various fields, each holding specific information or linking keys about Planning interface to TR header data available in SAP. These include MANDT (Client), LGNUM (Warehouse Number / Warehouse Complex), TBNUM (Transfer Requirement Number), STATU (Header Status of Transfer Requirement).. 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 or numeric)
SAP LEINT_LTBK 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 | |||
LGNUM | Warehouse Number / Warehouse Complex | LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
TBNUM | Transfer Requirement Number | TBNUM | NUMC | 10 | Assigned to domain | TBNUM | TBN | ||
STATU | Header Status of Transfer Requirement | LTBK_STATU | CHAR | 1 | LTBK_STATU | ||||
TRART | Shipment Type | LVS_TRART | CHAR | 1 | T333A | LVS_TRART | H_T333A | ||
TBPRI | Transfer Priority | TBPRI | CHAR | 1 | TBPRI | ||||
BNAME | User Name | LVS_BNAME | CHAR | 12 | USNAM | ||||
BDATU | Creation Date of Transfer Request | LTBK_BDATU | DATS | 8 | DATUM | ||||
BZEIT | Creation time of transfer request | LTBK_BZEIT | TIMS | 6 | UZEIT | ||||
TBKTX | Header Text of Transfer Requirement | LTBK_TBKTX | CHAR | 40 | TEXT40 | ||||
BETYP | Requirement Type | LVS_BETYP | CHAR | 1 | T308 | LVS_BETYP | |||
BENUM | Requirement Number | LVS_BENUM | CHAR | 10 | ALPHA | LVS_BENUM | |||
BWART | Movement Type (Inventory Management) | BWART | CHAR | 3 | T156 | BWART | BWA | ||
BWLVS | Movement Type for Warehouse Management | BWLVS | NUMC | 3 | T333 | BWLVS | BWL | ||
VLTYP | Source Storage Type | T333_VLTYP | CHAR | 3 | T301 | LGTYP | |||
VLPLA | Source storage bin | T333_VLPLA | CHAR | 10 | Assigned to domain | LGPLA | |||
VKDYN | Indicator: dynamic source bin | T333_VKDYN | CHAR | 1 | XFELD | ||||
NLTYP | Destination Storage Type | T333_NLTYP | CHAR | 3 | T301 | LGTYP | |||
NLPLA | Destination Storage Bin | T333_NLPLA | CHAR | 10 | Assigned to domain | LGPLA | |||
NKDYN | Indicator: dynamic destination bin | T333_NKDYN | CHAR | 1 | XFELD | ||||
PDATU | Date of Planned Execution of Transfer Request | LTBK_PDATU | DATS | 8 | DATUM | ||||
PZEIT | Time of Planned Execution of Transfer Requirement | LTBK_PZEIT | TIMS | 6 | UZEIT | ||||
MBLNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
MJAHR | Material Document Year | MJAHR | NUMC | 4 | GJAHR | GJAHR | MJA | ||
ANZPS | Number of Transfer Requirement Items | LTBK_ANZPS | DEC | 4 | LTBK_ANZPS | ||||
BRGEW | Total Weight of Transfer Request | LTBK_BRGEW | DEC | 11(3) | DEC8_3 | ||||
GEWEI | Weight Unit | GEWEI | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
KLFR2 | Indicator: Delivery document from superior system (R/2) | LTBK_KLFR2 | CHAR | 1 | XFELD | ||||
KFAR2 | Indicator: Production order from superior system (R/2) | LTBK_KFAR2 | CHAR | 1 | XFELD | ||||
TBRUE | Indicator: confirm transfer requriement | LTBK_TBRUE | CHAR | 1 | LTBK_TBRUE | ||||
RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
LZNUM | Additional Reference Number for Transport | LVS_LZNUM | CHAR | 20 | LVS_LZNUM | ||||
AUTTA | Automatic Transfer Order Creation | LVS_AUTTA | CHAR | 1 | T333N | AUTTA | |||
BDART | Requirement type | BDART | CHAR | 2 | BDART | BDA | |||
PKNUM | Control cycle number | PKNUM | CHAR | 7 | Assigned to domain | ALPHA | PKNUM | PKNUM | |
PKPOS | Kanban item number / control cycle item | PKPOS | NUMC | 3 | PKPOS | ||||
DIRTA | Automatic TO Creation Immediately After TR Generation | LVS_DIRTA | CHAR | 1 | XFELD | ||||
KBNKZ | Kanban Indicator | KBNKZ | CHAR | 1 | KBNKZ |
Key field | Non-key field |
How do I retrieve data from SAP structure LEINT_LTBK using ABAP code?
As LEINT_LTBK 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 LEINT_LTBK as there is no data to select.How to access SAP table LEINT_LTBK
Within an ECC or HANA version of SAP you can also view further information about LEINT_LTBK 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