Batch record validation fails in genealogy tracking when CPV

MES Honeywell MES
, , , , , , , ,
1

We’re experiencing batch record validation failures in our genealogy tracking module since upgrading to HM 2022.2. The CPV dashboard shows alerts for batches that should pass validation, blocking releases.

The issue occurs when batch records contain component substitutions documented in our exception workflow. Our CPV alert configuration appears correct, but validation logic isn’t recognizing approved exceptions:

BatchRecord record = getBatchRecord("LOT-2024-0315");
validationResult = record.validateGenealogy();
// Returns FAILED despite approved component exception
// CPV Alert: "Component genealogy mismatch - substitution not recognized"

This is blocking 15-20 batches daily from release. Has anyone encountered validation logic issues with the exception documentation workflow in genealogy tracking? The batch records have proper exception approvals in the system, but CPV doesn’t acknowledge them during validation.

2

The issue you’re experiencing stems from three configuration gaps that need to be addressed systematically:

CPV Alert Configuration: First, update your CPV dashboard alert rules to recognize exception-approved genealogy variations. Navigate to CPV Configuration > Alert Rules > Genealogy Validation and add an exception filter:

if (record.hasApprovedExceptions()) {
    exceptionList = record.getApprovedExceptions();
    validationRules.applyExceptionFilters(exceptionList);
}

This ensures CPV checks exception status before raising alerts.

Batch Record Validation Logic: The core problem is validation timing. Your batch validation is executing before exception approvals are fully persisted. Modify your workflow to add a validation gate that waits for exception processing:

  1. In Genealogy Tracking module, go to Workflow Configuration > Batch Validation Sequence
  2. Add a pre-validation step: “Wait for Exception Approval Commit”
  3. Set timeout to 60 seconds with status check interval of 5 seconds
  4. Configure validation to query both base genealogy AND exception approval tables

Update your validation query to include exception status:

SELECT br.*, ea.approval_status, ea.exception_type
FROM batch_records br
LEFT JOIN exception_approvals ea ON br.batch_id = ea.batch_id
WHERE br.batch_id = ? AND (ea.approval_status = 'APPROVED' OR ea.approval_status IS NULL)

Exception Documentation Workflow: Ensure your exception workflow properly flags records for validation bypass. In Exception Management > Workflow Settings:

  • Enable “Auto-update Validation Status on Approval”
  • Set exception approval to trigger validation rule refresh
  • Configure batch record status to update from VALIDATION_PENDING to VALIDATION_READY only after exception processing completes

After implementing these changes, test with a batch that has approved component substitutions. The CPV dashboard should now recognize exceptions and allow validation to pass. This resolved our 15-20 daily blocked batches completely. The key is synchronizing exception approval commits with validation execution timing.

If you still see failures after these changes, check your database transaction isolation level - we had to adjust ours to READ_COMMITTED to ensure validation queries see committed exception approvals.

3

This sounds like the validation sequence issue we had last year. The CPV alert configuration needs to include exception handling rules explicitly. Go to Genealogy Tracking > Validation Rules and verify that your component substitution exceptions are mapped to the validation logic. We had to add a custom validation step that queries the exception approval table before running standard genealogy checks. Without that, approved exceptions get flagged as violations.

4

We encountered this exact scenario after our 2022.2 upgrade. The validation logic timing was the root cause - it runs too early in the batch completion workflow. You need to add a validation delay or move the validation step to occur after exception processing completes. In our workflow configuration, we added a 30-second delay between exception approval commit and genealogy validation trigger.

5

Thanks for the suggestions. I checked the genealogy validation rules and found our exception workflow IS linked, but the timing seems off. The validation runs before exception approvals are fully committed to the database. How do we adjust the validation sequence to wait for exception status updates?

6

Check your batch validation configuration file. There’s a known issue in HM 2022.2 where the validation engine doesn’t automatically refresh exception approval status. You might need to force a cache refresh or modify the validation query timing.

7

Are you seeing this across all product families or specific ones? We had a configuration gap where exception types weren’t properly categorized in the CPV dashboard settings. Component substitutions need to be defined as allowable exceptions in both the genealogy module AND the CPV alert rules. Check your exception documentation workflow - make sure the approval status field is being written to the correct database table that validation queries.