Sp_afterSave_sPst (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_sPst'._

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_sPst.

What it does: Declares unused local sDeliverSrc, wraps sGuid in double-quotes if not already quoted, then unconditionally calls Sp_saveReturn_sPst(sGuid, sBrId, sSuId, 2, @sCode, @sReturn) (iFlag=2 = "after save" phase). Body carries several large commented-out blocks (UPDATE qlyproducttestmaster, MftWorkOrderSlave, mftproductionplanbillslave) that were once dynamic-SQL aggregators distributing pitproductinstoreslave totals upstream — all currently inert. Does not propagate the inner @sCode/@sReturn back to its own OUT params.

Invocation: Reached on two paths. (1) Sp_Check_sPst (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 192116810113315228246447250 (成品入库), itself triggered from Java CheckmodelServiceImpl via Sp_Invalidation.