# `Sp_Confirm_Zg` (procedure)

> 主管确认:通过


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sProInParam` | `varchar(10000)` |
| 2 | IN | `sMakePerson` | `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_Confirm_Zg`'`._

## Narrative

**Business context:** 销售管理 → 销售订单 — 主管确认:通过 ("supervisor confirm: approved") button handler on the sales-order list. Used when an order needs an extra in-line supervisor sign-off (separate from the formal 审核 workflow) — pushes the selected `salsalesordermaster` rows into the confirmed-by-supervisor state and notifies the original maker.

**What it does:** Parses the `sProInParam` JSON envelope, refusing with `请选择数据` ("please select data") when empty. For each selected slave-id, looks up the matching `salsalesordermaster` row (joining `salsalesorderslave`) to resolve the maker, bill-no and master sId via `Fun_GetLoginUser`, then writes the confirmation flags onto the master and prepares the in-app message payload for the original maker.

**Invocation:** Status: appears orphaned. No `gdsmodule` hook, `gdsconfigformmaster` reference, or other-routine caller; xly-src only ships the install script `script/标版/30100101/Sp_Confirm_Zg.sql` plus the symmetric `Sp_UnConfirm_Zg.sql`. Naming and signature match the `sp_btn_action*` dispatcher contract but no current binding was found. Candidate for maintainer audit.