Sp_eptmachinemaintenance_Lader (procedure)
维修后领导确认
- Type: PROCEDURE
- Deterministic: NO
- SQL data access: CONTAINS SQL
Parameters
| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | sProInParam |
varchar(10000) |
| 2 | IN | sMakePerson |
varchar(100) |
| 3 | IN | sUserId |
varchar(100) |
| 4 | IN | sMachineId |
varchar(255) |
| 5 | IN | sBrId |
varchar(100) |
| 6 | IN | sSuId |
varchar(100) |
| 7 | OUT | sReturn |
varchar(1000) |
| 8 | OUT | sCode |
int |
Body
Body is not pre-cached. To inspect: mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURESpeptmachinemaintenance_Lader'._
Narrative
Business context: 维修后领导确认 — leader-confirmation step after equipment maintenance is completed. The 设备维修单 (eptmachinemaintenancemaster) tracks 机长确认 and 领导确认 as two separate sign-offs; this proc stamps the 领导 (leader) confirmation on one or more selected maintenance records in a single action.
What it does: Parses sProInParam JSON for $.params[*].value[*].sId (the selected row IDs from a grid-style action) and UPDATE eptmachinemaintenancemaster SET bLeader=1, sLeaderPerson=sMakePerson, tLeaderDate=NOW() WHERE sId=p_sId for each. On LENGTH(sProInParam)<5 aborts with sReturn set via Sp_Sis_GetConst('paramsErro', ...) and sCode=-1.
Invocation: Status: appears orphaned. Not bound to any gdsmodule hook (sProcName/sSaveProName), no form-master reference, no other routine references it, no xly-src reference. The signature (sProInParam LONGTEXT + sMakePerson/sUserId/sMachineId/sBrId/sSuId + sReturn/sCode) matches xly's GenericProcedureCallServiceImpl.doGenericProcedureCall button-action contract — likely intended as the 领导确认 grid button on the 设备维修 form but never wired into a button-event row. Sibling Sp_eptmachinemaintenance_OEE performs the symmetric 机长确认 stamp and is similarly orphaned. Candidate for maintainer audit.