Hierarchy
⤷ CO-PC-PCP (Application Component) Product Cost Planning
⤷ CKJ1 (Package) Customizing for Product Costing
Basic Data
Data Element | CK_PERALT |
Short Description | Age in Periods |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC3 | |
Data Type | NUMC | Character string with only digits |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
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 | 6 | AgePer |
Medium | 13 | Age (Periods) |
Long | 13 | Age (Periods) |
Heading | 14 | Age in Periods |
Documentation
Definition
Together with the transfer strategy, this determines the periods in which the system searches for an existing cost estimate for the material. This includes the start date of the cost estimate.
Use
Procedure
Examples
Dependencies
For current, previous, and other cost estimates, the period age refers to the number of periods in the past (that is, before the start date of the cost estimate).
For future cost estimates, the period age refers to the number of periods in the future (that is, after the start date of the cost estimate) and in the past (before the start date).
With period-based cost estimates (period-based transfer), the period age has no effect, because in this case the system searches for cost estimates that have exactly the same keys (that is, costing type, valuation variant, costing version, and, if applicable, period).
Note
- A period age of zero means the current period. If you do not make any entries, the system interprets this as zero and searches for existing cost estimates in the current period only.
History
Last changed by/on | SAP | 19970812 |
SAP Release Created in |