Sp_afterSave_sOsa (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_sOsa'._

Narrative

Business context: Header says 采购到货保存后反写报价数量 ("Procurement Arrival - after-save back-write quoted qty"). Thin save-phase wrapper in the Sp_afterSave_s<Code> family that delegates the qty back-write to Sp_saveReturn_sOsa.

What it does: Wraps sGuid in double-quotes if not already quoted and, when sGuid is non-empty, calls Sp_saveReturn_sOsa(sGuid, sBrId, sSuId, 2, @sCode, @sReturn). Does not propagate the inner @sCode/@sReturn to its own OUT params. A -- set sCode = 1; debug comment sits below the inner BEGIN.

Invocation: Status: appears orphaned. Only routine-caller is Sp_Check_sOsa, which has no gdsmodule binding (no form's save-commit chain dispatches into it). Not present in the Sp_Invalid_backwriting form-id dispatch table. No xly-src refs. Candidate for maintainer audit — most likely a parallel-naming artefact for a 采购到货 variant that was never wired up (the live 采购到货 variant uses the _sPca member).