# `Sp_customerclassify_BtnEventInvalid` (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_customerclassify_BtnEventInvalid`'`._

## Narrative

**Business context:** 基础资料 → 客户分类 (`siscustomerclassify`) — sibling to `Sp_Customer_BtnEventInvalid` for the 客户分类 (customer-classify) master. Soft-deletes selected classify rows (`bInvalid=1`) and writes one `syslog` audit row per id with `sOperationType='作废客户分类'` and the classify name, keyed back to the form `sFormId='11811781131121915196321754040'`.

**What it does:** Standard JSON-batch shape: validates `sProInParam`, parses `$.params[].value[].sId`, explodes `-`-separated multi-id strings via `SUBSTRING_INDEX`. Per `sIdOne`: reads `siscustomerclassify.sName` to compose the log message (`'作废客户分类：' + sName`), runs `UPDATE siscustomerclassify SET bInvalid=1 WHERE sId=p_sIdOne AND sBrandsId AND sSubsidiaryId`, then `INSERT INTO syslog` with the audit row.

**Invocation:** `sp_btn_action*`-style — dispatched by `GenericProcedureCallServiceImpl.doGenericProcedureCall()` when the 作废 button on the 客户分类 form fires. No `gdsmodule` hook reference; binding lives in the form's button configuration. Not in xly-src install scripts — DB-only.
