SAP ABAP IMG Activity WLF_SOA_B2B_OUT_0001 (BAdI for Checking the Sending of an InvoiceRequest Message)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ LO-AB (Application Component) Agency Business (Global Trade)
     ⤷ WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
IMG Activity
ID WLF_SOA_B2B_OUT_0001 BAdI for Checking the Sending of an InvoiceRequest Message  
Transaction Code S_EBS_44000210   (empty) 
Created on 20101112    
Customizing Attributes WLF_SOA_B2B_OUT_0001   BAdI for Checking the Sending of an InvoiceRequest Message 
Customizing Activity WLF_SOA_B2B_OUT_0001   BAdI for Checking the Sending of an InvoiceRequest Message 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name WLF_CHECK_OUTBOUND_EVENT    

Use

Using this Business Add-In, you can check during the outbound process, if an outbound event is really relevant for processing depending on the data of the Agency Business document.

The parameter list of the method CHECK_EVENT of the BAdI interface IF_WLF_CHECK_OUTBOUND_EVENT contains the changing parameter CV_EVT_ALLOWED of type BOOLEAN. This parameter indicates, whether an outbound event should be executed or not. Within a BAdI implementation, the value of this parameter, which is set before by a standard implementation, can be overwritten, either by the value 'X' (execute event) or the value ' ' (do not execute the event).

Requirements

The function module WLF_CHECK_OUTBND_EVENT must be registered for the corresponding entries of Agency Business object types in the SAP Business Workflow tool for event type linkages (transaction SWETYPV).

Standard settings

In the standard system this BAdI is inactive.

There is no default implementation.

Activities

When you call up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already created other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this dialog box, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field and then choose Create. The initial screen for creating BAdI implementations appears.
  2. Enter a short text for the implementation in the Short Text for Implementation field on the initial screen.
  3. From the tab index, choose Interface. The Name of Implemented Class field is filled automatically on this tab page because the system assigns a class name using the name of your implementation.
  4. Save your entries, and assign the implementation to a development class.
  5. Position the cursor on the method and double-click to call up method processing.
  6. Enter the code for the implementation between the statements method <Interface Name> ~ <Name of Method> and endmethod.
  7. Save and activate your code. Return to the Edit Implementation screen.
  8. Save the entries on the Change Implementation screen.
    9. Note: It is also possible to create an implementation for a BAdI first and then activate it later. In this case, end your processing at this point.
  9. Choose Activate. The code you stored in the method will now be run through when the application program is executed.

Example

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  20101112 
SAP Release Created in 606