# `Sp_saveReturn_sCio` (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_sCio`'`._

## Narrative

**Business context:** 客户审核 — 反写 ("back-write") stub for the `sCio` (客户审核) module's save lifecycle. Follows the same iTag/sGuid/sBrId/sSuId signature as the other `Sp_saveReturn_s*` family, but the body is currently just the boilerplate envelope: parses `sGuid` (CSV) into `p_t_sId`, then exits without writing anything.

**What it does:** Sets `iTag = IFNULL(iTag, 0)` (1=pre-save, 2=post-save by convention). Builds temp table `p_t_sId(sId)`, normalises `sGuid` by stripping quotes, and uses `Fn_spit_length` / `Fn_split_string` to load each id into `p_t_sId`. **No subsequent UPDATE / INSERT.** Returns with `sCode`/`sReturn` unset.

**Invocation:** Called by `Sp_beforeSave_sCio` (with `iTag=1`) and `Sp_afterSave_sCio` (with `iTag=2`). Those before/after hooks would in turn be wired as `gdsmodule.sSaveProName(Before)` on the 客户审核 form, but the form is not present in this tenant's `gdsmodule` rows. Status: appears to be a scaffolded stub kept as a template alongside the working `Sp_saveReturn_s*` family — back-write logic has not been implemented (or has been intentionally cleared). Candidate for maintainer audit.
