QFHDE_1 SAP (Cross-notification reference objects) Structure details
Description: Cross-notification reference objects
Structure field list including key, data, relationships and ABAP select examples
QFHDE_1 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 "Cross-notification reference objects" 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_QFHDE_1 TYPE QFHDE_1.
The QFHDE_1 table consists of various fields, each holding specific information or linking keys about Cross-notification reference objects data available in SAP. These include REVLV (Revision Level), MAWERK (Plant), KUNUM (Customer Number), LIFNUM (Vendor Account 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)
SAP QFHDE_1 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 |
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| REVLV | Revision Level | REVLV | CHAR | 2 | NUMCV | REVLV | RVS | ||
| MAWERK | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| KUNUM | Customer Number | KUNUM | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | |
| LIFNUM | Vendor Account Number | LIFNUM | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | |
| VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
| CHARG | Batch Number | CHARG_D | CHAR | 10 | Assigned to domain | CHARG | CHA | ||
| LICHN | Vendor Batch Number | LICHN | CHAR | 15 | LICHN | ||||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| BKGRP | Purchasing Group | BKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| IDNLF | Material Number Used by Vendor | IDNLF | CHAR | 35 | IDNEX | ||||
| HERSTELLER | Number of Manufacturer | QLIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | |
| EMATNR | Material Number | EMATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
| FERTAUFNR | Order Number (Production Order) | FERTAUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| FERTAUFPL | Plan Number for Operations in Order (Production Order) | FERTAUFPL | NUMC | 10 | AUFPL | ||||
| VERID | Production Version | VERID | CHAR | 4 | MKAL | VERID | VER | ||
| SA_AUFNR | Run schedule header number | SA_AUFNR | CHAR | 12 | Assigned to domain | ALPHA | SA_AUFNR | ||
| IHAUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| MJAHR | Material Document Year | MJAHR | NUMC | 4 | GJAHR | GJAHR | MJA | ||
| MBLNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
| MBLPO | Item in Material Document | MBLPO | NUMC | 4 | MBLPO | POS | |||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| LS_KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| LS_KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
| LS_VBELN | Delivery | VBELN_VL | CHAR | 10 | Assigned to domain | ALPHA | VBELN | VL | |
| LS_POSNR | Delivery Item | POSNR_VL | NUMC | 6 | Assigned to domain | POSNR |
| Key field | Non-key field |
How do I retrieve data from SAP structure QFHDE_1 using ABAP code?
As QFHDE_1 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 QFHDE_1 as there is no data to select.How to access SAP table QFHDE_1
Within an ECC or HANA version of SAP you can also view further information about QFHDE_1 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