.svg)
The 5-Second Explanation:
Data lineage describes the complete path data takes – from its original source through every processing step to its current use. It shows where a data value comes from, what transformations it has gone through, and where it's being used today.
An Example:
A customer address is first created in the KNA1 table in the SAP ERP system. From there, it's extracted and transferred to a CRM system, where it's used for sales reporting. Data lineage traces exactly this path – and reveals where in the process outdated or incorrect data may have originated.
Why is this important?
- Error Analysis: When a metric looks off, data lineage lets you trace it back to pinpoint exactly which processing step caused the deviation.
- Trust in Data Products: Traceable data lineage shows whether a data product is based on reliable, up-to-date sources (see glossary entry "Data Products").
- Compliance and Audit Readiness: Documented data lineage can help meet regulatory documentation requirements more easily – though it does not replace a dedicated compliance review.
- Foundation for Data Governance: Only by understanding data lineage can responsibilities (data owners) and quality standards be meaningfully assigned across the entire data flow.
Want to trace the origin of your SAP data across systems? The Enterprise Glossary in Xtract Universal․iQ shows end-to-end lineage down to the table level – from the SAP source table all the way to the final report.
