SAP ABAP Data Element VVAPLAN (Cash management update period in years)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
FVV (Package) R/3 application development for Financial Assets Management
⤷
⤷
⤷
Basic Data
| Data Element | VVAPLAN |
| Short Description | Cash management update period in years |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM02 | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | CM period |
| Medium | 15 | CM period |
| Long | 20 | CM period |
| Heading | 2 | CM |
Documentation
Definition
Period in years for which planned records are generated automatically for a position (mainly based on conditions) are to be updated on the database.
At the same time, this period is also used as a basis for updating Cash Management.
To determine a standard end date for all positions, the period is added to the end of the next six-month period.
To refresh planned data for existing positions up to the current update period end, the corresponding update report has to be run at the start of every six-month period.
Example:
Current date 03/07/YY
Period 2 years
End of update 06/30/YY+2
History
| Last changed by/on | SAP | 19970708 |
| SAP Release Created in |