SAP ABAP IMG Activity HR_LSO_M1C5D2A3 (BAdI: Define Customer-Specific Cancellation Reasons)
Hierarchy
☛ EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR
   ⤷ PE-LSO-TM (Application Component) Training Management
     ⤷ LSO_IMG (Package) SAP Learning Solution - IMG
IMG Activity
ID HR_LSO_M1C5D2A3 BAdI: Define Customer-Specific Cancellation Reasons  
Transaction Code S_AX8_68000303   IMG Activity: HR_LSO_M1C5D2A3 
Created on 20020326    
Customizing Attributes HR_LSO_M1C5D2A3AT   BAdI: Define Customer-Specific Cancellation Reasons 
Customizing Activity HR_LSO_M1C5D2A3PO   BAdI: Define Customer-Specific Cancellation Reasons 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HR_LSO_M1C5D2A3    

In this step, you make the settings required for customer-specific cancellation reasons. If you want to provide your course participants with one or more situation-specific reasons for canceling participation in the Learner Portal, you must use the Business Add-In (BAdI) LSO_CANCELREASONS_C. The BAdI is only called for cancellations in the Learning Portal.

Example

Requirements

Standard settings

Recommendation

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.

Interface

Further notes

For more information on using BAdIs, refer to the SAP Library under Basis -> ABAP Workbench-> BC Changing SAP Standards -> Business Add-Ins.

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  20020618 
SAP Release Created in 2002_1_46C