# `Sp_Calc_sMsc` (procedure)

> 新材料测试申请(品质)


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

## Parameters

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

## Body

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

## Narrative

**Business context:** 新材料测试申请(品质) — second quality-department new-material-test request variant (same Chinese label as `Sp_Calc_sMpz`). Touches only `salsalesdevplanmaster`, suggesting an even leaner variant whose audit just flags the originating 销售开发计划 line without materialising an `elematerials` row.

**What it does:** Standard `Sp_Calc_s<Code>` skeleton: defaults the IN params, validates `sGuid` with `bInvalid` guard, branches on `iFlag`. The only data touch is `Update salsalesdevplanmaster` — flipping the test-approval flag for the linked dev-plan row.

**Invocation:** Status: appears orphaned. No `gdsmodule.sProcName` binding, no `gdsconfigformmaster` reference, no other routine refs, no xly-src grep hits. Alongside `Sp_Calc_sMft` and `Sp_Calc_sMpz` (same Chinese family), the live 新材料测试申请 audit is not currently routed through any of these procs. Candidate for maintainer audit; the sChinese duplication between `sMpz` and `sMsc` also suggests one is a renamed/forked copy of the other.