Exception Codes

Appendix A — Configuration Reference

Exception codes are short identifiers for documenting why a mapping deviates from the standard pattern. They provide a consistent, reportable vocabulary for conditions that need to be communicated to developers, reviewers, or the target system team — data quality issues, scope decisions, deferred work, and similar.

Fields

Code — The short identifier used in notation content and reports. Keep codes brief and self-documenting (e.g., DQ-NULL, DEFERRED, NO-SRC).

Description — A full explanation of what this code means and when it applies.

Severity — Classifies the exception as Info, Warning, or Error. Used for filtering and reporting.

Disposition — Documents the expected resolution or outcome for mappings carrying this code.

Usage Guidance — Optional notes on when to use this code versus similar ones.

Notes

Exception codes are a communication tool across the whole team — analysts document why a mapping deviates, developers know what conditions to handle in the loader, and SMEs and reviewers understand what to expect when something goes wrong. A well-defined set of codes means everyone is working from the same vocabulary rather than interpreting free-form notes independently.

The default logic templates include a Common Routines category whose templates are pre-written to reference the built-in exception codes. If you rename or replace those codes, update the corresponding templates to match.