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

What does OTTO do that finite scheduling doesn’t?

Anthony Etzel 0 36560 Article rating: 5.0

Finite scheduling identifies what constraints need to be overcome and it provides the best schedule given the constraints. But the objective is not only to overcome or remove the constraint but to prevent the constraint from even occurring. Only people can anticipate and overcome current constraints, and this requires time for analysis and people to apply their knowledge to the data. OTTO removes the non-value-added tasks of extracting and manipulating data and provides visibility to support people in solving near-term, complex problems. 

Crossroads RMC welcomes MBL (USA) Corporation

Anthony Etzel 0 35835 Article rating: 5.0

Crossroads RMC welcomes MBL (USA) Corporation as our newest Data Collection and Warehouse Management client.

MBL (USA) Corporation, with headquarters located in Ottawa, Illinois, manufactures all types of V-Belts, V-Ribbed Belts, Timing Belts, and Variable Speed Belts for both original equipment and service parts in the automotive, recreational, and industrial markets. In addition to supplying North, Central and South America markets, products are exported to countries worldwide. Their corporate parent is Mitsuboshi Belting LTD located in Japan.

MBL (USA) Corporation’s objective was to improve inventory visibility, eliminate paperwork, and use a bar code scanning solution to manage warehouse inventory and eliminate the manual process for inventory warehouse transactions.

Our discovery was able to highlight improvements to streamline the process in the warehouse and improve inventory visibility. Crossroads RMC is a reseller and support partner for TouchPath Warehouse Management which is integrated to MBL (USA) Corporation’s ERP/LX software. TouchPath Warehouse Management provides the insight into your inventory and the warehouse management tools to help you increase customer satisfaction and reduce costs.

We are proud to have MBL (USA) Corporation as our newest client and look forward to being a strategic partner and support their company growth and success.

Infor LX & BPCS Tip of the Week: Inventory Transfers for Outside Operations

Anthony Etzel 0 64743 Article rating: 5.0

This enhancement allows users who currently perform outside operation processing in shop floor programs to manage the transfer of components used in the outside operations to the vendor’s designated warehouse.

This enhancement provides modified and new INV511D screens and adds new logic to allow the user to identify all shop orders that have components linked to outside operations or to identify all the components linked to an outside operation on a shop order. The shop orders can be filtered by either a date range or by a specific vendor.

Inventory Transfers for Outside Operations enhances the management of external operations by providing screens that simplify the selection of the shop orders or items to transfer to a vendor.

Transfers to the vendor warehouse are performed in the Inventory Transfers, INV511D, screens.

Infor LX / BPCS Tip of the Week: Optional Authority to Maintain Reason Codes

Anthony Etzel 0 60957 Article rating: 5.0

This enhancement allows users to update Reason Code Maintenance, INV140D1, for Transaction Effects that they are not authorized to in any other programs. A new system parameter was added to Inventory Parameters, INV820D. The enhancement allows users who do not actually perform transactions in Infor LX to maintain the reason codes for the transactions.

Infor LN / Baan Tip of the Week: Deleting Records

Kathy Barthelt 0 89618 Article rating: 5.0

To improve performance and reduce database growth, deleting records is highly effective. The disadvantage of deleting records is that data is no longer available. Usually, however, not all records need to be saved. For example, line activities are stored by warehouse. Normally, you do not need to keep these records. Therefore, after closing a warehouse order, line activities can be removed. The User's Guide for ERP LN Archiving describes several sessions you can use to delete old data. Other data such as items and business partners can be reviewed once in a while, after which you can delete the data you no longer need. For every order and contract table a session is available to archive and delete old orders. In these sessions, you can specify several characteristics to select the orders to be removed, such as date or status. Run these sessions on a regular basis.

Explore your IDF programs

Anthony Etzel 0 38495 Article rating: 5.0

If you haven't already, you may want to start to explore your IDF programs. Currently they provide the replacement for the 300 series inquiry programs. In addition, navigation drill downs are far superior to any green screen presentation of the data.

Consistently meet customer commitments without last minute surprises

George Moroses 0 28672 Article rating: 5.0

What if you had a solution that allowed you to consistently meet customer commitments without last-minute surprises and unexpected extra effort and cost?

We do this by preventing slippage — slippage is any break in the plan that disrupts both normal material flow and the rhythm of the plant that is preventable by timely key user intervention.
Click here to learn more about OTTO, On-Time Orders.

First7879808183858687Last

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