How-toInfor LNCommon Data / Calendars

Calendars in Infor LN: create, assign and how they drive planning

Question
calendar infor ln

Also searched as

  • infor ln create calendar
  • infor ln enterprise unit calendar
  • infor ln work center calendar

Short answer

Infor LN calendars define working and non-working days and available hours. You create a calendar with its day types and exceptions, assign it to enterprise units (such as sites, work centers or warehouses), and planning, scheduling and delivery date calculations use the calendar of the relevant unit.

Applies to: Infor LN 10.x. Session names and codes vary by version.

Create and assign a calendar

  1. 1Create the calendar code in the Common Data calendar sessions and give it a description.
  2. 2Define the standard week pattern: working days, start and end times, and breaks, or shift patterns if used.
  3. 3Add exceptions for public holidays and planned shutdowns, with the date range and whether the day is working or not.
  4. 4Assign the calendar to the enterprise unit, work center or warehouse that should use it.
  5. 5Generate or update the derived calendar data so that the planning engine reads the new dates.
  6. 6Test with a simple order: check the calculated start and delivery dates cross the holiday as expected.

General calendars versus enterprise-unit calendars

A general calendar is a reusable pattern. An enterprise-unit calendar is the calendar actually in force for a site, work center or warehouse. Several units can point at one general calendar, which keeps the holiday list in one place.

Separate calendars are justified where plants have different shifts or national holidays. Over-differentiating makes maintenance painful each year.

What reads the calendar

Production scheduling uses work center calendars for operation start and end. Enterprise Planning uses the site calendar for lead-time offset. Purchase and sales use warehouse or supplier calendars for promised dates. A wrong calendar shows up as dates falling on weekends or planned orders offset by a day.

After changing a calendar, previously planned orders do not shift automatically. Re-run the planning or rescheduling to pick up the change.

Annual maintenance

Extend calendars before the year ends, otherwise date calculation beyond the last defined date can produce errors or defaults. Put it on the January and December admin checklist and keep one owner.

Try it here, free

Infor LN Company and Enterprise Unit Design Worksheet

Open full tool

Plan LN companies, enterprise units, sites and currencies row by row, with user and volume totals, and export to Excel.

Common pitfalls

  • !Calendar defined but not assigned to the unit that uses it.
  • !Forgetting to regenerate derived calendar data after edits.
  • !Calendar horizon running out at year end.
  • !Assuming existing orders reschedule on their own.
  • !Too many similar calendars.

How an ERP-grounded AI assistant handles this

An on-prem assistant can answer 'which calendar does work center X use and why did this order land on a Sunday' by reading calendar and assignment tables. Read-only, inside your network, with your LN roles respected.

Frequently asked questions

Where do I assign a calendar to a work center?

In the work center master data under Manufacturing. The calendar field points to the calendar code that governs availability for scheduling.

Why are dates ignoring my holiday?

The exception may be missing, the derived data may not be regenerated, or the unit may use another calendar. Check the assignment first.

Do calendar changes reschedule existing orders?

No. Re-plan or reschedule open orders to apply new dates.

Can one calendar serve multiple sites?

Yes, if working patterns and holidays are identical. Otherwise create separate calendars.

Related

How-to

Infor LN planning BOM: how it works, setup and use (and what people mean by SIC planning)

A planning BOM is a structure used by Enterprise Planning to plan at family or option level, rather than the production BOM used on shop orders. You maintain planning items and a planning structure with proportions, and the planning engine uses it to explode forecasts into component and capacity requirements. 'SIC planning' is not a term I can pin to a single standard LN feature, so check how your site uses it.

How-to

Infor LN Enterprise Planning Not Generating Planned Orders

When an item has demand but Enterprise Planning creates no planned orders, the cause is almost always planning master data: the item is not set to be planned, the planning horizon or time fences exclude the demand, the order policy or supply source is missing, or the planning run did not include the item. Check them in that order before suspecting the engine.

How-to

How to process inbound and outbound warehousing orders in Infor LN

Infor LN Warehousing splits every physical movement into inbound (goods arriving, mainly from purchase orders) and outbound (goods leaving, mainly for sales orders), each driven by its own warehouse order type. Inbound runs through intake, inspection if required, and put-away; outbound runs through order release, picking, packing and shipment confirmation, with each stage updating the order status other modules watch.

How-to

Infor LN item sales session, item purchase session and site data: where each lives

In Infor LN the item master is split by business function. General data sits in the Items - General table (tcibd001), sales data in Item - Sales (tdisa001) and purchase data in Item - Purchase (tdipu001). Site-dependent data such as ordering and planning parameters is held per item and site, so one item can behave differently in each site.

Error fix

Infor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It

A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.

Error fix

Infor LN Not Authorized to Run This Session: How to Fix It

Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.

AI for ERP

AI for Infor LN: Sessions, BODs, and Engineer-to-Order Work

Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.

AI for ERP

AI for Infor LN Warehousing: Inventory, Inbound and Outbound Exceptions Made Searchable

AI for Infor LN Warehousing: trace inventory discrepancies and inbound or outbound exceptions in plain language. On-prem option, approval on writes.

Stuck on Infor LN?

Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software