Hierarchy

⤷

⤷

Basic Data
Data Element | CY_DAPER |
Short Description | Unit in which the duration of a period is specified |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CY_DAPER | |
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 | Period |
Medium | 14 | Period unit |
Long | 15 | Period unit |
Heading | 4 | Unit |
Documentation
Definition
Key, with which you define the unit of time (day, week, month, calendar year) for the periods in workforce planning.
If you have set the Mixed period types indicator, specify the unit of time for each period split on the period split scrren.
Example
You have entered a planning period for workforce planning starting 3 months before the current date and ending 12 months after.
For this planning period you specify the following period split:
Period no. Period unit Number of periods
1 Week 11
2 Day 20
3 Week 4
4 Month 3
This means you display the past period at the start of the planning period in weeks. For the immediate future you select a very detailled display in days. For the more distant future you need less detail and therefore choose progressively longer periods.
If the period split does not cover the whole planning period, only those periods are displayed that have been defined. The system, however, does read the data for the whole planning period, so that you can display the missing periods by changing the period split in the transaction.
Note
The system can display up to 50 periods.
History
Last changed by/on | SAP | 19980428 |
SAP Release Created in |