Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KBAS (Package) Overhead Cost Controlling
Basic Data
Data Element | VERSN_COBK |
Short Description | Version in CO Document Header |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | COVERSI | |
Data Type | CHAR | Character String |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table | TKVS |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | KVT | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Version |
Medium | 15 | Version |
Long | 20 | Version |
Heading | 3 | Vsn |
Documentation
Definition
The version is a controlling-area-based collection of fiscal-year dependent indicators:
- Lock version
- Integrated planning
- Iterative price
- Average price
- Exchange rate type
- Value date
The header of a Controlling document displays the common version of all the line items in the document.
An exception exists for different valuations with transfer prices. In this case, the header displays the basic version (000), but individual line items may be posted in other versions as well.
Use
A controlling area always has at least one actual version (000). The system creates the version automatically with the creation of the controlling area. You must maintain the fiscal-year-dependent version data for version 000.
You can carry out cost center planning in multiple versions. For actual postings, you usually only have version 1 to choose from.
In the Activity-Based Costing component, you can also define a delta version if you want to use ABC in parallel calculations. If you use operative calculations, you must use version 000 again.
To use a delta version, you must use a valid version as a reference version. As soon as you enter the reference, the current version is marked as a delta version. When you use a delta version, you must determine in "Delta Version Transactions" which business transactions are valid for the delta version. You can create as many delta versions as required.
The Activity-Based Costing component offers the existing versions in each system transaction for your selection.
Supplementary Documentation - VERSN_COBK0001
Use
The system automatically sets version 0 for actual data.
Note
This does not apply to Activity-Based Costing.
If you use Activity-Based Costing in conjunction with Cost Center Accounting, you can specify a delta version.
Dependencies
To use a delta version, specify a valid version to which reference is to be made.
If you enter a reference version here, the current version is marked as a delta version.
If you use a delta version, you must specify under Own Delta Version Transactions which business transactions are to be added to the delta version.
You can create as many delta versions are you require.
Example
History
Last changed by/on | SAP | 19970827 |
SAP Release Created in |