# `Sp_afterSave_sOpn1` (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_sOpn1`'`._

## Narrative

**Business context:** Numbered variant of `Sp_afterSave_sOpn` (发外到货 — outsource-delivery receipt). Body is identical to `_sOpn` (still delegates to `Sp_saveReturn_sOpn`, not to a separate `_sOpn1` worker), so the "1" suffix is a fork-without-divergence — 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_sOpn(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_sOpn1`, which has no `gdsmodule` binding (no form's save-commit chain dispatches into it). Not present in the `Sp_Invalid_backwriting` form-id dispatch table. No xly-src refs. Candidate for maintainer audit — likely a placeholder for a 发外到货 mobile/variant form that was never wired up.
