# `Sp_bd_TeamOee` (procedure)

> 班组OEE展示


- **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` | `varchar(5000)` |
| 5 | OUT | `sCode` | `int` |
| 6 | OUT | `sReturn` | `longtext` |

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `Sp_bd_TeamOee`'`._

## Narrative

**Business context:** 看板管理 — "班组OEE展示" tile. The team-OEE bar chart showing the three utilisation metrics for the current team.

**What it does:** Builds the OEE payload from a hard-coded UNION — 速度稼动 = 89, 时间稼动 = 69, OEE = 29 — and serialises to JSON `{"data":[{"x":<label>,"y":<value>}...],"yUnit":"%"}` via OUT `sReturn`. No table lookups; the standard dashboard input params (`sLoginId`/`sBrId`/`sSuId`/`bFilter`) are accepted but unused.

**Invocation:** No install script in xly-src, no form-master, no `gdsmodule` hook, no Java caller, no other-routine caller. Reached only by an external dashboard HTTP endpoint that calls the proc by name. **The output is entirely demo data** — verify before relying on it.