Hierarchy
⤷ CA-GTF-TS (Application Component) Technical Application Support
⤷ BK (Package) CO Cross-application Objects
Basic Data
Data Element | CO_YRATE |
Short Description | Price Calculation with Period-Based Average Prices |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | AVERAGE_PRICE_IND | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Avg. price |
Medium | 15 | Average price |
Long | 20 | Average price |
Heading | 5 | Avg. |
Documentation
Definition
Indicator determining that activity prices for cost centers/activity types remain constant for the entire fiscal year.
Use
You can store a default value in the master data of an activity type or a business process.
You can overwrite the default value within planning if you are planning for the first time.
Procedure
This takes place either on the version level or per cost center/activity type in planning.
- Version
Activity prices for cost centers/activity types remain constant for the entire fiscal year in the version. The total plan costs and activity are taken into account when activity prices are calculated. Monthly fluctuations are ignored. Activate the "Average activity price" indicator from the fiscal-year dependent version parameters in the version as a planning method.
- Cost center/activity type
If you have not defined an average activity price for your version, you can define a constant activity price for the fiscal year for individual cost centers/activity types. Activity price calculation smoothes out fluctuations in the cost center/activity type activity price. Activate the appropriate indicator in activity type planning.
A default value for planning can be saved in the activity type master record. This value can be overwritten during planning.
Supplementary Documentation - CO_YRATE 0001
Notes
Field changes
This field can be changed at the fiscal year level (for example, for a new fiscal year).
Time dependency
This field is always time-based.
History
Last changed by/on | SAP | 19980909 |
SAP Release Created in |