Sp_plan_teamrate (procedure)

速度嫁动率(分组报表)机台

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

Parameters

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

Body

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

Narrative

Business context: 生产管理 → 计划、排程 (KPI/分组报表) — paged grouped report of 班组/机台 utilization rate. Comment names it 速度嫁动率(分组报表)机台 (speed-utilization rate, grouped by team/machine). Aggregates a month of plan and report data per team/machine for the KPI dashboard.

What it does: Defaults the window to NOW()-INTERVAL 1 MONTH → NOW(), then populates a temp table Sp_plan_teamrate keyed on sTeamId/sMachineId with columns including dPrintQty (班组产能), dProcessQty (标准产能), dReportProcessQty (实际产能), dReportHour (实际用时), sWorkType (印工/班). Returns paged results via the standard bFilter + Sp_Do_UpdateByPageSizeBefore contract; countMapJson carries column totals.

Invocation: Status: appears orphaned in the standard install. Not referenced by any gdsconfigformmaster.sSqlStr, gdsmodule.sProcName, or other DB routine. The only xly-src hit is script/客户/朝阳/Sp_plan_teamrate.sql — a customer-specific (朝阳) override that ships a different signature (sDay as the first IN). The deployed DB version exposes the saas-multi-tenant signature (sLoginId, sBrId, sSuId, …), suggesting it was promoted from a 朝阳 customisation but never wired to a saas-side form — candidate for maintainer audit.