Sp_SalSalesCheck1 (procedure)

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

Parameters

#	Mode	Name	Type
1	IN	sLoginId	varchar(100)
2	IN	sCustomerId	varchar(100)
3	IN	sBrId	varchar(100)
4	IN	sSuId	varchar(100)
5	IN	bFilter	text
6	IN	sUnTaskFormId	varchar(100)
7	IN	pageNum	int
8	IN	pageSize	int
9	OUT	totalCount	int
10	IN	countCloumn	text
11	OUT	countMapJson	longtext
12	IN	sFilterOrderBy	text
13	IN	sGroupby_select_sql	text
14	IN	sGroupby_group_sql	text

Body

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

Narrative

Business context: 销售管理 → 销售送货流程 → 3/4 送货单->销售对帐 — alternate / experimental variant of Sp_SalSalesCheck that joins additional sources (Viw_SalSalesOrder, Viw_MftWorkOrder, Viw_SalQualityAbnormal) into the to-be-reconciled list so the 对账 view can also pick from orders, work orders, and quality-abnormality bills, not just 送货单 / 退货单.

What it does: Same signature and same TmpSalSalesCheck shape as Sp_SalSalesCheck; reads CbxSrcNoCheck / CkxWebNotInFinance from SysSystemSettings, applies Fun_GetLookCustomer scoping, then assembles the union from the four Viw_* sources, calls Sp_Do_UpdateByPageSizeBefore for paging prep, and returns the final dataset to the form. The 1 suffix is the naming convention for a side-by-side alternate that the integrator can swap into the form binding.

Invocation: Not currently bound to any gdsconfigformmaster row (verified against the live DB) — superseded by Sp_SalSalesCheck for the 设定单据->销售对账 form (sId 11811781131121915181734332700). Sp_ProductCarryforward still references it in code paths. Status: appears retired in favour of the default variant — candidate for maintainer audit before removal.