Sp_SalesOrder_KpiObsoleteMemo (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 PROCEDURESpSalesOrder_KpiObsoleteMemo'._
Narrative
Business context: 销售管理 → 销售订单管理 → 销售订单 KPI 跟踪 (salsalesorderslave) — toolbar that lets the operator attach a 作废原因 / 结案备注 to a KPI-obsolete order line: writes sKpiObsoleteMemo (and any extra fields named in valueKey). Edit-variant of Sp_SalesOrder_KpiObsoleteClose, which is the simple flag-flip. Sibling 报价侧: Sp_SalesOrder_KpiQuoMemo.
What it does: Validates sProInParam, parses $.params[*].value[*].sOrderSlaveId and $.changeValue.textareaValue. Splits $.changeValue.valueKey on commas and builds p_setSql from $.changeValue[0].colN so any extra grid-editable columns are merged in. Appends sKpiObsoleteMemo=<textareaValue> to the SET-clause. For each sOrderSlaveId it CONCATs and PREPARE/EXECUTEs UPDATE salsalesorderslave SET <setSql> WHERE sId=p_sTmpId AND sBrandsId=sBrId AND sSubsidiaryId=sSuId.
Invocation: Generic-dispatch button signature (sProInParam, sMakePerson, sBrId, sSuId, OUT sReturn, OUT sCode) — dispatched by GenericProcedureCallServiceImpl.doGenericProcedureCall() from the KPI-tracking grid's memo-edit button. Install script: script/标版/30100101/Sp_SalesOrder_KpiObsoleteMemo.sql. No xly-src Java caller, no gdsmodule row — binding lives in the grid-button metadata.