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
27617 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

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories