SAP ABAP IMG Activity /LIME/COLLECTOR_ACT (BAdI: Fill LIME Collections)
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/COLLECTOR_ACT BAdI: Fill LIME Collections  
Transaction Code /LIME/86000087   (empty) 
Created on 20021029    
Customizing Attributes /LIME/COLLECTOR_ATT   BAdI: Fill LIME Collections 
Customizing Activity /LIME/COLLECTOR_OBJ   BAdI: Fill LIME Collections 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /LIME/COLLECTOR    

Use

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

The Business Add-In /LIME/COLLECTOR enables you to influence collections for communication with subsequent applications. You can:

  • Extend collections by adding customer-specific fields
  • Flag document items as relevant/irrelevant for the collections
  • Reset fields of a document item in order to aggregate collections

The Business Add-In is a filter-BAdI, so an implementation is necessary for each collection type. The allowed values for the collection types are defined in table /LIME/CUSY_COLL. For example, an implementation for the collection type BW (Business Warehouse) influences the updating of the BW collections in table /LIME/COLL_BW. It is not possible to define customer-specific collection types because this would involve program changes. The collection type LEG (legacy) is reserved for customer developments.

In a second step, the collections are read by the LIME dispatcher and distributed to the subsequent applications. The BAdI /LIME/DISPATCHER is available for the purpose of setting the dispatcher functions. An implementation of the BAdI /LIME/COLLECTOR only makes sense if a corresponding implementation of the BAdI /LIME/DISPATCHER exists.

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

Only the legacy collection (LEG) is provided for the link to external systems. SAP reserves the right to supply a standard implementation for all other collections in future releases.

The methods of the BAdI /LIME/COLLECTOR are called directly after the posting of a goods movement, HU movement, location movement, or stock report in LIME. In LIME, the stock has already been updated and a document generated. The BAdI is not invoked in the case of MAINTAIN functions (function modules /LIME/STOCK_MAINTAIN, /LIME/HU_MAINTAIN, /LIME/LOC_MAINTAIN or in the case of corresponding maintain lines in /LIME/DOCUMENT_POST).

The methods are invoked in the following order:

  1. GET_PARENT
  2. ADD_FIELDS
  3. RELEVANCE_CHECK
  4. CLEAR_FIELDS

The GET_PARENT method is first processed for all lines of the incoming documents. After this, the methods ADD_FIELDS, RELEVANCE_CHECK, and CLEAR_FIELDS are run through for the possible collection records.

Requirements

The collection type must have been activated for the process type in Customizing.

Standard settings

In the standard system supplied, standard implementations for the BW collection and the MMIM collection are active. There is no default implementation.

  • The Business Add-In is active in the standard system. The default code is executed automatically.
  • The Business Add-In can be used more than once. All active implementations are called and executed.
  • The Business Add-In is filter-dependent. Create an implementation for each desired filter category.

Activities

A standard implementation exists for the standard collection types BW and MMIM. You do not need to create an implementation for these collection types.

If you wish to connect an external system to LIME, you must create an implementation for the filter value LEG.

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.

Note that the Business Add-In can be used more than once, therefore all active implementations are called and run.

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

SAP does not supply an example implementation or a default implementation for this BAdI because a standard implementation exists.

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

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

See also

Documentation on BAdI methods:

Population of BAdI Structures for the Collections
ADD_FIELDS

Initialize Fields for Aggregation
CLEAR_FIELDS

Current Line Relevant to Collection
RELEVANCE_CHECK

Determination of Location/HU for Follow-On Application
GET_PARENT

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