# `PRO_ERPMERGEBASESISPAYMENT` (procedure)


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

## Parameters

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

## Body

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

## Narrative

**Business context:** Base data — 收付款方式 (Payment terms). When a payment-method row in `SISPAYMENT` is renamed, this proc pushes the new `sName` onto every historical row that references the term on work-order and sales-order merge-reporting tables.

**What it does:** reads `sName` from `SISPAYMENT` for the given id, then `UPDATE`s `sGetPayName` on `ERPMERGEWORKORDER` and `ERPMERGESALSALESORDER` rows whose `sGetPayId = sSisPaymentId`.

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