Sp_afterSave_tice (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 |
longtext |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpafterSave_tice'._
Narrative
Business context: 设备维修通知单据 (operates on eptmachinefixednoticeslave/master) — header says 回厂通知单保存后. Thin save-phase 反写 wrapper that delegates to Sp_saveReturn_tice (the in-line eptmachinefixedorderslave.dAuxiliaryFXQty denorm UPDATE chain is fully commented out).
What it does: Calls Sp_saveReturn_tice(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. No gdsmodule.sSaveProName/sDeleteProName/sProcName slot in this database points at this proc (no Sp_Calc_tice/Sp_Check_tice binding either), Sp_Invalid_backwriting has no dispatch entry for any 设备维修通知 form, and no other routine references it. Candidate for maintainer audit.