Sp_Check_sStl (procedure)

保存之前数据校验

• 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_sStl'._

Narrative

Business context: Empty stub for the Sp_Check_s<Code> post-save-validator family. The proc declares the standard 9-parameter signature with COMMENT '保存之前数据校验' and a top:BEGIN ... END; block but contains no logic — it sets sCode=1, sReturn='' and returns.

What it does: Nothing — placeholder body. Likely scaffolded for a future 销售提单/结算 (sStl = Sal-Settlement?) module that was never implemented, or generated by the system-administration "create new Save validator" template.

Invocation: Status: appears orphaned. No gdsmodule.sSaveProName/sSaveProNameBefore hook, no gdsconfigformmaster binding, no other-routine caller, no xly-src reference. Safe to ignore but a candidate for cleanup. The fact that the proc exists at all (and follows the standard signature) suggests the developer reserved the slot then never filled it.