Sp_afterSave_sPca1 (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_sPca1'._

Narrative

Business context: Numbered variant of Sp_afterSave_sPca (采购到货(送检)单据). Body still delegates to Sp_saveReturn_sPca (not _sPca1) — same logic, different name reservation.

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

Invocation: Status: appears orphaned. Only routine-caller is Sp_Check_sPca1, which has no gdsmodule binding. Not present in the Sp_Invalid_backwriting form-id dispatch table. No xly-src refs beyond install SQL. Candidate for maintainer audit — likely a placeholder for a 采购到货 variant form that was never wired up.