SAP ABAP IMG Activity CM_XX_AKST08 (BAdI: Subscreen Enhancement for Event Offerings)
Hierarchy
☛ IS-PS-CA (Software Component) IS-PUBLIC SECTOR CONTRACT ACCOUNTING
   ⤷ IS-HER-CM-AD (Application Component) Administration
     ⤷ PMIQ (Package) Campus Management
IMG Activity
ID CM_XX_AKST08 BAdI: Subscreen Enhancement for Event Offerings  
Transaction Code S_KK4_82000836   (empty) 
Created on 20011121    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_AKST08   BAdI: Subscreen Enhancement for Business Event Offerings 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00EVENTSUBSCEXT    

Use

This business add-in (BAdI) is used in the Campus Management Administration (IS-HER-CM-AD) component.

You can use this BAdI to implement user-defined enhancements for editing event offerings. The system calls this BAdI when you create and change event offerings.

In the PBO processing block of the subscreen, the program calls function module HRIQ_GET_CURRENT_EVENT_INFO (Read Data of Business Event Being Processed) to determine the values of the current business event. You can use function module HRIQ_GET_CURRENT_EVENT_FCODE (Read Function Code of Business Event Being Processed) to determine the current function code of the PAI processing block.

The program uses function module HRIQ_SET_SUBEXT_EVENT_INFTY (Set Infotypes to be Created for Events) to transfer to the application the user-defined infotypes which are created when you create business events; these infotypes are transferred in a table with the structure WPLOG. The table name of the function module is IT_WPLOG_INS. If you want the system to change user-defined infotypes when you change business events, you first have to delete the respective infotype records and then create them again. You transfer the tables (IT_WPLOG_INS and IT_WPLOG_DEL) with function module HRIQ_SET_SUBEXT_EVENT_INFTY. When you create a business event, you do not know its object ID. You therefore exclude this field when you fill the table with the structure WPLOG. The application automatically writes the relevant object ID to the table.

To maintain the attributes of a transaction (a LUW updates either all or no data), infotypes in the subscreen must be created with update type B (buffer).

Further notes

You should perform this activity only if both of the following conditions are satisfied:

  • The SAP standard processes do not cover your requirements.
  • You have an in-depth knowledge of the ABAP programming language.

Business add-in implementations are code extensions and therefore apply across clients. If you have a multiclient system, you have to define how the customer enhancement is to be used within the implementation for each client using the system variable SY-MANDT.

Business add-ins without multiple usages can have several implementations. However, only one of these implementations may be active at any one time.

You must also make sure that instance creation for the implementing class (Properties tab page) is declared as public and not as private, protected, or abstract. Otherwise unwanted short dumps may occur during runtime.

General information and implementation instructions for business add-ins are found in the SAP library under Basis Components -> ABAP Workbench (BC DWB) -> Changes to the SAP Standard (BC) -> Business Add-Ins. You can also access this documentation from the initial BAdI builder screen via Help -> Application help.

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

Method

Transfer Subscreen

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  20030127 
SAP Release Created in 464