# `Sp_Manufacture_InsertMftPlanBook` (procedure)

> 生产计划


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

## Parameters

| # | Mode | Name | Type |
|---|---|---|---|
| 1 | IN | `sWorkOrderGuid` | `varchar(5000)` |
| 2 | IN | `sWorkOrderBillNo` | `varchar(100)` |
| 3 | IN | `bCheck` | `int` |
| 4 | IN | `sLoginId` | `varchar(100)` |
| 5 | IN | `sBrId` | `varchar(100)` |
| 6 | IN | `sSuId` | `varchar(100)` |
| 7 | OUT | `sCode` | `int` |
| 8 | OUT | `sReturn` | `varchar(500)` |

## Body

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

## Narrative

**Business context:** 生产管理 → 生产计划管理 — book-mode variant of `Sp_Manufacture_InsertMftPlan`. Same signature, same role (explode work-order into `mftproductionplanmaster` + `MftProductionPlanSlave` rows on audit / re-plan), but tuned for the 书刊 / 装订 (book) production flow rather than the standard 平装 path.

**What it does:** For the given `sWorkOrderGuid` (or `sWorkOrderBillNo`), `INSERT INTO mftproductionplanmaster` + `INSERT INTO MftProductionPlanSlave` per process per the book-side 拆单方式, then `UPDATE MftProductionPlanSlave` to reconcile state. Mirror of the standard variant — same parameter list, same outputs.

**Invocation:** Status: appears orphaned in current metadata. No `gdsmodule` hook, no form-master binding, no in-DB caller, and the only xly-src hit is the install script `script/标版/30100101/Sp_Manufacture_InsertMftPlanBook.sql`. Likely called dynamically (e.g., via `sp_btn_action` dispatching on a book-specific module) or via metadata not yet surveyed — candidate for maintainer audit.
