# `Sp_interface_additems_adv_after` (procedure)

> 调用接口前参数组装 https://blog.csdn.net/m0_37179470/article/details/81271607


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sRequestParam` | `longtext` |
| 2 | IN | `sMakePerson` | `varchar(100)` |
| 3 | IN | `sBrId` | `varchar(100)` |
| 4 | IN | `sSuId` | `varchar(100)` |
| 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_interface_additems_adv_after`'`._

## Narrative

**Business context:** Integration hooks for the Infor SyteLine (SL) `IDORequestService/MGRestService.svc/json/SLJobTrans/additems/adv/` work-order push (印刷工单同步到 SyteLine ArtEstInterfaces). After-call counterpart of `Sp_interface_additems_adv_before` — runs once the third-party HTTP POST returns, intended to post-process the response and update local mirror tables.

**What it does:** Currently a stub. Defaults the OUT params (`sCode=1`, `sReturn='操作成功'`) and exits without reading `sRequestParam`. Effectively a no-op — the integration is wired into the dispatcher slot but no post-processing logic has been written yet (paired install script `script/标版/upgrade/20211115接口对接功能/Sp_interface_additems_adv_after.sql` shows the same skeleton).

**Invocation:** Wired into the SyteLine work-order push integration as the post-call hook. The xly-src install script lives next to `Sp_interface_additems_adv_before.sql` and `Sp_interface_SLJobTrans_before.sql`. Dispatcher is the same pattern as `JdInterfaceServiceImpl.JDUDFVOUCHER()` — a `procedureService.getCallPro()` call from an SL-specific interface service. No live Java reference grep hits in xly-src today; if the SyteLine integration is enabled at runtime, this is its declared after-hook.
