Sp_interface_insertsaleman (procedure)
第三方接口插入,可以做成通用插入(暂时定时) 模板
- Type: PROCEDURE
- Deterministic: NO
- SQL data access: CONTAINS SQL
Parameters
| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | sTableName |
longtext |
| 2 | IN | sData |
longtext |
| 3 | IN | sMakePerson |
varchar(100) |
| 4 | IN | sBrId |
varchar(100) |
| 5 | IN | sSuId |
varchar(100) |
| 6 | OUT | sCode |
int |
| 7 | OUT | sReturn |
varchar(5000) |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpinterface_insertsaleman'._
Narrative
Business context: Third-party-interface template for inserting a sales person (sissalesman) from an external system. Comment 第三方接口插入,可以做成通用插入(暂时定时) 模板 acknowledges it is intended to be generalised into a universal insert template later — for now it is wired narrowly to SisSalesMan.
What it does: Validates that sData is non-empty (未传入要插入的数据) and is valid JSON (传入的插入数据格式不匹配), returning sCode=-1 on failure. Walks the JSON array (expected shape "SisSalesMan":[{...}, ...]) and inserts each entry into sissalesman, using Fun_Sis_GetNewId-style id generation. sTableName is accepted but the body only handles the salesman case — broader-table support is not implemented.
Invocation: Status: appears orphaned. No gdsmodule hook, no form-master reference, no other routine CALLs it, no xly-src grep hit. Paired with sp_interface_delsaleman; both procs predate the JD/Kingdee-style interface wiring in JdInterfaceServiceImpl and were never adopted by the shipped Java code. Candidate for maintainer audit.