Cycle code

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.

AI in everyday work: Person starts with their own task instead of the learning pile

AI in everyday work: Here's how to find the right start

Anyone who wants to use AI in their daily work is familiar with this: You read an article about prompts. A new model appears in it ...

AI assistant meets SAP Business One: Two paths out of the Versino AI shop

AI assistants like Claude or Copilot write emails, compile documents, and explain technical terms. But when you ask them about the open-source code...

Sprint and Swirl: How an AI agent divides work and learns from trials

This series deals with artificial intelligence in conjunction with SAP Business One. It takes a close look at fundamental AI principles...

LATS: Considering several paths simultaneously with AI — and the availability check in SAP B1

This series focuses on artificial intelligence in conjunction with SAP Business One. Not as a collection of product announcements, but as...

ReAct and RLEF: How Artificial Intelligence Learns from Real Mistakes — and What Automated Bank Reconciliation in SAP Business One Has to Do with It

This is the fourth instalment in a series on this blog dealing with AI fundamentals in conjunction with SAP Business One...

SAP B1 10.0 FP2608: Service Layer AI as a transactional layer

The SAP Business One Service Layer has previously served predominantly as a passive data provider: applications requested data via OData, each ...