Sp_MftPlanPhase_BtnEventSave (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 | sBrId |
varchar(100) |
| 4 | IN | sSuId |
varchar(100) |
| 5 | OUT | sReturn |
varchar(1000) |
| 6 | OUT | sCode |
int |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpMftPlanPhase_BtnEventSave'._
Narrative
Business context: 生产管理 → 生产计划管理 → 生产计划跟进(部件) — toolbar save for the planner-memo / planner-set-date fields on mftworkordercontrol rows. Planners use the 跟进 grid to annotate which work-order parts they have scheduled; this proc commits those grid-cell edits back to the source row in one click.
What it does: Parses $.params[*].value[*] from sProInParam, pulling sId, sPlannerMemo, tPlannerSet for each selected part. When tPlannerSet arrives in mm-dd short form (length < 10) the proc prefixes the current year. For each id it UPDATE mftworkordercontrol SET sPlannerMemo = ..., tPlannerSet = ... WHERE sId = p_sId AND sBrandsId = sBrId AND sSubsidiaryId = sSuId. No status flag toggled — pure memo-write.
Invocation: Dispatched dynamically by GenericProcedureCallServiceImpl.doGenericProcedureCall() (POST /procedureCall/doGenericProcedureCall) — the 保存所选数据 button on the 生产计划跟进(部件) grid names Sp_MftPlanPhase_BtnEventSave as the action. xly-src ships script/标版/30100101/schedule/Sp_MftPlanPhase_BtnEventSave.sql (install script). Twin: Sp_MftPlanPhaseProduct_BtnEventSave for the 成品 grid.