SAP ABAP IMG Activity _ISPSFM_N_AVC_BADI01 (BAdI: Enhance Account Assignment Derivation for AVC Control Objects)
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 _ISPSFM_N_AVC_BADI01 BAdI: Enhance Account Assignment Derivation for AVC Control Objects  
Transaction Code S_ALN_01000562   (empty) 
Created on 20020110    
Customizing Attributes _ISPSFM_N_AVC_BADI01   BAdI:Enhance Account Assignment Derivation for Availability Control Objects 
Customizing Activity _ISPSFM_N_AVC_BADI01   BAdI:Enhance Account Assignment Derivation for Availability Control Objects 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FMAVC_DERI_AFMA    

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

Title

Business Add-In: Account Assignment Derivation of AVC Ledger

Use

With this Business Add-In you can enhance the derivation of availability control objects (strategy ID AFMA). It can only be implemented for the Budget Control System (BCS) in Funds Management. The methods of this BAdI are called in function module FMAVC_CALL_DERIVATION_ACO, immediately before or after deriving an availability control object.

Standard settings

SAP does not deliver any implementations of this BAdI. Therefore in the standard release the BAdI is not active.

Activities

If you would like to use additional source fields within your derivation strategy, first add these fields to the structure FMAVC_S_AFMA_ADDRESS_SUPPL in the ABAP Dictionary.

Next, implement this BAdI applying the following steps:

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.

Example

You wish to use the field AUGRP (authorization group) of the commitment item master data records as an additional source field in your derivation strategy:

  1. Add the field AUGRP (data element FM_AUTHGRP) to the include CI_FMAVC_S_AFMA_ADDRESS_SUPPL of the structure FMAVC_S_AFMA_ADDRESS_SUPPL in the ABAP Dictionary.
  2. Activate the structure FMAVC_S_AFMA_ADDRESS_SUPPL.
  3. Implement the method FILL_ADDRESS_SUPPL of the BAdI (see also the sample code for this method):
    1. Read the commitment item master data records, for instance by using the function module FM_COM_ITEM_READ_SINGLE_DATA.
    2. Fill the field AUGRP of structure FMAVC_S_AFMA_ADDRESS_SUPPL.
  4. Activate your BAdI implementation.

Requirements

Recommendation

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