SAP ABAP IMG Activity /TDAG/CP_BADI_005 (BAdI: Enhancement of Request and E-Mail Generation)
Hierarchy
☛ TDAGBCA (Software Component) TechniData Basic Components
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ /TDAG/CP (Package) Compliance for products
IMG Activity
ID /TDAG/CP_BADI_005 BAdI: Enhancement of Request and E-Mail Generation  
Transaction Code /TDAG/80000094   IMG activity: /TDAG/CP_BADI_005 
Created on 20071211    
Customizing Attributes /TDAG/CP_BADI_005   BAdI: Enhancement of Request and E-Mail Generation 
Customizing Activity /TDAG/CP_BADI_005   BAdI: Enhancement of Request and E-Mail Generation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /TDAG/CP_BADI_005    

Use

This Business Add-In (BAdI) is used in the SAP Product and REACH Compliance component. This BAdI enables you to enhance the generation of requests and e-mails. This BAdI provides the following methods:

  • EML_DETERMIN_RECIPIENTS
    You can use this method to determine the recipients for the request e-mails (To, CC, BCC).
  • EML_DETERMIN_SENDER
    You can use this method to determine the sender for request e-mails.
  • EML_EDIT_AND_SEND
    You can use this method to display the send e-mail dialog box.
  • EML_GENERATE_ATTACHMENTS
    You can use this method to generate additional documents to be attached to e-mails.
  • EML_GENERATE_EMAIL_TEXT
    You can use this method to generate the subject and body text of request e-mails.
  • EML_GENERATE_REQFILE (obsolete as of release 2.0)

Requirements

In the Customizing activities Specify Campaign and E-Mail Configuration and Specify Task Categories and Tasks, you have made settings for e-mails, categories, and types.

Standard settings

This Business Add-In is filter dependent. You must specify filter criteria to activate a customer-specific BAdI implementation. You can specify, for example, the request ID. This allows you to create a BAdI implementation that applies only to requests according to the filter criteria.

In the standard system, the Business Add-In is activated. The default code is executed automatically.

BAdI Implementations

/TDAG/CL_DEF_IM_CP_BADI_005 (default implementation)

Recommendation

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

See also

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/CP_BADI_005 0 HLA0100681 Product Safety 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on FLEISCHER  20091013 
SAP Release Created in 222_46C