Hierarchy
SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management⤷
FIN-BA (Application Component) Business Analytics⤷
UA_COCO_ADAPTER (Package) Concurrent Costing: Adapter for Satellite Systems
Basic Data
| Data Element | VERSN_BP |
| 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.
The maintenance of the following fiscal year parameters is absolutely necessary:
Planning:
- Lock version
- Intergrated planning
- Copying allowed
- Exchange rate type
- Value date
- Integrated planning with Cost Center Accounting and Activity Based Costing
- Version for indirect activity allocation for non-integrated order/ project planning
- Receiver version
- Valuation variant for CO Resource Planning
Price Calculation:
- Purely iterative price
- Plan price calculation: Determination method
- Actual price calculation: Determination method
- Recalculation with actual prices
- Cost component structure
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_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
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 320 |
