SAP ABAP IMG Activity /TDAG/CP_IMDS_BADI_2 (BAdI: Customer IMDS Communication)
Hierarchy
☛ TDAGBCA (Software Component) TechniData Basic Components
   ⤷ EHS (Application Component) Environment, Health and Safety
     ⤷ /TDAG/CP_IMDS (Package) IMDS Advanced Interface Integration
IMG Activity
ID /TDAG/CP_IMDS_BADI_2 BAdI: Customer IMDS Communication  
Transaction Code /TDAG/13000062   (empty) 
Created on 20101014    
Customizing Attributes /TDAG/CP_IMDS_BADI_2   BAdI: Customer IMDS Communication 
Customizing Activity /TDAG/CP_IMDS_BADI_2   BAdI: Customer IMDS Communication 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /TDAG/CP_IMDS_BADI_2    

Use

This Business Add-In (BAdI) is used in the SAP Product and REACH Compliance component. This BAdI enables you to adapt the IMDS communication for the customer MDS center. It is called when IMDS communication is triggered within the customer MDS center.

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.

BAdI Implementations

/TDAG/CL_DEF_IM_CP_IMDS_BADI_2 (Default implementation)
A default implementation is supplied for the following methods. In all cases, these methods comprise "only" the upload using the IMDS Advanced Interface and not the download of the result file:

PROPOSE
Encompasses the implementation for proposing a material data sheet (MDS) to a customer.

PUBLISH
Encompasses the implementation for publishing an MDS.

SEND_EDIT
Encompasses the implementation for sending an MDS to a customer in edit mode.

SEND_CUSTOMER
Encompasses the implementation for sending an MDS to a customer.

INTERNAL_RELEASE
Encompasses the implementation for releasing an MDS internally.

DELETE_RECIPIENT
Encompasses the implementation for removing one or more recipients from an MDS.

Each of these methods has a parameter that distinguishes the execution in dialog mode from the background execution.

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.

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