Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MCV (Package) R/3 application development: Sales Information System
Basic Data
| Data Element | MC_VDATUM |
| Short Description | Date of update for statistics updating |
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 | Proc date |
| Medium | 15 | UpdateDateStats |
| Long | 20 | Update date: stats. |
| Heading | 55 | Date of update for statistics updating |
Documentation
Definition
System date on which a document change was made.
Use
The date specifies the update period to which changes are to be assigned.
Dependencies
When a key figure is updated, the period is determined in which the key figure is cumulated. To determine the period, you need to specify a date field which defines the contents of the period.
The specific date field that you choose enables you to take various views into account, i.e. the date you choose (system date or entry date) is decisive for the subsequent interpretation of stored information.
Example
In January, you created a sales order with an item that has 100 pieces. In February you change the order quantity of this item to 50 pieces.
You now have a variety of options for updating this change to the information structures in accordance with the specific periods.
View 1: Updating takes place on entry date
The incoming order of the item occurred in January and the change shouldalso be updated in January. In this case, you need to use the entry date of the item, for example, to determine the period. This means that 50 pieces of the incoming order are shown for January.
View 2: Update on the current date (system date)
The order change in February should not change the order quantity in January. The change of the order is posted in February. The incoming order for January is 100 pieces, the incoming order for February is 50 pieces. Changes are always made in the period when the changes were made (=current).
History
| Last changed by/on | SAP | 19930713 |
| SAP Release Created in | 470 |
