Recipient is not an SAP System 
Recipient is not an SAP System
Purpose
If the receiving application is not an SAP System, the asynchronous driver requires an additional message header containing address information. The SAP APC protocol must also be observed.
Process flow
Message Header Structure
Field |
Type/Length |
Explanation |
UTMDAIND |
C8 |
Indicator for message header (set by the SAP-System) |
UTMDPAPPL |
C8 |
Application name of the SAP System (set by the SAP-System) |
UTMDPPROC |
C8 |
Processor name of the SAP application (set by the SAP-System) |
UTMDPCNVD |
X4 |
CONVID of the driver in the SAP System (set by the SAP-System) |
UTMDSAPPL |
C8 |
Application name of the partner application (set only if the SAP System is also the receiving system, otherwise not used) |
UTMDSPROC |
C8 |
Processor name of the partner application (set only if the SAP System is also the receiving system, otherwise not used) |
UTMDSCNVD |
X4 |
CONVID in the receiving system (set only if the SAP System is also the receiving system, otherwise not used) |
If the partner application receives a message with this message header from the SAP driver, it must use this header at the beginning of each APC confirmation message.
The message header is not part of the driver message. It must be removed before any further processing is made. Therefore, the message header is sent as a separate UTM partial message. The first FGET receives the message header, while the second FGET receives the driver message.