Introducing: Quality Management (2026 release wave 1)

Overview

The video introduces a new Quality Management extension. It first demos a purchase receipt that creates an inspection automatically, a failed test that creates a transfer order for the sample quantity, and a sales transaction blocked for the failed lot. It then shows rechecking the remaining quantity and the Certificate of Analysis and Non-Conformance Report documents.

The second part covers configuration: inspection results, quality tests and data types, result conditions and evaluation sequence, table lookups, templates, sampling, generation rules, and blocking by item tracking. It ends with actions for failed or passed inspections, quantity selection, built-in workflows with four events, and API exposure for Power Automate. The speaker says the layout is being changed, so the UI in the release will differ from the demo.

Key points

• Inspections can be created automatically from generation rules tied to events such as a purchase order receipt or a sales return receipt, manually, or on a schedule through a job queue option.
• One failed test marks the whole inspection as failed. A failed inspection can create a transfer order for the sample size tested, not the total received quantity.
• Blocking of sales, purchases and consumption by inspection result works only for items with an item tracking code. Items without tracking need another blocking method.
• When several result conditions apply to a test, the higher evaluation sequence takes precedence. Conflicting conditions need careful setup.
• Default test values mean the system does not register who performed the test, because the line is not modified.
• Table lookup tests let you pick a display field and filter. A row limit in Quality Management Setup controls lookup performance.
• Sampling is a fixed quantity or a percent of quantity, rounded to integers. Built-in workflows have four events (created, changed, finished, reopened) and run in the same transaction, so they roll back on error.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• other “Quality Management Role Center” at 11:33
• other “Certificate of Analysis” at 9:24
• other “Non-Conformance Report” at 10:08
• table “Quality Lookup Test lookup values” at 27:34
• table “Country” at 23:51
• table “GL entries” at 25:44
• table “quality test lookup table” at 28:37
• table “quality management setup” at 35:33

Not found in BC28-30: table “Quality Lookup Test lookup values”, table “Country”, table “GL entries”, table “quality test lookup table”, table “quality management setup”.

Quotes

• 0:06 “In this release, we are adding a new quality management extension. So, now you can install it and comply with the regulatory requirements and”
• 0:34 “you can trigger tests automatically when something happens in the system. You don’t need to worry about it. You can schedule them to do”
• 1:22 “It’s very easy to configure. And it might happen from time to time that as a result of the quality check you discover that”
• 5:01 “One failure is already enough to to mark the whole inspection as failed. So, you can see the result says fail.”
• 7:27 “my transaction my sales transaction was blocked because there is inspection with a result fail for this specific lot of this item and we”
• 12:13 “Set up data are installed automatically with extension, but it is very much isolated, so no impact on any other stuff or functionality of”
• 13:16 “By default, there are three different states, inspection not started or in progress and then failed or passed. But sometimes, the world is not”
• 13:16 “By default, there are three different states, inspection not started or in progress and then failed or passed.”
• 14:14 “result visibility. It says promoted or configuration only. So, promoted, it means it will be visible in many places. For example, in the inspection”
• 14:44 “there is an item with a lot 25 which has inspection in failed status”
• 16:41 “We do not allow inspector to make a typo and enter, for example, 1,000. So, the system just do not accept does not accept”
• 17:43 “But because they do not change the value in the lines, system will not register who actually check this specific line.”
• 26:16 “There is a setup in the quality management setup where we have some setups which actually dictates the number of rows to fetch in”
• 27:12 “As soon as you define decide to use table lookup, the table lookup configuration it gets automatically populated with a very specific table.”
• 29:30 “Now we define the test of different type integer or decimal or maybe date or maybe text or maybe something else. Option lookup and”
• 30:35 “We have two types in addition to to not define uh sample size. We have two types, fixed quantity and percent of quantity.”
• 33:10 “They only work for items with item tracking. For items without tracking, you need to use a different ways to to block them and”
• 35:43 “As I mentioned, once we install this extension because it will be preinstalled, but only for new environments. So, like if you create new”
• 36:44 “Everything else is super safe. So, unless you suspect that you will have a conflict with the quality inspection number series, you’re very safe”
• 38:14 “Uh reopen and deletion is limited by permission. So, if you are not quality management administrator, you cannot do these actions.”
• 39:33 “You can define what quantity to use. You can use the full quantity, you can specify quantity which you can specify here. Or you”
• 40:32 “The standard built-in workflows. We do not have templates because these workflows are very simple, I would say. They are not that complex to”
• 40:54 “When something happens, when event happened and there are four quality management related events.”
• 43:01 “we do expose the similar events and the similar responses through API. So, if you prefer to use Power Automate, go ahead.”
• 43:17 “if you when you create inspection and you plan to block lot, there is no point to call the external engine and do orchestration”
• 44:03 “It runs in the same transaction. So, if something goes wrong, it will be rolled back.”
• 44:27 “It’s actually very good for simple automation. If events and response are present. And for quality management, decent number of events and decent number”

Disclaimers in the video

• 9:35 subject-to-change: We are in the progress of changing layout. So, when you will see this video, I would expect you to see a very different layout.
• 35:43 preview: Quality management will be preinstalled, but only for new environments in the 2026 wave one release.
• 39:46 preview: sample quantity which is right now hiding is also available