SAP ABAP IMG Activity /LIME/DOC_CHECK_ACT (BAdI: Static Checks of Inbound 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/DOC_CHECK_ACT BAdI: Static Checks of Inbound Documents  
Transaction Code /LIME/86000093   (empty) 
Created on 20021030    
Customizing Attributes /LIME/DOC_CHECK_ATT   BAdI: Static Checks of Inbound Documents 
Customizing Activity /LIME/DOC_CHECK_OBJ   BAdI: Static Checks of Inbound Documents 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /LIME/DOC_CHECK    

Use

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

With this BAdI, you can check the LIME inbound documents for accuracy, and terminate processing in the event of errors.

The BAdI makes the method CHECK_DOC available, which is called in LIME prior to execution. The interface /LIME/IF_PN is passed on to the method CHECK_DOC. This interface facilitates access to the inbound document via appropriate GET methods.

The BAdI is called for different categories of inbound documents:

In accordance with the calling function module, you obtain the information on the inbound document via the associated GET methods. In this way, for example, you get location maintain lines via the method GET_LOC_MAINT_ITEM, goods movement lines via the method GET_ITEM, and so on.

You can interrupt the processing of the document by triggering an exception of the category /LIME/CX_BADI. This exception is logged in LIME.

Requirements

Depending on the process type, you can deactivate the BAdI call. However, this is not a Customizing setting - a modification of the SAP source code is necessary.

Standard settings

  • In the standard system, the Business Add-In is active.
  • There is no default implementation.

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

The example implementation of the BAdI ensures that stocks are updated with VSI=A (Virtual Stock Indicator) only via 'absolute stock postings'.

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  20031021 
SAP Release Created in 401