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: 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.

Backward scheduling is supported in all shop order release programs (SFC500, SFC550, and FAS510). Backward scheduling is recalculated if a shop order is maintained through SFC500 when the due date or the required quantity is changed; however, you cannot enter move and queue times through the maintenance program when adding an operation to the shop order.

Previous Article Infor LX & BPCS Tip: What is IDF and how could it make my life easier?
Next Article Infor LN & Baan Manufacturing Tip: All About Routings
Print
19413 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

Enterprise General Ledger (EGL) provides audit attributes to track journal entry changes and approvals.

To implement this enhancement, you can request and apply MR 81026.

This enhancement provides audit attributes for the last maintained user, date, time, and approval user, and date, and time on the Financial Journal Entry and Financial Journal Entry Lines. This audit function provides visibility to who and when the journal was last maintained and to who and when the journal was approved.

The programs or areas impacted include:

  • Financial Event
  • Financial Journal Entry
  • Financial Journal Entry Line
  • Financial Journal Entry Detail Line
  • Post Multiple Events

Did you know CLD provides you with the following benefits?

â–ª You can journalize and post-transaction data from any third-party application or Infor LX subsystem to the Configurable Ledger (CLD).

â–ª You can generate multiple journal entries across different charts of accounts, ledgers, and books within the CLD from one transaction line.

â–ª You can automatically post transaction amounts across different books using an appropriate exchange rate between the batch transaction currency and target book currency.

â–ª You can use validation reports to identify validation errors within the files that contain batch transaction data and then you can make any necessary corrections before resubmission.

â–ª You can use standard CEA grouping and summarization options for journals created during Batch Transaction Processing.

â–ª You can interface GLD journal entries into CEA for the BPCD version of Infor LX. This allows data to be interfaced into CEA without changing the way data is processed through Infor LX subsystems.

First2223242527293031Last

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