SAP ABAP IMG Activity /TDAG/CP_BADI_006 (BAdI: Set Functions to Handle Business Partner Contacts)
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_006 BAdI: Set Functions to Handle Business Partner Contacts  
Transaction Code /TDAG/57000002   (empty) 
Created on 20080710    
Customizing Attributes /TDAG/CP_BADI_006   BAdI: Set functions to handle business partner contacts 
Customizing Activity /TDAG/CP_BADI_006   BAdI: Set functions to handle business partner contacts 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /TDAG/CP_BADI_006    

Use

This Business Add-In (BAdI) is used in the SAP Product and REACH Compliance component. This BAdI enables you to specify the functions to determine business partner data.

This BAdI provides the following methods for determining address and contact data:

  • ADDR_READ:
    You can use this method to read business partner data as well as personal address data according to various selection criteria.
  • COUNTRY_READ:
    You can use this method to read the country and determines if the business partner is located within the regulation area.

This BAdI provides the following methods for handling representative assignments:

  • REPR_READ:
    You can use this method to determine representatives that are assigned to a given vendor. The determined representative can be a supplier or a legal entity.
  • REPR_WRITE:
    You can use this method to update representative assignments of vendors.
    Parameter value LINEMOD defines the action to perform:
    I: Assign a new representative to a vendor (create assignment)
    U: Update existing representative assignment
    D: Delete existing representative assignment
  • REPR_LOCK:
    You can use this method to lock or unlock representative assignment data.
  • REPR_CHECK:
    You can use this method to validate representative assignment data.
  • REPR_RECN:
    You can use this method to determine a new record number to store the representative assignment.

This BAdI provides the following methods for handling representative address and contact data:

  • OR_CREATE:
    You can use this method to create representative address and personal data.
    By default, a new supplier is created in the vendor master which is assigned the new address and personal data.
  • OR_DELETE:
    You can use this method to delete representative address and personal data.
    By default representative address and personal data is not deleted - only the representative assignment is deleted.
  • OR_UPDATE:
    You can use this method to update representative address and personal data.
  • OR_LOCK:
    You can use this method to lock or unlock representative address and personal data.

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 automatically deactivated.

BAdI Implementations

  • /TDAG/CL_DEF_IM_CP_BADI_006

    This BAdI contains a default implementation that supports the process industry (REACH) as well as the additional attributes for the discrete industry, such as the DUNS number, that otherwise cannot be stored in the vendor master in the standard system. The default implementation has the following settings:

    • Address data is read from the vendor master (supplier data) and business partner (legal entity data).
    • Representative assignments are handled by substance volume tracking (SVT). You can use transaction CBRC01 for maintenance.
    • Address and personal data is handled by the vendor master (read/write) and business partner (read only).
  • /TDAG/CL_EXM_IM_CP_BADI_006

    If you use only discrete industry processes, the standard system contains an example implementation that reads address data from the extended address maintenance (transaction /TDAG/CPO00) only.

    Note: Do not use this implementation if you have process industry processes.

    • Except method ADDR_READ, the default and example implementations of all methods are identical.

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/CP_BADI_006 0 HLA0100681 Product Safety 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on HAU  20090304 
SAP Release Created in 110_470