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 of the Week: Backward Scheduling

Operations are automatically backward scheduled at shop order release time. The backward scheduling algorithm starts with the shop order due date and schedules each operation based upon the standard move and queue times in the routings and the number of days the job is expected to run at standard. The system calculates and stores the operation scheduled start date. The dates may be modified by the shop order maintenance program. The number of days that a job is expected to run an operation is dependent upon the available capacity for that work center and the total hours scheduled for that operation.

The backward scheduling algorithm also considers the shop calendar for weekends, shutdowns, holidays, and partial days.

Backward Scheduling Process

The algorithm starts with the due date of the shop order or planned order. The system makes the following calculations for each operation in the reverse sequence:

  1. The number of move days is subtracted from the due date (or initial date of the previous operation) to get the due date for this operation. The move days are only used on valid shop calendar days.
  2. The system uses the following calculation for the number of clock hours for the operation: Standard run or machine hrs/No. of operators + setup hours
  3. The number of clock hours is spread over the available daily capacity of the work center for those given days. The system uses the following calculation for the daily capacity of the work center: Number of shifts x hours per shift x average efficiency/100
  4. Each day is checked against the shop calendar; the calculation bypasses inactive days or adjusts for any changes in the work center capacity for that day.
  5. Queue time days are subtracted in the same manner as move time days. The resulting date is the operation start date.

The algorithm then goes to the previous operation. When all operations have been included, the resulting date is the scheduled start date of the shop order. Note that MRP uses the item lead time to determine material requirement dates on planned orders.

Previous Article It's almost the end of the 1st Quarter of 2021 -  How are you doing on your 2021 goals?
Next Article Infor LX & BPCS Tip of the Week: Credit Card Processing Within LX
Print
20197 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.

12345678910Last

Theme picker

Tips: LN | Baan

Baan/LN Tip: New Mapping Scheme

After a new mapping scheme is copied from an existing one, it is possible to check transactions in a simulation mode, before activating the new scheme. However, before the simulation can take place, the new mapping scheme needs to have completed the “Check Mapping Scheme” step. When the check is completed, a transaction can be simulated by highlighting it and from the Specific menu, selecting “Map with Specific Mapping Scheme.” Any errors can be corrected without having to activate the new mapping scheme.

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

First7374757678808182Last

Theme picker

Categories