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

Infor LN & Baan: BIG DATA - Keeping Track of Key Metrics

Kathy Barthelt 0 62840 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

Infor LX & BPCS: Waste in Manufacturing

George Moroses 0 28801 Article rating: 5.0

In manufacturing, waste is anything that doesn’t add value to or benefit the end customer. Reducing waste enables manufacturers to save money and increase productivity. Where is the waste happening in your processes?

How often is your department spending time and resources on the following tasks?...

Infor LX & BPCS Tip: Overhead Costs - CST120D1

George Moroses 0 26926 Article rating: 4.0

Use this program to enter period overhead expenses to distribute to various work centers. You can set up this overhead cost allocation on either a per-hour or a per-piece basis, depending on the overhead allocation type specified for each work center on the Work Center Maintenance screen, CAP100D2-01. The system spreads the amounts entered across all shop orders posted by Shop Floor Posting, SFC600, or Production Reporting, JIT600, when you run Overhead Cost Allocation, CST510. The system stores allocated overhead in the Labor Ticket file, FLT, and updates actual item cost when you run Shop Order Close and Post, CST900.

Access: Menu CST

Infor LX & BPCS: BIG DATA - Keeping Track of Key Metrics

George Moroses 0 32136 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

Infor LX & BPCS Tip: Transaction History – Did you know?

George Moroses 0 29852 Article rating: 3.5

Did you know that the system stores a record of every inventory transaction and makes them available for inquiries and reports? Transaction history is available for immediate inquiry by item, or by item and location in the Material Status Inquiry program. The inventory transaction record holds data such as the quantity, date, reference number, cost/value, transaction type, scheduled date, and master reference number, lot numbers, and warehouse/location information.

Infor LN & Baan Tip: How to deal with data growth of your ERP system…

Kathy Barthelt 0 120429 Article rating: 5.0

Spending time on managing ERP data can deliver huge benefits, not just in reducing storage costs, but also in improving the experience of business users. Proactively managing application data also helps accelerate key business processes which has a positive impact on customers, suppliers, and partners. Use these solutions to reduce the data growth and disk storage used on your system:

• Use database compression. See...

Check-Ups are important… Including Infor LN & Baan ERP Check-Ups!

Kathy Barthelt 0 150208 Article rating: 5.0

What would you say to someone if they never went to a doctor for a check-up, or never took their car in for regular maintenance, like an oil change?

You might say that they were asking for problems, right? The point of those check-ups is to catch a problem early, or better yet before it occurs. Going for check-ups gives you the peace of mind that things are running well and if an issue is identified early enough you can reduce overall risk. Regular check-ups can help reduce out-of-pocket expenses over time.

What about Finance, Manufacturing, Supply Chain, and Company-wide Check-Ups for your Infor ERP system? What will happen if you NEVER hit pause?

Here are some questions by department to consider.

Finance:...

First3233343537394041Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

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
50079 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories