# `Sp_GetMachineByApsRule-luc` (procedure)

> 主计划：自定义排程规则(根据APS规则选择最合适机台)


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sWorkOrderGuid` | `varchar(5000)` |
| 2 | IN | `sWorkOrderProcessid` | `varchar(100)` |
| 3 | IN | `sProcessid` | `varchar(100)` |
| 4 | IN | `p_sMachineid` | `varchar(100)` |
| 5 | IN | `sBrId` | `varchar(100)` |
| 6 | IN | `sSuId` | `varchar(100)` |
| 7 | OUT | `sReturnMachineId` | `varchar(250)` |

## Body

_Body is not pre-cached. To inspect: `mysql --defaults-file=~/.my.cnf -e 'SHOW CREATE PROCEDURE `Sp_GetMachineByApsRule-luc`'`._

## Narrative

**Business context:** Developer-suffixed variant of `Sp_GetMachineByApsRule` (主计划：自定义排程规则) — APS rule-based machine picker for a work-order process. The `-luc` suffix follows the xly convention of developer-initials backup tags (cf. session-history pattern).

**What it does:** Same shape as the live sibling — picks `eleprocessmachine.bDefault` row when `p_sMachineid` is blank else excludes the current machine; falls through to a `Machine_Tmp` rule search over `eleprocessmachineapsrule` keyed by 印刷颜色/重量/长宽/工艺/材料/产品分类/客户备注 with three APS-quantity caps (`dAPSProcQtyMax`/`dAPSQtyMax`/`dAPSZQtyMax`). Carries newer APS-quantity columns the unsuffixed version uses but is half the size (no `sReturnInfo` trace).

**Invocation:** Status: appears orphaned. No caller found in any channel (form-master, gdsmodule hooks, other routines, xly-src grep across all extensions). Live caller path is `BtnCalculationServiceImpl.doSetTimeCalcMachineHour()` → `Sp_GetMachineByApsRule` (the unsuffixed 109K body).