Sp_AfterPost_sSod (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 PROCEDURESpAfterPost_sSod'._

Narrative

Business context: 销售订单 (sales order). Header says "销售订单执行后执行过程(线上获取订单,名片单页自动审核后，调用)" — designed as the post-审核 hook for orders auto-approved from the online/B2C 名片 single-page order channel. Sibling of Sp_AfterPost_sAcc / Sp_AfterPost_sQtt in the canonical post-审核 calc-proc tier.

What it does: Empty stub. Both iFlag=1 and else branches contain nothing but LEAVE top — the proc returns sCode=1 without touching any table.

Invocation: Status: appears orphaned. No caller found in any channel (form-master, gdsmodule hooks, other routines, xly-src grep, schema *Post* columns) — candidate for maintainer audit. The proc is a placeholder reserving the lifecycle slot for the 名片单页/B2C auto-approval flow but the body was never filled in; production sales-order post-审核 logic flows through Sp_Check_sSod / Sp_Calc_sSodAfter.