Sp_Opsoutsideprocess_BtnEventConfirm.md 1.84 KB

Sp_Opsoutsideprocess_BtnEventConfirm (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 PROCEDURESpOpsoutsideprocess_BtnEventConfirm'._

Narrative

Business context: 外协管理 / 工序外发 — toolbar-button handler that flips the 确认 (confirm) flag on selected 工序外发 (opsoutsideprocessslave) lines and propagates the same confirmation onto the upstream work-order-process record (mftworkorderprocess), marking the outsourced step as accepted by ops.

What it does: Parses $.params[*].value[*].sSlaveId from sProInParam. For each slave id, runs UPDATE mftworkorderprocess P INNER JOIN opsoutsideprocessslave S ON P.sId = S.sWorkOrderProcessTbId SET P.bConfirm=1, P.tConfirmDate=NOW(), P.sConfirmPerson=sMakePerson, S.bConfirm=1, S.tConfirmDate=NOW(), S.sConfirmPerson=sMakePerson WHERE S.sId = p_sId AND S.sBrandsId=sBrId AND S.sSubsidiaryId=sSuId. Pure tenant-scoped flag update; no validation, no inverse.

Invocation: Status: appears orphaned. No caller found in any channel (form-master, gdsmodule hooks, other routines, xly-src grep across all extensions, dynamic-dispatch search). Naming and $.params JSON shape match the Sp_BtnEvent_* button-click contract dispatched by GenericProcedureCallServiceImpl.doGenericProcedureCall(), so it would have been wired to a 确认 toolbar button on the 工序外发 grid — likely renamed or replaced; verify with maintainers before relying on it.