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

Hoffmaster Clintonville Plant Goes Live with Crossroads MES & LX

Anthony Etzel 0 28872 Article rating: No rating

On March 1, 2016, Hoffmaster’s Clintonville plant went live with Crossroads MES and LX. The goal of the project was to convert from another ERP to LX and replace a green screen MES system that required the manual recording of production and labor activity keyed from shop floor terminals.

Hoffmaster achieved their goal by completing a successful data conversion and detailed prototyping of LX and Crossroads. The project team remarked that the Crossroads MES implementation was by far the easiest part of the project. One of the critical requirements of the chosen MES solution was to verify UPC and UCC label formats that called for in-line labeling of product packages and cases. Crossroads MES satisfied that requirement, and also provided an interface to finished goods inventory via the scanning of LPN numbers when reporting production.

The Clintonville plant is a leading manufacturer of disposable tabletop products.

BPCS/LX Tip of the Week: Actual Costs for Manufactured Items

Anthony Etzel 0 33577 Article rating: 5.0

In LX, the actual costs that can be set up fall into three categories: Material, Labor, and Overhead. If your LX database is set up properly with the LX cost accounting, you should be able to identify:

  • How much the item should cost
  • How to track the cost of work underway
  • How much the item actually did cost
  • Why the job cost varied from the expected cost
     

Capturing the data to track activity with associated costs can be time-consuming. With an MES solution, the information you need for costing is tracked instantly.

Baan/LN Tip of the Week:GRINYA Reconciliation – What Could Go Wrong?

Kathy Barthelt 0 61146 Article rating: No rating

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Morrison Brothers Goes Live With Crossroads MES in Record Time!

Crossroads RMC 0 30640 Article rating: No rating

On February 18, 2016, the Maquoketa plant of Morrison Brothers went live with the Crossroads MES solution. The goal was to remove all the shop floor paperwork and eliminate the manual recording of production and labor. The company achieved this goal in just 96 days from project kick-off to go live. Included in the go-live was the ability to deliver drawings electronically to the Crossroads MES workstations. This was a critical component of the implementation as it ensured that each workstation would always be operating off the latest revision of the engineering documents.

A rollout of the Crossroads MES solution is planned for Morrison’s Dubuque plants later this year. 

Morrison Brothers is a major producer of petroleum marketing equipment in the United States and abroad.

Baan/LN Tip of the Week: Old Porting Set

Kathy Barthelt 0 52765 Article rating: No rating

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third-party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if the database is also running on the same server as the application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

BPCS/LX Tip of the Week: Establish Costing For Purchased Items

Anthony Etzel 0 32601 Article rating: No rating

How Does Infor LX Establish Costing For Purchased Items?

In LX, you will establish a standard cost (you define the standard) that LX will use for the purchase items. You also need to establish in LX the Cost Type, the Cost Bucket, and the Cost Set needed for cost accounting.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 58661 Article rating: No rating

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

Crossroads RMC Releases NextTrack Sales – Sales Analysis Tool for Baan, Infor LN and IBM i

Kathy Barthelt 0 30167 Article rating: No rating

Crossroads RMC is proud to announce the official release of NextTrack Sales – a sales analysis tool for Baan, LN, and IBM i. NextTrack Sales allows you to get the “big picture”, or get down into the finer details. The tool provides a sophisticated pivot grid and charting functionality, export to Excel, PDF printing, and emailing capabilities to bring your sales data to life. Analyze your Baan Sales data to examine trends, identify market opportunities, and much more. Click here for more details.

First99100101102104106107108Last

Tips:  LX | BPCS | M3

This enhancement provides additional views, additional order and line details, improved navigation, and additional capabilities to the IDF Customer Order Inquiry cards and to customer order-related business objects such as Allocations, Customer Invoices, Inventory Transaction History, Promotions, Drop Shipments.

Enhanced Order views based on user roles such as customer service, warehouse/logistics, salesperson/commission, data analysis/management reporting

  • Improved sort, select and filter capabilities
  • Enhanced navigation, data organization and data display
  • Improved customer service access to all transactions throughout the entire customer order life cycle – from quote to order, related invoices, and any RMAs, return orders, related credit memos
  • Improved grouping of related fields
  • New cards to present additional order and order line details
  • Consolidation of cards and card details when appropriate
  • Enhanced Display and Maintain capabilities for drillback to related customer, ship-to, item, carrier, terms, and other master file details
  • Improved display of dates, times and applicable time zones when Region Code time zone support is implemented
  • Multi language Description, Name and Address fields displayed in user’s language, if defined, else in base language

This enhancement provides search capabilities on segment value description in Segment Value List window (WINGSVD).

Segment Value List (WINGSVD):

  • Converted to a standard subfile
  • New action code 10=Search

This makes it easier to locate segment values when defining segment values in Model Account Builder or Alias definition. In addition, WINGSVD has been redesigned as a subfile to enable WebTop grid capabilities.

Last

Tips: LN | Baan

George Moroses

Infor LX & BPCS Tip: PowerLink

PowerLink is a Windows-based client for end-users within the Infor Development Framework (IDF). PowerLink allows exports/imports from/to the ERP database, but how much do you really know about it? Here is some helpful information about PowerLink.​

Why does PowerLink sometimes fail to export all records?
There's not a finite amount of records that PowerLink can export. However, PowerLink export was never intended to handle large volumes of data. It was designed as a quick snapshot of a fairly small subset and a simple view of the user's PowerLink card. 

What is the maximum amount of data that can be exported?
The maximum number of records is only limited by the system resource like memory, etc. When the system runs out of resources, an OutOfMemory error should occur. In previous testings, we have exported +1 million records, although the size of records differs greatly between business objects, the total size of the data could be an issue. For larger volumes of data, customers should investigate other tools such as the iSeries Access "Data Transfer from iSeries Server" feature to download directly to Excel.

How do I know if the size of the data is an issue?
1. When exporting to an external file (text, HTML) then importing to Excel: You can easily check the output (text, HTML) to see if the intermediate output has all the records. This can be done by visual inspection or through the use of column totals. Simply compare between the output and what you see in PowerLink. If the exported file has all the records, then the problem is definitely Excel.
2. When exporting to clipboard, then copy/paste to Excel: There is a clipboard export size limit that is controlled through client preferences. Check the exported data in the clipboard, and see if it contains all the records or only partial records due to the size limitation set in client preferences. If limited, change the client preferences using Customize from the Main browser > Preferences > Miscellaneous tab > Limit Clipboard Export, and try the export again. If the clipboard has all the records the problem is in Excel, which we don't have jurisdiction over.

Suggestions for improving the export process. 

  1. Reduce the number of columns seen in the view. This will serve to reduce the data being exported and may increase the number of records that can be exported. 
     
  2. Reduce the complexity of the view. If the view has one column that lives on a related object, then it has to build SQL behind the scenes to get that related record. If all of the columns come from a single business object, then the processing will be significantly faster.
     
  3. Export to HTML, which can be opened directly by Excel, Access, and many other programs. This reduces the processing of the export formatting because PowerLink needs only to put begin and end tags around each data element. This will also preserve column alignment when Excel or other programs open the file.
     
  4. Unless you are exporting a fairly small volume of data, export to a file, not clipboard. Clipboard is held in memory until the entire view is read, and records are written to the file as they are retrieved.
     

 Also see KB 1357068 for more information about testing your view.

Print
47013 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories