Ansicht
Dokumentation
SIMG_OHPIQ_6028 - Maintain Client-Specific User Exits
PERFORM Short Reference PERFORM Short ReferenceThis documentation is copyright by SAP AG.
In this activity, you define the user exit programs for client-specific user exits.
The following application areas are always client-specific and must therefore be maintained in view V_T80D Client-Specific User Exits in FI-SL:
- GBLR (Val./sub.: Exits for rules)
- GBLS (Val./sub.: Exits for substitutions)
In client-specific application areas, you can use the same exit program in each client. You do not have to create a new exit program for each client.
The following user exits are provided in Student Lifecycle Management:
| User exit key | User exit description |
|---|---|
| UCP1 | Replace average grades for admission |
| UCP2 | Replace academic calendars |
| UCP3 | Replace business events of students |
| UCP4 | Replace modules of students |
| UCP5 | Replace qualifications of students |
| UCP6 | Replace additional data of students |
| UCP7 | Replace test results and external subjects of students |
We recommend that you use these user exits as templates when you create your own user exits.
User exits are subroutines of exit programs. You must therefore maintain user exits via the exit program. You maintain an exit program by copying it, creating or changing the user exit(s), and entering the copied exit program in view V_T80D Client-Specific User Exits in FI-SL.
- Enter the name of the user exit program for the relevant application area.
- To enter a user exit program for a user-defined application area, proceed as follows:
- Choose New entries.
- Enter the application area and the user exit program.
- Save your changes.
The function of user exits is described in detail in the following using user exit UCP2 as an example (Replace academic calendars).
User exit UCP2 searches the academic calendars of a university during the program admission process. The academic calendar data it finds is made available in the central CM rules structure PQRULEMASTERS. The exit gets its data from the application for admission.
The system calls the function module HRIQ_ACAD_GET_TIMELIMTS. This function module determines the session variant for the program, the calendar data for the academic year, the academic session, and the session variant, and returns this data to the internal table LT_TIMELIMINITS. If the function module does not find any calendar data for the academic year, academic session, and session variant, the system exits the exit program without providing any calendar data. If this is the case, the required dates have not been maintained in the academic calendar.
If the academic calendar does contain the required data, the system searches for a free space in the central structure PIQRULEMASTERS and appends the data transferred by the function module to this structure.
When the user exit program has been processed, the central structure contains the requested calendar data. The dates of applications can then be checked against the calendar dates using the appropriate validations.
ROGBILLS - Synchronize billing plans CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 4130 Date: 20240523 Time: 220358 sap01-206 ( 61 ms )
