# `Sp_quoquotation_customeragree` (procedure)

> @author:zhucx 
		     @date: 
				 @describe:


- **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 PROCEDURE `Sp_quoquotation_customeragree`'`._

## Narrative

**Business context:** 销售管理 → 报价&估计管理 → 报价单 (quoquotationmaster) — toolbar button "客户已同意" that records the sales-rep's confirmation that the customer has accepted the quote. Part of the quote-lifecycle state machine sitting alongside `Sp_quoquotation_CustomerUnagree` (customer rejected → status 3), `Sp_quoquotation_CustomerAgreeAgain` (revert to active → status 1), `Sp_quoquotation_customeragreeWithdraw` (withdraw the agreement → status 1).

**What it does:** Validates `sProInParam` length, then iterates `$.params[*].value[*].sId` and runs `UPDATE quoquotationmaster SET sStatus='4', tStatus=SYSDATE() WHERE sId=p_sId AND sBrandsId=sBrId AND sSubsidiaryId=sSuId` for each. No further side-effects (no audit, no flow trigger).

**Invocation:** Standard generic-dispatch button handler (signature `sProInParam, sMakePerson, sBrId, sSuId, OUT sReturn, OUT sCode`) — invoked by `GenericProcedureCallServiceImpl.doGenericProcedureCall()` (POST `/procedureCall/doGenericProcedureCall`) when the 报价单 grid's 客户已同意 button is clicked. No `gdsmodule` hook or DB-side binding; the button names the proc directly.