SAP ABAP Data Element VVDKUENEXT (Next possible notice date typical for area)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FVVI (Package) R/3 appl.dev. for Financial Assets Management: Real estate
Basic Data
| Data Element | VVDKUENEXT |
| Short Description | Next possible notice date typical for area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | NxtNotice |
| Medium | 15 | NextPossNotice |
| Long | 20 | Next poss.notice dte |
| Heading | 10 | NxtNotice |
Documentation
Use
The date when the adjustment becomes effective is normally calculated using the "valid-as-from date" in the contract periods of notice as the basis.
If no periods of notice are specified in the contract, the adjustment is effective on the "next possible notice date typical for the area" which is specified here. In this case, an information message is written in the adjustment run log.
History
| Last changed by/on | SAP | 19990827 |
| SAP Release Created in |
