# `Sp_SalesMaterials_Memo2` (procedure)

> 车间主管反馈


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sProInParam` | `varchar(10000)` |
| 2 | IN | `sMakePerson` | `varchar(100)` |
| 3 | IN | `sUserId` | `varchar(100)` |
| 4 | IN | `sBrId` | `varchar(100)` |
| 5 | IN | `sSuId` | `varchar(100)` |
| 6 | OUT | `sReturn` | `varchar(1000)` |
| 7 | OUT | `sCode` | `int` |

## Body

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

## Narrative

**Business context:** 工单子表 (`mftworkorderslave`) — 车间主管反馈 button-event handler that writes the second feedback slot (`sFeedBack2Memo`, `sFeedBack2Name`, `tFeedBack2Date`) on selected work-order slave rows. Slot-2 sibling of `Sp_SalesMaterials_Memo1`; slot-3 sibling `Sp_SalesMaterials_Memo3` also flips `bSucceed`. Despite the `Sp_SalesMaterials_*` prefix the proc targets the manufacturing work-order slave, not anything in `sal*`.

**What it does:** Parses `$.params[*].value[*].sSlaveId` and `$.changeValue.sFeedBack2Memo` from `sProInParam`. Rejects with `sCode=-1, sReturn=Fun_Sis_GetConst('sEnterFeedBack')` (请输入反馈内容) if the memo is empty. Otherwise loops over every `sSlaveId` and runs `UPDATE mftworkorderslave SET sFeedBack2Memo=…, sFeedBack2Name=sMakePerson, tFeedBack2Date=NOW() WHERE sId=p_sId AND sBrandsId=sBrId AND sSubsidiaryId=sSuId`.

**Invocation:** Generic-dispatch button signature `(sProInParam, sMakePerson, sUserId, sBrId, sSuId, OUT sReturn, OUT sCode)` — dispatched by `GenericProcedureCallServiceImpl.doGenericProcedureCall()` when a 车间主管反馈(2) toolbar button posts to `/procedureCall/doGenericProcedureCall` with this name. No xly-src reference, no gdsmodule binding, no other proc references it — status: appears orphaned / candidate for maintainer audit (likely a customer-specific button that lost its grid configuration).