SAP ABAP Data Element VLAUK_VEDA (Validity period category of contract)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VA (Package) Application development R/3 Sales
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VA (Package) Application development R/3 Sales
Basic Data
Data Element | VLAUK_VEDA |
Short Description | Validity period category of contract |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | VLAUK_VEDA | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | TVLZ |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | VAL_PER_CAT | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Val.categ. |
Medium | 15 | Val.per.cat. |
Long | 20 | Val.period.category |
Heading | 4 | VCat |
Documentation
Procedure
Enter a value here to indicate what kind of validity period the contract has (6 months, one year, and so on). You can change the validity period defined for a contract in Customizing in the contract itself.
If the actual validity period of a contract differs from the validity period category, the system issues a warning message.
Use
The validity period category can be used for evaluation purposes. For example, you may want to perform an analysis on all contracts you have set up with the validity period category K1 (one year).
Note
A contract with the validity period category K1, for example, does not necessarily run for exactly a year. It may be valid for slightly less orslightly more than one year.
History
Last changed by/on | SAP | 19991102 |
SAP Release Created in |