Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KC (Package) Cost Accounting Controlling EIS
IMG Activity
| ID | OKCM_KCP7 | Create planning layout |
| Transaction Code | S_ALR_87000179 | IMG Activity: OKCM_KCP7 |
| Created on | 19981222 | |
| Customizing Attributes | OKCM_KCP7 | Create planning layout |
| Customizing Activity | OKCM_KCP7 | Create planning layout |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OKCM_KCP7 |
In this step, you define the planning layout or change those that are already available.
With the planning layout you determine what is contained in the header, rows and columns (elements) of the planning screen, depending on the business requirements of your planning.
You define the planning layout in a similar way to how you define a Layout for the entry of actual data.
The following differences to the creation of a data entry layout exist:
Cross-fiscal year planning
So that it is possible to plan cross-fiscal year data, enter a charact- eristic 'Period/fiscal year', such as 012.1997 instead of 'Period' and 'Fiscal year'. This allows for a rolling planning with the entry of the time frame 010.1997 to 003.1998, for example.
Plan and actual versions
You can enter plan data for a version in a planning layout. Plan data of other versions or actual data can be displayed as reference data.
If you include the plan/actual indicator in the general data selections, you must restrict it to plan data.
Seasonal distribution
In the planning layout, you have an additional attribute column. Apart from the unit column, you can insert a distribution key. Therefore, you distribute cumulated values to period values. Using the distribution key you have the possibility of displaying seasonal trends using the plan periods of a fiscal year. If you do not select the attribute 'Distribution key' for a column, an analog distribution takes place, meaning if no data is available yet, you get an even distribution. If data is available, the distribution is similar to this (see also Creating distribution keys).
Calculated key figures
You can include not only characteristics and basic key figures in the rows and columns in a planning layout, but also calculated key figures, meaning key figures that are stored as formulas. For example, sales per employee or contribution margin. In planning, the time-based aggregation rules SUM, AVG, LAS, NOP and the non-time-based aggregation rule SUM are supported. Therefore, you should only use calculated key figures that have been defined with these aggregation rules.
In the planning session you can change calculated key figures which consist of a ratio, for example, price (revenue/sales quantity). If you change the price, the revenue will be redetermined automatically within the planning session. You can find more information on this in the online documentation on Business Planning.
Formulas in the planning layout
You have the opportunity to define formulas in the planning layout, that calculate values from other columns or rows in the planning session. Both basic key figures and calculated key figures are supported as formula components. Two types of formula are supported in the planning layout:
- Formula column
- Inverse formula
- Definition of a formula column or row
Proceed as follows to define a formula column, meaning a value column that results from values of already defined columns:
Double-click on the free field to of a value column and select "Formula" as element type. In the following window you can create a calculation formula from the already defined value columns that are offered to you there; using the formula components. The column is automatically set to 'not ready for input'. - Definition of an inverse formula
In planning, an inverse formula allows you to enter values in a formula column from which the system calculates the values of an other column of the planning layout, for example the sales revenue can result from the sales quantity and the price. The price is not a calculated key figure on the database and is ready for input in the layout:
Example
Value column 1: (ready for input) Price (plan sales/plan quantity)
Value column 2: (calculated) Plan sales
To define an inverse formula proceed as follows: - Create a column 'plan quantity' and a column 'plan sales'.
- Create a formula column 'Price' (plan sales/plan quantity) as described above.
- Using 'Format -> Readiness for input on/off' make column 'price' ready for input.
- Highlight the column 'plan sales' and select 'Inv. formula'.
- Enter the inverse formula (Price * plan quantity).
- Make the column 'plan sales' not ready for input.
The price can be entered in the planning session, but is not saved on the database. In the planning layout you determine that a database field should be calculated from it. In the example, this is the plan revenue, which should only be displayed for information purposes.
Navigation attributes
In planning you can specify fixed navigation attributes using the general selections or define them as variables for the selection. Note that, since the attributes are non-chargeable, the underlying characteristic in the planning layout nust be specified. This function enables the selection of data for the planning session using an attribute, for example, you can select the plan data for customers using the attributes country and sales region. You can find further information on the maintenance of attributes under Navigation attributes.
Master data hierarchies in planning
For characteristics which are assigned to a EC-EIS or EC-BP master data hierarchy, you can enter a hierarchy node or variable instead of a characteristic value or variable. You can also specify a hierarchy node in the general selections or enter one as a variable for the selection. If you wish to create a variable you must still specify the hierarchy variant.
Note that, since the nodes are non-chargeable, the underlying characteristic in the planning layout nust be specified.
Further notes
Business Attributes
| ASAP Roadmap ID | 261 | Define Screen Control |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OKCM_KCP7 | 0 | HLA0009470 | Business Planning |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| IMGDUMMY | D - Dummy object | KCP7 | KCP7 | Create Planning Layout | ||
| IMGDUMMY | D - Dummy object | KCP8 | KCP8 | Change planning Layout | ||
| IMGDUMMY | D - Dummy object | KCP9 | KCP9 | Display planning layout |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
