Hierarchy
⤷ FI-SL-SL (Application Component) Basic Functions
⤷ GPLN (Package) FI-SL planning
Basic Data
Data Element | RPLAN |
Short Description | Plan parameters |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RPLAN | |
Data Type | CHAR | Character String |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
Value Table | T820 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | GPL | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Plan. par. |
Medium | 15 | Plan parameters |
Long | 20 | Plan parameters |
Heading | 9 | Parameter |
Documentation
Definition
Planning parameters define various data, values and settings used in planning. Appropriate transactions are available for maintaining planning parameters.
Planning parameters are divided into one general part and parts specific to Special Purpose Ledger and Profit Center Accounting. The following data is defined in the general part:
- The parameters are grouped together in planning parameter classes which ensures that particular planning parameters can only be used for specific applications (Special Purpose Ledger, Profit Center Accounting).
- You determine the start and end of the periods to be planned.
- You can define the period frequency. If this interval is 1, each period between the from and to period is planned. If you only want to plan every third period, you enter periods 3-12 with period frequency 3 instead of periods 1-12 with period frequency 1.
- In the planning parameters, you can define various default settings. For example, you can enter default settings for distribution keys separated according to quantity and currency field. Additionally, you can specify whether only values, only text, or values and text should be displayed for the characteristics of a dimension.
The Special Purpose Ledger part contains the following information:
- The set ID defines the dimensions to be planned. You can enter basic, single-dimension or multi-dimension sets. You can create and edit the set using the set maintenance transactions.
- In planning, you can store both planned values and planned quantities. The planned values can be stored either in transaction, second and/or third currency, depending on the ledger. If this type of field group is planned manually, the other field groups that are not to be planned manually are determined automatically. In addition to the quantity fields, you can also store additional quantity fields. The planning parameters also define which of the field groups appear first in the overview or period screen.
- To enable currency conversion using exchange rates defined only for planning, you can store an exchange rate type. This exchange rate type determines the kind of conversions in the exchange rate table and is used in planning. The standard SAP system delivers bank buying rate, bank selling rate, and average rate as exchange rate types. However, you do have the option of defining your own exchange rate types which would also be used in planning.
Supplementary Documentation - RPLAN 0001
Use
When copying the plan reference, the following planning parameter components are taken into account:
- From period or to period (general part)
- All the periods of a fiscal year lying between the from period and to period are copied.
- Set ID (FI-GLX part)
- The set entered here determines the data to be read from the data base, and also the dimensions (fields) to be copied.
All other parameters are not taken into account.
Procedure
Examples
You want to use the actual data of the previous year as a reference for the planning data of the following year.
Since the actual data contains detailed information, such as the cost center, but you do not want to use this data in planning, use a planning set that only contains the dimensions 'company code' and 'business area' when you perform the copy function.
When you copy the actual data of the previous year, data will be summarized for all cost centers at the same time.
Dependencies
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |