# `Sp_afterSave_sSfu` (procedure)

> 商机跟进存后反写数量


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sGuid` | `varchar(2000)` |
| 2 | IN | `sBrId` | `varchar(100)` |
| 3 | IN | `sSuId` | `varchar(100)` |
| 4 | OUT | `sCode` | `int` |
| 5 | OUT | `sReturn` | `varchar(4000)` |

## Body

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

## Narrative

**Business context:** 商机跟进单据 → 销售单据 → 销售管理 — header says 商机跟进存后反写数量. Thin save-phase 反写 wrapper in the `Sp_afterSave_s<Code>` family that delegates the actual back-write to `Sp_saveReturn_sSfu` (propagates the follow-up phase `sFollowUpPhase` upstream to `salsaleschancemaster.sFlow`).

**What it does:** Wraps `sGuid` in double-quotes if not already quoted and unconditionally calls `Sp_saveReturn_sSfu(sGuid, sBrId, sSuId, 2, @sCode, @sReturn)` (iFlag=2 = "after save" phase). The body carries a large commented-out dynamic-SQL block that would once have updated `salsaleschancemaster.sFlow` from the latest `salsalesFollowUpmaster.sFollowUpPhase` — inert. Does not propagate the inner `@sCode`/`@sReturn` back to its own OUT params.

**Invocation:** Reached only via dispatch. `Sp_Check_sSfu` calls this proc, but `Sp_Check_sSfu` itself has no live `gdsmodule.sSaveProName` binding. The live path is `Sp_Invalid_backwriting`, which dispatches to this proc on 作废/取消作废 of form `101251240115016035948853880` (商机跟进单据), itself triggered from Java `CheckmodelServiceImpl` via `Sp_Invalidation`.
