# `Sp_Calc_sCut333` (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(100)` |
| 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_sCut333`'`._

## Narrative

**Business context:** Backup / experimental variant of `Sp_Calc_sCut` (the 物料转换单据 audit on `MitMaterialsCutMaster`). The `333` suffix tags it as a sandboxed copy; same opening boilerplate as `Sp_Calc_sCut`, with a workflow hook (`CALL Sp_System_CheckFlow`) added that the production proc does not have.

**What it does:** Same as `Sp_Calc_sCut`: validates `sGuid`, on `iFlag=1` updates `MitMaterialsCutMaster`, `MitMaterialsStore`, `MftWorkOrderMaterials`, posts to `EleMaterialsStock`; additionally calls `Sp_System_CheckFlow` for OA/approval-flow start. The body opens with the same commented-out `SAVEPOINT sCut` block and the same `@author:zhucaixi 2012-12-28` legacy comment as the parent proc.

**Invocation:** Status: appears orphaned. No `gdsmodule.sProcName/sSaveProName/sDeleteProName/sSaveProNameBefore` binding, no `gdsconfigformmaster` reference, no other procedure or function calls it, no xly-src reference. The `333` suffix and the duplicated body confirm this is an internal A/B / staging copy of the live `Sp_Calc_sCut` audit — not expected to be called from production. Candidate for maintainer audit / deletion.