VLCFUNCDATA_HEAD_S SAP (VELO: Transfer Structure for Functions (Header Data)) Structure details
Dictionary Type: Structure
Description: VELO: Transfer Structure for Functions (Header Data)
Description: VELO: Transfer Structure for Functions (Header Data)
ABAP Code to SELECT data from VLCFUNCDATA_HEAD_S
Related tables to VLCFUNCDATA_HEAD_S
Access table VLCFUNCDATA_HEAD_S
Related tables to VLCFUNCDATA_HEAD_S
Access table VLCFUNCDATA_HEAD_S
Structure field list including key, data, relationships and ABAP select examples
VLCFUNCDATA_HEAD_S 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 "VELO: Transfer Structure for Functions (Header Data)" 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_VLCFUNCDATA_HEAD_S TYPE VLCFUNCDATA_HEAD_S.
The VLCFUNCDATA_HEAD_S table consists of various fields, each holding specific information or linking keys about VELO: Transfer Structure for Functions (Header Data) data available in SAP. These include VBELN (Sales Document), KUNNR_SD (Customer), KUNAM_SD (Name of Customer), KUNWE_SD (Ship-to party).. 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 VLCFUNCDATA_HEAD_S 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 Document | VBELN_VA | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
| KUNNR_SD | Customer | VLC_KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | DEBI |
| KUNAM_SD | Name of Customer | VLC_CU_NAME1_GP | CHAR | 35 | NAME | ||||
| KUNWE_SD | Ship-to party | KUNWE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| WENAM_SD | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| KUNRE_SD | Bill-to party | KUNRE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | |
| RENAM_SD | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| KUNRG_SD | Payer | KUNRG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
| RGNAM_SD | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
| ANGDT | Quotation/Inquiry is valid from | ANGDT_V | DATS | 8 | DATUM | ||||
| BNDDT | Date until which bid/quotation is binding (valid-to date) | BNDDT | DATS | 8 | DATUM | ||||
| AUDAT | Document Date (Date Received/Sent) | AUDAT | DATS | 8 | DATUM | ||||
| VBTYP | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
| AUART | Sales Document Type | AUART | CHAR | 4 | TVAK | AUART | AUART | AAT | |
| AUGRU | Order reason (reason for the business transaction) | AUGRU | CHAR | 3 | TVAU | AUGRU | |||
| VSART | Shipping type | VSARTTR | CHAR | 2 | Assigned to domain | VERSART | |||
| ABSTK | Overall rejection status of all document items | ABSTK | CHAR | 1 | STATV | ||||
| FAKSK | Billing block in SD document | FAKSK | CHAR | 2 | TVFS | FAKSP | |||
| NETWR | Net Value of the Sales Order in Document Currency | NETWR_AK | CURR | 15(2) | WERTV8 | ||||
| WAERK | SD Document Currency | WAERK | CUKY | 5 | TCURC | WAERS | FWS | ||
| VKORG | Sales Organization | VKORG | CHAR | 4 | TVKO | VKORG | VKO | C_VKORG | |
| VKORGTXT | Description of Sales Organization | VLC_VKORGT | CHAR | 20 | TEXT20 | ||||
| VTWEG | Distribution Channel | VTWEG | CHAR | 2 | TVTW | VTWEG | VTW | C_VTWEG | |
| VTWEGTXT | Description of Distribution Channel | VLC_VTWEGT | CHAR | 20 | TEXT20 | ||||
| SPART | Division | SPART | CHAR | 2 | TSPA | SPART | SPA | C_SPART | |
| SPARTTXT | Description of Division | VLC_SPARTT | CHAR | 20 | TEXT20 | ||||
| VKGRP | Sales Group | VKGRP | CHAR | 3 | TVKGR | VKGRP | VKG | ||
| VKBUR | Sales Office | VKBUR | CHAR | 4 | TVBUR | VKBUR | VKB | ||
| VDATU | Requested delivery date | EDATU_VBAK | DATS | 8 | DATUM | ||||
| BSTNK | Customer purchase order number | BSTNK | CHAR | 20 | BSTNK | ||||
| BSTDK | Customer purchase order date | BSTDK | DATS | 8 | DATUM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERDAT_SD | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERNAM_SD | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| UPD_TMSTMP | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
| POSNR | Sales Document Item | POSNR_VA | NUMC | 6 | Assigned to domain | POSNR | APO | ||
| CUOBJ_SD | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
| ARKTX | Short text for sales order item | ARKTX | CHAR | 40 | TEXT40 | ||||
| PSTYV | Sales document item category | PSTYV | CHAR | 4 | TVPT | PSTYV | |||
| POSAR | Item type | POSAR | CHAR | 1 | POSAR | ||||
| LFREL | Item is relevant for delivery | LFREL_AP | CHAR | 1 | XFELD | ||||
| FKREL | Relevant for Billing | FKREL | CHAR | 1 | FKREL | ||||
| ABGRU | Reason for rejection of quotations and sales orders | ABGRU_VA | CHAR | 2 | TVAG | ABGRU_VA | |||
| ZMENG | Target quantity in sales units | DZMENG | QUAN | 13(3) | MENG13 | ||||
| ZIEME | Target quantity UoM | DZIEME | UNIT | 3 | T006 | CUNIT | MEINS |
| Key field | Non-key field |
How do I retrieve data from SAP structure VLCFUNCDATA_HEAD_S using ABAP code?
As VLCFUNCDATA_HEAD_S 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 VLCFUNCDATA_HEAD_S as there is no data to select.How to access SAP table VLCFUNCDATA_HEAD_S
Within an ECC or HANA version of SAP you can also view further information about VLCFUNCDATA_HEAD_S 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