# `PRO_ERPMERGEBASESISPROCESSCLASSIFY` (procedure)


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sSisProcessClassifyId` | `varchar(100)` |

## Body

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

## Narrative

**Business context:** Base data — 工序分类 (Process Classification). When a process-classification row in `SISPROCESSCLASSIFY` is renamed, this proc pushes the new `sName` onto every historical `ERPMERGEPRODUCTIONREPORT` row that references the classification.

**What it does:** reads `sName` from `SISPROCESSCLASSIFY` for the given id, then `UPDATE`s `sProcessClassifyName` on `ERPMERGEPRODUCTIONREPORT` rows whose `sProcessClassifyId = sSisProcessClassifyId`.

**Invocation:** member of the `PRO_ERPMERGEBASE*` denorm-merge family. Called by `ProDao.proErpMergeBaseSisProcessClassify(map)` via MyBatis CALLABLE mapper `ProMapper.xml`, driven from `ChangeSisProcessClassifyServiceImpl.changeTableData()` after the JMS `CHANGE_GDS_MODULE` consumer detects a `SISPROCESSCLASSIFY` row mutation. See [Cache invalidation on metadata change](../../reference/maintainer/cache-invalidation.md).