SAP ABAP IMG Activity WLF_ERROR_CHECK_FUNC (BAdI: Error Handling for API Processing Check Module)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-AB (Application Component) Agency Business (Global Trade)
     ⤷ WZRE (Package) Agency Business
IMG Activity
ID WLF_ERROR_CHECK_FUNC BAdI: Error Handling for API Processing Check Module  
Transaction Code S_E4A_94000099   (empty) 
Created on 20080416    
Customizing Attributes WLF_ERROR_CHECK_FUNC   BAdI: Error Handling for API Processing Check Module 
Customizing Activity WLF_ERROR_CHECK_FUNC   BAdI: Error Handling for API Processing Check Module 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name WLF_ERROR_CHECK_FUNCTIONS    

Use

You can use this BAdI to react to errors in the inbound processing of agency documents via BAPI. The BAdI is called when an error occurs in a check module in BAPI inbound processing (for example: WLF_REGU_CHECK_KUNRE). You can adjust the external data and rerun the check. There is a specific method for each (internal) inbound structure (for example: KOMZRKE).

Requirements

The system calls the BAdI in the event of CREATE and CHANGE BAPIs.

Standard settings

As standard, the Business Add-In is inactive.

The Business Add-In can be used multiple times.

The Business Add-In is filter-dependent. You should create an implementation for each document category.

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.

Example

Within the scope of inbound processing, the system determines in function module WLF_REGU_CHECK_KUNRE that the submitted invoice recipient does not exist.

Usually, processing would be terminated at this point and the document would not be generated. You can use the BAdI method to replace the submitted invoice recipient and generate the document.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired 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  20080416 
SAP Release Created in 604