Sp_afterSave_sSck (procedure)

销售对账保存后反写数量

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

Parameters

#	Mode	Name	Type
1	IN	sGuid	varchar(2000)
2	IN	sBrId	varchar(100)
3	IN	sSuId	varchar(100)
4	OUT	sCode	int
5	OUT	sReturn	varchar(4000)

Body

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

Narrative

Business context: 销售对账单据 → 销售送货流程 → KPI流程操作菜单 — header says 销售对账保存后反写数量. Thin save-phase 反写 wrapper in the Sp_afterSave_s<Code> family that delegates the actual qty back-write to Sp_saveReturn_sSck. This is one of the few family members that calls the saveReturn proc unconditionally (no IFNULL(sGuid,'') <> '' guard).

What it does: Wraps sGuid in double-quotes if not already quoted, then unconditionally calls Sp_saveReturn_sSck(sGuid, sBrId, sSuId, 2, @sCode, @sReturn) (iFlag=2 = "after save" phase). Does not propagate the inner @sCode/@sReturn back to its own OUT params.

Invocation: Reached on two paths. (1) Sp_Check_sSck (the save-commit dispatch proc bound via gdsmodule.sSaveProName on 销售对账单据 11811781131121915184849572550) calls this proc near the tail of a successful save — note the same module also has sSaveProName='Sp_afterSave_sSck' recorded directly. (2) Sp_Invalid_backwriting dispatches to this proc on 作废/取消作废 of the same form, itself triggered from Java CheckmodelServiceImpl via Sp_Invalidation.