Sp_Calc_sAsq (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_sAsq'._

Narrative

Business context: 销售管理 → 销售单据 → 销售品质异常单据 — sales quality-abnormal report check / uncheck on salqualityabnormalmaster. Approves a customer-side quality-complaint write-up.

What it does: Validates sGuid. Reads master sBillNo, sCustomerId, sSalesManId, tCreateDate, sMakePerson, bInvalid. Refuses if bInvalid=1. With iFlag=1: refuses if already bCheck=1; sets bCheck=1, sStatus=1, sCheckPerson=sLoginId, tCheckDate=NOW(). With iFlag=0: symmetric uncheck (returns sNoCanCheckBybUnCheck on bCheck=0 row). Scoped by sBrandsId/sSubsidiaryId.

Invocation: Bound to gdsmodule.sProcName on 销售品质异常单据 (sId 15888249530003323555072594268700) under 销售管理 → 销售单据. Dispatched via the front-end "审核 / 反审核" button on that module's master form. xly-src deployment-bundle copies under script/标版/.

Flag: the leading variable declarations (sCustomerGuid, sBillNo, sSaleManGuid, etc.) are populated by SELECT INTO but never used — vestigial code left after a refactor that stripped the side-effect logic.