# `Sp_afterSave_sPmt` (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 PROCEDURE `Sp_afterSave_sPmt`'`._

## Narrative

**Business context:** 付款单 → 财务收付款 → KPI流程操作菜单 — catalog header says 付款单保存前反写数量 but the routine is the after-save (iFlag=2) wrapper, not the before-save (header label is misleading). Thin save-phase 反写 wrapper in the `Sp_afterSave_s<Code>` family that delegates the actual money back-write to `Sp_saveReturn_sPmt`.

**What it does:** Declares unused local vars (`iPayType`, `iOutType`), wraps `sGuid` in double-quotes if not already quoted and, when `sGuid` is non-empty, calls `Sp_saveReturn_sPmt(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_sPmt` (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 `192116810113315233387186220` (付款单), itself triggered from Java `CheckmodelServiceImpl` via `Sp_Invalidation`.
