Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NORD (Package) R/3MED: Services processing EDV-G
IMG Activity
| ID | SIMG_ISHMED_UEX_OP | Available User Exits Surgery Module |
| Transaction Code | S_KK4_98000077 | (empty) |
| Created on | 20031128 | |
| Customizing Attributes | SIMG_ISHMED_UEX_OP | Available User Exits Surgery Module |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ISHMED_UEX_OP |
Use
User Exits IS-H*MED OP
Requirements
The following is a list of user exits available for the Surgery module. BAdIs are listed separately. You should note that not all the named user exits are available in the Surgeries view type.
· Check OR Plan (Enhancement Component SAPLN1ON)
Valid for transaction N1PN only. This user exit can be used to perform checks when saving the OR plan (e.g. plausibility checks).
· Print OR Plan (Enhancement Component SAPLN1OP)
Valid for transaction N1PN only. This user exit can be used to reformat or redesign the OR plan before printing. The entire OUTTAB of the planning list including the team is transferred to the user exit.
· OR Schedule: Print (Enhancement Component SAPLN1OR)
Valid for transaction N1PG only. This user exit is called for the "Print" function of the OR schedule. This means you can print a user-defined OR schedule. From two tables, the user exit receives the complete information concerning the OR schedule (anchor services, services, times, rooms, patient name, etc.) and surgery team. To prevent the standard printout the user exit must set the return flag "Customer-Specific Printout" to ON.
· OR Schedule (Enhancement Component SAPLN1OO)
Valid for transactions N1PN and N1PG only. This user exit is called from the OR schedule and the planning list for every displayed surgery. Here you can select additional information which is then available as additional fields in the display variants of the OR schedule or the planning list. The module returns a string with the determined data, as well as the column header of the additional information to be displayed. This user exit can only be used to design the first row of the display.
· Planning List & OR Schedule: Menu Exit 1 (Enhancement Component SAPLN1O1)
Valid for transactions N1PN and N1PG only. This user exit is called either from the planning list or the OR schedule at the AT USER-COMMAND event of function code '+001'. An indicator (P = planning list, O = OR schedule) is transferred to the module as a parameter which indicates which list called the exit. The data of the planning list/OR schedule (data of OR plan) is provided to the module in a transfer table. The exit will return a flag, which indicates whether the planning list or OR schedule must be updated, as a return parameter.
· Planning List & OR Schedule: Menu Exit 2 (Enhancement Component SAPLN1O2)
Valid for transactions N1PN and N1PG only. This user exit is called either from the planning list or the OR schedule at the AT USER-COMMAND event of function code '+002'. The interface and functionality correspond to the user exit SAPLN1O1 (see above).
· Planning List & OR Schedule: Menu Exit 3 (Enhancement Component SAPLN1O3)
Valid for transactions N1PN and N1PG only. This user exit is called either from the planning list or the OR schedule at the AT USER-COMMAND event of function code '+003'. The interface and functionality correspond to the user exit SAPLN1O1 (see above).
· Surgery Started: Checks (Enhancement Component SAPLN1OQ)
This user exit is called when the 'Surgery Started' function is called (for example from the surgery monitor). Here additional checks which prevent the setting of the 'Surgery Started' stamp can be implemented. Input parameters are the anchor service, surgery date, surgery time, and operating room. The user exit returns an indicator whether an error was found as well as a table of error messages. If the error indicator is set to OFF and the error table contains messages, these are displayed as warnings and the surgery is flagged as started.
A sample coding of this user exit with the "Date must be earlier than or equal to current date" check is available.
· Planning List/OR Schedule: Additional Double-Click Functions (Enhancement Component SAPLN1OS)
Valid for transactions N1PN and N1PG only. You can use this user exit to define additional hotspots and double-click functions for the planning list and the OR schedule. You can also replace an existing double-click function/hotspot with your own implementation. All necessary data of the selected surgery are transferred from the planning list/OR schedule to the user exit. This returns whether the current row must be re-read and whether a standard double-click function was replaced. You can find a detailed description in the documentation for the function module EXIT_SAPLN1ON_009.
Sample coding exists for the user exit, which overrides an existing double-click function (instead of the surgery monitor the patient monitor is called in the planning list), and/or adds a double-click function for the planning list and OR schedule.
Standard settings
Activities
Example
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 |
History
| Last changed by/on | SAP | 20031201 |
| SAP Release Created in | 472 |
