Hierarchy

⤷

⤷

IMG Activity
ID | CM_XX_MOBU02 | BAdI: Module Booking - Callup Point 0001 |
Transaction Code | S_KK4_82000749 | (empty) |
Created on | 20010810 | |
Customizing Attributes | CM_XX_257_2_2 | Multiple Usage: Non-Critical Activity (IS-HER-CM-AD, ASAP 257) |
Customizing Activity | CM_XX_MOBU02 | BAdI: Module Booking - Callup Point 0001 |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRPIQ00MODULEREG_PBO |
Use
You can use this customer enhancement to implement the following methods for module booking in the business add-in HRPIQ00MODULEREG_PBO:
- ELIGIBILITY_CHECK (Check Admissibility of Booking)
- DEFAULT_VALUES_GET (Set Default Values)
The business add-in HRPIQ00MODULEREG_PBO is available at callup point 0001 (Module Booking (General)).
ELIGIBILITY_CHECK method
The system uses the ELIGIBILITY_CHECK method to check if the user is authorized to book modules for a specific student in the selected period.
The method uses the following parameters:
- Import parameters
- STUDENT: Student for whom the module bookings are made
- STUDY: Study for which the module bookings are made
- PROGRAM: Program in which the module bookings are made
- YEAR, PERIOD: Academic year and academic session for which the module bookings are made
- Export parameters
- SUBRC: Return value
- - SUBRC = 0 means: The booking process can be executed
- - SUBRC <> 0 means: Module bookings cannot be made
- MESSAGE: Message the system outputs if module bookings cannot be made
(The message is only output if SUBRC <> 0)
Note: If module bookings cannot be made (SUBRC <> 0), the system automatically switches to the display mode in the module booking maintenance interface.
DEFAULT_VALUES_GET method
You can use the DEFAULT_VALUES_GET method to define default values for the module booking process, for example:
- Tab page which is active when you call the module booking
- Content of specific data fields (empty or containing a specific value)
- Function of the radio button
By defining default values, you can accelerate the mass booking process and reduce the number of incorrect bookings. These default values appear in the module booking maintenance interface.
The method uses the following parameters
- Import parameters
- STUDENT: Student for whom default values are set in the module booking dialog
- STUDY: Study for which default values are set in the module booking dialog
- PROGRAM: Program in which default values are set in the module booking dialog
- PERYR: Academic year
- (If the basic setting is active, the system defaults to the current academic year. You can change the default value using this method, and transfer the new default value to the field PERYR of the export structure DEFAULT_VALUES.)
- PERID: Academic session
- (If the basic setting is active, the system defaults to the current academic session. You can change the default value using this method, and transfer the new default value to field PERID of the export structure DEFAULT_VALUES.)
- Export parameters
- DEFAULT_VALUES: Default values
- TAKE_DATA: If you want to use the default values the method proposes in the module booking process, set:
TAKE_DATA = 'X' - ACTIVE_TAB: Controls the tab page which is active when you first access the module booking process. The tab pages have the following values:
- - 2100: Module details
- - 2200: Booking history
- - 2300: Booking dialog
- - 2400: Selection
- PERYR: Default value for academic year
- PERID: Default value for academic session
- SEVERITY: Default value for academic level on the Selection tab page
- DISCIPLINE: Default value for discipline on the Selection tab page
- FLAG_MANDATORY: Default value for the indicator Only mand. items on the Selection tab page
- SELECTION_MODE: Default value for the selection method Direct entry on the Selection tab page
The functions of the radio button have the following values: - - 1: Module
- - 2: Business event package
Requirements
Standard settings
Activities
Examples
You can display sample code for the business add-in HRPIQ00MODULEREG_PBO on the BAdI Builder processing screen by choosing Goto -> Sample code -> Display.
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 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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
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 | 20030113 |
SAP Release Created in | 464 |