Sp_Calc_sSpp (procedure)

商机跟进

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

Parameters

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

Body

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

Narrative

Business context: Salutes the Sp_Calc_s* audit/un-audit signature (iFlag 1/0 → bCheck on a master), targetting salsalesprintplanmaster (印前计划主表). The proc's COMMENT says 商机跟进 but the actual table it touches is the prepress-plan master — the comment appears stale.

What it does: Validates sGuid, refuses if bInvalid=1 (cannot audit an invalidated row), refuses audit/un-audit when the row is already in the requested state, then UPDATE salsalesprintplanmaster SET bCheck = {1|0}, sCheckPerson = sLoginId, tCheckDate = NOW() for the given id. Strips dashes from sReturn at the end.

Invocation: Status: appears orphaned. No gdsmodule.sProcName binds this name — 商机跟进单据 uses Sp_Calc_sSfu, and 印前任务计划 uses Sp_Calc_sSdp. Only xly-src reference is script/标版/30100101/Sp_Calc_sSpp.sql (install script). No Java caller, no other-routine caller, no form-master reference. Candidate for maintainer audit — likely a renamed/abandoned earlier audit handler.