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_TR_SUPP | Transport Support for Master Data and Customizing |
| Transaction Code | S_KK4_96000545 | IMG Activity: SIMG_ISHMED_TR_SUPP |
| Created on | 20020305 | |
| Customizing Attributes | SIMG_ISHMED_TR_SUPP | Transport Support for Master Data and Customizing Settings |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_ISHMED_TR_SUPP |
Use
This document is relevant to system administrators and users responsible for customizing systems and entering master data.
The information in this document should support you when transporting master data and customizing settings in a downstream system. You should note that customizing should only be performed on one system and that downstream systems (quality assurance system, productive system, etc) should only be administrated using transports.
Caution If you perform customizing on downstream systems, you may cause data inconsistencies in subsequent transports.
The main focus of the description centers on i.s.h.med, however, associated IS-H objects are also mentioned as they represent a prerequisite for the correct transport of i.s.h.med settings.
Various services are available for transporting master data and customizing settings. The following is an overview of these functions and the definition of the sequence in which master data and customizing settings are transported. You should observe the sequence of described functions to avoid inconsistency in the target system.
- Organizational Units
Firstly, you must transport the organizational units to the downstream system. The report RNUTROE0 is available from IS-H for this purpose. You can transport the following entries using this report:
- IS-H: Organizational units and their long texts
- IS-H: Organizational unit hierarchy
- IS-H: Inter-departmental occupancy of an organizational unit by an organizational unit
- IS-H: Assignment of building units to organizational units
- IS-H: Statistical bed figures of organizational units
- IS-H: Cost center-organizational unit assignment (optional)
- IS-H: Cost center-organizational unit revenue account assignment (optional)
- i.s.h.med: Organizational process hierarchy of organizational units
Enter the data in a transport request that you can use to transport it to the downstream system.
Note that you must then release the organizational unit structure in the target system using the SAP menu Hospital -> Basic Data Administration -> Hospital Structure -> Organizational Structure -> Release Structure (transaction NB53).
For further information you should refer to the Report documentation.
- Building Units
You can then use the IS-H report RNUTRBE0 to transfer the building units. This report will transfer the following entries:
- IS-H: Building units
- IS-H: Building unit hierarchy
- IS-H: Facilities characteristics of a building unit
- IS-H: Door table for care unit overview graphic
- IS-H: Planning characteristics of a building unit
- IS-H: Assignment of building units to organizational units
Enter the data in a transport request that can be used to transport it to the downstream system.
We suggest you transport the data of the two reports, transferred in the transport request, in one process step.
For further information you should refer to the Report documentation.
- Service Master Data
In the next step you transfer the service master data (medical information). To do this, you can use the two reports RN1LSTEXP (i.s.h.med: Export Service Master Data and Assignments) and RN1LSTIMP (i.s.h.med: Import Service Master Data and Assignments).
During the export the system transfers the master data into a text file. During import, the system enters the data into the target system as table entries from this text file. You should note that the system will not overwrite existing entries in the target system with the entries from the text file. If there are entries in the database which also exist in text file, the data will not be imported. In such a case, you should adapt the service master data to be selected, i.e. exclude the services from the selection which cannot be transferred to the target system.
You will find a description of the object list in the RN1LSTEXP report documentation.
You cannot use the report to transfer service master data long texts (SAPscript texts). You should use the RSTXTRAN report for this. This report transfers long texts in a transport request.
In the initial screen of the report, you select the following:
- Name of Correction/Repair: Here you enter the task number of the transport request.
- Text Key - Object: NTPT
- Text Key - Name: Institution (4-digit), Service Catalog (2-digit), Service Key (10-digit). The use of wildcards is allowed. Example: 000101ENDO*
- Text Key - ID: 0001
- Text Key - Language: Abbreviation for the relevant language, e.g. EN for English
Once you have transferred these medical service master data, you can choose to transport IS-H service data using the report RNUTRLK0. This report will transfer the following entries:
- IS-H: Service item header data
- IS-H: Service catalog item description
- IS-H: Additional service master fields Germany
- IS-H: Service catalog columns
- IS-H: Service exclusions
- IS-H: Service highest values
- IS-H: Service highest values for service groups
- IS-H: Service inclusions
- IS-H: Service conditions, by pairs
- IS-H: Plan values by service and organizational unit
- IS-H: Service catalog items: Assignments/groupings
- IS-H: Flat rate insurance verification information - Item
For further information you should refer to the Report documentation.
- Remaining Master Data and Customizing Settings
You can then transfer the remaining master data and customizing settings from i.s.h.med.
Document Categories
For parameterized documentation, there are two reports which collect all definition data in a transport request and distribute it to the correct clients. Data is separated into report RN2UTDTS3 for transport between two systems and RN2UTDTM2 for copying between clients or institutions, because data must be adapted for import.
Report RN2UTDTS3 will transport all table entries for the selected document categories.
Using the checkbox options, you can also place development objects in the transport request.
Using report RN2UTDTM2 the transferred data is distributed to the productive clients and institutions. This can adapt the reference to development objects.
For further information you should refer to the Report documentation.
Text modules and markers, which are used in long text fields, are transported using text module administration (transaction N2TBS). You can transport markers according to institution, text modules must be specifically transported for the desired level (institution, department, documenting OU, user). However, as a rule you will usually enter text modules and markers on the productive system.
There is no transport function for the definition data of document categories which use the WordContainer.
Diagnosis Catalogs
Diagnosis catalogs are imported using IS-H functions.
Nursing Basic Data (only necessary if you use the i.s.h.med Nursing module)
You can import basic catalog entries for nursing planning by report. The report RN2UEPK1 enables the export of basic catalogs and assignment catalogs for the nursing support area, in a sequential file. The report RN2UIPK1 then enables the import of basic catalogs and assignment catalogs from the sequential file to the target system.
With these reports you can transfer the following entries:
- i.s.h.med: Basic nursing catalog
- i.s.h.med: Standard nursing plan
- i.s.h.med: Classification areas
- i.s.h.med: Standard nursing plan - basic catalog assignment
- i.s.h.med: Standard nursing plan - service catalog assignment
- i.s.h.med: Classification area assignment
- i.s.h.med: Standard nursing plan - classification area assignment
- i.s.h.med: Basic catalog - classification area assignment
- i.s.h.med: Service catalog - classification area assignment
For further information you should refer to the RN2UEPK1 report and the RN2UIPK1 report documentation.
Clinical Order Types
As of Release 4.72 Patch 11 clinical order types are also connected to the SAP transport system. This is an advance development of Release 6.00.
There are three ways of transporting clinical order types:
- Explicit transport from the overview screen for clinical order types (transaction N1COT).
- Explicit transport from the detail screen of the clinical order types.
- Automatic transport into the detail screen of the clinical order types: If the automatic logging of changes is activated in client management, clinical order types are automtaically transported (transaction NCC4).
You should note that
- In order to activate the transport functionality you must run the synchronization report RN1_SYNC_CORDERTYPES for each client in the system with the corresponding client (same client number) of the system with which you are sychronizing.
- Due to this necessary synchronization of table codes, the transport of order types is only possible between different systems (e.g. productive system - quality assurance ssystem - development system) with identical client numbers. Other&
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| 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_TR_SUPP | 0 | I010004300 | Clinical System |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20020326 |
| SAP Release Created in | 463B |
