Hierarchy
⤷ 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_FI |
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
Indicator that determines whether actual data is recorded in the version.
Use
In General Ledger Accounting, you can only record version 1 with actual data. You should not create any further actual versions.
In the special purpose ledgers, on the other hand, you can create several versions with actual data.
Procedure
Examples
Dependencies
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 | 20030130 |
SAP Release Created in | 470 |