SAP ABAP IMG Activity CM_XX_WAITL03 (BAdI: Sorting of Waiting Lists)
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_WAITL03 BAdI: Sorting of Waiting Lists  
Transaction Code S_PNI_82001572   (empty) 
Created on 20050418    
Customizing Attributes CM_XX_257_2_2   Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) 
Customizing Activity CM_XX_WAITL03   BAdI: Sorting of Waiting Lists 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPIQ00WAITLIST_SORT    

Use

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

You can use this BAdI to sort waiting lists according to your requirements. In waiting list administration (transaction PIQWAITLMOVE), the system sorts waiting lists by default according to:

  1. Waiting list booking priority
  2. Booking date
  3. Booking time

Entries with the lowest booking priority appear at the beginning of the sorted table. If all entries have the same booking priority, the system sorts them (in descending order) according to the booking date and booking time.

If you do not want to sort your waiting lists in this way, you must implement this BAdI and specify your requirements there.

The system calls this BAdI in program RHIQ_WAITL_MOVE (waiting list administration). The BAdI uses the method SORT_WAITLIST (Sort Waiting List).

Requirements

Standard settings

This BAdI is not active in the SAP standard system, and does not have multiple uses.

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

Sort Waiting List

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  20050420 
SAP Release Created in 600