sepvalid

This validation framework will take in any UNIFI 20022 formatted XML message and validate the set of rules published by the EPC.

The framework is completely operated by the call of one map, sepvalid. No matter what SEPA message type, this map will pass the data through the validation framework. The framework has the ability to determine if the data is ISO 20022 UNIFI schema data, or if the data is part of the EPC Technical Validation Set, which has two sets of schemas, CORE schemas, which allow only the fields that are required by SEPA, and the CORE plus AOS, which allow additional elements. Custom schemas can also be added.

The main map that is called is sepvalid. Three inputs are allowed:
  • The first input will be the SEPA message that needs to be validated.
  • The second input is used for the original message to support matching rules in the SEPA implementation guide. While the matching feature is deprecated, it will still be performed if the original message belongs to a message version currently supported by SEPA validation; otherwise, no matching will be performed.
  • The third input controls both UNIFI rule validation and support for unstructured formatted addresses. The default setting disables both features. In the updated configuration (with input card 3 renamed to config), use the following parameters:
    enableUNIFI - set to true to enable UNIFI validation, or false to disable it
    allowUnstrAddr - set to true to allow unstructured formatted addresses only, or false to restrict to structured format and hybrid addresses only

    Example:

    enableUNIFI:false;allowUnstrAddr:false - disables UNIFI validation and disallows unstructured addresses

There are 3 Output cards for the sepvalid map. Cards one and two do not produce output files, and card three produces the seperror.xml file that allows you to see all of the validation errors and framework messages produced from the data file. If debugging of the process is required, change the output for card 1 from SINK to File and assign it a file name. This debug file will then serve as a debugging tool, as it contains steps that document where in the process it has been, and what was performed.