# `Sp_Check_sMpt` (procedure)

> 产品工艺卡保存之前数据校验


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

## Narrative

**Business context:** Stub post-save validator nominally for 产品工艺卡 (per the procedure summary), delegating to `Sp_afterSave_sMpt`. Body initialises `sCode`/`iFlag`/`sReturn`, then immediately calls `Sp_afterSave_sMpt(sGuid, sBrId, sSuId, sCode, sReturn)` — no validation logic of its own.

**What it does:** Forwards `(sGuid, sBrId, sSuId, sCode, sReturn)` to `Sp_afterSave_sMpt` inside the `top:` block; relies on `Sp_afterSave_sMpt` to populate `sReturn`/`sCode` for the caller.

**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_sMpt.sql` (the install body). The matching `Sp_afterSave_sMpt` exists but this wrapper has no live caller — candidate for maintainer audit.