Inbound Mappers

The IBM® FIN Mapper Pack inbound mappers expect to have access to the information shown in Input mapper context data in Coding input mappers. The inbound mappers all start with the FINToISFMapper subflow. It starts with the BeginMapper subflow and terminates with the EndMapper subflow. It calls the FINToISFCommonMapper subflow for the processing in between.

Figure 1. FINToISFMapper subflow

The FinToISFCommonMapper is shown in the following figure.

Figure 2. FINToISFCommonMapper subflow

It starts with the CheckConfig node, which is responsible for preparing the input message for processing by the standard processing node. It also determines the business concept that the customer wants this SWIFT message to use. Valid messages are passed to the FxhStandardsProcessing node to convert the MTFIN (BLOB) messages into a MTXML (XMLNSC) messages.

Invalid messages are sent to the CreateErrorDoc node, which builds an error message for the physical transmission. If the FxhStandardsProcessing node encounters errors converting the message, it routes the results to the CreateSPNErrorDoc node, which builds an error message for the physical transmission.

The messages that are converted successfully by the FxhStandardsProcessing node are passed to the Process MT XML Input node, which stores the formatted message (blocks 1, 2, 3, 4, and 5) in the Environment.PMP.Variables.SWIFT_MT_MAPPER.Message. It also builds the skeleton of the EndMapper2 message, including the ISF skeleton in the output message.

The message is then passed to the Route to Mapper Sequence subflow, which determines the next subflow to pass the message to.

For more information about this process, see Routing Between Mapper Subflows. When the message has been mapped, the results are returned to the FinToISFMapperRouteBackLabel node. Finally, control is returned to the FINToISFMapper subflow.