Sp_Calc_sSodAfter (procedure)

销售订单执行后执行过程(线上获取订单,名片单页自动审核后，调用)

• Type: PROCEDURE
• Deterministic: NO
• SQL data access: CONTAINS SQL

Parameters

#	Mode	Name	Type
1	IN	iFlag	int
2	IN	iTmpCheck	int
3	IN	sFormGuid	varchar(100)
4	IN	sGuid	varchar(100)
5	IN	sLoginId	varchar(100)
6	OUT	sReturn	varchar(5000)
7	IN	sBrId	varchar(100)
8	IN	sSuId	varchar(100)
9	OUT	sCode	int

Body

Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpCalc_sSodAfter'._

Narrative

Business context: 销售管理 → 销售订单执行后执行过程 (post-audit hook for sales-order, fired specifically when an online (线上) order or business-card single-page order auto-audits after import). The hook exists so customer-specific deployments can inject extra logic after Sp_Calc_sSod finishes, without having to override the main audit proc.

What it does: The stock body is intentionally a no-op: validates parameters, then iFlag=1 and iFlag=0 both LEAVE top immediately. Customer overrides (e.g. script/客户/...) replace the body with deployment-specific writebacks.

Invocation: Called directly from Java by ErpOrderProcurementServiceImpl.doCallSsodAfter() immediately after doCallSsod() in the CheckErpOrderThread flow — i.e. only on the auto-audit path for online orders / business-card orders, not on the UI 审核 button. Exceptions inside are swallowed by the caller. No gdsmodule.sProcName binding (intentional — only the Java path drives it). xly-src ships the install script at script/标版/30100101/Sp_Calc_sSodAfter.sql.