Description
This program transfers all of the EDI data collection points for thecost objects (database table NKTR "cost object master data") to the newadministration table NC301KTR in IS-H Release 4.01.
All of the NKTR entries with data collection information are read. Aseparate entry in the NC301KTR table is created for each of these costobjects. The specified data collection point is copied directly. TheNKTR entry remains unchanged.
This program is not relevant for hospitals that are not using the §301or §321 functionality yet.
With all other hospitals (§301 and §321 users), the program must beexecuted before standard production operation starts. Otherwise datamay be lost with §3x1 processing.
If problems occur during the put, the put can be continued. Thisprogram must be restarted immediately afterwards (in the background).Any errors should be corrected first (see below).
The program can be restarted at any time. In this case, only thecorresponding entries from the NKTR are inserted in the NC301KTR tablethat are not already present. Discrepancies between the number ofexisting entries and the number of entries transferred are listed inthe log.

Output
A client-specific log of the activities carried out is output.Depending on how they are used, activities may not be possible ornecessary in certain clients. This could be due to:
1) Clients that do not use IS-H (e.g. 066 Early Watch) or the §301 and§321 functionality. The log then usually contains the message
TN00 could not be read for client 066
or
No NKTR entry with data collection point. Nothing to do in
client 066.
This is ok.
2) Clients in which the IS-H country version is not specified or wherethe country version is not 'DE' or 'AT'. This is indicated as follows:
TN00 country version missing in client 123
or
Nothing to do: TN00 country version in client 123 is US.
In this case, you must check whether IS-H is actually used in thecountry version 'DE' or 'AT' in these clients. If this is the case, youmust maintain the country version (in the client, transaction SM30,view TN00) and restart the program.
3) Clients whose data has already been fully processed in a previousrun. In this case, the following message is displayed:
0 NC301ktr entries inserted in client 123.
In addition to the above, the following messages or situations canoccur (particularly when the program is restarted (after put problems;otherwise this is not necessary/meaningful)):
1) The following message appears
Client 123 mismatch betw. NC301KTR & NKTR entries: 11 vs. 7.
In this case, the (new) table NC301KTR contains 11 entries even thoughthe program has determined that only 7 are to be copied from NKTR. Thismeans that entries have been added to the table NC301KTR in anotherway. The data may have been changed in the meantime (since the lasttime the program was executed). This situation cannot occur the firsttime the program is run. The different entries should be determined andanalyzed by the application (transaction SE16).
2) The following message appears
Client 123 mismatch betw. NC301KTR & NKTR entries: 7 vs. 11.
In this case, the table NC301KTR contains fewer entries than expected.This may be due to the fact that the INSERT failed repeatedly (duringthe initial run) or that the data was changed in the meantime. Thissituation can usually be rectified by restarting the program.