# `sp_doTestGgf` (procedure)

> 测试管智能华对接数据源过程


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

## Parameters

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

## Body

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

## Narrative

**Business context:** Scaffold/template for "管智能华对接数据源过程" (Guan-Zhihua external data-source handler). The body is the generator's JSON-loop boilerplate — declares `p_uniqueCode`, `p_palletNumber`, `p_PositionNo` from each `$.data[i]` element but does no business processing. Comment markers explicitly read "业务处理部分 开始 / 结束" with no code in between.

**What it does:** Validates `sBody` is JSON, walks the `$.data` array, extracts three fields per element, and returns `sCode=1`, `sReturn='操作成功'`, `sParam=''`. No reads or writes to any business table.

**Invocation:** Status: appears orphaned. No caller found in any channel — not bound to any gdsmodule hook or form-master, not referenced by another routine, and `grep -rln sp_doTestGgf` across xly-src returns nothing. The name and comment suggest it was scaffolded via the platform's data-source-integration code generator for a管智能华 (guan-zhihua) integration test, then never filled in or wired. Candidate for removal.
