Sp_Check_sPct1 (procedure)

品质首检(mobile单据)保存之前数据校验

• Type: PROCEDURE
• Deterministic: NO
• SQL data access: CONTAINS SQL

Parameters

#	Mode	Name	Type
1	IN	sTableName	varchar(100)
2	IN	sGuid	varchar(100)
3	IN	sFormGuid	varchar(100)
4	IN	sLoginId	varchar(100)
5	IN	sBrId	varchar(100)
6	IN	sSuId	varchar(100)
7	IN	iFlag	int
8	OUT	sCode	int
9	OUT	sReturn	varchar(4000)

Body

Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpCheck_sPct1'._

Narrative

Business context: Stub post-save validator for the _1 variant of 品质首检(mobile单据), delegating to Sp_afterSave_sPct1. Body is byte-identical in shape to Sp_Check_sPct — locals declared but no rule branches active, only the forwarding call.

What it does: Declares p_count, p_sBillNo, p_sId, p_sSrcSlaveId etc. (unused), checks IFNULL(sReturn,'') <> '' to short-circuit, then calls Sp_afterSave_sPct1(sGuid, sBrId, sSuId, sCode, sReturn). On non-empty sReturn after the peer call, sets sCode = -1.

Invocation: Status: appears orphaned. No gdsmodule.sSaveProName/sSaveProNameBefore/sProcName/sDeleteProName row references it; no form-master sSqlStr ref; no other DB routine calls it; xly-src grep finds script/标版/30100101/Sp_Check_sPct1.sql (the install body). Candidate for maintainer audit — both Sp_Check_sPct and this _1 variant lack a live binding.