VBVFE SAP (Blocked Schedule Lines Due for Shipping) Structure details
Description: Blocked Schedule Lines Due for Shipping
Structure field list including key, data, relationships and ABAP select examples
VBVFE 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 "Blocked Schedule Lines Due for Shipping" 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_VBVFE TYPE VBVFE.
The VBVFE table consists of various fields, each holding specific information or linking keys about Blocked Schedule Lines Due for Shipping data available in SAP. These include POSNR (Item number of the SD document), ETENR (Delivery Schedule Line Number), MANDT (Client), VSTEL (Shipping Point/Receiving Point).. 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 VBVFE 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 | |||
| ETENR | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
| LEDAT | Delivery Creation Date | LEDAT | DATS | 8 | DATUM | ||||
| LPRIO | Delivery Priority | LPRIO | NUMC | 2 | Assigned to domain | LPRIO | |||
| ROUTE | Route | ROUTE | CHAR | 6 | Assigned to domain | ROUTE | |||
| SPDNR | Forwarding agent | SPDNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
| WADAT | Goods Issue Date | WADAT | DATS | 8 | DATUM | ||||
| KUNWE | Ship-to party | KUNWE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| LIFSP | Delivery block for header or schedule line | LIFSP_VG | CHAR | 2 | Assigned to domain | LIFSP | |||
| KUNNR | Sold-to party | KUNAG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | |
| VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
| VTWEG | Distribution Channel | VTWEG | CHAR | 2 | Assigned to domain | VTWEG | VTW | C_VTWEG | |
| SPART | Division | SPART | CHAR | 2 | Assigned to domain | SPART | SPA | C_SPART | |
| VKBUR | Sales Office | VKBUR | CHAR | 4 | Assigned to domain | VKBUR | VKB | ||
| VKGRP | Sales Group | VKGRP | CHAR | 3 | Assigned to domain | VKGRP | VKG | ||
| ADRNR_AG | Address number of the sold-to party | ADRNR_AG | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| NAME_AG | Name of the sold-to party | NAME_AG | CHAR | 35 | NAME | ||||
| ORT01_AG | Location of the sold-to party | ORT01_AG | CHAR | 35 | ORT01 | ||||
| ADRNR_WE | Address number of the ship-to party | ADRNR_WE | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
| NAME_WE | Name of the ship-to party | NAME_WE | CHAR | 35 | NAME | ||||
| ORT01_WE | Location of the ship-to party | ORT01_WE | CHAR | 35 | ORT01 | ||||
| NETWR | Net value of the schedule line in document currency | NETWR_EP | CURR | 15(2) | WERTV8 | ||||
| WAERK | SD Document Currency | WAERK | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| KURSK | Exchange Rate for Price Determination | KURSK | DEC | 9(5) | EXCRT | KURRF | |||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| ARKTX | Short text for sales order item | ARKTX | CHAR | 40 | TEXT40 | ||||
| TABIX | Field defined as in SY-TABIX | TABIX_D | INT4 | 10 | TABIX |
| Key field | Non-key field |
How do I retrieve data from SAP structure VBVFE using ABAP code?
As VBVFE 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 VBVFE as there is no data to select.How to access SAP table VBVFE
Within an ECC or HANA version of SAP you can also view further information about VBVFE 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