# `Sp_afterSave_sSmoa` (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_sSmoa`'`._

## Narrative

**Business context:** 半成品出库申请单据 — header says 半成品出库申请存后反写数量. Thin save-phase 反写 wrapper in the `Sp_afterSave_s<Code>` family that delegates the actual qty back-write to `Sp_saveReturn_sSmoa` (the in-line `sgdsemigoodsoutstoreapplyslave` → `mftworkorderprocess.dProcessOutApplyQty` UPDATE chain is fully commented out).

**What it does:** Wraps `sGuid` in double-quotes if not already quoted and calls `Sp_saveReturn_sSmoa(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_sSmoa` (and additionally `Sp_Check_sSmo`) calls this proc near the tail of a successful save, although neither `Sp_Check_s` sibling currently has a live `gdsmodule.sSaveProName` binding in this database. (2) `Sp_Invalid_backwriting` dispatches to this proc on 作废/取消作废 of form `101801153119616759337728990` (半成品出库申请), itself triggered from Java `CheckmodelServiceImpl` via `Sp_Invalidation`.