c96d4ac8d6a19d91c2c0faf0ab05306a59853b4b
根因分析: 1. SQL查询 getRegRequestBaseInfo 未返回 medication_id/adviceDefinitionId 字段, 退回医嘱的 adviceDefinitionId 为 null,导致库存校验查询无法匹配到库存记录 2. 退回医嘱可能缺少 locationId,严格的 locationId 匹配导致校验失败 修复方案: 1. AdviceManageAppMapper.xml:在三个UNION查询中分别添加 medication_id/device_def_id/activity_id AS advice_definition_id 2. AdviceUtils.checkInventory(): - 过滤 null adviceDefinitionId,避免SQL查询异常 - 所有adviceDefinitionId为null时跳过库存校验 - 退回医嘱单个adviceDefinitionId为null时跳过该校验项 - 添加 locationId 容错匹配(为null时跳过location匹配) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Description
No description provided
Languages
Java
49.5%
Vue
44.8%
JavaScript
4.6%
HTML
0.7%
SCSS
0.1%