Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

George Moroses

Infor LX & BPCS Manufacturing Tip: Shop Calendar Maintenance – SFC140D1

Shop calendar maintenance, SFC140D1 This program features multiple-level shop calendar maintenance. You can maintain a shop calendar at the global, facility, or work center level. Global level entries override default values found in Work Center Maintenance, CAP100D1, for any program that uses the shop calendar.

Facility overrides affect all work centers in a Facility and are exceptions to the global level. Exceptions defined at the Facility level apply to all work centers for the facility. Work Center calendar entries are the most specific. These entries apply to a single work center and override any Global or Facility conditions.

If you have deleted a work center in Work Center Maintenance, CAP100D1, you cannot delete its shop calendar. The system treats the work center shop calendar like a global calendar for that year. If you try to delete it, you will delete the global shop calendar for that year.

Range processing provides daily or weekly maintenance of all overrides for a period of up to one year with a single command.

The following explains how Infor LX uses calendars for manufactured and purchased parts planning:

  • Infor LX treats purchased and manufactured parts in the same way.
  • Infor LX does not use the work center calendar.
  • In facility planning, Infor LX uses the facility calendar.
  • If the global calendar has additional days blocked out relative to the facility calendar, MRP/MPS plans consider both the facility and global days-off.


In all cases, the system uses the item master/CIC lead time parameter to determine the release date for the planned order regarding the due date from the forecast or parent demand. The system considers days blocked out in the facility and global calendars when it determines the planned order release date.

Example: Assume the entire system (Global) has a specific date set as a regular workday. If one particular Facility recognizes this day as a holiday, no hours are available on work centers within that facility. If conditions at one work center are an exception to this holiday, that work center can be maintained with its own set of conditions.

Simulation Mode

The Shop Calendar Selection/Maintenance Simulation program, MRP747B, uses the Shop Calendar Maintenance programs, SFC140D, in a simulation mode. The MRP program allows you to maintain shop calendar information to simulate capacity planning and to view the results before you use the data in live capacity planning.

When you run MPS by facility, you cannot maintain global calendars. This safeguard prevents a user from unintentionally overwriting the live global calendar if the user runs Copy to Live, MRP770D.

Access: Menu SFC

Previous Article Infor LX & BPCS Materials Tip: Over-Receipts
Next Article Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)
Print
32277 Rate this article:
5.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Industry Insight: Why ERP Data Stays Siloed, and What to Do About It

Most manufacturers don't have a data problem. They have a connection problem.

Production data lives in one system. Sales and customer data lives in another. Finance runs somewhere else entirely. Each system does its job well on its own, but without a way to connect them, the organization never gets the full picture, and neither do the people trying to run the business.

Why This Happens
ERP systems are often the core of a manufacturer's operations, but they rarely operate alone. Over time, businesses add third-party software for CRM, e-commerce, warehouse management, EDI, and more. Each addition solves an immediate need, but without integration, it also creates another silo.

The result is familiar across manufacturing: teams end up manually re-entering data between systems, waiting on reports that should be immediate, and making decisions without visibility into what's happening elsewhere in the business.

Integration vs. Enhancement
There are two ways to close this gap, and they solve different problems:

  1. ERP Integration connects your ERP to the third-party software you use every day, creating a single source of data instead of several disconnected ones. Whether it's a one-way, two-way, or complex systems integration, the goal is the same: eliminate errors, reduce manual entry, and give everyone access to the same real-time information.
  2. ERP Enhancement goes a step further, creating new functionality or modifying existing functionality within the ERP itself, so the system matches how your business actually operates rather than forcing your business to adapt to the system's limitations. Done right, enhancements use parameter-co

Categories