SAP ABAP IMG Activity BW_BCT_PLM_MCB01 (Define Planning Scenarios and Budgeting Methods)
Hierarchy
☛ BI_CONT (Software Component) Business Intelligence Content
   ⤷ BW-BCT-PLA-MCB (Application Component) PLM Maintenance Cost Budgeting
     ⤷ UPA_MCB (Package) Planning Application PLM Maintenance Cost Budgeting (MCB)
IMG Activity
ID BW_BCT_PLM_MCB01 Define Planning Scenarios and Budgeting Methods  
Transaction Code S_B52_73000034   (empty) 
Created on 20040310    
Customizing Attributes BW_BCT_PLM_MCB01   Define Planning Scenarios and Budgeting Methods 
Customizing Activity BW_BCT_PLM_MCB01   Define Planning Scenarios and Budgeting Methods 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BW_BCT_PLM_MCB01    

Use

In this IMG activity you configure the budgeting method and the corresponding planning scenarios. You need these settings for the Definition of the Planning Application.

SAP provides standard settings that are used for defining the standard application for the budget planning (Planungsgebiet 4MCBA004), in particular.

The following individual configurations are available:

  • Configuration of the budgeting method for defining (both) the basic options for creating a budget:
    • History-based budgeting method: Creation of a budget on the basis of historic data (particularly on the basis of historic actual costs from maintenance and service orders)
    • Zero-based budgeting method: Creation of a budget on the basis of simulated planned costs (particularly on the basis of the tasks planned in the task lists and maintenance plans)

      Note that you should not change the budgeting method within your Customizing activities, particularly not if you want to use the planning application (4MCBA004) provided.

  • Configuration of planning scenarios within a budgeting method:
    • Actual costs (Hist)
    • Ad-hoc (Hist)
    • Maintenance plan (Zero)
    • Task list (Zero)
    • Ad-hoc (Zero)

      Note that you should not change the planning scenarios within your Customizing activities, particularly not if you want to use the planning application (4MCBA004) provided.

  • Restriction of the planning scenario to certain budget categories
  • Restriction of the planning scenario to certain budget uses

To recapitulate, changing (enhancing) the standard settings is only advisable in certain cases, such as:

  • You want to enhance the planning application provided by SAP by, for example, defining some restrictions of the planning scenarios to certain budget categories and budget uses.
  • You want to create a customer-specific planning application and still use the existing Customizing logic or the overlying access logic in the BPS (using exit variables, whose value determination is implemented in the function group UPA_MCB_01.

If you want to make enhancements in the standard Customizing, make them in the customer namespace. That is, they should start with 9, x, y, or z. If possible, you should not delete the settings in the SAP namespace, as otherwise we cannot guarantee the smooth functioning of the planning application delivered.

However, there are no namespace conventions for restricting the planning scenarios to certain budget categories or budget uses. That is, you can delete the standard settings, if necessary.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 899   not to be assigned 
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 BW_BCT_PLM_MCB01 0 ARS0000023 Business Content and Extractors 
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
UPA_MCB_01VC C - View cluster SM34  
History
Last changed by/on SAP  20040324 
SAP Release Created in 352