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
26568 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Understanding: How many hours remain in total and at each operation?

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

FirstLast

Tips: LN | Baan

Categories