SAP ABAP IMG Activity BADI_EHSB_RC_GET_TEX (BAdI: Read Language-Dependent Description for Technical IDs)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-BD-CCK (Application Component) Compliance Check
     ⤷ CBBA_REGCOMPL (Package) Compliance Check
IMG Activity
ID BADI_EHSB_RC_GET_TEX BAdI: Read Language-Dependent Description for Technical IDs  
Transaction Code S_PRN_53000760   (empty) 
Created on 20070410    
Customizing Attributes BADI_EHSB_RC_GET_TEX   BAdI: Read Language-Dependent Description for Technical IDs 
Customizing Activity BADI_EHSB_RC_GET_TEX   BAdI: Read Language-Dependent Description for Technical IDs 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_EHSB_RC_GET_TEXT_DESCR    

Use

This Business Add-In (BAdI) is used in the Compliance Check (EHS-BD-CCK) component.

This BAdI is used to determine the language-dependent descriptions of the constraint types. The system uses the language-dependent descriptions in the detailed result of the check when it displays the status of the constraints.

The following constraint types are available in the standard system:

  • PROH (Prohibited)
  • REST (Restricted)
  • COMP (Required)
  • QPOS (Qualitatively positive)
  • QNEG (Qualitatively negative)

When you create a new constraint type, you have to integrate the corresponding language-dependent description using an implementation of the BAdI.

Requirements

Standard settings

The default implementation CL_EHSB_RC_GET_TEXT_DESCR is active in the standard system.

The BAdI is not intended for multiple use.

The BAdI is not dependent on a filter.

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.

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

To display the sample code, select the example displayed in the Implementation Examples screen area of the BAdI Builder.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
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  20070410 
SAP Release Created in 700