Sp_Check_sSdp (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_sSdp'._

Narrative

Business context: Inferred from the name and routine comment: PLM管理 → PLM单据 → 开发计划 / 印前任务计划 / 项目立项 — placeholder post-save validator for the project/development-planning form family. The body is a no-op stub that delegates to Sp_afterSave_sSdp and returns immediately.

What it does: Initialises sCode=1, defaults iFlag to 0, clears sReturn, opens an empty top: block, and calls Sp_afterSave_sSdp(sGuid, sBrId, sSuId, sCode, sReturn). No table touch, no validation.

Invocation: Status: appears orphaned. The peer Sp_Calc_sSdp is bound on 开发计划 (101251240115016044841089590), 印前任务计划 (101251240115016054411974580) and 项目立项单据 (101251240115016147549171140) — all under PLM管理 → PLM单据 — via sProcName, but Sp_Check_sSdp itself is not wired as sSaveProName/sSaveProNameBefore on any of them. No other routine references it, no xly-src hit (no install script). Effectively a stub awaiting a rule — candidate for maintainer audit.