What this category's data looks like
Laboratory hazardous chemicals procurement and ledgers involve three core types of materials: hazardous chemicals procurement applications, usage registrations, and inventory ledgers. Procurement applications come from each laboratory group and are submitted weekly, with fields including item name, specification, quantity, application date, and approval signature; usage registrations are filled in on site by the user, including usage date, quantity, purpose, and user signature; inventory ledgers are maintained by the warehouse keeper by batch, including inbound date, balance quantity, storage location, and review signature. When these three types of materials enter the progress recording and statistical verification function, procurement applications serve as the starting point of progress, usage registrations serve as the basis for consumption, and inventory ledgers serve as the baseline for balances. The three are summarized under the same statistical scope to form a progress table and statistical scope description, for use in weekly or monthly reports. The update rhythm is weekly summary once and month-end verification once, and the field characteristics require that names, quantities, dates, and signatures can be matched item by item.
Configuration and implementation checks
This part is executed by the connection configuration of the deployment environment (server side), not by the capability of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | Application date, item name, quantity, and approval signature can be matched item by item in the progress table and statistical scope description | Take one week of procurement applications and verify whether the application date, item name, quantity, and approval signature are consistent with the progress table |
| Usage registration | Usage date, quantity, and user signature can be matched item by item in the progress table and statistical scope description | Take one week of usage registrations and verify whether the usage date, quantity, and user signature are consistent with the statistical scope description |
| Inventory ledger | Inbound date, balance quantity, and review signature can be matched item by item in the progress table and statistical scope description | Take one week of inventory ledgers and verify whether the inbound date, balance quantity, and review signature are consistent with the progress table |
| Main business database connection variable | MONGODB_URI points to the main business database actually in use and can connect | In the deployment environment, verify that the variable value is consistent with the database address, and check the connection result in the startup logs |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the procurement application and the inventory ledger. Cause: The two materials are entered separately and are not verified under the same statistical scope.
- Symptom: The usage registration and inventory ledger versions are not synchronized, causing deviations in the weekly report totals. Cause: The update rhythm is inconsistent, and the versions are not unified before summarization.
- Symptom: The procurement application lacks an approval signature or the usage registration lacks a receipt. Cause: The signature and receipt steps are not included in the scope of progress table verification.
How to verify the setup
This function's acceptance: connect once item by item to the main business database, log database, cache, and vector database, check the connection results in the startup logs, and verify that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the deployment instructions.
Business test: use one week of records to verify the totals, and see whether the scope and exceptions are clearly written.
- Take one week of procurement applications, usage registrations, and inventory ledgers, and verify item by item the names, quantities, dates, and signatures according to the statistical scope description.
- Verify the values of the connection variables for the main business database, log database, cache, and vector database, and check whether the startup logs report a connection timeout.