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

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

  • Release date & due date
  • How many hours remain in total and at each operation
  • The quantity required, what was finished and the remaining quantity
  • What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

In Infor LX, there are two ways to enter indirect labor. You can use either SFC600 or SFC650.
 

  1. If you use SFC600 and enter a reason code for the indirect labor, the reason you entered is written to the Labor Ticket file.
  2. If you use SFC650 and enter a reason code for the indirect, the reason code is not written to the labor Ticket file.

 

In either case, the reason code is not validated from the transaction file because there is no indirect transaction code. The indirect code that can be setup is machine downtime. If you need to validate and track indirect by reason and validate the reason code, then you may want to explore an MES solution that works with Infor LX.

 

First140141142143145147148149Last

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:

12345678910Last

Theme picker

Categories