Sp_bd_OrderProgress.md 1.89 KB

Sp_bd_OrderProgress (procedure)

生产计划看板

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

Parameters

# Mode Name Type
1 IN sCustomerName varchar(255)
2 IN tStartDate datetime
3 IN tEndDate datetime
4 IN sWorkOrderNos varchar(255)
5 IN sLoginId varchar(4000)
6 IN sBrId varchar(100)
7 IN sSuId varchar(100)
8 IN bFilter varchar(5000)
9 IN pageNum int
10 IN pageSize int
11 OUT totalCount int
12 IN countCloumn varchar(5000)
13 OUT countMapJson longtext
14 IN sFilterOrderBy varchar(5000)
15 IN sGroupby_select_sql varchar(5000)
16 IN sGroupby_group_sql varchar(5000)

Body

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

Narrative

Business context: 生产计划看板 — order-progress board for the production-plan dashboard. Lists work orders filtered by customer / date window / 工单号 with pagination, optional grouping, and a side count map.

What it does: Materialises temp table p_TempTable with rows joining mftworkordermaster and its slaves (parts, products, customer, plan quantities, in-store quantity, deliver date, process state). Honours the standard dashboard pagination contract: pageNum/pageSize/totalCount plus countCloumncountMapJson plus sFilterOrderBy / sGroupby_select_sql / sGroupby_group_sql for dynamic ORDER BY and GROUP BY injection.

Invocation: Installed by xly-src/script/标版/30100101/Sp_bd_OrderProgress.sql. No form-master, no gdsmodule hook, no other-routine caller, no Java caller. Reached only by an external dashboard HTTP endpoint that calls the proc by name.