# `Sp_afterSave_sPct1` (procedure)

> 品质首检(mobile单据)存后反写数量


- **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_sPct1`'`._

## Narrative

**Business context:** 品质首检(mobile单据) → 功能操作 → 移动端管理 → 现场 — header says 品质首检(mobile单据)存后反写数量. Mobile-form sibling of `Sp_afterSave_sPct`; unlike `_sPct` which uses the shared `Sp_saveReturn_sPct` worker, this one delegates to a dedicated `Sp_saveReturn_sPct1` worker keyed to the mobile-form schema.

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

**Invocation:** Reached via `Sp_Invalid_backwriting` (Java `CheckmodelServiceImpl` → `Sp_Invalidation`) on 作废/取消作废 of form `12012615914116373957014740` (品质首检(mobile单据)). The save-commit chain through `Sp_Check_sPct1` is also wired (its body calls this), though `Sp_Check_sPct1` itself currently has no `gdsmodule` binding — dispatched dynamically by a parent-module entry.
