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_OPNKRS | Define number ranges for OR system |
| Transaction Code | S_KK4_74000614 | IMG Activity: SIMG_ISHMED_OPNKRS |
| Created on | 19990816 | |
| Customizing Attributes | SIMG_ISHMED_OPNKRS | Define number ranges for OR system |
| Customizing Activity | SIMG_ISHMED_OPNKRS | Define number ranges for OR system |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_OPNKRS |
Here you can maintain the number range intervals for the OR system.
General Notes:
If department-specific OR numbers are set, an in-house surgery can only be uniquely determined by the combination of the surgery number and the OR department.
Before a number range can be set-up for the allocation of OR numbers, a code for a subobject (the OR deprtment) must be created in the table N2OPFABT. You can also enter the code for the department.
In the next step, a number range interval is created for this subobject for the number range object "ISH_N2OPNM".
For the year-related number allocation, a number range interval must always be created for both of the last two digits of the year. This can take place sequentially or each year starting with zero. The intervals may not overlap.
After this, the subobject must be assigned in the OU-related settings (basic surgery data) using the parameter N2OPFABT of the performing (operating) OU.
In order to ensure a passing surgery number, buffering for the number range object should be switched off!
Exceptional Case - All-department Allocation
If universal, multi-departmental number ranges are used, you can illustrate this by the settings for N2OPFABT. For example, multiple surgical departments can mutually count the surgery number in which for all of them the same object is entered.
If the entire building only uses one number range, then "*" can be entered for the OU.
Example
- Operating department: OPCHIR in the Institution 1
- Subobject for number allocation: ABCHIR
- For the number range object ISH_N2OPNM, the number range interval maintenance is called, where the subobject ABCHIR (DESURG) is entered.
- For the year 1997 you enter an interval 97, and for the year 2000 you enter an interval 00.
- The following are entered for the OU-related parameter for Institution: 1 OU: OPCHIR Parameter: N2OPFABT Value: ABCHIR
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | 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_OPNKRS | 0 | I010004312 | Surgery 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 |
| N2OPFABT | S - Table (with text table) | N2OT | IS-H*MED: Maintenance of the OR Departments | |||
| N2ON | T - Individual transaction object | N2ON | OPNR | IS-H*MED: Maintenance of Number Ranges for Surgical Procedures |
History
| Last changed by/on | SAP | 20000810 |
| SAP Release Created in |
