# `Sp_PlanListtDeliverDate_BtnRepair_memo` (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 | `sBrId` | `varchar(100)` |
| 4 | IN | `sSuId` | `varchar(100)` |
| 5 | OUT | `sReturn` | `varchar(1000)` |
| 6 | OUT | `sCode` | `int` |

## Body

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

## Narrative

**Business context:** Snapshot/memo copy of `Sp_PlanListtDeliverDate_BtnRepair` (生产计划 → 主计划 delivery-date adjust). Body is byte-identical to the active proc — kept as a `_memo` rollback variant per the convention that backs up a routine before a destructive edit. Per wiki convention, snapshot copies are not narrated separately; see `Sp_PlanListtDeliverDate_BtnRepair` for the substantive narrative.

**What it does:** Same as `Sp_PlanListtDeliverDate_BtnRepair` at the time of copy — cascades a new `tDeliverDate` from `$.params[*].value[*].sId` rows of `mftproductionplan` into `salsalesorderslave`, `mftworkorderslave`, `mftproductionplanslave`, `mftproductionplan` (with 偏离/满足 flag), `saldelivernotifyslave`; writes a 调整交期 `syslog` row.

**Invocation:** Not expected to be called from production. No `gdsmodule.sProcName` binding, no form-master sSqlStr reference, no xly-src install script. Status: snapshot — verify before relying on it.
