LEMOBBUTTON SAP (Additional push button for mobile computing - GR/GI) Structure details
Description: Additional push button for mobile computing - GR/GI
Structure field list including key, data, relationships and ABAP select examples
LEMOBBUTTON 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 "Additional push button for mobile computing - GR/GI" 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_LEMOBBUTTON TYPE LEMOBBUTTON.
The LEMOBBUTTON table consists of various fields, each holding specific information or linking keys about Additional push button for mobile computing - GR/GI data available in SAP. These include RGTO (Pushbutton: Generate TO), RDELIT (Pushbutton: Display Delivery Item screen), RSHIP (Pushbutton: Shipment), RDIFF (Pushbutton: Differences in GR/GI transactions).. 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 LEMOBBUTTON 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 |
| RPOST | Pushbutton: Inventory menu - Posting change | MOBPOST | CHAR | 1 | LVS_DOKU | ||||
| RGTO | Pushbutton: Generate TO | MOBGTO | CHAR | 1 | LVS_DOKU | ||||
| RDELIT | Pushbutton: Display Delivery Item screen | MOBDELITEM | CHAR | 1 | LVS_DOKU | ||||
| RSHIP | Pushbutton: Shipment | MOBSHIP | CHAR | 1 | LVS_DOKU | ||||
| RDIFF | Pushbutton: Differences in GR/GI transactions | MOBDIF | CHAR | 1 | LVS_DOKU | ||||
| RSPLIT | Pushbutton: Split Delivery | MOBSPLIT | CHAR | 1 | LVS_DOKU | ||||
| RSEL | Pushbutton: Select from List | MOBSEL | CHAR | 1 | LVS_DOKU | ||||
| RCHECK | Pushbutton: Checking the differences in GR/GI transactions | MOBCHEC | CHAR | 1 | LVS_DOKU | ||||
| RPACK | Pushbutton: Packing from Delivery Header screen | MOBPACK | CHAR | 1 | LVS_DOKU | ||||
| RPICK | Pushbutton: Picking System-Guided | MOBPICKSYS | CHAR | 1 | LVS_DOKU | ||||
| RMORE | Pushbutton: More | MOBMORE | CHAR | 1 | LVS_DOKU | ||||
| RUNPACK | Pushbutton: Unpack from Delivery Header screen | MOBUPACK | CHAR | 1 | LVS_DOKU |
| Key field | Non-key field |
How do I retrieve data from SAP structure LEMOBBUTTON using ABAP code?
As LEMOBBUTTON 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 LEMOBBUTTON as there is no data to select.How to access SAP table LEMOBBUTTON
Within an ECC or HANA version of SAP you can also view further information about LEMOBBUTTON 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