Sp_SalesMaterials_Memo1 (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 PROCEDURESpSalesMaterials_Memo1'._

Narrative

Business context: 工单子表 (mftworkorderslave) — 车间主管反馈 button-event handler that writes the first feedback slot (sFeedBack1Memo, sFeedBack1Name, tFeedBack1Date) on selected work-order slave rows. Sibling pair: Sp_SalesMaterials_Memo2 (slot 2), Sp_SalesMaterials_Memo3 (slot 3, also flips bSucceed). The "Sales" in the name is a misnomer — the proc updates the manufacturing work-order slave, not anything in sal*.

What it does: Parses $.params[*].value[*].sSlaveId and $.changeValue.sFeedBack1Memo 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 sFeedBack1Memo=…, sFeedBack1Name=sMakePerson, tFeedBack1Date=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 车间主管反馈(1) toolbar button on a 工单 grid 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).