PRO_ERPMERGEBASESISCUSTOMERCLASSIFY (procedure)

• Type: PROCEDURE
• Deterministic: NO
• SQL data access: CONTAINS SQL

Parameters

#	Mode	Name	Type
1	IN	sSisCustomerClassifyId	varchar(100)

Body

Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDUREPROERPMERGEBASESISCUSTOMERCLASSIFY'._

Narrative

Business context: Base data — 客户分类 (Customer Classification). When a customer-classification row in SISCUSTOMERCLASSIFY is renamed, this proc pushes the new sName onto every historical row of the three merge-reporting tables that references this classification, so reports keep displaying the current name.

What it does: reads sName from SISCUSTOMERCLASSIFY for the given id, then UPDATEs sCustomerClassifyName on ERPMERGEWORKORDER, ERPMERGEPRODUCTIONREPORT, and ERPMERGESALSALESORDER rows whose sCustomerClassifyId = sSisCustomerClassifyId.

Invocation: member of the PRO_ERPMERGEBASE* denorm-merge family. Called by ProDao.proErpMergeBaseSisCustomerClassify(map) via MyBatis CALLABLE mapper ProMapper.xml, driven from ChangeSisCustomerClassifyServiceImpl.changeTableData() after the JMS CHANGE_GDS_MODULE consumer detects a SISCUSTOMERCLASSIFY row mutation. See Cache invalidation on metadata change.