sepvalid
This validation framework will take in any UNIFI 20022 formatted XML message and validate UNIFI rules and 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 first input will be the SEPA message that needs to be validated.
- The second input will be the original pacs003 FI To FI Customer Direct Debit message, or the pacs008 FI To FI Customer Credit Transfer. If no original data file is provided, then the matching rules in the SEPA implementation guide will not be processed.
- The third input is a true false value that is passed to turn the UNIFI rules validation on or off. If you want to validate the data for UNIFI rules, then no input is needed, as this is the default. If you want to turn off UNIFI validation, pass in an echoin 0 (zero), as the third input.
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.