SAP ABAP IMG Activity PSM_FM_REQUEST_GL_AC (BAdI: Enhance Derivation of G/L Account)
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 PSM_FM_REQUEST_GL_AC BAdI: Enhance Derivation of G/L Account  
Transaction Code S_ALN_01002173   (empty) 
Created on 20030407    
Customizing Attributes PSM_FM_REQUEST_GL_AC   BAdI: Enhance Derivation of G/L Account 
Customizing Activity PSM_FM_REQUEST_GL_AC   BAdI: Enhance Derivation of G/L Account 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FM_REQUEST_GL_ACC    

Use

You use this Business Add-In (BAdI) to implement your own derivation of G/L account from commitment item, funds center and fund.

The BAdI is mainly called when entering requests. However, the BAdI is also run for programs that use the G/L account determination for requests, for example, when the derivation is configured for earmarked funds.

Starting from Release 1.10, the derivation of the G/L account is supported only in accordance with the commitment item. The funds center or fund are no longer considered with the G/L account determination as this can cause an error to occur in the account assignment when using component CO at the same time. This is due to the flow of account assignment derivations:

Overview of flow of account assignment derivation for requests

  1. Manual entry of account assignments such as commitment item, CO account assignment and so on.
  2. Derivation of G/L account from the commitment item and calling the BAdI
  3. Derivation of more account assignments using the account assignment block and simultaneous calling of the Define Account Assignment Derivation for deriving FM account assignments (for example, funds center from cost center or funds center as default funds center of the respective commitment item).

In accordance with this flow logic (steps 1 - 3), the following problems may occur when using the BAdIs:

  • If you do not enter the funds center in step 1 manually, but it is first derived in step 3, you cannot use the funds center to derive the G/L account in step 2.
  • If you enter the funds center in step one instead, then the G/L account is derived through the activated BAdI depending on step 2. If a different funds center is derived in step 3, the derived G/L account may not match the derived funds center.

If you want to enter a funds center and fund (in spite of the mentioned problems) for the G/L account derivation, you can create a customer- specific implementation using this BAdIs. You can use the coding example of the BAdI delivered by SAP for this. With this coding example the G/L account is derived in accordance with the commitment item, funds center and fund entered in the request.

In this case, you must ensure that:

  1. the funds center or fund of the user necessary for the derivation (step 1) has been entered
  2. the funds center and fund entered are not overwritten by derived values with the account assignment derivation (step 3)

Requirements

Standard settings

The BAdI is not active in the standard delivery.

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.

In order to copy the sample coding example to your customer method, on the initial screen of your implementation, choose Go To -> Coding Example -> Copy.

Example

Notes

Documentation on BAdI method DERIVE_GL_ACCOUNT

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 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030407 
SAP Release Created in 200