SAP ABAP IMG Activity FAGL_VAL_MAPPING_BAD (BAdI: Mapping ACCIT Fields to Customer Fields)
Hierarchy
SAP_FIN (Software Component) SAP_FIN
   FI-GL (Application Component) General Ledger Accounting
     FAGL_POSTING_SERV_EHP3 (Package) Services for Posting FI Documents (EhP3)
IMG Activity
ID FAGL_VAL_MAPPING_BAD BAdI: Mapping ACCIT Fields to Customer Fields  
Transaction Code S_EB5_05000566   (empty) 
Created on 20091209    
Customizing Attributes FAGL_VAL_MAPPING_BAD   BAdI: Mapping ACCIT Fields to Customer Fields 
Customizing Activity FAGL_VAL_MAPPING_BAD   BAdI: Mapping ACCIT Fields to Customer Fields 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAGL_VAL_MAPPING_BADI    

Use

This Business Add-In (BAdI) is used in the component General Ledger Accounting (FI-GL) (New) to include customer fields in the validation of account assignment combinations.

Furthermore, you can use this BAdI to map fields from structure Interface to Accounting: Item Information (ACCIT) to customer fields that you have defined in the customer namespace in customer include structure CI_FAGL_VAL_DERIVE_SRC_ADD.

The BAdI is called before the validation check is performed. You define this validation check in the Financial Accounting Global Settings (New) under Define Validation Rule for Account Assignment Combinations.

Requirements

In the customer namespace, you have defined customer fields in customer include structure CI_FAGL_VAL_DERIVE_SRC_ADD.

Standard settings

The BAdI is nicht activated in the standard delivery.

If the BAdI is activated without any changes, this has no effect on the program.

No default program code is executed if you do not have any implementation.

The BAdI is not filter-dependent.

This BAdI is not intended for multiple use.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

For example program code, see implementation example class CL_FAGL_VAL_MAPPING_EXAMPLE.

To display the example program, choose Goto -> Sample Code -> Display.

See also

The present BAdI belongs to enhancement spot ES_FAGL_VAL_CUST.

The present BAdI has the following method: Map ACCIT Fields to Customer Fields (MAPPING_FIELDS).

For more information on validating account assignment combinations, see the Implementation Guide for Financial Accounting Global Settings (New) under Define Validation Rule for Account Assignment Combinations. To define additional checks that extend beyond the available validation rules, you can use the BAdI Enhancements for Document Validation (FAGL_VAL_CUST_EXIT_BADI).

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
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  20091209 
SAP Release Created in 605