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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

123578910Last

Theme picker

Tips: LN | Baan

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...


TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

123578910Last

Theme picker

Categories