# `Sp_saveReturn_sStl` (procedure)

> 客户审核反写


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

## Parameters

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

## Body

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

## Narrative

**Business context:** Customer-audit back-write hook (`COMMENT '客户审核反写'`) — slot in the standard `Sp_saveReturn_<code>` family for a 客户 (customer) workflow, but the body is currently a stub: it only parses the `sGuid` id-list into the temp table and exits. No upstream tables are touched.

**What it does:** Splits `sGuid` (comma-separated) into temp table `p_t_sId` using `Fn_split_string` / `Fn_spit_length`. After the WHILE loop the proc returns without doing any UPDATE or aggregate work.

**Invocation:** No DB caller references it directly, and there is no `Sp_beforeSave_sStl` / `Sp_afterSave_sStl` wrapper in this schema — the proc is reachable only by the standard naming-convention dispatch from `BusinessBaseServiceImpl` if some module's sCode is `sStl`, but no module binds it. Status: appears to be a stub/placeholder retained for the symmetry of the saveReturn family — candidate for maintainer audit (either complete the back-write body or drop the proc).
