# `Sp_Calc_sSpfu` (procedure)

> 商机跟进


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `iFlag` | `int` |
| 2 | IN | `iTmpCheck` | `int` |
| 3 | IN | `sFormGuid` | `varchar(100)` |
| 4 | IN | `sGuid` | `varchar(100)` |
| 5 | IN | `sLoginId` | `varchar(100)` |
| 6 | OUT | `sReturn` | `varchar(5000)` |
| 7 | IN | `sBrId` | `varchar(100)` |
| 8 | IN | `sSuId` | `varchar(100)` |
| 9 | OUT | `sCode` | `int` |

## Body

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

## Narrative

**Business context:** 销售打样跟进 (sales sample-printing follow-up — `salsalesprintfollowupmaster`) audit / un-audit. The 打样跟进 records progress against a 打样申请 (sample-print application); auditing freezes the follow-up so it can drive downstream costing.

**What it does:** Validates `sGuid`/`bInvalid`, then on `iFlag=1` sets `bCheck=1`, `sCheckPerson`, `tCheckDate` on `salsalesprintfollowupmaster`; `iFlag=0` reverses the flag. No KPI, no flow-check, no downstream writeback in the deployed body.

**Invocation:** Status: appears orphaned. No `gdsmodule.sProcName` binding, no form-master `sSqlStr` ref, no other-routine caller, no Java caller — only the install script at `script/标版/30100101/Sp_Calc_sSpfu.sql`. Despite the page comment 商机跟进, the deployed body targets `salsalesprintfollowupmaster` (打样跟进), not `salsalesFollowUpmaster` (商机跟进 — that's `Sp_Calc_sSfu`). Candidate for maintainer audit.

Flag: page comment `商机跟进` does not match the deployed body (which targets `salsalesprintfollowupmaster`, the 打样跟进 bill). One of the two is stale — candidate for maintainer audit.