# `Sp_Manufacture_ProductionPlanInfoLock_detail` (procedure)

> 机台排程：排程从表(点击排程+号调取)


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sLoginId` | `varchar(100)` |
| 2 | IN | `sBrId` | `varchar(100)` |
| 3 | IN | `sSuId` | `varchar(100)` |
| 4 | IN | `p_sId` | `longtext` |

## Body

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

## Narrative

**Business context:** 生产管理 → 生产计划管理 → 生产排程 — header label 机台排程：排程从表(点击排程+号调取). Lock variant of `Sp_Manufacture_ProductionPlanInfo_detail`: returns the same 排程从表 child-row payload for one parent 排程 id, but the body is laid out for use under the locked-row code path (the version planners hit when a row is currently being scheduled / frozen).

**What it does:** Takes parent ids in `p_sId` (longtext) and `CONCAT`s a dynamic `SELECT` over `mftproductionplanslave` projecting the same schedule child columns as `Sp_Manufacture_ProductionPlanInfo_detail` (`sWorkOrderId`, `sCustomerId`, `sProductId`, `sProcessId`, `sMachineId`, qty/time fields, status flags, ordering). Executes the prepared SQL and returns the result set.

**Invocation:** No `gdsconfigformmaster.sSqlStr`, `gdsmodule` hook, other-routine, or Java caller references it directly — only the install script `xly-src/script/标版/30100101/schedule/Sp_Manufacture_ProductionPlanInfoLock_detail.sql`. Likely called dynamically by the same lock-path code that wraps `Sp_Manufacture_ProductionPlanInfo_detail`, or kept as a fallback for the row-lock UI. Status: candidate for maintainer audit — confirm which code path still resolves this name.
