# `Sp_System_UpdateWorkProcessMemo` (procedure)

> 业务单据保存校验


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

## Parameters

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

## Body

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

## Narrative

**Business context:** 制造 → 工单 (生产工单) — narrow save-side hook (header comment: "业务单据保存校验") that propagates the 工序备注 (process remark) from the 工单工序 master rows into the per-排产 slave plan rows. Ensures `mftproductionplanslave` displays the same `sProcessMemo` the planner typed against `mftworkorderprocess`.

**What it does:** Single statement: `UPDATE mftproductionplanslave A INNER JOIN mftworkorderprocess B ON A.sWorkOrderProcessTbId=B.sId SET A.sProcessMemo=B.sProcessMemo WHERE B.sParentId=sGuId`. No other reads or writes, no parameter handling, no error path.

**Invocation:** Status: appears orphaned. No `gdsmodule.sSaveProName`/`sSaveProNameBefore` binding, no form-master, no other-proc, no xly-src match. The signature shape (`sFormGuid,sGuid,sTableName,sLoginId,sReturn,sBrId,sSuId,sCode`) is the standard sSaveProName slot — likely the save-side hook on the 工单/排产 form's "复制工序备注到排产" toolbar action or a pre-save hook for the 工单 master. Dispatch must be via a string-keyed lookup invisible to grep. Candidate for maintainer audit.
