Skip to content

On demand · Product video

Create a corrective action report from a failed test in Quality Inspector

For quality teams that need a corrective action or non-conformance report started every time a receiving inspection fails.

Recorded May 31, 2023 · 11 minutes

Quality Inspector corrective action reports video thumbnail

Summary

Quality Inspector can create one test from the result of another, such as a corrective action report when a receiving test fails. The video sets up a receiving test that is created when a purchase order is received, a corrective action report template with a test generation rule based on quality inspection tests, and a source configuration that carries the item, variant, and lot forward. A Business Central workflow creates the corrective action report whenever a receiving test is finished with a failing grade. The video then receives a lot, fails the test, fills in the corrective action report, and runs a non-conformance report.

Key topics

  • Generate a follow-up test from another test
  • Carry the item, variant, and lot to the new test
  • Create a corrective action report with a Business Central workflow when a test fails
  • Run a non-conformance report on the results
Read the transcript

We’re going to walk through an example of creating a test from the results of another test. One example of where you might want to do this is a corrective action report or a non-conformance report. When an inspection has failed, you might need to issue another test that somebody else works on, or that somebody else uses to analyze the root cause. In today’s example, we’re going to use a receiving test as the initial test that introduces the failure.

Let’s look at our test templates. We have a couple of receiving examples, but the one we’re using today has height, length, width, and a visual inspection, and we’re associating it with anything we receive. If you wanted it to be item-specific, you’d put in conditions for the item, or perhaps the item category. On our Quality Inspector setup page, we also have the receiving automation set for when the purchase order is posted. So the rule, the template, and the setting together say that whenever a purchase order has been posted, automatically create this test.

Our secondary test is this corrective action report. It has some of the common questions you might ask: the kind of corrective action report, its classification, the objective evidence, root cause findings, and things of that nature. For the test generation rules here, we’re generating it based on a quality inspection test whenever the template code is any of the receiving template codes. You’ll notice I’m using a pattern, not referencing a specific template. You could leave it blank, or put in a specific one if you wanted one-to-one mapping of a follow-up test, such as a corrective action report, to an individual test. It’s all configurable.

So we have two tests that we’re linking together: the corrective action report is the secondary one, and the receive test is the one that originally produces it. The final step on the table configuration is the source configuration. Here we’re creating a test from a test, so our from table is the quality inspection test, and we’re creating this corrective action based on the same item, variant, and lot. In your processes, the secondary test might be based on something different, perhaps the customer, the vendor, or the purchase order itself. Whatever information you have available to connect it, that’s all you need to carry it forward.

So now we’ve told the system how to map the fields: item, variant, and lot. We have our two templates. We’re triggering the receive template off the purchase line, and the corrective action template off another quality inspection test. The very final thing is on the Business Central workflow side. You could probably do this with Power Automate, but we’re using a workflow so it’s all within the same transaction. If you didn’t care about transaction integrity, you could use Power Automate and connect it up with the actions, so when the record has been created, call back and create a test. That’ll work fine.

We call the workflow Issue a Corrective Action Report, and we say when a test is finished. This is in the context of the first test, the receiving test. When I’m finishing a receiving test and the grade is failed, then I choose what to do. So whenever the test is finished, that triggers this workflow; the template code can be any template that starts with REC, and whenever one of those fails, we create another test. We enable it, and that should be it.

Let’s walk through an example. We create a purchase order and choose an item that’s lot tracked, our ethernet cable, from the Green location in CRONUS, and we’ll choose 16. We release the purchase order and create the warehouse receipt. If you’re using Warehouse Insight or WMS Express, when you receive the goods into your facility you’d typically use a scan gun. We’ll pretend we’re using something like that and type in the lot number directly, receiving the full 16.

We post our receipt, and this automatically creates that first test for us. We see the receive test in progress, and now we want to fail it and get the corrective action report test created automatically. We put in some values that cause a failure: 29, just under the boundary, and for the packaging visual state, heavy damage. The test is now in a failed state. We say we’re finished testing, these are definitely the values, and finishing it triggers the Business Central workflow for when a test is finished. We see it created a new test, the corrective action report.

In circumstances like this, you could connect to Power Automate for things like notifying in Teams or sending an email if you needed to notify somebody immediately, or add other actions in the Business Central workflow. Regardless, we now have this corrective action report, and it’s associated with the same item and the same lot. Again, you can connect this up to whatever you happen to be configuring it with.

Let’s put in some initial values. For the requirement clause, initial spec not met. This is a major failure. The non-conformance is that the cords should be gray, and these cords are blue. The objective evidence could be an attached photo; you could take a picture and attach it immediately, or use attachments. For containment actions, we’ll say we won’t do this again. The root cause is a missed specification to the vendor, so in this case it’s our fault. Verification of effectiveness is a visual inspection on the vendor spec going forward, and we choose the customer service representative from our database.

Now we have some data, and we can run one of the built-in reports, or your own reports, to help categorize this kind of secondary test. Here’s our non-conformance report, and you could also run some of the other example reports we have out of the box. So this is an example of how you associate one test with another, such as a non-conformance report or a corrective action report. You can change these as much as you want, or you can use Power Automate to integrate with things like notifications or hooks from SharePoint.

Questions about this webcast?

Send your question and the Insight Works team will reply by email. Ready to plan a project? Contact your Microsoft Partner.

Ask a question

Webcast Questions