Understanding Party validation
The BL_020__VS_RI_EC_PARTY job sequence orchestrates the execution of the Party validation jobs.
In order to save processing time, the sequencer first checks the parsed datasets prepared by the SIF Import stage to see if records specific to each RT/ST being processed exist before executing the validation logic for that RT/ST. If there are no records to be validated for a specific RT/ST, the validation job will be bypassed for that RT/ST and an empty dataset with correct metadata and name (to be consumed by downstream jobs) will be created instead.
Party Validation jobs
The BIL Party Validation jobs check all the code types against the code tables in the InfoSphere 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.
Party 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 following table summarizes the BIL Party Validation jobs. It presents each BIL job with their corresponding RT/ST and the validation shared container it references.
|RT/ST||BIL Party Validation Job||Validation Shared Container|