VEDAPO SAP (Contract Data) Table details
Dictionary Type: Table
Description: Contract Data
Description: Contract Data
Table field list including key, data, relationships and ABAP select examples
VEDAPO is a standard SAP Table which is used to store Contract Data data and is available within R/3 SAP systems depending on the version and release level.
The VEDAPO table consists of various fields, each holding specific information or linking keys about Contract Data data available in SAP. These include VBELN (Sales Document), VPOSN (Sales Document Item), VLAUFZ (Validity period of contract), VLAUEZ (Unit of validity period of contract).. 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: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Not classified
SAP VEDAPO table 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 | |||
| VBELN | Sales Document | VBELN_VA | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
| VPOSN | Sales Document Item | POSNR_VA | NUMC | 6 | VBUP | POSNR | APO | ||
| VLAUFZ | Validity period of contract | VLAUF_VEDA | NUMC | 3 | NUM3 | ||||
| VLAUEZ | Unit of validity period of contract | VLAUE_VEDA | CHAR | 1 | KDZEH | ||||
| VLAUFK | Validity period category of contract | VLAUK_VEDA | CHAR | 2 | TVLZ | VLAUK_VEDA | |||
| VINSDAT | Installation date | VIDAT_VEDA | DATS | 8 | DATUM | ||||
| VABNDAT | Agreement acceptance date | VADAT_VEDA | DATS | 8 | DATUM | ||||
| VBEGDAT | Contract start date | VBDAT_VEDA | DATS | 8 | DATUM | ||||
| VUNTDAT | Date on which contract is signed | VUDAT_VEDA | DATS | 8 | DATUM | ||||
| VKUESCH | Assignment cancellation procedure/cancellation rule | VKUES_VEDA | CHAR | 4 | TVKS | VKUES_VEDA | |||
| VAKTSCH | Action at end of contract | VASCH_VEDA | CHAR | 4 | TVAS | AKTVT | |||
| VEINDAT | Date on which cancellation request was received | VEDAT_VEDA | DATS | 8 | DATUM | ||||
| VWUNDAT | Requested cancellation date | VWDAT_VEDA | DATS | 8 | DATUM | ||||
| VKUEPAR | Cancellation party | VKPAR_VEDA | CHAR | 1 | VKPAR_VEDA | ||||
| VKUEGRU | Reason for Cancellation of Contract | VKGRU_VEDA | CHAR | 2 | TVKG | KUEGRU | |||
| VENDDAT | Contract end date | VNDAT_VEDA | DATS | 8 | DATUM | ||||
| VBELKUE | Cancellation document number of contract partner | VBELK_VEDA | CHAR | 20 | CHAR20 | ||||
| VBEDKUE | Date of cancellation document from contract partner | VBEDK_VEDA | DATS | 8 | DATUM | ||||
| VBEGREG | Rule for calculating contract start date | VBREG_VEDA | CHAR | 2 | TVRG | VDREG_VEDA | |||
| VVORZEIT | Lead time for cancellation prevention activities | VZEIT_VEDA | NUMC | 3 | NUM3 | ||||
| VVOREIN | Time unit of lead time | VZEIE_VEDA | CHAR | 1 | KDZEH | ||||
| VDEMDAT | Dismantling date | VDDAT_VEDA | DATS | 8 | DATUM | ||||
| VASDA | Date for action | VASDA | DATS | 8 | DATUM | ||||
| WIMID | Work item ID | WIMID | NUMC | 12 | SWWWIHEAD | SWW_WIID | |||
| VASDR | Date rule for action | VASDR | CHAR | 2 | TVRG | VDREG_VEDA | |||
| VENDREG | Rule for contract end date | RGVTE | CHAR | 2 | TVRG | VDREG_VEDA |
| Key field | Non-key field |
How do I retrieve data from SAP table VEDAPO using ABAP code
The following ABAP code Example will allow you to do a basic selection on VEDAPO to SELECT all data from the tableDATA: WA_VEDAPO TYPE VEDAPO.
SELECT SINGLE *
FROM VEDAPO
INTO CORRESPONDING FIELDS OF WA_VEDAPO
WHERE...
How to access SAP table VEDAPO
Within an ECC or HANA version of SAP you can also view further information about VEDAPO 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