BORGR_HEBU SAP (Help structure for the ID handling class and TR. VL60) Structure details
Description: Help structure for the ID handling class and TR. VL60
Structure field list including key, data, relationships and ABAP select examples
BORGR_HEBU 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 "Help structure for the ID handling class and TR. VL60" 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_BORGR_HEBU TYPE BORGR_HEBU.
The BORGR_HEBU table consists of various fields, each holding specific information or linking keys about Help structure for the ID handling class and TR. VL60 data available in SAP. These include POSNR (Item number of the SD document), AREST (Current Remaining Quantity in Sales Unit), LFIMG (Actual quantity delivered (in sales units)), VBUMG (GR-Posted Quantity in SUn).. 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 BORGR_HEBU 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 |
| VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| POSNR | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
| AREST | Current Remaining Quantity in Sales Unit | 0 | |||||||
| LFIMG | Actual quantity delivered (in sales units) | LFIMG | QUAN | 13(3) | MENG13 | ||||
| VBUMG | GR-Posted Quantity in SUn | VBUMG | QUAN | 13(3) | MENG13 | ||||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| CHARG | Batch Number | CHARG_D | CHAR | 10 | Assigned to domain | CHARG | CHA | ||
| VRKME | Sales unit | VRKME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| MAX_BUCH | Maximum Quantity That Can Be Posted in Sales Unit | 0 | |||||||
| VEMEH | Base Unit of Measure of the Quantity to be Packed (VEMNG) | VEMEH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| REST | Remaining Quantity in Sales Unit | 0 | |||||||
| HUMNG | Total HU Quantity in Sales Unit (except SumJC HUs) | 0 | |||||||
| SUMHU | Total HU Quty. (Sales Unit)for Which GR Has Not Posted | 0 | |||||||
| SUMPHU | Total GR-Posted HU Quantity in Sales Unit | 0 | |||||||
| SUMSHU | Total Select. HU Quty. (SU) for Which GR Has Not Been Posted | 0 | |||||||
| SUMPSHU | Total GR-Posted, Selected HU Quantity in Sales Unit | 0 | |||||||
| MABMNG | Total Summarized JIT Call Quantity in Sales Unit | 0 | |||||||
| SUMMAB | Total JIT Call Quty. (SU) for Which GR Has Not Been Posted | 0 | |||||||
| SUMPMAB | Tatal GR-Posted SumJC Quantity in Sales unit | 0 | |||||||
| SUMSMAB | Total Sel. JIT C. Quty.(SU) for Which GR Has Not Been Posted | 0 | |||||||
| SUMPSMAB | Total GR-Posted, Select SumJC Quantity in Sales Unit | 0 | |||||||
| SERNRMNG | Sum SERNR Quantity in Sales Unit | 0 | |||||||
| SUMSERNR | Sum for non-GR-Posted SERNR Quantity in Sales Unit | 0 | |||||||
| SUMPSERNR | Total GR-Posted SERNR Quantity in Sales Unit | 0 | |||||||
| SUMSSERNR | Sum for non-GR-Posted, Selected SERNR Quantity in Sales Unit | 0 | |||||||
| SUMPSSERNR | Total GR-Posted, Selected SERNR Quantity in Sales Unit | 0 | |||||||
| NBREST | Remaining Quantity That Was Not Posted in Sales Unit | 0 | |||||||
| BREST | Remaining Posted Quantity in Sales Unit | 0 | |||||||
| EBU_MAX | Maximum EBUMG in Sales Unit | 0 | |||||||
| EBU_MIN | Minimum EBUMG in Sales Unit | 0 | |||||||
| MDIFF_MAX | Maximum MDIFFMG in Sales Unit | 0 | |||||||
| MDIFF_MIN | Minimum MDIFFMG in Sales Unit | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BORGR_HEBU using ABAP code?
As BORGR_HEBU 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 BORGR_HEBU as there is no data to select.How to access SAP table BORGR_HEBU
Within an ECC or HANA version of SAP you can also view further information about BORGR_HEBU 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