Sp_afterSave_sMpa (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_sMpa'._

Narrative

Business context: 领料申请单据 / 补料申请单据 / 补版申请单据 → MES单据 → 生产执行 — header says 领料申请存后反写数量. Thin save-phase wrapper in the Sp_afterSave_s<Code> family that delegates the actual qty back-write to Sp_saveReturn_sMpa.

What it does: Wraps sGuid in double-quotes if not already quoted and, when sGuid is non-empty, calls Sp_saveReturn_sMpa(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_sMpa (the save-commit dispatch proc bound via gdsmodule.sSaveProName on 领料申请/补料申请/补版申请单据) calls this proc near the tail of a successful save. (2) Sp_Invalid_backwriting dispatches to this proc on 作废/取消作废 of form 101251240115016082594412050 (产品工艺卡), which is itself triggered by Java CheckmodelServiceImpl through Sp_Invalidation.