15. Governed replenishment and approved-source proposals

Select root item, site, ownership pool, optional area/project and bounded dates. Select the exact released MBOM for each make item/revision. Approved dated policies must specify one procurement method; missing, ambiguous, inaccessible or inactive-planner policies block proposals. Parent-before-component netting spends stock once across shared components. Only new make proposals explode reviewed gross issue quantities; existing builds already contribute authoritative requirement/output rows.

MRP BUY proposals use independently approved supplier source lists when configured for the material and site. Priority selects the first eligible supplier; quota compares quota base plus eligible firm PO quantities and earlier new lots in this run, divided by quota share. Source validity uses the requirement date minus inspection days. Each proposal retains the supplier code, source-list version and calculation evidence. V9 quota history counts current quantities on released, acknowledged and change-requested POs linked to the same source-list version. Approved amendments change those quantities; cancelled orders do not count, and receipts are not added again. The QUOTA_PINNED_FIRM_PO_HISTORY label identifies this scope. Unlinked/manual orders, requisitions, scheduling agreements and cross-version carry-over are excluded. Missing procurement permission, hidden commitments or inconsistent unit/lineage evidence block quota planning. Configured but missing, expired, ambiguous or unavailable approved sources block the affected proposal; materials with no source-list history retain manual RFQ supplier selection. Retained V9 runs freeze supplier decisions and exact quota-history evidence for replay; older snapshots stay readable. A firmed sourced proposal requires its supplier among RFQ invitees, and current source evidence, quota-history fingerprint and supplier qualification are checked again before issue.

V12 excludes a protected TRANSFER proposal after its exact converted request is fully received and the immutable receipt events and matching custody ledger pairs prove the complete quantity. Review the fulfilled-anchor section for the request, transfer, receipts and original run/proposal. The original FIRM event and historical runs stay unchanged; no automatic UNFIRM or inventory posting occurs in preview. Current stock supplies the timeline, and moving that stock away can expose a new shortage. Invalid/hidden execution evidence blocks the calculation. Planned, in-transit, partially received and cancelled requests keep existing behavior; partial transfer and BUY/MAKE execution reconciliation remain open.

V11 can select a unique policy or the lowest explicitly approved MRP priority among internal replenishment policies for the exact material, destination site, ownership pool and shared stock. The policy must cover planned release through need; source and destination must be different sites in your scope, with suitable classifications and storage clearance. Multiple effective lanes require distinct priorities from 1 to 999 on every alternative; ties, mixed missing priorities or hidden/unsuitable alternatives block selection. Priorities are captured at draft creation and cannot be edited; retire and independently approve a replacement. Ranking is at destination-site level across existing lanes; one-active-policy-per-target controls remain. Area/project sourcing is not inferred. Review retained endpoint codes, policy identity and the ordered candidate list. Conversion rechecks the complete source-set fingerprint, including lower-ranked changes. The policy supplies only the lane: MRP quantity/lead-time settings remain authoritative, and stock is checked at conversion and dispatch. No policy preserves manual source selection; configured unavailable policy blocks new proposals. Conversion rechecks frozen source evidence even on carried proposals, and exact pinned endpoints cannot be overridden. Retirement blocks new conversion but does not rewrite retained runs or cancel an already created request.

Review quantity, need/release dates, source coverage, policy/MBOM witnesses and exceptions. V5 links each dated requirement to existing or proposed supply; component allocations identify their parent proposal and MBOM line. Proposal links are capped at uncovered demand, while MOQ/pack surplus can cover later demand. Maximum lots split. Late existing supply requires rescheduling rather than duplicate procurement. Revisions, owners and projects stay separate. V2 includes scoped shared safety-stock and min/max buffers. Approved master-schedule buckets can hand off to MAKE planning only with one exact released MBOM; dependent requirements then enter multi-level netting. Statistical forecast integration and capacity feasibility remain open; automatic production-version selection is available through AUTO_UNIQUE when exactly one released version resolves. A currently firmed, freshly revalidated shared-stock TRANSFER proposal can create an exact planned transfer request and enter the normal dispatch/independent-receipt custody workflow. Project/tracked-stock transfer conversion and committed peg protection remain open. A retained run is advisory; only a currently firmed and freshly revalidated BUY, MAKE or eligible TRANSFER proposal can enter its separately governed RFQ, planned assembly-order or transfer-request workflow.

Enable a buffer on an independently approved policy with one approved item revision, ownership pool, reorder point, target and maximum stock. Safety <= reorder <= target <= maximum is required. Demand mode restores safety stock; min/max and combined modes replenish to target at or below reorder. An area must explicitly override its buffer rather than multiplying a site target. Buffer targets are non-consuming checkpoints after normal daily demand, including policy changes and unused-stock expiry. Only new make buffer supply explodes component demand. Missing operational source permissions, unresolved records, unavailable revision authority, project-only scope or active overlapping legacy replenishment rules block buffer recommendations. Min/max-only does not plan project or other-revision demand; use a suitable demand/combined policy.

Read position before the buffer, target, uncovered quantity before proposals, exact policy versions and proposal IDs. Late existing/planned supply requires rescheduling, not another procurement order. MOQ/pack inflation that exceeds maximum stock is rejected; existing overstock is reported. V1 retained snapshots stay unchanged and are labelled as historical calculations without integrated buffers. A new V2 run captures effective policy windows and buffer authority for independent replay. Recommendations still create no execution.

Enter a planning run name (3–160 characters) and rationale (10–2000 characters), then Calculate and retain run. This performs a fresh calculation and atomically saves immutable input timelines, selected verified structures, resolved policy definitions, results and evidence fingerprint. It requires replenishment:write as well as normal preview/source permissions. Retrying an unchanged request returns the same run. Retaining a run creates no orders, reservations or stock movements.

Choose earlier/later runs from the 50 most recent accessible records for the selected site. Opening shows the historical result, timestamp and classification without recalculating. Comparison requires the same root item, site, area, ownership and project scope; dates may differ. Quantities stay separate by revision, project, ownership, method and need/release dates, with added/removed exceptions. Changed material base units block comparison. Access requires the creator clearance, all captured site scopes and captured source read permissions; this conservative envelope may restrict a site-only viewer from an administrator-created run.

Select an item/site and exact eligible source: customer demand, requisition line, assembly requirement, PO line or in-transit transfer line. Create an immutable planning-metadata version with ownership, optional approved area, classification and rationale. Transfers require an arrival date no earlier than dispatch and destination membership in any selected area. Existing source ownership/project are retained; external-owner demand requires exact source/ownership contract agreement.

Submit with a specific review note, then a different authorised user approves or rejects. Source permissions, current evidence and reference scope are rechecked. A new approved version atomically supersedes the prior version; older drafts cannot be restored after a later version was approved, even if that later version was retired. Changed or closed source evidence prevents activation and excludes stale metadata from the timeline. Create a fresh version instead.

Choose item, site, active ownership pool, optional area/project and a start/through date spanning at most 365 days. This current-snapshot projection shows authorized stock, direct customer demand, requisitions, assembly requirements/outputs, PO schedules and undated transfers when your existing source permissions allow them. It does not reconstruct historical stock or promise delivery.

Linked reserved/issued kits reduce requisition demand once; reserved/consumed assembly quantities reduce component requirements once; a linked build dates the canonical assembly output without adding supply. Submitted base-unit receipts reduce the current approved PO schedule earliest-date first. Authority, ASN and advisory proposals are not additional supply. Customer/requisition ownership and transfer arrival dates remain unresolved unless current independently approved planning assignments bind them. Unapproved or stale metadata cannot enter a position.

Positions stay separate by exact revision, ownership pool and project. Shared stock does not automatically cover a project. Held, closed-container, expired, unready instance, calibration and controlled-tooling stock is excluded. FEFO allocation expires only unused quantity. A later receipt retains the shortage recorded at need and reports later coverage. Area views flag site demand/PO supply without a current approved area assignment. Source coverage, exceptions and the fingerprint define the limits of this read-only calculation. Multi-level MRP and the approved master-schedule-to-dependent-MRP handoff are available; firmed BUY, MAKE and eligible shared-stock TRANSFER proposals have controlled conversion paths. Statistical forecast integration, dedicated MPS firming/time fences, project/tracked-stock transfer conversion and committed pegging remain open.

In Independent demand and master production schedule, choose Master-schedule item and create dated base-unit quantities. Submit and obtain a different user's approval. These fixed buckets do not consume customer demand. The MRP preview hands shortages to MAKE planning only when an exact released MBOM is selected; new component requirements are then netted normally. No production order is created. Dedicated MPS profiles, SAP firming/time fences, and automated production-version selection remain open.

In Material and planning policies, create a complete immutable item/site version: responsible planner, combined/demand/min-max method, buy/make/transfer methods, safety stock, order bands, pack multiple, procurement/production/inspection lead days, horizon and freeze days. Submit for a different user's approval. The advisory MRP preview consumes approved definitions; it creates no execution documents.

Create an area from assigned non-quarantine locations at one site. Approved areas cannot share a location. An item/area version overrides only checked settings; unchecked fields inherit approved site defaults. Zero and a blank maximum-order limit are explicit overrides when checked. Approved defaults must cover the entire override period. Retire dependent overrides before retiring defaults or an area.

Select exact item, location, ownership, optional project and as-of date. Read resolved values, site/area source provenance, missing-policy exceptions and differences against the effective existing replenishment rule. Compared fields include sourcing method, procurement lead days, minimum/maximum order and pack multiple. Preview changes no operational rule and does not equate safety stock with reorder or target stock.

Available unrestricted stock at the target location + same-site quarantine + transfers currently inbound to that target. Reserved, blocked, MRB, allocated, subcontractor and repair quantities are reported separately and are not silently treated as usable.

Every calculation is restricted to one ownership pool. Optional project-reserved demand is displayed separately because physical stock is not relabelled as project property merely by a proposal.

Either an ACTIVE/APPROVED vendor-list record or a controlled internal source location in the planner's assigned sites. An accepted vendor proposal still requires current screening and an approved receipt authority.

Target need is raised to at least the minimum order, rounded up to the pack multiple and capped by maximum order and maximum-stock headroom.

An EOL or obsolete item cannot have its proposal accepted unless a separate same-project last-time-buy request has already been independently approved for at least the suggested quantity.

Records that a different authorised person accepts the calculation as planning evidence. It creates no purchase order, receipt authority, transfer, reservation, ASN, receipt or stock-ledger row.