TJ_SP_PoIQCInfoAfter (procedure)

MES --> Infor Syteline ERP（MES，调用Infor ERP数据库里的存储过程）

• Type: PROCEDURE
• Deterministic: NO
• SQL data access: CONTAINS SQL

Parameters

#	Mode	Name	Type
1	IN	Flag	int
2	IN	ErrorMessage	longtext
3	IN	sAfterIn	longtext
4	IN	sBrId	varchar(100)
5	IN	sSuId	varchar(100)
6	OUT	sReturn	longtext
7	OUT	sCode	int

Body

Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURETJSP_PoIQCInfoAfter'._

Narrative

Business context: 第三方接口 → Infor Syteline ERP (per COMMENT 'MES --> Infor Syteline ERP（MES，调用Infor ERP数据库里的存储过程）') — error-handler tail of a paired "Before/After" call into the Infor Syteline SQL Server side. The "Before" proc shapes the SQL+params, Java executes them against the third-party DB, then this "After" proc is dispatched by the framework with the success/error flag.

What it does: Trivial wrapper. Sets sCode=1, sReturn='调用INFO成功'. If Flag=0 (Java reports failure) it flips sCode=-8 and sReturn=ErrorMessage (or 'INFO调用失败。' if no message). sAfterIn (the proc-defined post-call payload from the pair) is accepted but unused.

Invocation: Designed to be invoked by InfoSqlserverServiceImpl after doViewTable("<srcTable>","<doPro>","<doProAfter>") runs the third-party-side SQL — the "After" name is fed in as the second proc to call via procedureService.getCallPro(...). The active xly-src has every doViewTable("inforarrive","TJ_TJMES_GRNLine","TJ_TJMES_GRNLineAfter") call commented out (InterfaceController.testdhrk() is fully commented), and there is no TJ_TJMES_GRNLineAfter proc in this DB. Likely the bridge for the PoIQCInfo feed; sister proc TJ_SP_PoIQCInfo does not exist either. Status: bridge is wired but the Java entry point is disabled — feature appears dormant.