What this category's data looks like
Laboratory hazardous chemical procurement and ledgers involve three types of materials: procurement application forms, requisition registration forms, and inventory ledgers. Procurement application forms record the item name, specification, quantity, application date, and approval signature; requisition registration forms record the requisition date, requisitioner, quantity, and receipt signature; inventory ledgers record the balance quantity, date, and custodian signature. The materials are updated weekly or monthly, and field names and date formats are often inconsistent across different materials. When entering this function, the procurement application form serves as the application basis, the requisition registration form serves as the consumption voucher, and the inventory ledger serves as the balance baseline; together, the three constitute the material source for progress recording and statistical verification.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the input parameters and return in the call record). The "progress table and statistical scope description" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Procurement application form | The fields include item name, specification, quantity, application date, and approval signature; check whether the name and quantity match those in the requisition registration form | Open the tool node to introduce the fields and confirm that the description is readable on its own; check the parameter introduction and whether it is required; run a trial with a question missing the approval signature to see whether it asks a follow-up question |
| Requisition registration form | The fields include requisition date, requisitioner, quantity, and receipt signature; check whether the date and quantity match those in the inventory ledger | Check the diamond connectors and node status on the canvas; inspect the input parameters and return in the call records of toolChoice and functionCall |
| Inventory ledger | The fields include balance quantity, date, and custodian signature; check whether the balance matches the total of procurement and requisition | Open each parameter configuration one by one and check the introduction and whether it is required; run a trial with a question missing the date to see whether it asks a follow-up question first rather than fabricating directly |
Three common errors
- Symptom: The name and quantity of the same record do not match between the procurement application form and the requisition registration form. Cause: The two materials are maintained separately, without field mapping and version synchronization.
- Symptom: The inventory ledger lacks a custodian signature or receipt. Cause: Signatures were not added promptly after requisition, and material flow and ledger updates are disconnected.
- Symptom: Values that do not exist in the business materials appear in the tool return result. Cause: The model fabricates parameter values on its own when required parameters are missing, instead of calling according to the introduction.
How to verify the setup
Acceptance of this function: run a trial with a question missing required parameters, inspect the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; check whether toolChoice and functionCall appear in the call record.
Business test: use one week of records to verify the totals, see whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match.
- Open the tool node to introduce the fields and check whether this description can be understood when taken out on its own; open each parameter configuration one by one and check the introduction and whether it is required.
- Check the diamond connectors and node status on the canvas; run a trial with a question missing that field to see whether it asks a follow-up question first rather than fabricating directly.