SAP ABAP IMG Activity FMKU_GROUPING_KEY (BAdI: Define Grouping Key)
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 FMKU_GROUPING_KEY BAdI: Define Grouping Key  
Transaction Code S_ALN_01002030   (empty) 
Created on 20030324    
Customizing Attributes FMKU_GROUPING_KEY   BAdI: Define Grouping Key 
Customizing Activity FMKU_GROUPING_KEY   BAdI: Define Grouping Key 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FMKU_GROUPING_KEY    

Use

Using this Business Add-In (BAdI), you can assign any FM account assignment to a group of FM account assignments, which can be identified by a grouping key. If an active implementation exists, the system ensures that:

  • posting and budget addresses belong to the same group
  • in AVC the grouping keys of budget addresses and the corresponding control objects are identical
  • in the case of residual carryforward, the grouping key of the sender FM account assignment is the same as that of the receiver FM account assignment
  • the mass transfer of residual budget supports only one grouping key for all referenced sender FM account assignments and one for the receiver FM account assignments.

Example

In your FM area, the multi-year budget execution has been activated. The budget ID has been coded into the fund data, so that each fund is uniquely assigned to a budget ID. You need to ensure the following:

  • Every posting object and the corresponding budget object must be assigned to the same budget ID.
  • In availability control, the control object and the corresponding budget objects must have the same budget ID.

You do this by creating an implementation of this BAdI, which returns the budget ID as the grouping key for each FM account assignment.

Requirements

In order to use the grouping key for multi-year budget execution, you must first activate period-based encumbrance tracking (PBET) in the IMG activity Override Update Profile.

Standard settings

Recommendation

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Further notes

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
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 FMKU_GROUPING_KEY 0 ALN0000195 Budgeting 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030707 
SAP Release Created in 200