SAP ABAP IMG Activity PLM_EXPO_ADDOBJECTSI (BAdI: Instantiate Additional Classes to Call Event Handler)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ LO-PDM (Application Component) Product Data Management
     ⤷ PLM_FOX_OBJ_COM (Package) Basis and Help Classes of PLM_FOX Implementation
IMG Activity
ID PLM_EXPO_ADDOBJECTSI BAdI: Instantiate Additional Classes to Call Event Handler  
Transaction Code S_PEN_05000357   (empty) 
Created on 20050615    
Customizing Attributes PLM_EXPO_ADDOBJECTSI   BAdI: Instantiate Additional Classes to Call Event Handler 
Customizing Activity PLM_EXPO_ADDOBJECTSI   BAdI: Instantiate Additional Classes to Call Event Handler 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PLM_EXPO_ADDOBJECTSI    

Use

This Business Add-In (BAdI) lets you insert customer-specific objects in a structure explosion with Framework for Object Explosion (FOX). You use this BAdI to make customer-specific object implementations known to FOX. You can also define tags for the application log for the new objects.

Requirements

Maintain the new object types and object relationships with their descriptions in the database tables EXPO_OBJ_TYPE, EXPO_OBJ_TYPE_TX, EXPO_LTYPE, and EXPO_LTYPE_TX.

Standard settings

This BAdI is called when initializing FOX.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Example

  • You want to extend the existing functionality of a FOX object, and you provide a customer-specific implementation.
  • You implement a new object type and want to use this object in a structure explosion.

See also:

Methods

Expo Package Initialized

Extend Mapping of Object Types to Tags

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 PLM_EXPO_ADDOBJECTSI 0 ALN0000162 Product Data Replication 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20050615 
SAP Release Created in 600