What this category's data looks like
This page addresses the category of research funding budget adjustment and reimbursement. The materials come from three types of documents: budget adjustment applications, reimbursement forms, and contract invoices, with update cadence rolling along with project cycles and financial month-end closing. Budget adjustment applications record accounts, amounts, and approval signatures; reimbursement forms record items, quantities, and dates; contract invoices record supplier names, amounts, and receipts. When the materials enter the deployment and upgrade feature, each plays a different role: budget adjustment applications correspond to the basis for version changes, reimbursement forms correspond to migration task records, and contract invoices correspond to data row index status. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures, and common inconsistencies are also exposed in these four categories.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting the image version, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use. Upgrades do not produce business materials, nor are they a prerequisite for enabling the interface.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Accounts, amounts, dates, and signatures must be aligned item by item with the reimbursement form | Compare the application with the reimbursement form, check names, quantities, dates, and signatures, and check whether the MONGODB_URI and PG_URL connections are consistent |
| Reimbursement form | Items, quantities, dates, and receipts must be consistent with the contract invoice | Compare the reimbursement form with the contract invoice, check names, quantities, dates, and receipts, and check whether the REDIS_URL and DB_MAX_LINK connections are consistent |
| Contract invoice | Supplier names, amounts, and receipts must be consistent with the budget adjustment application | Compare the contract invoice with the budget adjustment application, check names, quantities, dates, and signatures, and check whether the image version identifier is the same target version |
| Migration task record | The two migration scripts are executed in sequence and leave a trace | On the administrator version upgrade page, view the execution records of the historical chunk training task migration and the knowledge base rebuild status migration, and check the time and status |
Three common errors
- Symptom: the service can start but the data row status is still the old marker. Cause: the knowledge base rebuild status migration was not executed or not completed, and the old rebuilding marker was not switched to the new index status system.
- Symptom: the name, quantity, and date of the same record do not match between the budget adjustment application and the reimbursement form. Cause: the two materials were entered separately and were not aligned item by item according to signatures and receipts.
- Symptom: the two image version identifiers are inconsistent. Cause: the main service and commercial edition images were not synchronously updated to the same target version, and one item is missing from the upgrade record.
How to verify the setup
This feature's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in sequence, confirming that the historical chunk training task migration comes first and the knowledge base rebuild status migration comes second, and that the data row index status has been switched.
Business test: check item by item once according to the handover form to see which record is missing, focusing on checking the names, quantities, dates, and signatures of the budget adjustment application, reimbursement form, and contract invoice.
- On the administrator version upgrade page, check the main service and commercial edition image version identifiers, and confirm that both are the same target version.
- View the execution records of the historical chunk training task migration and the knowledge base rebuild status migration in sequence, and sample one data row to check the index status field.