Integration with Quality Requirements & Specifications

The Advanced Planning extension is designed to work seamlessly with the Quality Requirements & Specifications (QRS) app, enhancing planning accuracy in shelf-life-sensitive and quality-driven industries.

When both apps are installed, Advanced Planning inherits additional setup options and planning rules that allow the planning engine to evaluate lots based not only on expiration, but also on sell-by constraints and customer-specific minimum shelf-life requirements.

Setup

When the Quality Requirement Specification extension is installed, two fields are introduced on QRS Setup:

• Plan with Sell-By Restrictions (Boolean) - When enabled, planning applies sell-by / shelf-life checks.
• Sell‑By Evaluation Method (Enum) – enabled only if Plan with Sell‑By Restrictions = True.
  • Lot Sell‑By Date
  • QRS Minimum Shelf Life

Business Rules

Planning behavior (Calculate Regenerative Plan)

Sell-by / shelf-life logic is only applied when Plan with Sell‑By Restrictions is enabled. If disabled, planning behaves normally and for Sales demand ignores sell-by restrictions (other eligibility rules may still apply, like blocked).

Sell‑By Evaluation Methods:

Method Lot Sell‑By Date: When selected, planning uses the Sell‑By Date stored on the Lot No. Information card:

• If Sell‑By Date is valid after the demand due date → eligible
• If Sell‑By Date is on or before the demand due date → exclude

Fallback rules:

• If the lot has no Sell‑By Date → use Expiration Date as fallback.
• If sell-by is defined at item level but the lot has no Expiration Date, the lot is excluded for planning purposes (for cases where expiration is required to validate).

Method QRS Minimum Shelf Life: When selected, planning uses the Minimum Shelf Life requirement from QRS Document Lines attached to the demand (Sales Order Line / Production Component).

Special rules:

• If the user manually deletes the QRS Document Line, the system assumes all lots are acceptable for that demand and does not apply sell-by/expiration restrictions for that line (blocked still depends on APL setup).
• If Minimum Shelf Life exists but the lot has no Expiration Date, the lot is excluded.

Demand-type Specific Rules

There are different evaluation depending on demand source:

• Assembly Orders demand: exclude if Lot Expiration Date < Requisition Line Due Date (expiration-based).
• Demand Forecast (not component): fall back to Sell‑By Date evaluation; compare Sell‑By Date with demand due date; if Sell‑By Date ≤ due date → exclude.
• Sales Orders demand: apply method chosen (Sell‑By Date or QRS Minimum Shelf Life) using due date comparison.
• Production Order Components demand: apply method chosen (Sell‑By Date or QRS Minimum Shelf Life) using component due date comparison.

Rolling supply (not yet in inventory)

For future supply, the system also evaluates predicted dates:

• Predicted Expiration Date is computed using Expiration Calculation logic.
• Predicted Sell‑By Date is calculated as: Predicted Expiration Date + Minimum Shelf Life (from Item Card)

Log Planning Information

When QRS integration is present, the Log Planning Information page has the following new fields:

• Sell‑By Date (from Lot No Information)
• QRS Minimum Shelf Life (from QRS Document Lines)

The log is also extended with new message patterns when inspection status causes exclusion:

• “Lot with Sell‑By Date %1” (red)
• “Does not meet customer minimum shelf life (required: %1)” (red)
• “Predicted Sell‑By Date MM/DD/YYYY – supply excluded from planning” (red)