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

Baan/LN Tip of the Week: Aborted Finalization Run

Kathy Barthelt 0 85784 Article rating: No rating
When a finalization run is aborted and in the batches selected for this finalization run are transaction types having the update mode finalization, you must use the Restart Finalization Run session. This session can be found in the Transaction Processing menu of the General Ledger Module of the Finance Package.

BPCS/LX Tip of the Week: SFC600

Anthony Etzel 0 87867 Article rating: No rating
In addition to SFC650, this ERPLX program is also used to capture and post shop floor information.

The key difference between the two is that SFC600 only captures Labor (run time) reporting, machine time, downtime and indirect time.

If you use SFC600, then all shop order material receipts and issues would be captured using INV500.

Both Inventory and Shop Floor Transaction entry is keyboard dependent, unless you incorporate an automated method like an MES solution to capture the data.

BPCS/LX Tip of the Week: Downtime Reasons

Anthony Etzel 0 85494 Article rating: No rating

Using SFC600 to enter downtime.

You are tracking downtime and using SFC600 to enter the downtime, but you don’t know where to go to setup downtime reasons. You can set up the downtime reason codes in the INV application by selecting the reason code maintenance program INV140D1.

Once you are in the reason code maintenance program, position to the transaction effect code “D”. Using the transaction effect code “D” you can now setup as many downtime reason codes as needed. The reason code field is alpha numeric, so be creative with your reason code assignments.

Baan/LN Tip of the Week: Restricted User Access

Kathy Barthelt 0 83542 Article rating: No rating
Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

BPCS/LX Tip of the Week: Work Center - Cells

Anthony Etzel 0 67137 Article rating: No rating
The LMP module (Lean Manufacturing Process) uses work centers but refers to them as production cells.

A cell is one or more work centers that produces an end item. So when a company decides to adopt the lean manufacturing philosophy, the concept of work centers takes on a new meaning.

In lean terms, the work center, or group of work centers, becomes a production cell. In other words, a mini-factory producing end items with similar characteristics.

Baan/LN Tip of the Week: Closed, Final Closed, Provisional Close – What’s The Difference?

Kathy Barthelt 0 88261 Article rating: No rating

Fiscal, Reporting and Tax Periods can have status Open, Closed or Final Closed. If a period is Closed or Final Closed, you cannot post entries to those periods. If a period is Closed, you can re-set it to Open and post entries. If a period is Final Closed, you cannot post and you cannot set it back to Closed or Open.

A Provisional Close is run at year-end to bring the balances forward for the new year without having to close the previous year. A Provisional Close can be run as many times as you like. After a Final Close, a Provisional Close cannot be run.

The Provisional Close allows you to continue into the new year with all financial reporting and not have to rush with the Final Close until all adjusting entries are made and any final signoffs have been completed.

Baan/LN Tip of the Week: Product Families

Kathy Barthelt 0 83564 Article rating: No rating

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

BPCS/LX Tip of the Week: Create the Master Schedule

Anthony Etzel 0 85949 Article rating: No rating

In the master schedule creation, you have the flexibility to enter a planning start date, or default to the facility planning start date. Infor LX uses the planning date to plan both orders with forecasts and customer orders as demand.You can create your master schedule from the Master Production Scheduling module (MPS).

First132133134135136138140141

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 2

Understanding: How many hours remain in total and at each operation?

Now let’s look at what information is being supplied from the shop floor.

It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.

The big question is, is anything done with the data? Is it collected and keyed to a  spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.

Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:

  • The type of hours being reported – machine, run labor, setup labor
  • If reporting setup and run labor you want an employee clock number
  • The shop order and the operation that is being reported
  • Is the operation complete
  • How many good were produced at this operation
  • How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.

Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.

Previous Article BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 1
Next Article BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 3
Print
67789 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Why this matters

Many integration challenges come from systems that don’t communicate effectively. Data is often duplicated, delayed, or manually transferred between applications, creating inefficiencies and limiting visibility.

What this solves

Infor ION provides a structured way to connect applications and enable consistent data flow across your environment, helping reduce manual processes and improve how information is shared.


How it works

Infor ION acts as a central integration layer, allowing systems to communicate using standardized messages.

In Infor LN, ION is natively integrated, enabling streamlined data exchange across applications.
In Infor LX environments, ION can be used as part of an integration strategy to connect ERP with external systems and platforms.

This enables:

Categories