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 | FLGPL |
Short Description | Indicator: consistent or level-by-level planning |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLGPL | |
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 | Planning |
Medium | 15 | Planning method |
Long | 20 | Planning method |
Heading | 7 | Plng |
Documentation
Definition
Specifies which planning method you want to be used for this information structure. The following planning methods are possible:
- consistent planning (K)
- level-by-level planning (I)
- delta planning (D)
Consistent Planning
In consistent planning, planning levels are interdependent. The user enters data for a characteristic value or characteristic values combination. This data is automatically aggregated and disaggregated up and down the planning hierarchy every time the user regenerates the planning table, for example, by pressing ENTER. The sum of the key figure values at the detailed level (the lowest level in the planning hierarchy) gives the key figure value at the total level (the total level is defined by the characteristic values entered by the user when calling the planning table). Only data at the detailed level is saved on the database.
Level-By-Level Planning
In level-by-level planning, planning data is saved for every characteristic, that is, at every level, of the information structure. The user plans each level separately. Thus, planning levels are independent of each other (although they can still be aggregated and disaggregated if user-defined macros have been created for this purpose).
Delta Planning
In delta planning, planning data is aggregated automatically but not disaggregated.
Dependencies
Do not specify consistent planning for an information structure with the characteristic "product group".
History
Last changed by/on | SAP | 19950401 |
SAP Release Created in |