Sp_Check_sYstb (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_sYstb'._

Narrative

Business context: 预算填报 (departmental budget entry) post-save validator on departmentalBudgetMaster. Enforces uniqueness — one department may only file one budget bill per calendar year — so a second 填报 attempt for the same sDepartId + sYear is rejected.

What it does: Reads NetMoney/NetPrice precisions (declared but unused after the existence check). Pulls sYear, DATE_FORMAT(tCreateDate,'%m') and sDepartId from the current departmentalBudgetMaster into local vars. Aborts with sDepartCompleteBudget ("该部门已填写今年的预算填报单，请重新检查后输入") if any other departmentalBudgetMaster row exists for the same year+department under the same brand/subsidiary. The chained Sp_afterSave_sDgn call at the end is commented out.

Invocation: Status: appears orphaned. No gdsmodule.sSaveProName/sSaveProNameBefore hook on any 预算 module in the current DB snapshot (the only matching module — 年度费用预算KPI设定(暂不开放), sId 16310732640001916514361957702100 — is explicitly marked 暂不开放 "not yet open"), no form-master binding, no other-routine caller, no xly-src reference. The 预算填报 feature itself appears to be staged but not yet wired into the live UI. Candidate for maintainer audit.