Sp_Bd_bi22 (procedure)

@author:zhucx @date:20220111 @describe: 印刷现场

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

Parameters

#	Mode	Name	Type
1	IN	iFlag	int
2	IN	iTmpCheck	int
3	IN	sFormGuid	varchar(100)
4	IN	sGuid	varchar(100)
5	IN	sLoginId	varchar(100)
6	OUT	sReturn	varchar(4000)
7	IN	sBrId	varchar(100)
8	IN	sSuId	varchar(100)
9	OUT	sCode	int

Body

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

Narrative

Business context: 印刷现场 — four-machine 现场看板 (workshop kanban) for the 印刷 (printing) line, sibling to Sp_Bd_bi20 (喷码现场), Sp_Bd_bi21 (模烫现场), Sp_Bd_bi23 (糊盒现场), Sp_Bd_bi24 (品检现场). Returns the four-tile status board for PLCs 1, 2, 13, 23.

What it does: Hardcodes a 4-row p_Bd_PlcNo_No(iPlcNo,iNo) map, then for each PLC reads elemachine/plc_currentmachinevalue/mft_workorder* to assemble per-machine 当前状态/当前工单/已生产数量/调机时间/异常 tiles into p_Bd_workshop5, finally emitting a JSON board into sReturn.

Invocation: Installed by xly-src/script/标版/30100101/kanban/Sp_Bd_bi22-印刷现场.sql. No form-master sSqlStr, no gdsmodule hook, no Java caller. Status: reachable only via an external dashboard HTTP endpoint that invokes the proc by name — kanban procs sit outside the routine call-graph wiring this catalog tracks. The MES-fork Sp_Bd_bi22_nomes is the non-MES variant.

Flag: the four PLC literals 1, 2, 13, 23 are tenant-deployment-specific (no elemachine.sName lookup) — re-mapping needed if cloned. The header comment @describe: 印刷现场 matches the body.