The purpose of this transaction is to edit incoming electronic messages. In practise, this may become necessary if a message cannot be processed because of problems inherent in the structure of the message - such as an incorrect sequence in Tag 27, for example.
If incomplete partial messages are corrected in such a manner that the association is automatically identified, then the messages will be joined.
Use the “Search panel” to select the relevant message.
Clicking creates a duplicate of the message that can then be amended manually.
The copy of the message is displayed in an editable file on the “Edit” panel and can be edited as required.
The transaction does not carry out any plausibility checks or verifications to establish whether the message is correct in technical/structural terms. The user is responsible for the content-related and structural correctness of the message.
Clicking [ Save] saves the edited message as a copy of the original and displays this as an SPT incoming messages is the list of pending transactions under todays date.
In the process, the mapping is additionally carried out for the message edited and/or the partial messages that are now joined.
The original message remains unchanged, and the SPT may have to be processed manually by the user.
Clicking the button [ Show Diff] will display the changes made to the original message.
Datafield | Description |
---|---|
All Visible Entities | If this checkbox is checked, the transaction carries out the configured functions (generating queue entries and prioritization/load distribution) for all entities for whom the executing user is authorized. |
Datafield | Description |
---|---|
External Key | cf Appendix A, Table SMH field EXTKEY |
Creating User | cf Appendix A, Table SMH field CREUSR |
Name | cf Appendix A, Table SMH field NAM |
Timestamp of Creation | cf Appendix A, Table SMH field CREDATTIM |
Direction ('>'=Outgoing, '<'=Incoming) | cf Appendix A, Table SMH field DIR |
Structure/Syntax of Message (SWT, LET, TLX, TCO) | cf Appendix A, Table SMH field CORTYP |
Type of Copy | cf Appendix A, Table SMH field ORIFLG |
Document Path (Relative to Application or Data Root) | cf Appendix A, Table SMH field DOCPTH |
Internal Unique ID | cf Appendix A, Table SMH field INR |
Document Name (File ID) | cf Appendix A, Table SMH field DOCFIL |
Object Type | cf Appendix A, Table SMH field OBJTYP |
Object INR | cf Appendix A, Table SMH field OBJINR |
Document Format (RTF, TIF, TXT etc.) | cf Appendix A, Table SMH field DOCFXT |
Type of Transaction | cf Appendix A, Table SMH field TRNTYP |
Transaction Handling the Document | cf Appendix A, Table SMH field TRNINR |
Position of Message in Document | cf Appendix A, Table SMH field MSGPOS |
Length of Message in Document (0=Rest of Document) | cf Appendix A, Table SMH field MSGLEN |
Frame Used to Create the Transaction | cf Appendix A, Table TRN field INIFRM |
INR of the 1st of Split/Partial Messages | cf Appendix A, Table SMH field GRPINR |
Sequence Number of Partial Messages | cf Appendix A, Table SMH field GRPSEQ |
Counter of Partial Messages | cf Appendix A, Table SMH field PARTFLG |
PTA Receiving Documents | cf Appendix A, Table SMH field PTAINR |
External Key | cf Appendix A, Table ADR field EXTKEY |
Application Form | cf Appendix A, Table SMH field APF |
Name | cf Appendix A, Table ADR field NAM |
Receiver Key (BIC/Telex#/Fax#/Email) | cf Appendix A, Table SMH field SNDKEY |
Datafield | Description |
---|---|
SWIFT | This checkbox defines if incoming SWIFT messages should be imported. Details are determined on the relevant panel. |
Text for Header | cf Appendix A, Table PRT field HEATXT |
Technical Form | cf Appendix A, Table PRT field TEF |
Use Printer Configuration from: | cf Appendix A, Table PRT field GETPRT |
Printer | cf Appendix A, Table PRT field PRT |
Paper Tray | cf Appendix A, Table PRT field BIN |
Tray for 2nd Page | cf Appendix A, Table PRT field BIN2 |
Number of Copies | cf Appendix A, Table PRT field CPYCNT |
Unzip attachments | If this flag is checked, Zip files from incoming Score messages will automatically be unzipped and added to the message. This is in addition to the zip file (i.e., the actual zip file will also be present in the message). |
Unzip and Delete attachment | If this flag is checked, the original zip file will be deleted after it is unzipped in the message. That means, only the actual files of the zip file which were unzipped, will be available in the message for viewing. However, this flag will be enabled for selection only if “Unzip zipped Score Fileattachments” flag is selected. |