Sp_afterSave_sSdp (procedure)
开发计划保存后反写报价数量
- Type: PROCEDURE
- Deterministic: NO
- SQL data access: CONTAINS SQL
Parameters
| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | sGuid |
varchar(2000) |
| 2 | IN | sBrId |
varchar(100) |
| 3 | IN | sSuId |
varchar(100) |
| 4 | OUT | sCode |
int |
| 5 | OUT | sReturn |
varchar(4000) |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpafterSave_sSdp'._
Narrative
Business context: 开发计划 / 印前任务计划 / 项目立项单据 → PLM单据 → PLM管理 — header says 开发计划保存后反写报价数量. Thin save-phase 反写 wrapper in the Sp_afterSave_s<Code> family that delegates the actual qty back-write to Sp_saveReturn_sSdp.
What it does: Wraps sGuid in double-quotes if not already quoted and, when sGuid is non-empty, calls Sp_saveReturn_sSdp(sGuid, sBrId, sSuId, 2, @sCode, @sReturn) (iFlag=2 = "after save" phase). Does not propagate the inner @sCode/@sReturn back to its own OUT params.
Invocation: Status: appears dormant. Its only caller Sp_Check_sSdp is itself orphan: gdsmodule.sSaveProName slot on the three PLM forms (开发计划, 印前任务计划, 项目立项单据) is empty, and the live sProcName is Sp_Calc_sSdp — so Sp_Check_sSdp is not bound on any module. Sp_Invalid_backwriting has no dispatch entry for any of these forms. Candidate for maintainer audit.