# `Sp_Manufacture_PlanStatusSet` (procedure)


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sGuid` | `varchar(50)` |
| 2 | IN | `sStatusValue` | `int` |
| 3 | OUT | `sCode` | `int` |
| 4 | OUT | `sReturn` | `varchar(50)` |

## Body

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

## Narrative

**Business context:** 生产管理 → 生产计划管理 — name suggests a 计划状态设置 stub (set production-plan status by GUID). The signature `(sGuid, sStatusValue, sCode, sReturn)` matches a status-toggle button handler, but the live body is a 97-char placeholder: a `SELECT * FROM elecustomer LIMIT 0,1`, then `sReturn='oppr'`, `sCode=1`. Effectively a no-op shell — never received a real implementation.

**What it does:** Runs one throwaway `SELECT` from `elecustomer` (ignored), then sets `sReturn='oppr'` and `sCode=1`. No update to any plan row, no validation, no side effects.

**Invocation:** No `gdsmodule` hook, no `gdsconfigformmaster` binding, no other routine in `xlyweberp_saas_ai` references it, no caller in xly-src outside its own install script `xly-src/script/标版/30100101/Sp_Manufacture_PlanStatusSet.sql`. Status: appears orphaned / stub — candidate for maintainer audit (either wire to a real 计划状态 button or drop).