# `sp_interface_delsaleman` (procedure)

> 删除销售人员


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

## Parameters

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

## Body

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

## Narrative

**Business context:** Third-party-interface helper for deleting a sales person (`sissalesman`) by `sNo`. Paired with `Sp_interface_insertsaleman` — together they form a primitive CRUD façade an external system can call when synchronising its sales-rep master into xly.

**What it does:** Trivial. Sets defaults on the OUT params then `DELETE from sissalesman where sNo = salemanNo`. No tenant scoping (`sBrId`/`sSuId` accepted but ignored), no soft-delete (`bInvalid` flag is not used), no cascade to dependent rows. Always returns `sCode=1, sReturn='操作成功'` regardless of whether a row was actually removed.

**Invocation:** Status: appears orphaned. No `gdsmodule` hook (the UI 销售人员 module owns its own save/delete proc), no form-master reference, no other routine `CALL`s it, no xly-src grep hit. The proc comment "第三方接口插入" suggests it was scaffolded for an external integration that never went live. Candidate for maintainer audit; if revived, add tenant scoping before deleting.