Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KE1C (Package) Customizing for Profit Center Accounting
IMG Activity
| ID | SIMG_CFMENUORK17KEA | Maintain Planning Layout for Costs/Revenues |
| Transaction Code | S_ALR_87003677 | IMG Activity: SIMG_CFMENUORK17KEA |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORK17KEA | Maintain Planning Layout for Costs/Revenues |
| Customizing Activity | SIMG_CFMENUORK17KEA | Maintain Planning Layout for Costs/Revenues |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORK17KEA |
Here you can define or change planning layouts for planning costs and revenues.
In order to be used for planning costs and revenues, the layout must contain the following characteristics:
- Profit center
- Account
- Fiscal year
- Period
- Company code
- Version
You must specify a characteristic value, a group, an interval, or a variable for each of these characteristics. If you specify a variable, it must be a mandatory variable, so that users are required to specify a value in planning.
The plan/actual indicator lets you distinguish between plan and actual data in the layout. If you do not want to display any actual data, you do not need to choose this characteristic at all. Otherwise you need to specify a plan/actual indicator for each row or for each column of the layout. For plan data, you must specify a version for each row or column, while for actual data, you cannot specify a version.
The characteristics "Functional area", "Partner profit center" "Partner company", "Representative material", "Plant", "Object class", and "Quantity unit" are optional in the layout and can be defined as optional variables. In that case, users do not need to specify a characteristic in planning.
Note that the partner profit center is used to eliminate internal business in the information system and consolidation. If you want to plan values that should NOT be eliminated when you analyze a highly summarized profit center group, do not plan these values in a layout that contains the partner profit center, even if you do know the partner profit center. (Example: planning direct consumption in profit center P1 from the inventory in profit center P2).
The characteristic "Origin object" is optional, though it must be specified if used in the layout. If you wish to summarize data across the origin object, it cannot be contained in the layout as a characteristic.
You must define at least one key figure that contains currency amounts in your planning layout. If you choose the key figure "Transaction currency", you must specify the transaction currency (or currencies) in which you want to plan. Note that the system only records the transaction currency if you explicitly enter one. Otherwise the data is updated without a value in the transaction currency.
In addition to currency amounts, you can also plan quantities. However, you cannot plan quantities without a corresponding currency value. If you want to plan quantities, you should also choose the characteristic "Quantity unit" in the layout. If you do not specify a quantity unit for a quantity, the system updates the quantities without a unit. Note that once you have entered plan quantities without a unit, you can later change the quantity but cannot specify a unit.
You can display actual values as well as balance sheet accounts in layouts for planning costs and revenues. You can also use them to calculate other amounts. However, these values are locked so that you cannot manually enter or change them.
In the standard R/3 System, planning layouts only exist in client "000". To be able to use these as templates for your own planning layouts, you need to import them to the client you are using.
Activities
- Create planning layouts for planning costs and revenues.
- Change an existing planning layout.
Additional information
How to define a planning layout
Notes on transporting
A separate function is available in Customizing for transporting planning layouts.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 259 | Establish Forms and Messages |
| 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 | SIMG_CFMENUORK17KEA | 0 | HLA0001516 | Plan Data |
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 |
| 7KEA | T - Individual transaction object | 7KEA | 7KEA | Create planning layout for costs/revenues | ||
| 7KEA | T - Individual transaction object | 7KEB | 7KEB | Change planning layout for costs/revenues | ||
| 7KEA | T - Individual transaction object | 7KEC | 7KEC | Display planning layout for costs/revenues |
History
| Last changed by/on | SAP | 19990226 |
| SAP Release Created in |
