Hierarchy
⤷ CO (Application Component) Controlling
⤷ KISTCORE (Package) Cost Accounting Actual Data: General Services
Basic Data
Data Element | SPRKZ |
Short Description | Lock Indicator |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | YNFLG | |
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 | Lock ind. |
Medium | 15 | Lock indicator |
Long | 20 | Lock indicator |
Heading | 0 |
Documentation
Definition
Indicator determining whether an activity type is locked for activity input planning.
If the indicator is active, the affected activity type cannot be included.
Notes
If planning is reconciled, meaning plan activity = scheduled activity, the indicator should be activated so that the plan quantity remains unchanged.
If the indicator is inactive, the activity type can be drawn upon for activity input planning and indirect activity allocation in plan.
If active, the lock indicator has no effect on
- actual postings
- planning, other than activity input planning and indirect activity allocation in plan
- activity price changes
Supplementary Documentation - SPRKZ 0001
Use
If the blocking indicator for revaluation is set, it is not possible to run or reverse this revaluation.
Procedure
Examples
Dependencies
Supplementary Documentation - SPRKZ 0009
Note
Field changes
The data in this field can be changed daily.
Time dependency
You can define this field as time-based in the configuration menu of Cost Center Accounting.
- If you activate this indicator, you can maintain separate data for any number of different time intervals.
- If you do not activate this indicator, you can make only one field entry valid for all intervals. If, however, you change a time-based field, you can enter a new value in the non-time-based field that is valid for the interval of the time-based field.
History
Last changed by/on | SAP | 19990223 |
SAP Release Created in |