# `Sp_Check_sPct` (procedure)

> 品质首检(mobile单据)保存之前数据校验


- **Type:** PROCEDURE
- **Deterministic:** NO
- **SQL data access:** CONTAINS SQL

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sTableName` | `varchar(100)` |
| 2 | IN | `sGuid` | `varchar(100)` |
| 3 | IN | `sFormGuid` | `varchar(100)` |
| 4 | IN | `sLoginId` | `varchar(100)` |
| 5 | IN | `sBrId` | `varchar(100)` |
| 6 | IN | `sSuId` | `varchar(100)` |
| 7 | IN | `iFlag` | `int` |
| 8 | OUT | `sCode` | `int` |
| 9 | OUT | `sReturn` | `varchar(4000)` |

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `Sp_Check_sPct`'`._

## Narrative

**Business context:** Stub post-save validator nominally for 品质首检(mobile单据) (per procedure summary), delegating to `Sp_afterSave_sPct`. The body declares the usual local variables for a 首检 check but the actual rule branches are commented out — only the forwarding call remains.

**What it does:** Declares `p_count`, `p_sBillNo`, `p_sId`, `p_sSrcSlaveId` etc. (unused), checks `IFNULL(sReturn,'') <> ''` to short-circuit, then calls `Sp_afterSave_sPct(sGuid, sBrId, sSuId, sCode, sReturn)`. On non-empty `sReturn` after the peer call, sets `sCode = -1`.

**Invocation:** Status: appears orphaned. No `gdsmodule.sSaveProName`/`sSaveProNameBefore`/`sProcName`/`sDeleteProName` row references it; no form-master `sSqlStr` ref; no other DB routine calls it; xly-src grep finds only `script/标版/30100101/Sp_Check_sPct1.sql` (the install body for the `_1` variant) — not the bare `Sp_Check_sPct` body. Candidate for maintainer audit.