SAP ABAP IMG Activity /LIME/DISPATCHER_ACT (BAdI: Distribution of LIME Documents)
Hierarchy
SAP_AP (Software Component) SAP Application Platform
   AP-LIM (Application Component) AP-LIM Logistics Inventory Management Engine
     /LIME/RFC_CORE (Package) Core Package of the RFC Interface
IMG Activity
ID /LIME/DISPATCHER_ACT BAdI: Distribution of LIME Documents  
Transaction Code /LIME/86000096   (empty) 
Created on 20021113    
Customizing Attributes /LIME/DISPATCHER_ATT   BAdI: Distribution of LIME Documents 
Customizing Activity /LIME/DISPATCHER_OBJ   BAdI: Distribution of LIME Documents 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /LIME/DISPATCHER    

Use

This Business Add-In (BAdI) is used in component SCM-ECT-LIM.

With BAdI /LIME/DISPATCHER, the collections are transferred to the subsequent applications. The communication can take place both snychronously and asynchronously with program /LIME/DISPATCHER_EXEC. The LIME documents to be sent are first combined in BAdI /LIME/COLLECTOR for each application.

The Business Add-In /LIME/DISPATCHER is a filter BAdI, in other words, an implementation is necessary for each subsequent application and communication type. For each application (collection type), the standard system only supports one communication type. The allowed filter values are defined in table LIME/CUSY_FLTDI. The decision about which filter value will be run by the implementation of the BAdI for a particular collection type, is made according to the Customizing data of the IMG activity Set Filter Values for Dispatcher (/LIME/V_CUST_FDR).

An implementation of BAdI /LIME/DISPATCHER is only useful when a corresponding implementation of BAdI /LIME/COLLECTOR exists.

In the standard system, there are currently only collector/dispatcher functions intended for SAP R/3 MMIM and for SAP BW. SAP delivers standard implementations for BAdI /LIME/COLLECTOR and service classes for BAdI /LIME/DISPATCHER for both collection types.

BAdI /LIME/COLLECTOR and therefore also BAdI /LIME/DISPATCHER is not called for MAINTAIN functions (function modules /LIME/STOCK_MAINTAIN, /LIME/HU_MAINTAIN, /LIME/LOC_MAINTAIN or corresponding Maintain lines in /LIME/DOCUMENT_POST).

The methods are called when posting a goods movement in the following sequence:

  • SET_DISPATCH_IMMEDIATELY
  • SET_COLLECTION
  • TAKE_NO_FROM_NORANGE
  • SET_DISPATCH_EXT_DOC
  • CALL
  • GET_COLL_DISPATCHED

With method SET_DISPATCH_IMMEDIATELY, the user implementing the BAdI receives the information about whether the implementation was just called in a synchronous process or from programm /LIME/DISPATCHER_EXEC. This information is important for a possible COMMIT control within the BAdI implementation. In the case of a synchronous dispatcher call, a COMMIT WORK should not be implemented within the implementation, as this can lead to inconsistent and incomplete data. The COMMIT WORK is executed in this case by the calling application.

The method SET_COLLECTION transfers the collections to be dispatched to the user who is implementing the BAdI.

The TAKE_NO_FROM_NORANGE and SET_DISPATCH_EXT_DOC methods provide the user implementing the BAdI with a number range service. This is then useful when a document-related link from the LIME inbound document to the document for the subsequent application is required.

With method TAKE_NO_FROM_NORANGE, you can transfer the information that you want to use this service, and with method SET_DISPATCH_EXT_DOC you will receive a number that was determined for number range object /LIME/DIEX. This can then be transferred to the subsequent application as an external number.

In method CALL, the call for the subsequent application or the actual sending of data to the subsequent application is to be implemented.

The method GET_COLL_DISPATCHED is for returning the information to the calling program, which collections could be sent successfully, and with which external document number this is transferred to the subseqent application.

Requirements

In Customizing, the subsequent application (= collection type) must be activated for the process type.

Standard settings

In the standard system, only one communication type is supported for each subsequent application (collection type).

Activities

To activate the Business Add-In, you must create an active implementation. To do so, go to Customizing and choose the relevant IMG activity under Business Add-Ins (BAdIs).

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.

For more information, see the SAP Library under SAP Web Application Server -> ABAP Workbench (BC-DWB) -> Changing the SAP Standard (BC) -> Business Add-Ins -> Implementing Business Add-Ins.

Example

To display default code, choose Goto -> Default Code -> Display.

To display example code, choose Goto -> Example Code -> Display.

See also

You can also call the documentation for a BAdI method from the menu:

  1. Select tab page Interface.
  2. Double-click on the corresponding method.
  3. Click the right-hand mouse button and choose Documentation on Component.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030205 
SAP Release Created in 401