Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
PS-CRP-WFP (Application Component) Workforce Planning⤷
CYMP (Package) Workforce Planning
Basic Data
| Data Element | CY_PERNUMB |
| Short Description | Number of periods in a period unit |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| 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 | 10 | No.periods |
| Medium | 15 | No. of periods |
| Long | 20 | Number of periods |
| Heading | 6 | NoPer |
Documentation
Definition
Specifies the number of period in the period split that have the corresponding period unit.
Note
The system can display up to 50 periods.
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.
History
| Last changed by/on | SAP | 19990317 |
| SAP Release Created in |
