# `Sp_afterSave_sOis` (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_sOis`'`._

## Narrative

**Business context:** 工序发外确认 → 发外加工流程 → KPI流程操作菜单 (also 发外报工(mobile单据)/工序发外确认单据 under 功能操作 → 移动端管理). Header says 工序发外确认后反写数量. Thin save-phase wrapper in the `Sp_afterSave_s<Code>` family that delegates the qty back-write to `Sp_saveReturn_sOis`.

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

**Invocation:** Reached on two paths. (1) `Sp_Check_sOis` (bound via `gdsmodule.sSaveProName` on 工序发外确认 / 发外报工(mobile单据) / 工序发外确认单据) calls this proc near the tail of a successful save. (2) `Sp_Invalid_backwriting` dispatches to this proc on 作废/取消作废 of form `192116810113315234275562360` (工序发外确认), itself triggered by Java `CheckmodelServiceImpl` via `Sp_Invalidation`.
