Sp_NotReceivables_hz (procedure)

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

Parameters

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

Body

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

Narrative

Business context: Summary (汇总) variant of Sp_NotReceivables under 1/1 销售对账->收款 — per-customer rollup of unreceived sales bills instead of per-bill detail. Intended for an AR overview view where the user wants one row per customer with totals only.

What it does: Same SysAccountPeriod.tAPDate cutoff and Sp_Sis_GetConst constant lookups as Sp_NotReceivables; populates the same ReceivablesWarning shape; final dynamic SQL collapses the per-bill UNION by sCustomerId so dProductMoney/dReceiptMoney/dNoReceiptMoney are pre-summed before paging through Sp_Outstanding_Query.

Invocation: Status: appears orphaned. No gdsconfigformmaster binding, no gdsmodule hook, no other proc/function references the name — only the install script script/标版/30100101/Sp_NotReceivables_hz.sql. The deployed form 1/1 销售对账->收款 uses Sp_NotReceivables (detail), not this 汇总 variant. Candidate for maintainer audit.