SAP ABAP IMG Activity _ISPSFM_N_AVC_BADI02 (BAdI: Enhance Derivation Strategy for Tolerance Profile of AVC Ledger)
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_BADI02 BAdI: Enhance Derivation Strategy for Tolerance Profile of AVC Ledger  
Transaction Code S_ALN_01000573   (empty) 
Created on 20020115    
Customizing Attributes _ISPSFM_N_AVC_BADI02   BAdI: Enhance Derivation Strategy for Tolerance Profile of AVC Ledger 
Customizing Activity _ISPSFM_N_AVC_BADI02   BAdI: Enhance Derivation Strategy for Tolerance Profile of AVC Ledger 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FMAVC_DERI_AFMT    

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

Title

Business Add-In: Derivation of Tolerance Profile for AVC Ledger

Use

With this Business Add-In you can enhance the derivation of tolerance profiles (strategy ID AFMT). It can only be implemented for Funds Management, component Budget Control System (BCS). The methods of this BAdI are called in function module FMAVC_CALL_DERIVATION_TOLPROF, immediately before or after deriving a tolerance profile.

Standard settings

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

Activities

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

Now 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_AFMT_ACO_ADDR_SUPPL of the structure FMAVC_S_AFMT_ACO_ADDRESS_SUPPL in the ABAP Dictionary.
  2. Activate the structure FMAVC_S_AFMT_ACO_ADDRESS_SUPPL.
  3. Implement the method FILL_ACO_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_AFMT_ACO_ADDRESS_SUPPL.
  4. Activate your BAdI implementation.

Requirements

Recommendation

Further notes

Documentation for the BAdI method FILL_ACO_ADDRESS_SUPPL

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