What data looks like for this category
Data for this category typically comes from ERP/WMS systems, barcode or RFID collection devices, purchase work orders, bin location ledgers, AGV conveyance systems, and weighing equipment. Daily maintenance documents include receiving slips, putaway slips, material picking and return slips, stock transfer slips, inventory counts, lot ledgers, first-in-first-out (FIFO) and expiration date records.
Data update frequencies cover real-time (such as bin location changes from barcode scans), daily (such as material picking and return statistics), and monthly inventory (such as book vs. physical stock reconciliation). Document fields include material code, lot number, bin location number, expiration date, inspection status, and material quantity. Common units are pieces, kilograms, or cubic meters.
Constraints for knowledge base retrieval and recall
Business data for this category includes structured fields such as lot numbers and bin locations, plus unstructured content like expiration date descriptions and inspection records. Retrieval workflows must support both structured fields and natural language queries.
Multiple data sources and differing update frequencies require separating real-time data from historical inventory records. This prevents use of expired book vs. physical stock entries. Document types are unique to this category. Retrieval scope must be limited to avoid mixing in redundant data from other workshops or categories. Precise matching of material identities and lot information is required. Failure to do so will result in mismatches or incomplete retrieval results.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
similarity | 0.72–0.85 | Matches precise business fields such as warehousing lots and bin locations, filters low-relevance redundant material records |
limit | Top 8–12 entries | Covers material lot information required for single work order kitting, aligns with reasonable upper limits for knowledge base citations |
searchMode | mixedRecall | Combines keyword retrieval and semantic retrieval, supports structured fields like barcode numbers and lot numbers, plus unstructured content such as expiration date descriptions |
usingReRank | Enabled | Reorders retrieval results by business relevance, prioritizes core entries matching expiration dates and bin locations |
datasetSearchUsingExtensionQuery | Enabled | Automatically supplements business keywords such as lot numbers and bin locations, expands retrieval scope and resolves incomplete retrieval issues |
collectionIds | Fill in based on bound warehousing document sets | Limits retrieval scope to dedicated documents including receiving slips and lot ledgers, avoids mixing in redundant data from other categories |
Three common configuration errors
- Phenomenon: The number of retrieval results remains insufficient, and cannot cover the material information required for work order kitting. Cause: The
limitparameter value is too low, anddatasetSearchUsingExtensionQueryis not enabled. Business keywords such as lot numbers are not supplemented. - Phenomenon: Retrieval results include material records from other workshops or categories. Cause:
collectionIdsis not configured correctly. The retrieval scope is not limited to the dedicated warehousing document set. - Phenomenon: After calling different knowledge bases in the workflow, subsequent logical processing cannot be executed uniformly. Cause: Unified retrieval field mapping is not configured for different knowledge bases. Return result structures differ across
collectionIds.
How to confirm the configuration is correct
- Upload one recent receiving slip and lot ledger, enter "Find the bin location information for steel material from lot 12 of 2024". Check if the returned results include the corresponding bin location, expiration date, and inspection status.
- View the FastGPT v4.17.0 retrieval log. Confirm whether business keywords such as lot numbers and bin locations are automatically supplemented. Verify that
datasetSearchUsingExtensionQueryis active. - Adjust the
similarityparameter to 0.75. Compare changes in retrieval result relevance, confirm the value meets business matching requirements. - Check the document set bound to
collectionIds. Confirm it only includes documents related to warehousing, lot tracking, and in-plant logistics, with no redundant data from other categories.
The values provided are common starting points and should be measured against the reader's own samples.