Replenishment policies and proposals
Govern immutable forecast and master-schedule buckets, consume them against eligible firm demand, and review advisory MRP/replenishment proposals without creating procurement or inventory transactions.
Screen orientation
Reading requires replenishment:read; drafting/submission, due reviews and decisions require replenishment:write, replenishment:run and replenishment:approve respectively. Site scope and clearance apply. Policy decisions exclude the author and submitter; proposal decisions exclude the policy author and proposal generator.
A no-autonomous-procurement notice precedes the Material and planning policies panel, min/max draft form, policy register and advisory proposal queue. The planning panel contains register, area creation, policy-version creation and mapping preview views. Due review runs from the header; accepted proposals link to a separate authority workflow.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Assignment site / item / planning source type / source record | Selects | An assigned site, approved item and exact eligible source are required. Existing source read permission applies. | Choose customer demand, requisition, assembly requirement, PO line or in-transit transfer. The source revision, project and existing ownership are pinned by the server; they cannot be supplied or changed by the caller. | Selects typed immutable source evidence for a planning-metadata version. |
| Assigned ownership pool / assigned planning area / planned transfer arrival | Selects and conditional date | Active ownership required; approved same-site area optional; arrival required only for transfers. | Existing source ownership cannot change. Externally owned unassigned demand requires a matching source contract. Transfer arrival cannot precede dispatch, and a selected area must contain the actual destination. | Governs planning scope and arrival evidence without relabelling stock or changing demand/procurement/transfer execution. |
| Assignment classification / rationale / review note | Select and text | Classification covers source/pool/area within clearance; rationale 10–2000 characters; review note at least three. | Explain planning scope and timing. A different user must decide, including for administrator-authored drafts. Supersession retains prior evidence; retirement does not cancel the source. | Retains attributable independent planning authority and source freshness. |
| Timeline item / site / planning area / ownership pool / project | Scope filters | Item, assigned site and active pool required. Area/project optional; source-specific read permissions still apply. | Use an entire-site view for dated site demand. Area views exclude site demand or PO supply without an area assignment. Revisions, owners and projects are never pooled automatically. | Scopes authorized current stock and explicit demand/supply records. |
| Timeline start date / through date | Dates | Required; through must be on/after start and no more than 365 days later. | Dates define a projection horizon over current balances, not a historical reconstruction. Outstanding overdue demand carries to the start; overdue supply needs a new authoritative date. | Bounds dated source rows and availability calculations. |
| Planning role / dated master-schedule quantities | Select and CSV | Master-schedule items use additive, fixed quantities and the existing independent approval lifecycle. | Create a separate master-schedule version for the exact item revision, site, owner, project and optional planning area. Customer demand does not consume these buckets. Submit for independent review. | Approved master-schedule requirements can enter MAKE planning only with an exact released MBOM; component requirements then use multi-level netting. |
| Projected position / short at need / covered later | Read-only timeline | Calculated only for eligible dated records with a revision and ownership pin. | Later supply preserves the original shortage. Review exclusions and source evidence. Submitted receipts reduce PO schedules; kit reservations and consumption must not be deducted twice. | Explains date-sensitive shortages without reserving stock or creating execution. |
| Planning site / Planning item / Policy scope | Selects | Site and approved active item required; scope is site defaults or an approved area override. | Keep common Item identity. Create complete site defaults before area overrides; locations in an area must belong to one assigned site and cannot be quarantine or overlap an approved area. | Defines a versioned operational planning scope without changing existing replenishment. |
| Responsible planner / Planning method / Permitted procurement methods | Selects and checkboxes | Complete for site defaults; explicitly checked override fields for areas. | Choose an active site-assigned planner, demand/min-max/combined planning and buy/make/transfer methods. These are future planning assumptions, not executable sourcing authority. | Retains planner and method settings with inheritance provenance. |
| Safety stock / Order bands / Lead days / Planning horizon / Freeze days | Decimals and whole days | Nonnegative safety stock and lead/freeze days; positive order minimum, pack and horizon. Maximum order is optional. | Freeze cannot exceed horizon; any maximum order must fit minimum rounded to pack. Area overrides inherit unchecked fields and retain explicit zero or no-limit values. | Stores immutable validated site defaults and partial area overrides. |
| Planning review note | Text | At least three characters for submit, decision or retire. | Enter a specific reason. Authors and submitters cannot approve or reject their own definitions, including administrators. | Retains attributable review evidence. |
| Integrated shared-stock buffer | Approved revision / ownership / reorder / target / maximum | Optional governed whole-object setting; safety <= reorder <= target <= maximum. Null explicitly disables it. | Pin one approved revision and pool. Area planning requires its own explicit buffer override. Demand mode protects safety; combined/min-max restore target at reorder. Retire conflicting legacy rules and resolve missing operational authority first. | Non-consuming dated target probes; new supply uses lot limits and only new make proposals explode components. V1 retained evidence is unchanged; V2 captures buffer checks and replay authority. |
| MRP root / site / area / ownership / project / dates / released MBOMs | Preview scope and exact released structure selections | Same bounded date and authorized scope as the timeline; up to 50 selected MBOM versions. | Select root and all make-component MBOMs. Only one exact effective structure and one approved procurement method can plan a shortage. Master-schedule requirements require MAKE and one exact effective released MBOM. Review omitted sources, optional-line exclusions, late supply, past/frozen releases and source-selection gaps. | Read-only V6 multi-level proposals with explicit requirement-to-supply allocations. Component links retain parent proposal and MBOM line; proposal allocations do not exceed uncovered demand. Active firmed proposals carry forward as fixed nettable supply with their original MAKE component requirements until an audited UNFIRM decision. Statistical forecasting, complete SAP firming behavior, capacity and execution conversion remain open. |
| MRP source priority | Optional integer 1–999 | Shared cross-site internal replenishment policies only; 1 is highest. | Enter at draft creation and obtain independent approval. Every effective alternative needs a distinct priority for ranking. Retire and approve a replacement to change it; priority is database-immutable. | V11 selects the lowest priority and retains all reviewed candidates. It does not rank by stock, cost or capacity and does not permit duplicate min/max policies for one target. |
| Fulfilled transfer anchors | Read-only V12 completion witnesses | Shown for a fully received exact converted request with verified custody history. | Review the original firming anchor, request/transfer numbers, receipt quantities and proof fingerprint retained with the run. A received status alone is insufficient; exact revision/owner/endpoints, independent receipt and both ledger entries must match. | The original fixed proposal is excluded while current inventory is planned normally. FIRM history is preserved and preview posts nothing. Partial transfers and BUY/MAKE reconciliation remain open; hidden or inconsistent proof blocks planning. |
| TRANSFER source policy / endpoints | Read-only proposal lineage | Shown when a unique or explicitly prioritized approved lane covers the release-to-need window. | Review the policy number and source/destination site and location codes. Configured but expired, retired, hidden or ambiguous sources block new proposals; no policy preserves manual sourcing. V11 freezes source evidence, priorities and the complete ordered candidate witness for replay and carry-forward. | Request conversion uses the exact pinned endpoints and rejects changed source authority. MRP quantities and lead times remain separate; stock is checked at conversion and dispatch. Priority selection rechecks all alternatives at conversion; changed lower-ranked authority also invalidates the old decision. Transfer quotas/cost/capacity ranking, area/project lanes and upstream plant planning remain open. |
| BUY supplier / source-list evidence | Read-only proposal lineage | Shown when an approved effective source list selects a supplier. | Review supplier code, source-list version, validity date, priority or quota method, quota base and prior allocation in this run. Source validity is checked at need minus inspection days. V9 includes current firm PO quantities pinned to this source-list version; approved amendments change them, cancellation removes them and receipts do not count again. Manual/unlinked orders and other purchasing document types remain excluded. Missing permissions, hidden or inconsistent evidence block quota planning. | Retained V9 runs freeze choices and authorized quota-history rows for replay. Configured unavailable lists block proposals; unconfigured materials keep manual RFQ sourcing. The selected supplier must be invited and current evidence revalidated at draft/issue. |
| Planning run name / rationale | Text | Name 3–160 characters; rationale 10–2000. | Describe the planning purpose and the reviewed input scope. Calculate and retain performs a new calculation, rather than saving a client-supplied result. | Creates an immutable advisory record and audit entry. |
| Earlier planning run / Later planning run | Recent accessible run selectors | At most 50 recent runs, filtered by selected site and recorded access envelope. | Choose comparable scope and inspect historical timestamps. Different horizons are disclosed; changed units cannot be compared. | Opens original results or compares base quantities and exceptions without creating execution. |
| Mapping item / target / ownership / project / as-of date | Preview filters | Item, location, ownership and date required; project optional. | Inspect the resolved settings, field sources, missing defaults and legacy differences. No source or policy is migrated by the preview. | Shows dated mapping witnesses while existing replenishment remains authoritative. |
| Policy name | Text | Required; 3–160 characters. | Name the item/location buffer and planning intent clearly. | Identifies the immutable policy snapshot. |
| Item | Select | Required; approved and active catalogue item. | Select the governed part to review, not a free-text substitute. | Pins the item for planning calculations. |
| Target location | Select | Required; assigned non-quarantine location. | Choose the controlled destination whose stock level needs review. | Defines the target stock scope. |
| Ownership pool | Select | Required; active pool. | Keep owned and customer/government material in their correct custody pool. | Separates stock calculations by ownership. |
| Project reference | Text | Optional; at least two characters if supplied. | Record the project context when a project-specific policy is needed. | Adds project scope and separate project-reserved context. |
| Approved source type | Select | Required; Approved vendor or Internal location. | Choose one source type; switching it clears the previous source selection. | Determines the required source field and recommended downstream workflow. |
| Approved vendor / Internal source | Conditional select | Exactly one source required. | Use an active approved vendor, or an assigned non-quarantine internal location different from the target. | Pins the proposed source without authorising a purchase or transfer. |
| MAKE output location / released MBOM work center | Select and text | Required only when converting a currently firmed MAKE proposal. | Choose an in-scope non-quarantine location at the planning site and a work center present in the selected released MBOM. The API rechecks current firming, MRP evidence, BOM effectivity and classifications. | Creates one planned assembly work order with exact proposal quantity and run/proposal lineage. It does not reserve, consume or post stock. |
| Classification | Select | Required; within your clearance and no lower than the governed item, locations, ownership and source. | Choose the highest classification required by the policy context. | Controls visibility of the planning record. |
| Reorder point / Target stock / Maximum stock | Decimals | Required; reorder may be zero, target and maximum must be positive. | Keep reorder ≤ target ≤ maximum. Maximum-stock headroom at reorder must fit the minimum order rounded to its pack multiple. | Sets the trigger, desired position and upper stock limit. |
| Minimum order / Maximum order / Pack multiple | Decimals | Positive minimum and pack multiple required; maximum optional. | Keep any maximum at least the minimum and pack multiple. Use quantities supported by the selected source. | Constrains suggested order size and pack rounding. |
| Review cadence (days) / Lead time (days) | Whole numbers | Required; cadence 1–3650, lead time 0–3650. | Record the review interval and lead-time assumption separately. | Schedules reviews and retains planning assumptions. |
| Effective from / Effective to | Dates | Start required; end optional and not before start. | Choose the governed policy period. An already ended period cannot be approved. | Bounds policy eligibility. |
| Planning rationale | Long text | Required; 10–2000 characters. | Explain thresholds, readiness need and source assumptions. | Retains the basis for independent review. |
| Projected position / Suggested quantity / DMSMS gate | Read-only proposal | Calculated by a due review. | Read the state-by-state quantities and calculation version. LTB_REQUIRED blocks advisory acceptance until the independent last-time-buy requirement is satisfied. | Explains the recommendation without converting held or external stock into availability. |
Actions and effects
When to use: Existing replenishment write/approve permissions plus source read, assigned sites and sufficient clearance.
What it does: Creates and reviews immutable metadata with current-source fingerprint checks. Approval atomically replaces older authority; stale sources and older-draft reactivation are denied. No stock, procurement commitment or transfer action is created.
When to use: With replenishment:read and stock:read; selecting released MBOMs also requires manufacturing:read.
What it does: Calculates advisory buy/make/transfer proposals from approved dated single-method policies and exact verified released MBOMs in one read-only snapshot. Shows lot sizing, lead offsets, shared-component netting, demand coverage and authority witnesses. Ambiguous methods, missing effective structures and MBOM/policy sourcing conflicts block recommendations. No retained run or execution is created.
When to use: With replenishment:write plus normal preview and selected-source read permissions; name 3–160 and rationale 10–2000 characters.
What it does: Calculates fresh inputs and saves immutable timelines, verified structures, policy definitions, results and audit evidence atomically. Idempotent retries reuse the original run; the same key cannot change inputs. No execution is created.
When to use: With replenishment:write, manufacturing:read and assembly:plan; the caller must retain an accessible run, active firming, released MBOM and eligible output location.
What it does: Recalculates and revalidates the source before creating one planned assembly order. Exact quantity, released BOM component lines and retained run/proposal identity are preserved. Retries are idempotent; another order from the same proposal is blocked. No stock reservation, consumption, receipt or ledger post occurs.
When to use: Current access must cover the run's captured source permissions, all site scopes and creator clearance.
What it does: Open a historical immutable snapshot from the 50 recent accessible runs. Compare only the same item/site/area/ownership/project scope, with revision, schedule and method kept separate. Base-unit changes reject comparison. Review quantity deltas and added/removed exceptions; nothing converts to execution.
When to use: With replenishment:read and stock:read; individual source read permissions control adapters.
What it does: Computes a repeatable-read projection, source coverage and SHA-256 witness. Missing ownership, dates, revisions or conversions are explicit exclusions. No source, audit, outbox or execution record is written.
When to use: With replenishment:write and valid scope, classifications and rationale.
What it does: Creates an immutable draft. Submit for an independent decision; approved policy periods cannot overlap within the same scope.
When to use: With replenishment:approve and a review note; decisions exclude author and submitter.
What it does: Retains history. Retire dependent overrides before defaults or area retirement. Replacements require new independent approval.
When to use: With replenishment:read and an exact dated scope.
What it does: Shows inherited values and comparison of source method, lead days, order limits and pack multiple against the legacy rule. Creates no planning run or transaction.
When to use: By an eligible planner with complete, non-duplicate policy scope.
What it does: Creates an immutable draft, then submits it for independent approval; neither action moves stock.
When to use: For a pending policy, by a user independent of author and submitter.
What it does: Activates the approved policy or records rejection. The screen supplies standard decision notes rather than a free-text decision form.
When to use: For an active policy after confirmation.
What it does: Stops future use while retaining proposals and audit evidence; changed assumptions require a new policy.
When to use: With run authority when active policies are due.
What it does: Snapshots planning quantities and creates advisory proposals where the calculation requires replenishment.
When to use: For a pending proposal, by an independent reviewer; acceptance requires the DMSMS/LTB gate and source checks to pass.
What it does: Records review of the recommendation only; creates no PO, receipt authority, transfer or ledger movement.
When to use: For an accepted proposal.
What it does: Navigates to receipt authorities or transfers; a separately authorised transaction must still be created there.
Lists and states
- Policy register: number, status, classification, item, target, pool/project, source, thresholds, order band, pack multiple, next review and creator/decider explain the active planning assumptions.
- Advisory proposal queue: available target, quarantine, inbound transfer, reserved, blocked/MRB, allocated, subcontractor, repair, project-reserved and source quantities remain separate from projected position and suggested quantity.
Authority boundary
Replenishment is advisory only. Even an accepted proposal creates no PO, receipt authority, transfer or ledger movement; source screening, DMSMS/LTB and custody approvals remain separate authorities.