TDS_RFC_VEDA_COMV SAP (Lean Order - RFC - Contract Data (Values)) Structure details
Description: Lean Order - RFC - Contract Data (Values)
Related tables to TDS_RFC_VEDA_COMV
Access table TDS_RFC_VEDA_COMV
Structure field list including key, data, relationships and ABAP select examples
TDS_RFC_VEDA_COMV 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 "Lean Order - RFC - Contract Data (Values)" 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_TDS_RFC_VEDA_COMV TYPE TDS_RFC_VEDA_COMV.
The TDS_RFC_VEDA_COMV table consists of various fields, each holding specific information or linking keys about Lean Order - RFC - Contract Data (Values) data available in SAP. These include VBEGDAT (Contract start date), VENDDAT (Contract end date), VBEGREG (Rule for calculating contract start date), VENDREG (Rule for contract end date).. 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: Cannot Be Enhanced
SAP TDS_RFC_VEDA_COMV 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 |
| HANDLE | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
| VBEGDAT | Contract start date | VBDAT_VEDA | DATS | 8 | DATUM | ||||
| VENDDAT | Contract end date | VNDAT_VEDA | DATS | 8 | DATUM | ||||
| VBEGREG | Rule for calculating contract start date | VBREG_VEDA | CHAR | 2 | TVRG | VDREG_VEDA | |||
| VENDREG | Rule for contract end date | RGVTE | CHAR | 2 | TVRG | VDREG_VEDA | |||
| VLAUFK | Validity period category of contract | VLAUK_VEDA | CHAR | 2 | TVLZ | VLAUK_VEDA | |||
| VLAUFZ | Validity period of contract | VLAUF_VEDA | NUMC | 3 | NUM3 | ||||
| VLAUEZ | Unit of validity period of contract | VLAUE_VEDA | CHAR | 1 | KDZEH | ||||
| VINSDAT | Installation date | VIDAT_VEDA | DATS | 8 | DATUM | ||||
| VABNDAT | Agreement acceptance date | VADAT_VEDA | DATS | 8 | DATUM | ||||
| VUNTDAT | Date on which contract is signed | VUDAT_VEDA | DATS | 8 | DATUM | ||||
| VDEMDAT | Dismantling date | VDDAT_VEDA | DATS | 8 | DATUM | ||||
| VAKTSCH | Action at end of contract | VASCH_VEDA | CHAR | 4 | Assigned to domain | AKTVT | |||
| VASDA | Date for action | VASDA | DATS | 8 | DATUM | ||||
| VASDR | Date rule for action | VASDR | CHAR | 2 | Assigned to domain | VDREG_VEDA | |||
| VKUESCH | Assignment cancellation procedure/cancellation rule | VKUES_VEDA | CHAR | 4 | Assigned to domain | VKUES_VEDA | |||
| VKUEGRU | Reason for Cancellation of Contract | VKGRU_VEDA | CHAR | 2 | Assigned to domain | KUEGRU | |||
| VEINDAT | Date on which cancellation request was received | VEDAT_VEDA | DATS | 8 | DATUM | ||||
| VWUNDAT | Requested cancellation date | VWDAT_VEDA | DATS | 8 | DATUM | ||||
| VBELKUE | Cancellation document number of contract partner | VBELK_VEDA | CHAR | 20 | CHAR20 | ||||
| VKUEPAR | Cancellation party | VKPAR_VEDA | CHAR | 1 | VKPAR_VEDA | ||||
| VBEDKUE | Date of cancellation document from contract partner | VBEDK_VEDA | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure TDS_RFC_VEDA_COMV using ABAP code?
As TDS_RFC_VEDA_COMV 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 TDS_RFC_VEDA_COMV as there is no data to select.How to access SAP table TDS_RFC_VEDA_COMV
Within an ECC or HANA version of SAP you can also view further information about TDS_RFC_VEDA_COMV 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