Hierarchy
⤷ 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_GUISTAT | Specify User-/User Group-Specific GUI Status |
Transaction Code | S_KK4_96000335 | (empty) |
Created on | 20000302 | |
Customizing Attributes | SIMG_ISHMED_GUISTAT | Specify User-/User Group-Specific GUI Status |
Customizing Activity | SIMG_ISHMED_GUISTAT | Specify User-/User Group-Specific GUI Status |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_ISHMED_GUISTAT |
Alternately to the GUI status which is available as standard, it is possible in the IS-H*MED Programs
- Medical Unit List
- Request Overview
- Waiting List
- Worklist
- Document List
- Surgery Planning List
- OR Schedule
- Preregistration List
- Nursing Plan
- Nursing Worklist
- Nursing Overview
to define a new GUI status dependent on the user, the user group or the organizational unit of the users. The "user group" is the user group stored in the user master.
For a OU-dependent definition, the "individual organizational unit of the user", which is stored in the user parameter OEE, is included in the query.
The table queries have this sequence:
1. User
2. User Group
3. Organizational Unit
4. Institution
You can only input an organizational unit or the institution. If you try to specify an institution and an organizational unit on one line, the system will not allow this.
If you do not make an entry in a field, then this will count as a wildcard entry (*) (for all users, user groups, organizational units or institutions).
Example
For the user group "Surgery Nursing" and the function "OR Schedule", an
individual GUI status is defined that contains a subset of all standard menu options planned for the OR Schedule. You can select the Surgery Nursing function by pushbutton in the selected functions of the OR Schedule.
Requirements
Standard settings
The GUI statuses included in the standard are not stored in this table but are technically set by programs.
Recommendation
We recommend that you create the alternative GUI status in the customer namespace as a copy of the standard GUI status. This makes the implementation of modifications after a release upgrade unnecessary.
Activities
We recommend that you copy an existing GUI status into the customer namespace and then change the copy with the menu painter. When changing a GUI status, you must make sure that the OK codes, which are assigned to the individual menu options, are not changed. The programs mentioned above interpret the OK codes. The OK codes are used to call the desired functions.
Further notes
After a release upgrade, it is possible to set all table entries to "Original Status" so that the system will activate the newly shipped statuses in the standard and so that the system will recognize possible new functions.
If these new functions are also needed in the user-specific GUI status, you must install them into the user-specific status with the menu painter.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_ISHMED_GUISTAT | 0 | I010004300 | Clinical System |
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 |
N1GUISTATUS | S - Table (with text table) | SM30 | 0000000000 | Generated Table Maintenance N1GUISTATUS |
History
Last changed by/on | SAP | 20000302 |
SAP Release Created in |