Understanding Contract validation
The BL_021__VS_CONTRACT job sequencer orchestrates the execution of the Contract validation jobs.
In order to save processing time, the sequencer first checks the parsed datasets produced by SIF Import phase to see if records specific to each RT/ST being processed exist before executing the validation logic. If there are no records to be validated for a specific RT/ST, the validation job will be bypassed for that RT/ST. An empty dataset with correct metadata and name (to be consumed by downstream jobs) will be created instead
Contract validation jobs
BIL Contract validation jobs check all the code types against the code tables in the MDM database and applying business rules when necessary. The validation jobs capture, format and output Data Quality Errors it encounters into a related Data Quality Error Message text file.
Contract Validation jobs consists of a VSVAL* shared containers containing RT/ST specific validation logic and an Edit/Extension Point shared container. The Edit/Extension Point shared containers are an advanced feature to allow for customization by the client / customer.
The new BIL Import SIF process creates a RI_Contract_SUBSET dataset that will overwritten by the BL_021_VS_Contract job when validation is required.
The following table summarizes the BIL Contract Validation jobs. It presents each BIL job with their corresponding RT/ST and the validation shared container it references.
|RT/ST||BIL Contract Validation Job||Reference Shared Container|