Walkthrough: Tomato Intake
This walkthrough describes how to set up Aptean Quality Control for Food and Beverage (BC) after installation so that incoming tomato deliveries are inspected on arrival, and the outcome of each inspection controls what the warehouse may do with the received stock.
Scenario
Tomatoes are received from growers against purchase orders. Each received lot must be inspected on arrival, the results recorded against the lot, and the outcome of the inspection must determine whether the lot can be used, reworked, or rejected. Inspections are performed by a dedicated intake quality team.
What the finished setup does
When a purchase receipt for tomatoes is posted, the system raises one quality control check per received lot and assigns it to the intake team. The inspector records a few readings for the delivery as a whole and then examines two samples, counting defects in each. Two calculated readings turn those counts into a major and a minor damage percentage for each sample.
Posting the check grades the delivery green, amber, or red from those percentages, and the grade sets an inspection status on the lot: accepted stock is free to use, stock held for rework can be processed but not sold, and rejected stock is blocked outright. The sugar reading taken at the door is written to the lot as an attribute, so it travels with the stock.
Before you start
This walkthrough assumes that:
- The Aptean Quality Control for Food and Beverage (BC) extension is installed and enabled. For more information, see Introduction.
- The relevant permission sets are assigned to the users who will configure and perform the checks. For more information, see Manage permission sets.
- Items, vendors, and purchase documents for the incoming tomatoes already exist in Business Central, and the items are lot tracked.
No setup data specific to quality control is assumed to exist. The walkthrough starts from an empty configuration.
Two steps depend on other Aptean extensions and can be skipped if those extensions are not installed. The walkthrough notes what is lost in each case.
In this walkthrough
Follow the steps in order. Each one builds on the records created before it.
| Step | What it covers |
|---|---|
| 1. Configure quality control setup | The number series every other record needs, the reason code for inspection status changes, and where quality check images are stored. |
| 2. Set up the quality control users and teams | The intake team, the manager and inspector who staff it, and the membership that decides who sees which checks. |
| 3. Create the question categories | The major and minor severities that the defect questions are grouped by. |
| 4. Create the quality control equipment | The instruments and methods a reading is taken with, shown to the inspector on the check. |
| 5. Create the quality control options | The fixed answer lists for the readings that are not numbers — a yes or no, and the ripeness stages. |
| 6. Create the Brix lot attribute | The lot attribute that carries the sugar reading on the received lot. Requires Aptean Advanced Attributes. |
| 7. Create the quality control questions | The thirteen readings that make up the inspection, and the type of answer each one takes. |
| 8. Create the tomato intake plan | The inspection itself: how many samples, which questions are asked once and which per sample, what is compulsory, and the two calculated percentages. |
| 9. Add the line targets | The acceptable range for individual readings, so the inspector gets a verdict on each answer as it is entered. |
| 10. Create the score codes | The three grades a delivery can receive, and the result each one carries. |
| 11. Create the inspection statuses | The statuses that control what may be done with the stock. Optional; requires Aptean Inspection Status. |
| 12. Configure the scoring | The thresholds that decide which grade a delivery gets, and certifying the finished plan. |
| 13. Create the intake trigger | The event that raises a check automatically when a delivery is received. |
| 14. Complete the first inspection | Running one delivery end to end to confirm the setup works. |
What gets created
The walkthrough produces the following records. The codes are examples — use your own naming if you prefer, and keep it consistent as you go.
| Record type | Codes created |
|---|---|
| Quality control team | INTAKE |
| Question categories | MAJOR, MINOR |
| Equipment | BRIX, THERMOMETER, VISUAL |
| Options | YES/NO, COLOR |
| Lot attribute | Brix |
| Questions | COLOR, DMG, PHOTOPALL, TEMP, QTY, BRUISING, DECAY, DISCOLOR, MOLD, PHOTOPROD, BRIX, MAJOR, MINOR |
| Quality control plan | TOMATO |
| Score codes | GREEN, AMBER, RED |
| Inspection statuses | QC PASS, REWORK, QC FAIL |
| Quality control trigger | One trigger on posting a purchase receipt |
Start with Configure quality control setup.