SAP ABAP IMG Activity SIMG_MM_DETITEMREL (BAdI: Relevance Determination on Document Item Level)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   LO-AB-IFW (Application Component) Invoice Forecasting
     CIWB (Package) Invoice Forecasting Worklist: Core objects
IMG Activity
ID SIMG_MM_DETITEMREL BAdI: Relevance Determination on Document Item Level  
Transaction Code S_EBS_44000352   (empty) 
Created on 20110119    
Customizing Attributes SIMG_MM_DETITEMREL   BAdI: Relevance Determination on Document Item Level 
Customizing Activity BADI_ITEMRELDETERM   BAdI: Relevance Determination on Document Item Level 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ITEM_RELVANCE_DETERMINATION    

Use

This Business Add-In (BAdI) is used in the components Treasury and Risk Management Integration (LO-INT-TRM), Sales (SD-SLS), and Purchasing (MM-PUR). The BAdI ITEM_RELVANCE_DETERMINATION is designed to provide a single point of entry for the commodity relevance determination.

Through the inferface IF_RELEVANCE_DETERMINATION, the BAdI provides you with various methods for determining the commodity relevance.

When generating a BAdI, the system uses a filter that is based on the source document type. Therefore, depending on the source document type (for example, trading contract, purchase order, purchase contract, sales order), you can implement your own, application-specific, logic.

Requirements

Standard settings

For more information about the standard settings (filters, single, or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

BAdI Implementations

  • LOG_SO_COMMODITY_RELEVANCE
    Commodity Relevance: Sales Orders and Sales Contracts
  • LOG_PO_COMMODITY_RELEVANCE
    Commodity Relevance: Purchase Order Item

    Note:

    When determining whether a purchase order item is relevant for differential invoicing, the default implementation LOG_PO_COMMODITY_RELEVANCE uses the filter value 02 Purchase Order and proceeds as follows:

    • The purchase order item is indicated as Relevant if you have set the value Relevant in the Differential Invoicing field in the associated info record.
    • The purchase order item is indicated as Not Relevant if you have set the value Not Relevant in the Differential Invoicing field in the associated info record or if no info record is available.

      If you deactivate the default implementation, the system handles the purchase order items as NOT relevant for differential invoicing. If you have your own customer implementation you should deactivate the default implementation.

      Note that the commodity relevance determination for differential invoicing is subject to some restrictions in the current release version. For information about this, see SAP Note 1584025 and the restriction documentation attached to this SAP Note.

  • LOG_MM_CTR_COMMODITY_RELEVANCE
    Commodity Relevance: Purchase Contract Item

Activities

For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

See also

BAdI method documentation:

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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  20111214 
SAP Release Created in 606