Sp_NotPayAbles_expen.md 1.93 KB

Sp_NotPayAbles_expen (procedure)

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

Parameters

# Mode Name Type
1 IN sSupplyGuid varchar(4000)
2 OUT bOut int
3 IN sLoginId varchar(4000)
4 IN sBrId varchar(100)
5 IN sSuId varchar(100)
6 IN bFilter varchar(5000)
7 IN sUnTaskFormId varchar(100)
8 IN pageNum int
9 IN pageSize int
10 OUT totalCount int
11 IN countCloumn varchar(5000)
12 OUT countMapJson longtext
13 IN sFilterOrderBy varchar(5000)
14 IN sGroupBy_select_sql varchar(5000)
15 IN sGroupBy_group_sql varchar(5000)

Body

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

Narrative

Business context: Variant of Sp_NotPayAbles (1/1 对账( 采购&外协)->付款 — supplier-payables warning) — the smaller-scope "expense" variant: same parameter list and same p_tmp_PayablesWarning shape, but its UNION drops the procurement/material-receipt sources and feeds the temp table only from the expense (费用) payables track. Likely an internal split kept for an "费用付款" branch that never made it to a deployed form.

What it does: Same overall mechanism as Sp_NotPayAblesSysAccountPeriod.tAPDate cutoff, Sp_Sis_GetConst for PayInit/Advance/FinancialAdjust/Receipt labels, p_tmp_PayablesWarning build, then hand-off to Sp_Outstanding_Query for paging/filter/total — minus the procurement leg.

Invocation: Status: appears orphaned. No gdsconfigformmaster binding, no gdsmodule hook, no other proc/function references the name, no xly-src caller (Java, MyBatis, install script) — candidate for maintainer audit; the deployed form uses Sp_NotPayAbles instead.