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

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
     

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

First3637383941434445Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories