SAP ABAP IMG Activity BCS_VC_FMPEP_CUST (Define Layout for Multiple Budget Entry)
Hierarchy
☛ EA-PS (Software Component) SAP Enterprise Extension Public Services
   ⤷ PSM-FM-MD (Application Component) Master Data
     ⤷ FMCC (Package) FIFM: Cash budget management customizing
IMG Activity
ID BCS_VC_FMPEP_CUST Define Layout for Multiple Budget Entry  
Transaction Code S_AEN_10000278   (empty) 
Created on 20050114    
Customizing Attributes BCS_VC_FMPEP_CUST   Define Layout for Multiple Budget Entry 
Customizing Activity BCS_VC_FMPEP_CUST   Define Layout for Multiple Budget Entry 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BCS_VC_FMPEP_CUST    

Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).

Use

In this IMG activity, you can define one or several layouts for the multiple budget entry transaction FMPEP. This transaction enables you to maintain budget for several budget categories on one screen, as well as select between different types of database update (additive/non-additive modes) for budgeting.

Requirements

Standard settings

The following standard layouts beginning with SAP* are predelivered:

  • SAP001    Posted Payment Budget
  • SAP002     Payment and Commitment Budgets
    This layout can be used to enter the payment budget for the current fiscal year and the commitment budget for the four following years of cash effectivity.
  • SAP005    Payment Budget Preposted
    This layout can be used to create preposted entry documents. The documents can be posted in the Budgeting Workbench.
  • SAP006    RECHNUNGSERG
    This layout can be used in the context of the financial result scenario. See Release Note Financial Result for further information.

Activities

You can define as many layouts as you want:

  1. In order to define a new layout, click on New Entries and enter a name starting with Y or Z.
  2. Select the line you created and click on Header.
  3. Assign values to the parameters belonging to the header section of transaction FMPEP.
  4. Save the header data.
  5. Next, double click on Tabstrips to define one or several tabstrips, and activate them. At present, only one tabstrip can be used. The tabstrips allow you to group individual columns into different categories. If you do not want to split your set of columns, create only one tabstrip.
  6. Save the tabstrip data.
  7. Then define the contents of individual columns for each created tabstrip: select the desired tabstrip and double-click on Entry Columns or Display Columns. Entry columns are columns for which a parameter has to be entered by the user, while display columns are columns used to display the value of a predefined key figure, for example. Display columns are greyed out in Tr. FMPEP.
  8. Create as many entry columns and display columns as you want. Note that you must number your columns sequentially, that is, you cannot use "1" as the column header more than once. You must start numbering with the number '"01" and create numbers sequentially without any gap.
  9. By scrolling to the right, you can enter up to four predefined text variables, containing, for example, the budget categories and/or fiscal years that you will be using (available for Entry Columns only)
  10. Save your entries individually for the entry columns and for the display columns.
  11. Repeat the last three operations for each tabstrip you have created.

Consistency checks on columns

Some checks are performed on the entry and display columns each time you save your data. These checks are intended to prevent you from creating inconsistent columns, such as duplicate columns. When creating your columns, follow these rules:

  • Do not create exact duplicate columns (columns whose values in all fields are identical)
  • When using the # metavalue in a field (user input required) of an entry column, be careful not to define another column with a standard value in the same field and with all other fields identical. See the example below.

If you do not observe these rules, you will receive error or warning messages.

Example

Example of redundant columns which trigger a warning message:

Column    Budget Category    Fiscal Year    YCE    Value Type    Budget Type

1    Payment    #    2006    Budget    BT01

2    Payment    2005    2006    Budget    BT01

3    Payment    2006    2006    #    #

All three columns are potentially redundant, because an inappropriate entry in place of the # metavalue can lead to duplicate columns.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
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 BCS_VC_FMPEP_CUST 0 ALN0000195 Budgeting 
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
VC_FMPEP_CUST C - View cluster SM34  
History
Last changed by/on SAP  20050207 
SAP Release Created in 600