Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCP2 (Package) R/3 application development: Sales & Operations Planning
Basic Data
Data Element | PLPER |
Short Description | Maintain planning periods in Customizing |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR01 | |
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 | Plng perds |
Medium | 19 | Planning periods |
Long | 22 | Planning periods |
Heading | 22 | Planning periods |
Documentation
Definition
Indicates which period indicators can be used to plan this information structure.
If the planning method is consistent planning, you can plan this information structure using more than one period indicator. For these period indicators, you generate a technical period that is saved in the form of a fiscal year variant. The following example explains how to plan in weeks and months.
Example
- Set the information structure parameters for this function in Set parameters of info structures and key figures as follows:
- Press F4 on the Planning periods field. (The Storage periodicity field is not ready for input.)
- In the planning periods box on the next screen, enter 'W' and 'M' in the PI column.
- Enter a name for your technical fiscal year variant. This name should consist of two letters.
- Enter a generation horizon. This horizon should encompass the planning horizon - both past and future periods - that you wish to plan with this information structure.
- Save these settings.
If you intend to plan using just one period indicator, do only steps (1a), (1b), and (1e). The period indicator that you enter in (1b) is then saved as the storage periodicity.
- Exactly which weeks and which months are displayed in the planning table depends on the time buckets grid. A time buckets grid specifies the number and sequence of the time buckets that you wish to plan. You define and assign a time buckets grid in the planning type.
Create a time buckets grid in your planning type as follows:
- Create the following time buckets grid for future periods:
Selection Sequence Number Remaining
Weeks 1 4
Months 2 11 x
- Create the following time buckets grid for historical periods:
Selection Sequence Number Remaining
Months 2 11 x
Weeks 1 4
The planning table looks like this:
11 months|4 weeks || 4 weeks|11 months
--------------------------------------------------------->
Historical periods Future periods
Further notes
You can only create a time buckets grid if your technical fiscal year variant contains more than one period indicator.
You cannot use "T" (days) in a time buckets grid.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in |