Browser-based message printing

Users of the MER facility can manually print the currently viewed message or several messages from a message list on a printer that can be accessed from the browser. In addition, MER actions can be configured to automatically initiate the printing of the processed message on such printers. For each MER queue you can configure:
  1. A print action to print a selected message.
  2. A standard business action or a custom action which initiates printing of the message that was submitted for business routing. Any standard business action or custom action available for this queue can be configured for printing.

For details, see Creating new queues.

When printing is initiated, a formatted output of the message is created. The Web browser is responsible to print the formatted output. Message printing is not initiated if the standard business or custom action is interrupted or an error is encountered.

The printout format consists of the following areas:
  • General information (like queue name, user action, message type, or print timestamp)
  • Context information (like OU name, message ID, or local address)
  • Message header information
  • Message payload information
Each field in the payload is formatted according to the message definition. The print format includes only fields that contain data. Each line is limited to 80 characters. A message ends with a separator line. Figure 1 shows an example of a printed message.
Figure 1. Example of an MT103 message printout format
Msg Type: FIN103                          Queue : FIN1Authorize
UTC Time: 20160123 093355                 Action: Reject
================================================================================
Context Information
--------------------------------------------------------------------------------
OU            : OU1
Message ID    : 7f28e108430411e48bff0998504600000000000000000000
MER Message ID: 101084
--------------------------------------------------------------------------------
Local Address : IBMADEFFAXXX
Remote Address: IBMADEF0AXXX
Comment       : This is a comment line
================================================================================
Basic Header
          Application Id F APDU Id 01 LT Address IBMADEFFAXXX
          Session Number 0000 Sequence Number 000000
Application Header
          Input Identifier I Message Type 103
          Destination Address IBMADEF0AXXX Priority N
          Delivery Monitoring Obsolescence period
Sender's Reference *20
          MSG2016011400001
Bank Operation Code *23 Option B
          Type CRED
Value Date/Currency/Interbank Settled Amount *32 Option A
          Date 140922 Currency EUR Amount 113,5
Currency/Instructed Amount 33 Option B
          Currency EUR Amount 113,
Ordering Customer *50 Option A
          Account 12345678
          Identifier Code IBMADEFF
Beneficiary Customer *59 Option A
          Account /12345678
          Identifier Code IBMDDEFF
Details of Charges *71 Option A
          Code SHA
Sender's Charges 71 Option F
          Currency EUR Amount 1,
========================================================= End of Message 1/1 ===

If message warehouse recording is enabled in your business routing flows, the time of the last standard business or custom action invoked by browser-based message printing is stored in field MWH_EXTENSION_DEF1 of the corresponding record.