FBG_VBSK SAP (Follow-On Doc. Generation: Delivery Header Data Structure) Structure details
Description: Follow-On Doc. Generation: Delivery Header Data Structure
Structure field list including key, data, relationships and ABAP select examples
FBG_VBSK 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 "Follow-On Doc. Generation: Delivery Header Data 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_FBG_VBSK TYPE FBG_VBSK.
The FBG_VBSK table consists of various fields, each holding specific information or linking keys about Follow-On Doc. Generation: Delivery Header Data Structure data available in SAP. These include MANDT (Client), SAMMG (Group), SMART (Group type), ERNAM (Name of Person who Created the Object).. 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 FBG_VBSK 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 |
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
SAMMG | Group | SAMMG | CHAR | 10 | Assigned to domain | ALPHA | SAMMG | GRN | |
SMART | Group type | SMART | CHAR | 1 | TVSA | SMART | GRA | ||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
UZEIT | Time | UZEIT | TIMS | 6 | UZEIT | ||||
VBNUM | Number of created documents | VBNUM | NUMC | 4 | NUMC4 | ||||
ERNUM | Number of errors that occurred | ERNUM | NUMC | 4 | NUMC4 | ||||
BRGEW | Gross weight of all processed documents | BRGEW_SG | QUAN | 13(3) | MENG13 | ||||
GEWEI | Weight Unit | GEWEI | UNIT | 3 | T006 | CUNIT | MEINS | ||
VOLUM | Volume of all processed documents | VOLUM_SG | QUAN | 13(3) | MENG13 | ||||
VOLEH | Volume unit | VOLEH | UNIT | 3 | T006 | CUNIT | MEINS | ||
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | TVST | VSTEL | VST | ||
VTEXT | Description | BEZEI30 | CHAR | 30 | TEXT30 | ||||
MAXZT | Maximum labor capacity of the shipping point in days | MAXZT | DEC | 5(2) | DEC3_2 | ||||
PROGRAMM | ABAP Program Name | PROGRAMM | CHAR | 40 | Assigned to domain | PROGRAMM | RID | ||
SELSET | ABAP: Name of variant (without program name) | VARIANT | CHAR | 14 | Assigned to domain | VARIANT | |||
BATCH | Indicator: Processing in background | BATCH_COLL | CHAR | 1 | ANKREUZ | ||||
ANZLP | Number of delivery items created in collective processing | ANZLP | INT4 | 10 | TABIX | ||||
ANZGP | Number of items read in collective processing | ANZGP | INT4 | 10 | TABIX | ||||
ANZGI | Number of indexes read in collective processing | ANZGI | INT4 | 10 | TABIX | ||||
KWPRO | Picking wave profile | KW_PROFIL | CHAR | 6 | T318 | KW_PROFIL | |||
KAPTP | Shift definition | KAPTPROG | CHAR | 4 | Assigned to domain | KAPTPROG | |||
LGNUM | Warehouse Number / Warehouse Complex | LGNUM | CHAR | 3 | T300 | LGNUM | LGN | ||
BEDAT | Date of deliveries in picking waves | BELEG_DATUM | DATS | 8 | DATUM | ||||
WRAST | Timeslot group | WRAST | CHAR | 4 | Assigned to domain | KAPTPROG | |||
.INCLU--AP | 0 | ||||||||
SAMMG_V | Software maintenance process run number | /SAPHT/SW_SAMMG_V | CHAR | 10 | Assigned to domain | ALPHA | SAMMG | GRN | |
LFDNR_FB_KOPF_POSTAB | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
ITEMS_PER_HEADER | Natural Number | INT4 | INT4 | 10 | INT4 |
Key field | Non-key field |
How do I retrieve data from SAP structure FBG_VBSK using ABAP code?
As FBG_VBSK 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 FBG_VBSK as there is no data to select.How to access SAP table FBG_VBSK
Within an ECC or HANA version of SAP you can also view further information about FBG_VBSK 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