Sp_Check_sCio (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_sCio'._

Narrative

Business context: 销售 → 客户信息 / 客户报备信息 — placeholder post-save hook on customer-audit forms (sCio = sales-customer-info). The body is a no-op stub that returns sCode=1, sReturn='', leaving the validation contract in place for future rules without yet enforcing any.

What it does: Initialises sCode=1, defaults iFlag to 0, clears sReturn, opens an empty top: block, and exits. No table touch, no validation.

Invocation: Status: appears orphaned. The peer Sp_Calc_sCio is bound on 客户信息 (192116810111915048607109671) and 客户报备信息单据 (101251240115015977193229000) modules' sProcName, but Sp_Check_sCio itself is not wired as sSaveProName/sSaveProNameBefore on those modules. No other routine references it, no xly-src hit. Effectively a stub awaiting a rule — candidate for maintainer audit.