Individual MX validation maps
The MX validation maps validate for schema, BIC, IBAN, currency code, decimal places, and country codes for supported message types.
The map source for these maps is organized into map source files named according to their business function. For example, mx_acmt_validation is for all of the acmt messages. See List of supported messages for a full list of supported MX messages.
These maps all have the same five inputs and four outputs:
| Input/output | Description |
|---|---|
| Input 1 (mx) | The MX data file compatible with the map input card definition. This card is overridden when this map is called from the swiftval framework map. |
| Input 2 (mxconfig) | The MX map configuration data. See MX configuration file. |
| Input 3 (bicDirectory) | The BIC information file. |
| Input 4 (ccyCtryCodeList) | The currency code and decimal places information file. |
| Input 5 (errorMsgList) | The source file for all of the error messages. |
| Output 1 (SchemaValidation) | This card uses the GETXMLERRORMSG function to retrieve all of the XML schema errors in the XML document. This card uses the Sink adapter. |
| Output 2 (CurrencyAndAmountsList) | This card collects all of the elements from the data that needs to be validated. This card uses the Sink adapter. |
| Output 3 (validate) | This card uses the output from the CurrencyAndAmountsList output card to validate the data. It captures the errors through a series of rule checks to validate BIC, IBAN, country code, currency code, and decimal place values. |
| Output 4 (ErrorCollector) | This card collects all of the error information that is generated by the map. The SchemaValidation and the validate card outputs are captured in this card, and then sent as output from the map through the file adapter by default. When used as a RUN map, this output is passed back to the framework by use of the ECHOIN function. |
You can run the individual MX validation maps using the framework map, or you can run the validation map that is in the relevant map source file to override the first input with MX data to validate. The other inputs remain static for optimal performance. The first four inputs for these maps are overridden when using the framework map in calling these extended validation maps.