# `sp_OEE_Exit` (procedure)

> @author:钱豹
							@date:20210908 封存
							@describe: OEE登录成功时：
							1、更新班组下岗标记


- **Type:** PROCEDURE
- **Deterministic:** NO
- **SQL data access:** CONTAINS SQL

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sMachineId` | `varchar(100)` |
| 2 | IN | `sTeamId` | `varchar(100)` |
| 3 | IN | `sBrId` | `varchar(100)` |
| 4 | IN | `sSuId` | `varchar(100)` |
| 5 | OUT | `sReturn` | `varchar(1000)` |
| 6 | OUT | `sCode` | `int` |

## Body

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

## Narrative

**Business context:** OEE管理 — "下岗" (sign-off) hook fired when a 班组 (shift team) leaves an OEE machine workstation. Counterpart to `sp_OEE_loading` (sign-on); flips the team's `bWorking` flag back to 0 so the next sign-on starts from a clean slate.

**What it does:** Single `UPDATE eleteam SET bWorking = 0 WHERE sId = sTeamId AND sBrandsId = sBrId AND sSubsidiaryId = sSuId`. Header comment `@author:钱豹 @date:20210908 封存` marks the routine as archived/legacy. The "登录成功时" wording in the comment is mislabelled — the body acts on sign-off.

**Invocation:** Install script ships at `script/标版/30100101/schedule/sp_OEE_Exit.sql`. No `gdsconfigformmaster` binding, no `gdsmodule` hook, no other proc/function call, no Java reference in xly-src — paired logically with `sp_OEE_loading` but currently not reached by any code path. Status: appears orphaned; candidate for maintainer audit.