Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | VER_ACTUAL |
| Short Description | Record actual data for the relevant version? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Act. Data |
| Medium | 20 | Record Actual Data |
| Long | 20 | Record Actual Data |
| Heading | 6 | Actual |
Documentation
Definition
This indicator controls whether actual data can be written to the version.
Use
In overhead cost controlling, actual data is updated in the operational version 0.
You only use actual versions different from 0
- if you are working with parallel valuations (additional versions)
- if you use delta versions of activity based costing
Procedure
Examples
Dependencies
Version 0 must always exist. In version 0, the Planning and Actual indicators must be activated.
In version 1, the Actual indicator cannot be active.
If an update of actual data is not allowed in the General Version Definitions, the same rule applies to the Controlling Area Settings for this version.
If an update of actual data in the version is allowed in the General Version Definitions, you can cancel this by deactivating the indicator in the Controlling Area Settings for each controlling area.
Supplementary Documentation - VER_ACTUAL0001
Use
Actual data always updates the system in overhead cost management in version 0.
If you are working with parallel valuation approaches/transfer prices, you define additional parallel actual versions for the various valuations along with the operational actual version "000".
In activity-based costing you can add actual data to various delta versions of activity-based costing. A version becomes a delta version if a reference version is assigned to it.
Supplementary Documentation - VER_ACTUAL1
Use
The SAP system always updates actual data in overhead cost controlling in the version 0.
The indicator is only relevant for delta versions.
A exception to this is present in activity-based costing. Actual data for activities defined in delta versions is updated in various versions other than 0.
A version becomes a delta version when a reference version is assigned to it.
Supplementary Documentation - VER_ACTUAL_FI0001
Use
In Overhead Costs Controlling, the SAP system always posts actual data in version 0.
If you are working with multiple valuation approaches/transfer prices, you have to define additional parallel actual versions for the different valuations - in addition to operative actual version 000.
In Activity-Based Costing, you can store actual data in various Activity-Based Costing delta versions. A version is a delta version if a reference version is assigned to it.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
