Ansicht
Dokumentation
RNUNLOPM - IS-H: Migrate Table NLOP to NICP - NLICZ - NDICZ
rdisp/max_wprun_time - Maximum work process run time BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Description
The new surgical data transaction was released with IS-H Release 4.03A. With this release, the data
model has been modified in the area of surgical data. The table NLOP, which documented the assignment
of services to procedures and diagnoses in previous IS-H Releases, has been replaced by three new tables.
All dependent programs (statistics, for example) now access the tables NICP, NLICZ and NDICZ instead of the table NLOP.
This applies equally to all programs developed by customers. If this is not the case, incorrect results are returned.
To be able to use the new surgical data transaction and the existing statistics, you are required to migrate the data in the table NLOP to the new tables.
For this reason, SAP recommends that you run this program in the background immediately after upgrading your system to IS-H Release 4.03A.
This program determines all data records in the table NLOP that have still to be migrated and uses the data from the table NLOP to create the tables NICP, NLICZ and NDICZ. Non-migrated data records are recognized by the value of the field NLOP-MIGKZ. If this value is not 'X', the table entry in question is a data record that has still to be migrated to the new structures.
The following data is saved in the new structures:
- NICP - Procedures for the case and movement
- NLICZ - Assignment of service to procedure
- NDICZ - Assignment of procedure to diagnosis
If the service from the table NLOP or the assigned movement or the case is canceled, a record with the
cancellation indicator set is created in the table NICP. In such cases, the assignment tables NLICZ and NDICZ are not filled.
If the diagnosis in the table NLOP is canceled, an assignment of the procedure to the canceled diagnosis is not created.
If the program is run for one institution and one or more case numbers, an additional log is output,
detailing the data records read from the table NLOP and the data records created from these in the tables NICP, NLICZ and NDICZ.
With these parameters you can migrate the data for a particular case and check the result.
If you run the program for all institutions and cases, a log is not output.
The existence of the field NLOP-MIGKZ means that you can run this program as often as you like. The program only ever processes the data that has not yet been successfully transferred to the new structures.
Once this report has successfully run it triggers the report RN2UNLOM, if IS-H*MED is active.
By means of the tables NLOP and NLLZ the report RN2UNLOM transfers anchor service-to-surgical
procedure code assignment records or requested service-to-surgical procedure code assignment records
to NLCI for the service-to-surgical procedure code records already in NLCI, and completes the procedure texts in the table NICP.
The report RN2UNLOM can also be called independently of this report, but only processes records for which field NLOP-MIGKZ is not empty.
For more information, please read the program documentation on program RN2UNLOM.
Notes
You cannot start this program in parallel in one client, since this would result in duplicate entries in the new table.
Since as of IS-H Release 4.03A all IS-H programs (dialog programs, statistics, etc.) access the new structures, you must execute this program immediately after upgrading your system to IS-H Release 4.03A. To avoid adverse effects on performance, you should only execute the program in the background and when the system load is low.
Please note that the new surgical data transaction is active immediately after the data has been successfully migrated from the table NLOP. In other words, a user may have been processing a case with the old transaction and a moment later the new surgical data screen appears.
You must run the program in each client.
Requirements
Before running this program, you must maintain the technical number range for the object ISH_NICP in Customizing. To do this, choose
Settings -> Maintain Technical Number Ranges -> Object ISH_NICP.
Note that you
should create the technical number range from 0000000001 to 8999999999 for the object ISH_NICP. The interval 9000000000 to 999999999 must not be used.
Output
Example
BAL Application Log Documentation Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 4876 Date: 20240520 Time: 073944 sap01-206 ( 98 ms )
