1. Ticket Details
| Field | Description |
|---|---|
| Ticket ID | AMM-1420 |
| Severity | Critical |
| Category | Bug |
| Affected Module / Feature | MMU |
2. Issue Description
For SJVN and APL MMU project we are missing 238 beneficiaries demographic and transactional data
3. Root Cause Analysis (RCA)
Use one or more of the following techniques for RCA:
5 Whys
Fishbone (Ishikawa) Diagram
Fault Tree Analysis
Log/Trace review
Primary Root Cause Identified: The issue occurred because the VanSerialNo (used as the foreign key for beneficiary identity) was not mapped correctly in some tables, causing demographic and transactional data to be missed.
Why it happened: The sequence and mapping logic for VanSerialNo was not implemented properly, so the foreign key relationship between tables was broken due to missing VanSerialNo.
Why wasn't it caught earlier? There was no validation or reconciliation check to ensure VanSerialNo mapping across all tables, and testing did not cover this specific scenario.
4. Corrective Actions (Fixes for this instance)
| Action | Owner | Target Date | Status |
|---|---|---|---|
| Corrected the data mapping logic to ensure VanSerialNo is properly set as the foreign key across all relevant tables. | Vanitha | 2025-08-11 | Completed |
| Adjusted the sequence of data population so that VanSerialNo is assigned before dependent demographic and transactional records are saved. | Vanitha | 2025-08-11 | Completed |
| Validated and reprocessed the affected data to restore proper linkage between beneficiary identity, demographic details, and transactional data. | Vanitha | 2025-08-11 | Completed |
Immediate actions to resolve the issue and restore service.
5. Preventive Actions (To prevent recurrence)
| Action | Owner | Target Date | Status |
|---|---|---|---|
| Enforce mandatory validation for VanSerialNo before saving demographic or transactional records. | Vanitha | ||
Add database-level constraints (e.g., NOT NULL / foreign key checks) to prevent records from being created without a valid VanSerialNo. | Vanitha | ||
| Implement automated data integrity checks and alerts to identify any record missing VanSerialNo. | Vanitha |
Systemic changes, monitoring, alerting, process updates, or automation.
6. Verification of Effectiveness
Post-fix validation confirmed that VanSerialNo is now consistently mapped across all demographic and transactional tables.Monitoring reports for recent syncs show no missing or null VanSerialNo values.
Database audit queries run after the fix confirmed 100% integrity in mapping.
7. Lessons Learned
Sequence of data mapping is critical — dependencies like VanSerialNo must always be assigned before saving linked records.
Missing foreign key values can cascade into multiple downstream data issues (demographic and transactional data mismatches).
Clear communication between development, QA, and operations teams ensures awareness of such critical linkages.
8. CAPA Review & Closure
| Reviewed By | Date | Remarks |
|---|---|---|