SAP ABAP IMG Activity /TDAG/RCS_BADI_014 (BAdI: Duplicate Use Checks)
Hierarchy
☛ TDAGBCA (Software Component) TechniData Basic Components
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ /TDAG/RCS (Package) REACH Compliance - General
IMG Activity
ID /TDAG/RCS_BADI_014 BAdI: Duplicate Use Checks  
Transaction Code /TDAG/13000072   (empty) 
Created on 20101126    
Customizing Attributes /TDAG/RCS_BADI_014   BAdI: Duplicate Use Checks 
Customizing Activity /TDAG/RCS_BADI_014   BAdI: Duplicate Use Checks 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /TDAG/RCS_BADI_014    

Use

This Business Add-In (BAdI) is used in SAP Product and REACH Compliance. This BAdI enables you to implement a different handling for your use data. This BAdI is called in the determination check and the coverage check.

Requirements

Standard settings

In the standard system, the Business Add-In is activated. The default code is executed automatically. If you activate your own implementation, the default code is deactivated automatically. The BAdI is not filter-dependent.

The following methods are provided to enable use data to be handled in a different way:

  • AGGREGATE_USE
    • This method is called during the determination check. It can be used to manipulate the use data stored for each customer before it is forwarded to the use set on the product level. The following parameters are provided:

Parameter    Type    Description

IR_USESET_CUST_USES    Importing    Reference to use set with customer uses

IS_BOS_PARENT    Importing    BOS explosion

XR_USESET_REAL_SUB    Changing    Reference to use set with product uses

XV_FLG_ERROR    Changing    Flag indicating an error

XT_MESSAGES    Changing    Message table

  • COMBINE_USE
    • This method is called during the coverage check. Within this BADI the combine logic between uses of a product can be adjusted. The combine logic covers the comparison of uses on different levels. The following parameters are provided:

Parameter    Type    Description

IR_USESET    Importing    Reference to use set with uses to combine

ER_USESET_COMBINED    Exporting    Reference to use set with combined uses

XV_FLG_ERROR    Changing    Flag indicating an error

XT_MESSAGES    Changing    Message table

  • DRILLDOWN_USE
    • This method is called during the coverage check. It can be used to change the handling of use data when use data is forwarded from a product to its component. The following parameters are provided:

Parameter    Type    Description

IR_USESET_FATHER    Importing    Reference to use set with parent uses

IR_USESET_CURRENT    Importing    Reference to use set with child uses

ER_USESET_CURRENT    Exporting    Reference to use set with resulting child uses

XV_FLG_ERROR    Changing    Flag indicating an error

XT_MESSAGES    Changing    Message table

  • ADJUST_REG_STATUS
    • This method is called during the coverage check. It can be used to adjust the logic for how the registration status is forwarded to the product level. The following parameters are provided:

Parameter    Type    Description

IR_USESET_COMBINED    Importing    Reference to use set with combined uses

IV_FLG_IGNORE_CUST    Importing    Flag indicating that customer uses are to be ignored

IV_FLG_PURCHASED_PART    Importing    Flag indicating a purchase part

XR_USESET_CURRENT    Changing    Reference to use set with resulting uses

XV_FLG_ERROR    Changing    Flag indicating an error

XT_MESSAGES    Changing    Message table

Activities

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.

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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /TDAG/RCS_BADI_014 0 HLA0100681 Product Safety 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on ANDREE  20101223 
SAP Release Created in 200_600