# `Sp_ProductProcess` (procedure)


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

## Parameters

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

## Body

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

## Narrative

**Business context:** 销售管理 — sales-side helper that resolves a 销售订单 by `sBillNo` and flags every slave line as stock-up complete. Signature (`sSrcNo, sBrId, sSuId, …`) does not match the generic `BtnEvent` dispatch shape (it lacks `sProInParam`/`sMakePerson`), so it has to be called from another stored proc, not directly from the BtnEvent generic-dispatcher.

**What it does:** `SELECT sId INTO p_sId FROM salsalesordermaster WHERE sBillNo=sSrcNo AND sBrandsId=sBrId AND sSubsidiaryId=sSuId; UPDATE salsalesorderslave SET bStockupComplete=1 WHERE sParentId=p_sId AND tenant matches`. No state checks, no syslog row, no return code logic beyond the initial `IFNULL` guards.

**Invocation:** Status: appears orphaned. No caller in `gdsmodule` hooks, `gdsconfigformmaster` form-master columns, other stored procs/functions, or the xly-src tree (only its own install script `script/标版/30100101/Sp_ProductProcess.sql` references the name). The companion `Sp_ProductProcess_BtnEventProductProcess` duplicates the same body in BtnEvent-compatible packaging. Candidate for maintainer audit — likely superseded.
