# `PRO_ERPMERGEBASESISFORMULA` (procedure)


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

## Parameters

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

## Body

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

## Narrative

**Business context:** Base data — 工资公式 (Wage Formula). When a wage-formula row in `SISFORMULA` is renamed in the formula maintenance page, this proc pushes the new name onto every historical `ERPMERGEPRODUCTIONREPORT` row that uses the formula, so payroll-related production-report queries keep displaying the current label.

**What it does:** reads `sName` from `SISFORMULA` for the given id and updates `sWageName` on `ERPMERGEPRODUCTIONREPORT` rows whose `sWageId = sSisFormulaId`.

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