How do you ensure data integrity when pulling from multiple disparate legacy systems?
Use the provided legacy source records, identifier mappings, and canonical AMD product data to produce an integrity audit. Flag every source record that is duplicated, unmapped, mapped to a missing canonical product, or inconsistent with its canonical attributes.
record_id, source_system, legacy_part_id, canonical_part_id, integrity_status, and issue_detailssource_system, legacy_part_id, and record_id ascending| Column | Type | Description |
|---|---|---|
| record_idPK | INT | Unique source record identifier |
| source_system | VARCHAR(50) | Name of the legacy source system |
| legacy_part_id | VARCHAR(50) | Part identifier from the source system |
| part_name | VARCHAR(150) | Part name extracted from the source |
| unit_price | DECIMAL(12,2) | Unit price extracted from the source |
| extracted_at | DATE | Date the source record was extracted |
| Column | Type | Description |
|---|---|---|
| map_idPK | INT | Unique mapping identifier |
| source_system | VARCHAR(50) | Legacy source system name |
| legacy_part_id | VARCHAR(50) | Source system part identifier |
| canonical_part_id | VARCHAR(50) | Mapped canonical product identifier |
| Column | Type | Description |
|---|---|---|
| canonical_part_idPK | VARCHAR(50) | Canonical product identifier |
| part_number | VARCHAR(50) | Canonical product number |
| canonical_name | VARCHAR(150) | Approved canonical product name |
| standard_unit_price | DECIMAL(12,2) | Approved standard unit price |
| active | BOOLEAN | Whether the canonical product is active |