Description
The program transfers the old entries from the message exclusion tableTNC301EX into the new table TNC301MX.
The program is not relevant for hospitals that have still to implementthe EDI functionality.
All other hospitals must run this program before commencing normalproduction operation. Otherwise message exclusions are without effectin message dispatch.
Should problems arise during the release upgrade, the upgrade can becontinued. However, you must execute the this program again afterwards.
You can execute the program again at any time.

Output
The program outputs a log of the actions performed by client. Dependingon which EDI procedure is used in certain clients, actions may not bepossible or necessary:
In such cases, the following message is issued:
No entries to copy. Nothing to do in client xxx
If Customizing entries or SAP tables are not correctly maintained, thefollowing error messages are issued:
RESET N1
T000 could not be read
Clients could not be read.
No standards assigned in TNC301GS
EDI procedures/standards are not defined.
Entries in TNCT0 are missing
Messages types are not defined for the standards.
EDI procedure xxxx in table TNC301GS not found.
An entry from TNC301EX could not be transferred, since the proceduredoes not exist. Check whether this is a valid procedure, and, if so,manually maintain the entry.
Other messages can be issued while the data is being copied:
RESET N1
Update of TNC301MX failed: institution insurance message-type
Insert failed. Try again later or make a manual entry in Customizing.
Client xxx 10 entries already exist in TNC301MX.
20 of 30 entries inserted.
A number of the entries to be inserted already exist and are notinserted again. (Can be issued during a repeat run of the program).
123 entries inserted.
All of the entries from TNC301EX were transferred into TNC301MX.