Sp_Customer_BtnEventCancelInvalid (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 PROCEDURESpCustomer_BtnEventCancelInvalid'._

Narrative

Business context: 基础资料 → 客户 (elecustomer) — symmetric inverse of Sp_Customer_BtnEventInvalid. Reactivates a soft-deleted customer (bInvalid=0) and logs the action as '取消作废客户' against the customer form (sFormId='192116810111915048607109671').

What it does: Same JSON-batch shape as the invalidate sibling: validates sProInParam, parses $.params[].value[].sId, splits on - for multi-id payloads, then per sIdOne reads the customer name, runs UPDATE elecustomer SET bInvalid=0 ..., and INSERT INTO syslog with sLog='取消作废客户：'+sCustomerName and sOperationType='取消作废客户'.

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