Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BK (Package) CO Cross-application Objects
Basic Data
| Data Element | VERSN |
| Short Description | Version |
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 | KVS | |
| Default Component name | VERSION | |
| 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
For each controlling area, a collection of year-dependent indicators for planning data, such as
- Delta version
- Lock version
- Integrated planning
- Allow copying
- Iterative price
- Average prices
- Exchange rate type
- Value date
Use
There is one specific version for actual and planned costs (version 0) in each controlling area. The SAP System creates this version automatically when you set up a controlling area. You only need to maintain the fiscal year data for planning in version 0.
In addition to version 0, you can create any number of extra planning versions in which you can enter planning figures using the planning transactions.
When posting actual costs you do not have the option of entering a version. The actual values are automatically posted to version 0.
Version 0 is unique in that prices from the version's activity types are used for allocating actual costs. This means that you need to plan your prices in activity type planning
- In Version 0 only, or
- Copy your alternative version to Version 0 before posting actual costs for the first time, if you want to use these prices for direct activity allocation.
For planning, you need to maintain the following fiscal year parameters:
In Activity Based Costing you can also use a delta version by specifying a valid version that can be used for reference. Once you have done this, the current version is designated as a delta version. When you use a delta version, you need to specify the business transactions to be added to the delta version in "Own transactions of delta version".
Supplementary Documentation - VERSN 0100
Use
Procedure
Examples
If you are using a plan version not equal to 0, your cost center list will show you the actual data of version 0 together with the values you planned under the version you enter here.
Dependencies
Supplementary Documentation - VERSN 1021
Use
Procedure
You must always specify version 000 for actual line items.
Examples
Dependencies
Supplementary Documentation - VERSN 1022
Use
Procedure
You do not need to enter anything here for actual line items.
Examples
Dependencies
Supplementary Documentation - VERSNR 0001
Use
When maintaining patient-related insurance relationships, you specify the patient's most recent health insurance number here. This number is used as a default value for new cases.
When maintaining case-related insurance relationships, you can specify the case-related health insurance number here.
Manual maintenance of the health insurance number is not possible if the number was transferred from the patient's healthcare smart card.
If the insurance number in the patient-related insurance relationship was transferred from the healthcare smart card, this number is always overwritten by the insurance number of the last case, providing this is also transferred from the healthcare smart card.
Thus, the value of the card last imported is always in the patient- related health insurance number field.
No comparison is carried out when the heath insurance number is entered manually.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSNR 0002
Use
You store the patient's most recent health insurance number here.
The field is not ready for input if the number was transferred from the patient's healthcare smart card.
If the health insurance number in the patient-related insurance relationship was transferred from the healthcare smart card, this number is always overwritten by the health insurnce number of the last case, providing this is also transferred from the healthcare smart card.
Thus, the patient-related health insurance number is always from the most recently imported healthcare smart card.
No comparison is carried out when the health insurance number is entered manually.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSNR 0003
Use
You store the case-related health insurance number here.
The field is not ready for input if the number was transferred from the patient's healthcare smart card.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSN_011 0001
Use
In this field you store the financial statement version (for each depreciation area) to which the Asset Management evaluations are to refer. If you start evaluations with a sort variant which the financial statement item (field ERGSO/ERGHB - table ANLAV) uses as a search criterion, the system determines the relevant financial statement item by means of this financial statement version.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSN_011 0010
Use
When entering a balance sheet/P+L version, you receive the following data provided a selected G/L account of this balance sheet/P+L version is allocated:
- Balance sheet/P+L version
- Financial statement key debits
- Financial statement key credits
- Indicator: The balance of the group determines the debits/credits
- Indicator which determines that no account numbers but group account numbers are allocated for the definition of the financial statement version.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSN_ABGR0000
Use
All the results analysis parameters are assigned to the results version.
You can. for example define a version in which results analysis for the object is carried out according to German law, and a version in which results analysis is carried out according to American law. You can save the two versions separately.
Supplementary Documentation - VERSN_ABGR0010
Use
Procedure
Select a results analysis version that is permitted for transfer to for profit center accounting in financial accounting.
Examples
Dependencies
Supplementary Documentation - VERSN_BP 0100
Use
Procedure
Examples
If you use a plan version that is not equal to 0, your cost center list will display the actual data of version 0 and the data you planned in accordance with the version entered here.
Dependencies
Supplementary Documentation - VERSN_BP 1021
Use
Procedure
You must always enter the version '000' for the actual line item.
Examples
Dependencies
Supplementary Documentation - VERSN_BP 1022
Use
Procedure
You must make any entry for the actual line item here.
Examples
Dependencies
Supplementary Documentation - VERSN_CO 0451
Definition
Using versions, you can manage different plan data in parallel for the same object.
Use
Specify the plan version which references the earned value basis.
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 | 19981111 |
| SAP Release Created in |
