Cycle code

E-invoicing in Germany: How to implement the obligation with SAP Business One

Of the Cycle code In SAP Business One, a shortcut for a predefined order interval is disposition (MRP). It determines the temporal rhythm at which an item should be reordered or produced – for instance, daily, weekly, fortnightly, monthly, or quarterly – and bundles several individual demands into a common procurement or manufacturing process.

Context

Cycle codes are created in the definition (table OCYC, Field Order Interval) and in the article master data on the tab planning in the field Order intervals (OITM.OrdrIntrvl) is referenced. During an MRP run, SAP Business One takes the stored cycle code into account along with other planning parameters such as Order multiples (OrdrMulti), Minimum order quantity (Minimum Order Quantity) and tolerance days (Tolerance DayInstead of creating a separate order proposal for each open requirement, the system consolidates all requirements within a cycle and proposes exactly one order or production order. This reduces setup, ordering, and shipping costs and smooths procurement peaks. The cycle code also affects the recommended delivery date calendar: new requirements within the same cycle will land on the same proposal as long as the lead time remains sufficient.

Demarcation

The cycle code is not a procurement type; it does not determine whether an item is manufactured or the way it is purchased. Procurement method Buy/Make. He is also not identical to Replacement days or Waiting roomsThese determine the lead time, not the rhythm. The cycle code must also be distinguished from Recurring Order Transactions, which automatically generate regular sales or order documents for recurring contracts — they live alongside the MRP logic and use their own scheduler with Next Execution Date.