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

Is Your ERP System Hurting Your Business?

The Importance of an Integrated System

Kathy Barthelt 0 13970 Article rating: 5.0

It could be if your ERP system isn't integrated with other systems that contain mission-critical business data.

Having data in two (or more) systems that don’t talk to one another is like baking a pizza crust in one oven and the toppings in another. Once baked, you may have food to snack on, but it sure isn’t pizza! Pizza requires the cheese, sauce and spices to bake with the crust, so all the flavors meld together when you take that first delicious bite. 

That’s the value of an integrated ERP system. When you...

Optimize with Infor Development Framework: IDF

Infor LX | BPCS | M3

George Moroses 0 16449 Article rating: 5.0

Why You Need IDF

The Infor Development Framework (IDF) not only helps you modernize the look and feel of your LX software but also the interactions of the IBM i software with other applications in your business.

“The IDF is a multi-user interface, single codebase architecture that’s metadata-driven (and) provides a lot of flexibility to adapt the software for their processes.” says Infor. This is the direction that Infor is going starting...

Managing the Inventory Risk

Infor LN & Baan

Kathy Barthelt 0 14695 Article rating: 5.0

Proper Inventory Management & Planning is not for the weak!

Any of these ever happen to you?

  • My supplier can’t provide the raw materials I need when I need them because I waited too long to order.
  • I underestimated how much raw material I had on hand and now my customer’s order is waiting on hold until I can get the parts I need.
  • I couldn’t meet the desired delivery date for my customer’s order, so they took their business somewhere else.
  • I ordered too many raw materials or made too many sub-assemblies because I didn’t have good visibility to my on-hand inventory.

...

LN & Baan | LX & BPCS Tip: 9 Tips for Secure Manufacturing Business Systems Through OT Cybersecurity Vulnerability Management

Infor LX, BPCS, Infor M3, Infor LN & Baan

Crossroads RMC 0 20642 Article rating: 5.0

Always happy to share a good article on protecting your business from cybersecurity threats. 

9 OT Cybersecurity Strategies To Secure Manufacturing Industries

By Will Fastiggi - Technology for Learners - January 23, 2023

Let’s delve into the details of how to secure manufacturing industries through OT cybersecurity vulnerability management. Below are some tips and tricks.

1. Implement a...

First2021222325272829Last

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

[EasyDNNnews:IfExists:Event]
[EasyDNNnews:IfExists:EventRegistration][EasyDNNnews:EventRegistration:RegisterButton][EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:Payment][EasyDNNnews:Price][EasyDNNnews:EndIf:Payment] [EasyDNNnewsLocalizedText:Eventdate]: [EasyDNNnews:EventDate] [EasyDNNnewsLocalizedText:ExportEvent] [EasyDNNnews:IfExists:EventLocation]

[EasyDNNnewsLocalizedText:EventLocation]: [EasyDNNnews:EventLocation]

[EasyDNNnews:EndIf:EventLocation] [EasyDNNnews:IfExists:EventRegistration]
  • [EasyDNNnewsLocalizedText:NumberOfAttendants]: [EasyDNNnews:EventRegistration:NumberOfAttendants]
  • [EasyDNNnewsLocalizedText:MaxNumberOfTickets]: [EasyDNNnews:EventRegistration:MaxNumberOfTickets]
  • [EasyDNNnewsLocalizedText:NotUsedTickets]: [EasyDNNnews:EventRegistration:NotUsedTickets]
  • [EasyDNNnews:IfExists:Payment]
  • [EasyDNNnewsLocalizedText:Price]: [EasyDNNnews:Price]
  • [EasyDNNnews:EndIf:Payment]
[EasyDNNnews:EventRegistration:InfoMessage] [EasyDNNnews:EndIf:EventRegistration] [EasyDNNnews:IfExists:EventSignUp]

[EasyDNNnewsLocalizedText:AreYouGoing]

[EasyDNNnews:SignUpActionBar]
[EasyDNNnews:EndIf:EventSignUp]
[EasyDNNnews:EndIf:Event]
George Moroses
/ [EasyDNNnewsLocalizedText:Categories]: [EasyDNNnews:Categories]

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

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories