LXDCKM_LDOCV_ALERT SAP (Logistic document view alert structure) Structure details
Description: Logistic document view alert structure
Related tables to LXDCKM_LDOCV_ALERT
Access table LXDCKM_LDOCV_ALERT
Structure field list including key, data, relationships and ABAP select examples
LXDCKM_LDOCV_ALERT 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 "Logistic document view alert structure" 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_LXDCKM_LDOCV_ALERT TYPE LXDCKM_LDOCV_ALERT.
The LXDCKM_LDOCV_ALERT table consists of various fields, each holding specific information or linking keys about Logistic document view alert structure data available in SAP. These include LGNUM (Warehouse Number), DOCTY (Reference Document Type), DOCNR (Reference Document), DOCPR (Reference Document Priority).. 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 LXDCKM_LDOCV_ALERT 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 |
LIGHTS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
LGNUM | Warehouse Number | LEINT_LGNUM | CHAR | 3 | Assigned to domain | LGNUM | LGN | H_T300 | |
DOCTY | Reference Document Type | LXHME_DOCTY | CHAR | 2 | LXHME_DOCTY | ||||
DOCNR | Reference Document | LEINT_DOCNR | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
DOCPR | Reference Document Priority | LXHME_DOCPR | NUMC | 2 | NUMC2 | ||||
TKNUM | Shipment Number | TKNUM | CHAR | 10 | Assigned to domain | ALPHA | TKNUM | TNR | SD_F4_SHP_ID |
XPLDT | Time Reference for Cross-Dock Planning | LXDCK_XPLDT | DEC | 15 | TSHME | LXHME_TSTMP | |||
RLSDT | Release Time | LXHME_RLSDT | DEC | 15 | TSHME | LXHME_TSTMP | |||
MTCDT | Matching Date & Time | LXHME_MTCDT | DEC | 15 | TSHME | LXHME_TSTMP | |||
KODAT | Picking Date | LXHME_KODAT | DEC | 15 | TSHME | LXHME_TSTMP | |||
LDDAT | Loading Date | LXHME_LDDAT | DEC | 15 | TSHME | LXHME_TSTMP | |||
TDDAT | Transportation Planning Date | LXHME_TDDAT | DEC | 15 | TSHME | LXHME_TSTMP | |||
WADAT | Planned Goods Movement Date | LXHME_WADAK | DEC | 15 | TSHME | LXHME_TSTMP | |||
LFDAT | Delivery Date | LXHME_LFDAT | DEC | 15 | TSHME | LXHME_TSTMP | |||
VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
VTWIV | Distribution channel for intercompany billing | VTWIV | CHAR | 2 | Assigned to domain | VTWEG | VTW | ||
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
PRVBE | Production Supply Area | PRVBE | CHAR | 10 | Assigned to domain | PRVBE | PVB | ||
TERNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
KUNAG | Sold-to party | KUNAG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | |
KUNNR | Ship-to party | KUNWE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
KDGRP | Customer group | KDGRP | CHAR | 2 | Assigned to domain | KDGRP | VKD | ||
AULWE | Route Schedule | AULWE | CHAR | 10 | Assigned to domain | AULWE | |||
LSTEL | Loading Point | LSTEL | CHAR | 2 | Assigned to domain | LSTEL | |||
ABLAD | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
VSART | Shipping type | VSARTTR | CHAR | 2 | Assigned to domain | VERSART | |||
GMSTS | Overall status of warehouse management activities | LXHME_LVSTK | CHAR | 1 | LXHME_STATV | ||||
VSBED | Shipping Conditions | VSBED | CHAR | 2 | Assigned to domain | VSBED | |||
LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
LIFEX | External Identification of Delivery Note | LIFEX | CHAR | 35 | TEXT35 | ||||
BENUM | Requirement Number | LVS_BENUM | CHAR | 10 | ALPHA | LVS_BENUM | |||
LZNUM | Additional Reference Number for Transport | LVS_LZNUM | CHAR | 20 | LVS_LZNUM | ||||
TRAID | Means of Transport ID | TRAID | CHAR | 20 | TRAID | ||||
ITEMS | Number of Document Items | LXHME_ITEMS | NUMC | 4 | NUMC4 | ||||
GRPNR | Group | SAMMG | CHAR | 10 | Assigned to domain | ALPHA | SAMMG | GRN | |
IMWRK | Delivery has Status 'In Plant' | IMWRK | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure LXDCKM_LDOCV_ALERT using ABAP code?
As LXDCKM_LDOCV_ALERT 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 LXDCKM_LDOCV_ALERT as there is no data to select.How to access SAP table LXDCKM_LDOCV_ALERT
Within an ECC or HANA version of SAP you can also view further information about LXDCKM_LDOCV_ALERT 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