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 32378 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 31605 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 59041 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 55075 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 81745 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 33977 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 23869 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.

First7071727375777879Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Default Order Frequency

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In ERP LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Previous Article Baan/LN Tip of the Week: Safety Time
Next Article Baan/LN Tip of the Week: Month End Closing – Projects
Print
79598 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories