Product lifecycle states are the primary configuration tool for defining the phase a product is in (e.g., Draft, Released, Obsolete). They can trigger automated actions, such as changing default order settings and restricting transactions, which aligns perfectly with the requirement to update procurement settings and manage inventory movement upon reaching the ‘obsolete’ state.

Finite capacity scheduling considers the actual booked capacity and remaining available time on resources (like a work cell) when calculating job start and end dates. Enabling it ensures that new production orders are scheduled only when the resource has available time, leading to more accurate delivery promises based on real workload, unlike infinite capacity which ignores existing bookings.

The standard and intended process for cycle or physical counting in Warehouse Management is to enter the physically counted quantity. The system then automatically compares it to the expected (system) quantity and generates a discrepancy. This discrepancy is later reviewed and posted as an adjustment journal by a supervisor or manager, maintaining control and audit trails. Workers should not create manual journals or use movement menus during a count.

A batch reservation hierarchy allows you to define the order and rules by which inventory dimensions are reserved. You can configure it to reserve by Batch number (or in this case, a serial number prefix) before other dimensions. This ensures that when the frame serial number (which dictates the required prefix) is scanned, the system will first try to reserve the wheel set with the matching batch/prefix, enforcing the specific kit requirement.

Cash discounts (like 2%10, Net30) are configured in the Cash discounts setup and are linked to vendors through their posting profile or directly on the vendor record. This setup allows the system to automatically calculate and propose the discount on vendor invoices if payment is made within the specified discount period, which is distinct from line discounts or manual fields.

The Production floor execution interface is a purpose-built, real-time dashboard for shop floor supervisors. It visually displays production orders in a status-based view (e.g., ‘Not started’, ‘Started’, ‘Reported as finished’), often grouped by work cells or resources. It allows quick interaction like starting jobs or reporting feedback, providing the consolidated, actionable overview described, unlike static lists or planning charts.

A reorder point model triggers a replenishment order when the on-hand + ordered inventory falls below a defined point. For an item with variable lead times, using a dynamic safety stock calculation (based on lead time variability and demand) as part of the reorder point helps protect against stockouts during the replenishment lead time. This balances service level needs without simply setting a statically high minimum quantity, which would increase holding costs.

Warehouse slotting is the process of determining the optimal storage location for items based on factors like demand frequency (fast/slow moving), item characteristics (size, weight), and pick/pack efficiency. The slotting feature analyzes historical work (movement) data to provide recommendations on where to store items to minimize travel time and maximize space utilization, directly addressing the described problem.

For finite capacity scheduling, the system requires an active, available resource with capacity to perform the operation. If all primary resources in the assigned resource group are inactive, the system cannot schedule a job for that operation. Activating a resource makes it available for scheduling. Simply re-running scheduling with different parameters or deleting the operation bypasses the underlying resource constraint issue.

Product lifecycle states are the primary configuration tool for defining the phase a product is in (e.g., Draft, Released, Obsolete). They can trigger automated actions, such as changing default order settings and restricting transactions, which aligns perfectly with the requirement to update procurement settings and manage inventory movement upon reaching the ‘obsolete’ state.0