Sp_afterSave_sOpc (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_sOpc'._

Narrative

Business context: 工序发外 → 发外加工流程 → KPI流程操作菜单 — header says 工序发外保存后反写数量. Thin save-phase wrapper in the Sp_afterSave_s<Code> family that delegates the qty back-write to Sp_saveReturn_sOpc.

What it does: Wraps sGuid in double-quotes if not already quoted and, when sGuid is non-empty, calls Sp_saveReturn_sOpc(sGuid, sBrId, sSuId, 2, @sCode, @sReturn). Does not propagate the inner @sCode/@sReturn to its own OUT params.

Invocation: Reached on two paths. (1) Sp_Check_sOpc (bound via gdsmodule.sSaveProName on 工序发外) calls this proc at the tail of a successful save. (2) Sp_Invalid_backwriting dispatches to this proc on 作废/取消作废 of form 101801153119616594919790770 (a stale 工序发外 form-id no longer present in gdsmodule but kept in the dispatch table for legacy installs), itself triggered by Java CheckmodelServiceImpl via Sp_Invalidation.