SAP ABAP IMG Activity /TDAG/RCS_BADI_013 (BAdI: Input 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_013 BAdI: Input Use Checks  
Transaction Code /TDAG/13000071   (empty) 
Created on 20101126    
Customizing Attributes /TDAG/RCS_BADI_013   BAdI: Input Use Checks 
Customizing Activity /TDAG/RCS_BADI_013   BAdI: Input Use Checks 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /TDAG/RCS_BADI_013    

Use

This Business Add-In (BAdI) is used in SAP Product and REACH Compliance. This BAdI enables you to implement enhanced checks for use data. This BAdI is called when use data is displayed, changed and saved.

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 which comprise in all cases the possibility to check use data and to return messages to the user:

  • CK_INIT_USE
    • This method is used to check use data before it is displayed in the compliance workbench. The following parameters are provided:

Parameter    Type    Description

IR_CALLER    Importing    Reference to calling object

XT_DATA    Changing    Use data for ALV display

XR_USE_SET    Changing    Reference to use set with existing uses

XR_INTERACTIVE_SET    Changing    Reference to use set with interactive uses

XV_FLG_ERROR    Changing    Flag indicating an error

XV_FLG_WARNING    Changing    Flag indicating an warning

XT_MESSAGES    Changing    Message table

  • CK_SAVE_USE
    • This method is used to check use data before it is saved in the compliance workbench or task management. The following parameters are provided:

Parameter    Type    Description

IV_FLG_COMMIT    Importing    Flag indicating whether a commit is executed

IV_FLG_NO_RESET    Importing    Flag indicating whether buffer is reset

IV_FLG_UPDATE_TASK     Importing    Flag indicating whether program is running in update tacts

IV_FLG_UNLOCK    Importing    Flag indicating whether locks are deleted

XT_MESSAGES    Changing    Message table

XV_FLG_ERROR    Changing    Flag indicating an error

  • CK_MODIFY_USE
    • This method is used to check modified use, for example, after use data is changed by a user in the compliance workbench. The following parameters are provided:

Parameter    Type    Description

IR_CALLER    Importing    Reference to calling object

XR_USE_SET    Changing    Reference to use set

XV_FLG_ERROR    Changing    Flag indicating an error

XV_FLG_WARNING    Changing    Flag indicating a warning

XT_MESSAGES    Changing    Message table

  • CK_INPUT
    • This method is used to process the consistency check for use records.

The default implementation of this method considers following situations:
  1. The use is not marked as intermediate use: The use record is checked according the rules which are specified in the Specify Rules for Consistency Check Customizing activity. If the use record does not fulfill the specified rules, the evaluation status is set to Not Relevant automatically. For more information, see the Customizing documentation.
  2. The use is an intermediate use: The consistency check result returns that the use record is valid independent of the applied use descriptors.
    3. The following parameters are provided:

Parameter    Type    Description

IS_USEAPI    Importing    Use record

ES_USEAPI    Exporting    Use record with input check result (fields INPUT_CHECK_VALID and INPUT_CHECK_MSGS are filled) and the evaluation status is set if a rule violation is detected

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_013 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