Sp_Calc_tice (procedure)

印刷工单审核

• 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	longtext
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 PROCEDURESpCalc_tice'._

Narrative

Business context: Has the Sp_Calc_s* audit/un-audit signature against eptmachinefixednoticemaster (设备固定资产报修通知主表 — equipment fixed-asset repair-notice master). COMMENT says 印刷工单审核 but that's stale copy-paste; the actual table is the equipment-asset notice bill. The proc name's _tice suffix comes from "no*tice*".

What it does: Validates sGuid; refuses on bInvalid=1. With iFlag=1, refuses when already bCheck=1; otherwise UPDATE eptmachinefixednoticemaster SET bCheck=1, sStatus=1, sCheckPersON=sLoginId, tCheckDate=NOW(). With iFlag=0 symmetric un-audit. (Note: column name is mis-cased as sCheckPersON in the body — case-sensitive on case-sensitive collations.)

Invocation: Status: appears orphaned. No gdsmodule.sProcName row binds this name; xly-src has no occurrence anywhere. No Java caller, no other-routine caller, no form-master reference. Candidate for maintainer audit — together with sibling Sp_Calc_tore (same body shape against eptmachinefixedinstoremaster), these look like a stalled-out repair-notice / asset-storage audit pair.