Sp_QlyProcessTestJudge (procedure)
工序检验自动判断抽检及合格
- Type: PROCEDURE
- Deterministic: NO
- SQL data access: CONTAINS SQL
Parameters
| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | sFormGuid |
varchar(100) |
| 2 | IN | sGuid |
varchar(100) |
| 3 | IN | sTableName |
varchar(100) |
| 4 | IN | sLoginId |
varchar(100) |
| 5 | OUT | sReturn |
varchar(4000) |
| 6 | IN | sBrId |
varchar(100) |
| 7 | IN | sSuId |
varchar(100) |
| 8 | OUT | sCode |
int |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpQlyProcessTestJudge'._
Narrative
Business context: 质量管理 / 工序检验 — meant to be the auto-judge button hook for the 工序检验 (QlyProcessTestMaster / QlyProcessTestSlave) form: roll a per-line pass/fail based on dSReserve3 quantity and roll up to master iTestResult. Twin of Sp_QlyComeMaterialsJudge / Sp_QlyProductJudge / Sp_QlyOutSideJudge for the in-process inspection flow.
What it does: The active body is empty — every UPDATE statement (slave sActValue set from dSReserve3>0, master iTestResult rolled up from slave 不合格 count, and the "请选择实测值" validation) is commented out. The proc declares p_sTestItem and returns immediately without touching any table. Effectively a no-op skeleton.
Invocation: Status: appears orphaned. No caller found in any channel (form-master, gdsmodule sSaveProName/sCalcProName, other routines, xly-src grep across all extensions). Signature matches the standard 自动判断 button-action contract (sFormGuid, sGuid, sTableName, sLoginId, sReturn, sBrId, sSuId, sCode) and the name pattern follows the Judge family — likely a stub left during a feature pause; candidate for maintainer audit or deletion.