VBLBKOM SAP (VBLB fields to be incorporated in communication structure) Structure details
Dictionary Type: Structure
Description: VBLB fields to be incorporated in communication structure
Description: VBLB fields to be incorporated in communication structure
Structure field list including key, data, relationships and ABAP select examples
VBLBKOM 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 "VBLB fields to be incorporated in communication 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_VBLBKOM TYPE VBLBKOM.
The VBLBKOM table consists of various fields, each holding specific information or linking keys about VBLB fields to be incorporated in communication structure data available in SAP. These include ABART (Release type), DOCNUM (IDoc number), ABEFZ (Cumulative Quantity Received by Customer), ABRAB (Dlv. sched. valid from).. 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: Not classified
SAP VBLBKOM 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 |
| POSNR | Sales Document Item | POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
| ABART | Release type | ABART | CHAR | 1 | ABART | ||||
| DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
| ABEFZ | Cumulative Quantity Received by Customer | ABKFZ | QUAN | 15(3) | MENGV15 | ||||
| ABRAB | Dlv. sched. valid from | ABRAB | DATS | 8 | DATUM | ||||
| ABRBI | SA rel. valid to | ABRBI | DATS | 8 | DATUM | ||||
| LABNK | Customer number for forecast / JIT dlv. sched. | LABNK | CHAR | 17 | TEXT17 | ||||
| ABRDT | Delivery Schedule Date | ABRDT | DATS | 8 | DATUM | ||||
| TERSL | Date key for schedule line dates | TERSL | CHAR | 1 | TERSL | ||||
| LFDKD | Date of last delivery posted by the customer | LFDKD | DATS | 8 | DATUM | ||||
| LFNKD | Last delivery confirmed by the customer | LFNKD | CHAR | 10 | Assigned to domain | ALPHA | VBELN | ||
| ABFDA | Start of production go-ahead | ABFDA | DATS | 8 | DATUM | ||||
| ABFDE | End of production go-ahead | ABFDE | DATS | 8 | DATUM | ||||
| ABMDA | Start of material go-ahead | ABMDA | DATS | 8 | DATUM | ||||
| ABMDE | End of material go-ahead | ABMDE | DATS | 8 | DATUM | ||||
| ABHOR | JIT horizon | ABHOR | DATS | 8 | DATUM | ||||
| AKMFZ | Actual cumulative material go-ahead quantity | AKMFZ | QUAN | 15(3) | MENG15 | ||||
| AKFFZ | Actual cumulative production go-ahead quantity | AKFFZ | QUAN | 15(3) | MENG15 | ||||
| AKLFZ | Actual cumulative delivery go-ahead quantity | AKLFZ | QUAN | 15(3) | MENG15 | ||||
| HIFFZ | Highest cumulative production go-ahead quantity | HIFFZ | QUAN | 15(3) | MENG15 | ||||
| HIMFZ | Highest cumulative material go-ahead quantity | HIMFZ | QUAN | 15(3) | MENG15 | ||||
| HILFZ | Highest delivery go-ahead cumulative quantity | HILFZ | QUAN | 15(3) | MENG15 | ||||
| KRITB | Key for high priority stock | KRITB | CHAR | 1 | CHAR1 | ||||
| LABKY | Requirements status key | BSTAS | CHAR | 1 | CHAR1 | ||||
| VBRST | Customer point of consumption | VBRST | CHAR | 14 | CHAR14 | ||||
| EDLLS | Last dlv. note sent by ext. service agent to the customer | LFEDL | CHAR | 20 | CHAR20 | ||||
| EDLDT | Date of last delivery sent by external agent to customer | EDLDT | DATS | 8 | DATUM | ||||
| LFMKD | Last delivery quantity received by the customer | LFMKD | QUAN | 13(3) | MENG13 | ||||
| USR01 | Additional data field 1 for delivery schedules | USR01_D | CHAR | 35 | TEXT35 | ||||
| USR02 | Additional data field 2 for delivery schedules | USR02_D | CHAR | 35 | TEXT35 | ||||
| USR03 | Additional data field 3 for delivery schedules | USR03_D | CHAR | 35 | TEXT35 | ||||
| USR04 | Additional data field 4 for delivery schedules | USR04_D | CHAR | 10 | CHAR10 | ||||
| USR05 | Additional data field 5 for delivery schedules | USR05_D | CHAR | 10 | CHAR10 | ||||
| CYEFZ | Cumulative quantity reached on date zero setting made | CYEFZ | QUAN | 15(3) | MENGV15 | ||||
| CYDAT | Date on which cumulative received quantity set to zero | CYDAT | DATS | 8 | DATUM | ||||
| MFLAUF | Material go-ahead - validity period | MFLAUF | NUMC | 3 | NUM3 | ||||
| MFEIN | Material go-ahead - unit validity period | MFEIN | CHAR | 1 | EHFR | ||||
| FFLAUF | Production go-ahead - validity period | FFLAUF | NUMC | 3 | NUM3 | ||||
| FFEIN | Production go-ahead - Unit validity period | FFEIN | CHAR | 1 | EHFR | ||||
| LFMAIS | Last pick-up sheet sent by the customer | LFMAIS | CHAR | 20 | BSTNK | ||||
| MAIDT | Date of last pick-up sheet | MAIDT | DATS | 8 | DATUM | ||||
| REFOBJTYPE | Object Type | SWO_OBJTYP | CHAR | 10 | Assigned to domain | OJ_NAME | OBJ | ||
| REFOBJKEY | Object key | SWO_TYPEID | CHAR | 70 | SWO_TYPEID | ||||
| REFLOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| VJKUN | Customer fiscal year which is not yet closed | VJKUN | NUMC | 4 | GJAHR | GJAHR |
| Key field | Non-key field |
How do I retrieve data from SAP structure VBLBKOM using ABAP code?
As VBLBKOM 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 VBLBKOM as there is no data to select.How to access SAP table VBLBKOM
Within an ECC or HANA version of SAP you can also view further information about VBLBKOM 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