Non Conformance Management
Release: Non Conformance Management – 27.0.9679.34444
Description
This release introduces a major new feature for root cause analysis through Reason Code and Sub Reason Code management, adds a Document Date field on Non-Conformance records, and fixes several bugs including French translation corrections and action plan user-task synchronization. These enhancements strengthen the NCM module’s ability to support quality investigations, statistical reporting, and continuous improvement — particularly relevant for Food & Beverage industry compliance and QMS alignment.
User Stories
| Title | Description | Setup Instructions | Impact on previous version |
|---|---|---|---|
| [23786] – Reason Code and Sub Reason Code missing | Added hierarchical Reason Code / Sub Reason Code classification to Non-Conformance records, enabling root cause analysis, Pareto analysis, and quality KPI reporting. Reason Codes represent why an issue occurred (distinct from Source/Origin which is where it was detected). New tables briNCM_NonConformanceReason (8121070) and briNCM_NonConformanceSubReason (8121071) with Code[20] + Description Text[200]. Fields added on NC Header (fields 21, 22), NC Card (new “Analysis” group), NC List (hidden columns), API v1.0 query, Report v2.00, and Word Labels. Assisted Setup includes a default demo dataset for industry-standard reason codes. |
Reason Codes are configured via Non Conformance Setup > Reasons action. Sub Reasons are accessed via drilldown from a Reason Code. The Assisted Setup wizard now includes a step to create default demo Reason Codes. Impacted objects: Tables 8121070, 8121071; Pages 8121070, 8121071; Table 8121050 (fields 21, 22); Pages 8121013, 8121061, 8121004; Query 8121000; Report 8121001; Codeunit 8121004, 8121041; PermissionSets 8121000, 8121001, 8121002. | New additive fields — no breaking change. Existing Non-Conformance records will have empty Reason/Sub Reason Code until manually populated. Permission sets updated to include new tables and pages. |
| [24199] – Add Document Date Field On Non Conformance | Added an editable Document Date field on the Non-Conformance Header, allowing quality managers to record a date prior to the system/work date when there is a delay in creating the non-conformance. Document Date is initialized to WorkDate() on record creation and is used as the base date for Estimated Closure Date calculation. | No additional setup required. The Document Date field appears in the General group of the NC Card (editable when Status = New) and as a visible column on the NC List. Impacted objects: Table 8121050 (field 20); Pages 8121013, 8121061; Report 8121001; Codeunit 8121031. | New additive field — no breaking change. The GetCreateByUserName method has been renamed to GetCreatedByUserName (internal only, no external impact). Estimated Closure Date is now calculated from Document Date instead of WorkDate(). |
Bugs
| Title | Description | Impact on previous version |
|---|---|---|
| [23959] – Report selection for non conformity reports: wrong translation in French | The French caption of the Report Selection page for Non-Conformances (briNCM_RprtSelctnNonConformnce, page 8121028) was incorrectly translated as “Sélection du rapport - Non-conformité”. Corrected to “Sélection des états : Non-Conformité” to align with standard Business Central terminology in French. |
Translation-only fix. No functional or data impact. |
| [23961] – Non-conformance line: wrong French translation in the “Source Amount” field | The French translation of the “Source Amount” field on Non-Conformance Lines was incorrectly rendered as “quantité de source” (Source Quantity). Corrected to “Montant Source”. | Translation-only fix in .xlf files. No functional or data impact. |
| [23969] – Action plan task given to another person not following into action plan card | When a User Task assigned to an Action Plan line was reassigned to a different user via the User Task list/card, the change was not reflected in the Action Plan line’s “Assigned User Task To” field. Root cause: no event subscriber was wired to the Assigned To field validation event on the User Task table. Fix: a new subscriber OnAfterValidateAssignedTo in briNCM_UserTaskSubscriber (codeunit 8121014) now subscribes to OnAfterValidateEvent on field “Assigned To” of the User Task table, calling UserTaskManagement.UpdateRelatedActionPlanLineAssignment(Rec) to propagate the change. |
Low regression risk. New subscriber is additive. The UpdateRelatedActionPlanLineAssignment procedure in codeunit 8121015 was already present but not being triggered. |
Events
No event added or updated in this release.