# `Sp_afterSave_sStl` (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_sStl`'`._

## Narrative

**Business context:** 财务调整单据 → 财务单据 — header says 后反写数量. Thin save-phase 反写 wrapper in the `Sp_afterSave_s<Code>` family that delegates to `Sp_saveReturn_sStl`.

**What it does:** Wraps `sGuid` in double-quotes if not already quoted and, when `sGuid` is non-empty, calls `Sp_saveReturn_sStl(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:** Status: appears dormant. `Sp_Check_sStl` exists but does not call `Sp_afterSave_sStl` internally (the save-commit chain skips this hook), and the 财务调整单据 module's `sSaveProName`/`sDeleteProName` slots are empty (only `sProcName = Sp_Calc_sStl` is bound). `Sp_Invalid_backwriting` has no dispatch entry for any 财务调整 form. No callers found in any other channel — candidate for maintainer audit.