Hierarchy
IS-H (Software Component) SAP Healthcare⤷
IS-HMED (Application Component) Clinical System⤷
N1BASE_MED (Package) IS-H*MED: Basic Functionality
IMG Activity
| ID | SIMG_ISHMED_COMPCON | Maintain Settings for Medical Service Entry |
| Transaction Code | S_PNI_98000309 | (empty) |
| Created on | 20050525 | |
| Customizing Attributes | SIMG_ISHMED_COMPCON | Maintain Settings for Medical Service Entry |
| Customizing Activity | SIMG_ISHMED_COMPCON | Maintain Settings for Medical Service Entry |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_COMPCON |
Use
With these settings you can create different medical service entry configurations and save them using an ID. A configuration is a presetting of the performing and requesting OUs and the service range favorites.
You maintain the settings for service entry by entering the value " " in the Object Type field and select the module "SAP_MEDSRV" in the list of modules.
You can then either select from a list of existing configurations and change one, or enter a new ID in the "New Configuration ID" field and create a new one. You then maintain the configuration data. These are:
- Display the hit list integrated or as a popup. The integrated display requires a high screen resolution in order to be able to enter services clearly.
- Layout and function variant
- Display area
- Further settings
- Presettings of performing and requesting organizational units
- Favorites: You use drag&drop to define favorite services from the service range of the performing OU. You should note that you can only define favorites, if a value is entered in the Performing OU field.
In a BAdI implementation of the BAdI N1_WP_LSTAMB: Enhancements for Outpatient Clinic / Service Facility View Type you can then access a configuration defined here and include service entry presettings.
Requirements
You should adhere to the following customer namespace for the identification of configurations:
- Number at beginning (0* - 9*)
- A*
- B*
- C*
- E*
- F*
- Z*
Standard settings
Activities
Example
You should check the supplied sample implementation of the BAdI N1_WP_LSTAMB. In this BAdI access to a configuration is implemented as an example. You can transfer the sample coding and must then only change the identification of the configuration.
Business Attributes
| ASAP Roadmap ID | 103 | Set up development systems |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_ISHMED_COMPCON | 0 | I010004302 | Service Management |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| N1COMPCON | T - Individual transaction object | N1COMPCON |
History
| Last changed by/on | SAP | 20050525 |
| SAP Release Created in | 600 |
