Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CO-PC-IS (Application Component) Product Cost Controlling Information System⤷
KKB (Package) Reporting for Costing
Basic Data
| Data Element | KKB_VERSN |
| Short Description | Plan 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 | ||
| 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 | Plan version |
| Long | 20 | Plan version |
| Heading | 0 |
Documentation
Definition
Controlling-area-based combination of year-dependent indicators for planning data such as:
- Lock plan version
- Write line items
- Set opening balance
- Copying allowed
- Referencing allowed
- Iterative activity price
- Exchange rate type
- Values
Use
There is one actual and plan version (version 0) within a controlling area. The sytem creates it automatically when a controlling area is created. You only need to maintain the year-dependent version data for plan version 0.
Besides the standard version 0, you can create as many plan versions as you like and save them in planning.
When posting actual costs, you cannot enter a version in the request screens. The system automatically posts in actual version 0.
Plan version 0 charges using the actual activity prices of this version. This means that:
- You have to carry out activity price planning within activity type planning only within plan version 0 or
- Before the first actual costs are posted, you have to copy the alternative plan version to version 0 if these prices are to be taken for direct cost allocation later.
You can maintain the plan version using the appropriate function. Using this function, you can lock plan versions and use a line item indicator. After locking a plan version you can no longer change planned values. If you use the line item indicator, totals records and line items are saved. These line items contain the changes made during each planning.
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in |
