Ansicht
Dokumentation

FAGL_VAL_CUST_EXIT_B - BAdI: Enhancements for Document Validation

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the General Ledger Accounting (FI-GL) component.

You use this BAdI to implement additional checks during the validation of account assignment combinations. These checks supplement the validation rules defined in the IMG activity Define Validation Rule for Account Assignment Combinations. (For information about how this BAdI is linked with this IMG activity, see the "Prerequisites" section.)

The BAdI is called at the time when the validation strategy takes effect: When a document needs to be posted, the system applies the validation rule that you defined to the account assignments entered in the document, classifies the documents as invalid if necessary, and consequently rejects the posting.

You have defined and activated a validation strategy in the Financial Accounting Global Settings under Define Validation Rules for Account Assignment Combinations. You have selected the step type Enhancement.

You use the import parameters of method CUSTOMER_EXIT to govern how the BAdI is executed. These import parameters transfer the name of the validation strategy as well as the step ID.

The BAdI is not 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 an active implementation.

The BAdI is not filter-dependent.

This BAdI is not intended for multiple use.

After you have called the IMG activity, proceed as follows:

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

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

The present BAdI belongs to enhancement spot ES_FAGL_VAL_CUST.

The present BAdI has the following method: Enhance Document Validation (program FAGL_VALIDATION) (CUSTOMER EXIT).

For more information on validating account assignment combinations, see Customizing for Financial Accounting Global Settings under Define Validation Rule for Account Assignment Combinations.

To include customer fields in the validation of account assignment combinations, you can use the BAdI Mapping ACCIT Fields to Customer Fields.

CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4723 Date: 20240523 Time: 201158     sap01-206 ( 67 ms )