Ansicht
Dokumentation
RN2UNLOM - Enhancement Migration Table NLOP into NLICZ
PERFORM Short Reference Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Description
ISH-Release 4.03A supplies an active, modified data model in the area of surgical data. This release
replaces the previous table NLOP, which documents the assignment of services to procedures, using three (3) new tables.
From now on, all dependent programs will no longer access table NLOP, but instead, they will access tables NICP, NLICZ and NDICZ (i.e. statistics).
This must also apply to customized programs, since the system would otherwise deliver incorrect results.
The surgery monitor from i.s.h.med is also one of the dependent programs which has programs that access
NLOP. Here, you must transfer other surgical service code records into table NLICZ and enhance the procedure
text in table NICP. For this reason, program RN2UNLOM must run in the background after executing program RNUNLOPM, which will execute the global conversion of the NLOP data.
In order to use the new surgical data transaction as well as the previous statistics, it is necessary to transfer the data of table NLOP into the new tables.
Also, in order to use the surgery monitor, it is necessary to transfer the additional surgical service code records into table NLICZ and add the procedure text in table NICP.
Program RNUNLOPM saves the following data in the new structures:
- NICP - Procedures for the Case and the Movement
- NLICZ - Assignment between Service and Procedure
- NDICZ - Assignment between Procedure and Diagnosis.
If you cancel the service from table NLO or the assigned movement or the case, the system will create
a record with the deletion flag in table NICP. The system will then not fill in assignment tables NLICZ or NDICZ.
If you cancel the diagnosis from table NLOP, the system will not create an assignment between the procedure and the canceled diagnosis.
Program RN2UNLOM will transfer tables NLOP and NLLZ to the surgical service code records already existing in NLICZ as well as anchor surgical service code records and request surgical service code records in NLICZ and will add procedure text in table NICP.
If you call the program with an institution and one or more case numbers, you will also receive the
following: a detailed log of the data records that the system has read from tables NLOP and NLLZ as
well as the data records the system has created from these in table NLICZ and from the enhanced records in table NICP.
You can use these parameters to convert a specific case and to check the result. If you call the program for all institutions and cases, you will not receive a log.
Field NLOP-MEDMIGKZ allows you to start the program as often as you like. The system will process the data for which NLOP-MIGKZ has been set, which includes the data for which program RNUNLOPM ran, as well as data where the NLOP-MEDMIGKZ field is still blank.
Notes
Since in ISH-Release 4.03A, all IS-H programs (dialog programs, statistics, and so on) access the new structures, you must run the program directly after the put on Release 4.03A. Due to performance reasons, the system will only start the program in the background and at low-volume times.
You must also make sure that after you successfully convert table NLOP, that the surgery monitor immediately accesses the new tables.
You must execute the program in every client.
Requirements
A prerequisite for this program is that i.s.h.med is active. You must also have run
the program RNUNLOPM, which indicates the correctly transferred NLOP records with an X in the NLOP-MIGKZ field.
For the update mode, the new Transaction NEW_OP must be active, which program RNUNLOPM will set to active, if all NLOP records in the NLOP-MIGKZ field have been indicated with an X.
Output
Example
ROGBILLS - Synchronize billing plans SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4237 Date: 20240531 Time: 114224 sap01-206 ( 81 ms )
