RQMHU SAP (QM: Prepared Handling Unit Information) Structure details
Description: QM: Prepared Handling Unit Information
Structure field list including key, data, relationships and ABAP select examples
RQMHU 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 "QM: Prepared Handling Unit Information" 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_RQMHU TYPE RQMHU.
The RQMHU table consists of various fields, each holding specific information or linking keys about QM: Prepared Handling Unit Information data available in SAP. These include LGORT (Storage Location), BESTQ (Stock Category in the Warehouse Management System), SOBKZ (Special Stock Indicator), SONUM (Special Stock Number).. 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 RQMHU 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 |
WERKS | Plant | HUM_WERKS | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W | |
LGORT | Storage Location | HUM_LGORT | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
BESTQ | Stock Category in the Warehouse Management System | BESTQ | CHAR | 1 | BESTQ | ||||
SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
SONUM | Special Stock Number | LVS_SONUM | CHAR | 16 | ALPHA | LVS_SONUM | |||
OEXIDV | QM: Highest-Level Handling Unit | QOEXIDV | CHAR | 20 | ALPHA | EXIDV | |||
EXIDV | External Handling Unit Identification | EXIDV | CHAR | 20 | ALPHA | EXIDV | HU_IDENT_ALLG | ||
VENUM | Internal Handling Unit Number | VENUM | CHAR | 10 | Assigned to domain | ALPHA | VENUM | VEL | |
VEPOS | Handling Unit Item | VEPOS | NUMC | 6 | Assigned to domain | VEPOS | |||
VEMNG | Base Quantity Packed in the Handling Unit Item | VEMNG | QUAN | 15(3) | MENG15 | ||||
VEMEH | Base Unit of Measure of the Quantity to be Packed (VEMNG) | VEMEH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
VENUMHIGH | Internal Handling Unit Number | VENUM | CHAR | 10 | Assigned to domain | ALPHA | VENUM | VEL | |
QMGBUCHHUM | Target Stock for Quantity Posting from UD for Handling Units | QMGBUCHHUM | CHAR | 10 | QMGBUCHHUM | ||||
QMHUPOST | QM: Quantity already posted | QMHUPOST | CHAR | 1 | QKZ | ||||
ICON_MSG | Status of HU Quantity Posting | QICONHU | CHAR | 132 | TEXT132 | ||||
HUWMINFO | Posting Information | QMSGHU | CHAR | 132 | CHAR132 | ||||
HU_LGORT | Content is Located at an HU-managed Storage Location | HU_LGORT | CHAR | 1 | HU_LGORT | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
PC_ALLOWED | Transfer posting | QPCALLOWED | CHAR | 1 | QKZ | ||||
PC_WO_SLCH | Transfer Posting Allowed, If No Change to Storage Location | QPCWOSLCH | CHAR | 1 | QKZ | ||||
PC_RECEIPT | Goods receipt allowed | QPCRECEIPT | CHAR | 1 | QKZ | ||||
PC_ISSUE | Goods issue allowed | QPCISSUE | CHAR | 1 | QKZ |
Key field | Non-key field |
How do I retrieve data from SAP structure RQMHU using ABAP code?
As RQMHU 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 RQMHU as there is no data to select.How to access SAP table RQMHU
Within an ECC or HANA version of SAP you can also view further information about RQMHU 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