In the data architecture of Dynamics 365 Supply Chain Management, transactional entities such as non-conformances are defined using a standard pattern. The primary table, which holds the main header information for each unique non-conformance record (e.g., non-conformance ID, date, problem type, status), is referred to as a document table. This table serves as the foundation for the non-conformity entity. While other tables may store related details like corrections or logged history, the document table is the essential component used to introduce and define the core entity.

A: A document history table is designed to store posted, finalized transactions for archival and auditing purposes, not to define active, in-process entities like a new non-conformity.

C: While a non-conformity can have related details, the term "supplemental table for lines" is not the standard architectural component for defining the main entity itself; it would hold subordinate detail records.

1. Microsoft Learn. "Create and process a nonconformance." Dynamics 365 Supply Chain Management Documentation. This document outlines the process of creating a new non-conformance, which involves creating a new record in the main header table (InventQualityOrderTable), demonstrating the role of a central document table in defining the entity.

2. Microsoft Learn. "Tables in finance and operations apps." Finance and Operations apps development Documentation. This article discusses table properties, including the TableGroup property. The primary table for non-conformances (InventQualityOrderTable) belongs to the Transaction group, which is characteristic of document tables that hold the main records for business events.