Kontakt

Ansicht
Dokumentation

SIMG_ISHMED_TR_SUPP - Transport Support for Master Data and Customizing

SIMG_ISHMED_TR_SUPP - Transport Support for Master Data and Customizing

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

This information is for 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 into a downstream system.

Please note that Customizing is done only in one system. You should administrate the downstream systems (quality assurance system, production system, etc.) exclusively through transports. ‎If you manually perform customizing in downstream systems, subsequent transports may result in data inconsistencies.

The main focus of this information for the transport of master data and customizing settings centers on data of the clinical system (i.s.h.med). The associated SAP Patient management (IS-H) objects are also mentioned since they are a prerequisite for the correct transport of i.s.h.med data. Various services are available for transporting master data and customizing settings.

They must be performed in the specified sequence. You should observe the sequence of described functions to avoid data inconsistencies in the target system.

  1. Organizational Units
Firstly, transport the organizational units (OUs) into the downstream system. The report RNUTROE0 is available in 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

Include the data in a transport request that you can use to transport the data into the downstream system. Now release the organizational unit structure in the target system from the SAP Easy Access screen by choosing Hospital → Basic Data Administration → Hospital Structure → Organizational Structure → Release Structure (transaction NB53) ).
For more information, see the documentation for the report.
  1. Building Units
Now use the IS-H report RNUTRBE0 to transfer the building units. You can use this report to transport 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

Include the data in a transport request that you can use to transport the data into the downstream system.
For more information, see the documentation for the report.

Note that the data of the two reports RNUTROE0 and RNUTRBE0 for the transport of OUs and building units, which was included in a transport request, should be transferred in a single process step.

  1. Service Master Data
Now transport the service master data (medical information). To do this, you can use the following reports:
  • RN1LSTEXP (i.s.h.med: Export Service Master Data and Assignments)

  • 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 creates the data from this text file as table entries in the target system.
Note that the system does not overwrite existing entries in the target system with the entries from the text file. If there are entries in the target system's database which also exist in text file, it is not possible to import the data. If need be, you should adapt the service master data to be selected for the import process, i.e. exclude the services, which cannot be transferred into the target system, from the selection.
You will find a description of the object list in the documentation for the report RN1LSTEXP.
You cannot use this report to transfer service master data long texts (SAPscript texts). You should use the report RSTXTRAN for this. This report transfers the long texts into a transport request.
On the initial screen of the report, 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: Key for the relevant language, e.g. EN for English

Once you have transferred this medical service master data, you can choose to transport IS-H service data using the report RNUTRLK0. This report transfers 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 maximum values

  • IS-H: Service maximum 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: Preapproved insurance - item

For more information, see the documentation for the report.
  1. Remaining Master Data and Customizing Settings
Now transfer the remaining master data and customizing settings from i.s.h.med.
Document Categories
For parameterized documentation, there are two reports that collect all definition data in a transport request and distribute it to the correct clients. Data is separated into reports RN2UTDTS3 for transporting between two systems and RN2UTDTM2 for copying between clients or institutions, because otherwise data must be adapted during the import process.
You use report RN2UTDTS3 to transport all table entries for the selected document categories.
Using the checkbox options, you can also include development objects in the transport request.
You use the report RN2UTDTM2 to distribute the transported data to the production clients and institutions. In the process, you can adapt the reference to development objects.
For more information, see the documentation for the report.
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 production system.
There is no transport function for the definition data of document categories which use the WordContainer.
Diagnosis Catalogs
You can import the diagnosis catalogs using IS-H functions.
Nursing Basic Data (only necessary if you use the i.s.h.med Nursing module)
You can export the basic catalog entries for nursing planning using the report RN2UEPK1. This report enables the export of basic catalogs and assignment catalogs for the nursing support area, in a sequential file. The report RN2UIPK1 enables the import of basic catalogs and assignment catalogs from the sequential file into the target system.
You can use these reports to 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 more information, see the documentation for the reports RN2UEPK1 and RN2UIPK1.
Clinical Order Types
As of Release 4.72 Patch 11 order types for clinical orders are connected to the SAP transport system.
There are three ways of transporting order types:
  • Explicit transport from the overview screen for order types (transaction N1COT).

  • Explicit transport from the detail screen for the order type

  • Automatic transport in the detail screen of the order type

If the automatic recording of changes is activated in client administration, the system will automatically transport order types for clinical orders (transaction SCC4).
You should note the following:
  • In order to activate the transport functionality, you must execute the synchronization report RN1_SYNC_CORDERTYPES once for each client of the source system with the corresponding client (same client number) of the target system.

  • Due to this necessary synchronization of the table keys, it is only possible to transport order types between different systems (e.g. production system - quality assurance system - development system) with the same client number. For other system landscapes and transport routes (e.g. between clients of different systems with different client numbers or between clients of the same system) you cannot use the connection of the order types to the transport system.

You should also refer to the notes in the documentation of report RN1_SYNC CORDERTYPES, in particular the prerequisites listed there.
Remaining Objects
In principle, the automatic transport connection will automatically include other customizing settings (e.g. cancellation reasons, service statuses, transport types, degrees of infection, etc.) in the transport requests when you process these customizing settings. The system will only transfer entries to the object list of the transport request which were created or changed before you executed the save function.
Note that, due to the integration of the position assignments (table N1MAPS, i.s.h.med: Employee-Position Staffing) in the automatic transport connection, the employee master data to be taken into consideration must already exist in the target system before you import the transport request.
The system does not automatically transfer the following object by means of the transport connection:
  • Number ranges and number range intervals

Number ranges and number range intervals You can include this data in the transport request using the Transport Interval function in the initial screen of interval maintenance. This also applies for the setting up of number ranges for requests and the request type definition. The IMG activity Assign Interval to Number Range Object is an exception since it is included in the automatic transport connection.
  • System Parameters: Tables TN00P, TN00Q, TN00R, TN00S

  • Cycles: Tables N1STZY, N1STZT, N1ZYINF and, as of Release 4.63 N1STZYOE (since number range used)

  • Cycle Groups: Tables N1CYGROUP, N1CYGROUPT

  • The assignment of document categories to organizational units (table N2DO) and the assignment of document categories to services (table N2DL)

  • Material proposal MM: Table N1MLZUO (since sequence number is used)

  • Planning object area: Tables NPOB, N1TPGA, TN40B, N1TPGO, N1KGTPL, N1TPGL, NTPGK, NTPGP, N1POBKL, NWPG (since number ranges are used for planning objects. You can create employees as planning objects. This could cause problems if there are differences in the employee master of the source and target systems).

  • Display variants of the planning grid: Tables N1WPLACE_PG, N1WPLACE_PG_USZ, N1WVIEW_PG_CL, N1WVIEW_PG_DT, N1WVIEW_PG_DT_OU, N1WVIEW_PG_OU, N1WVIEW_PG_PO, NWPLACE, NWVIEW, NWPVZ. Note that the tables NWPLACE, NWVIEW, and NWPVZ are tables of the clinical work station. Entries concerning display variants can be identified on the basis of the fields VIEWTYPE (see value range of domain NVIEWTYPE [= PG1, PG2, PG3]) and WPLACETYPE (see value range of domain NWPLACETYPE [= PG1]) . Master data for clinical order types:

  • Master data for clinical order types: Tables N1COMP, N1COMPT, N1COMPDEFA, N1FATTR, N1FATTR_TYPE, N1FATTR_TYPET, N1FATTR_VALUE, and N1FATTR_VALUET. Tables TJ20 and TJ30 are also involved. These can be added to a transport request using the Transport Status Profile function.

  • Transport service transport times: Table N1FWZ

  • Drug catalogs: Tables N1DC, N1DCT, N1DCURL

  • Drug catalog levels: Tables TN1FORMLEVEL, TN1FORMLEVELT

You must manually include these objects and table entries in the transport request and then transport them into the target system. Beforehand, you must set up the relevant number range objects with the corresponding intervals or manually transport them.
Note that with the automatic transfer of settings in Customizing, you must make sure that objects, which these settings refer to, have already been transferred (see example).
You can control the correctness of the data transfer sequence in the target system using the import sequence of the transport requests in the target system.

Organizational units, the service catalog and the service master data must exist in the target system before you automatically transfer the service ranges.

Before you transport the assignments of intervals to number ranges ( Implementation Guide under Industry-Specific Component Clinical System → Service Management → Requests → Assign Interval to Number Range Object), you must transport the corresponding number ranges and intervals (i.e. manually add them to a transport request) or maintain them identically in the target system.






ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 19824 Date: 20240607 Time: 195837     sap01-206 ( 239 ms )