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 LX/BPCS Tips & Tricks for FINANCE: Increase A/P Retention Days

George Moroses 0 1997 Article rating: 5.0

This enhancement allows reconciled payables and payments to be retained in the system for over 200 years. It extends the retention period in A/P Application Control Maintenance (ACP180) to support up to five digits. This gives LX customers the ability to retain data online for significantly longer durations.

Embracing Industry 4.0: The Future of Smart Manufacturing is Here

WEBINAR - Join us: Thursday, April 17th, 2025 from 1:00 to 1:30 (US/Eastern)

Anthony Etzel 0 2268 Article rating: 5.0

We’re standing in the middle of the Fourth Industrial Revolution—Industry 4.0—a transformation that’s redefining how products are made, moved, and managed. But many companies are still operating with Industry 3.0 systems: digitized, yes, but not yet intelligent, connected, or adaptive.

So, what makes Industry 4.0 different? And more importantly—where does your company stand in this transformation?

Automation to Intelligence: The Shift from Industry 3.0 to 4.0
Industry 3.0 introduced computers, electronics, and early automation into manufacturing. It marked the beginning of digital systems and the rise of Manufacturing Execution Systems (MES) as a bridge between planning and the shop floor. Industry 4.0 takes it further: it brings interconnectivity, real-time data, and AI-powered intelligence into every corner of the industrial environment. It’s about smart factories, self-optimizing systems, and predictive capabilities that weren’t possible before.

8 Pillars of Industry 4.0:

1...

Dive Into IDF for ERP LX! - Part 2

Anthony Etzel 0 7029 Article rating: 5.0

Learn all this and more in our webinar -Thursday, March 20th at 1:00 PM Eastern / noon Central.

Presenter: Nick Olson, Crossroads RMC Solutions Consultant

In this session, we will explore customizing the User Interface:

  • Want to see only the objects you need?
    • Build a Card!  
  • Constantly recreating the same filter row criteria?
    • Build it into a Subset!  
  • Too many irrelevant or not enough pertinent columns of data?
    • Build a custom View!  
  • Need to draw attention to a particular piece of information?
    • Build a Presentation Scheme!  
  • Tired of scrolling back and forth to see key data?
    • Freeze columns!  
  • Need to add and view attachments?
    • Build an Attachment Viewer Card!

Register TODAY: https://ibmi.workoutloud.com/Event/dive-into-idf-for-lx-part-2

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails

Kathy Barthelt 0 18328 Article rating: 5.0

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Infor LN & Baan Tips & Tricks for OPERATIONS: Using Country of Origin for Purchase Orders

Kathy Barthelt 0 24550 Article rating: 5.0

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.

Infor LN & Baan Tips & Tricks for FINANCE: Remap Posted Integration Transactions (tfgld4282m100)

Kathy Barthelt 0 25192 Article rating: 5.0

Use this session to remap Posted transactions that were mapped incorrectly.

To remap integration transactions successfully, several conditions must be fulfilled. For details, refer to To remap integration transactions.

Enter the ranges of selection criteria for the integration transaction or range of integration transactions to be remapped. You can select the integration transactions of a range of business objects or of a specific business object.

You must select a specific integration document type or an integration document type group.

To evaluate the remapping before you perform the actual remapping, you can select the Simulate check box and the Error Report check box. After you solve the errors, you can run the session again and clear the Simulate check box.

After remapping the integration transactions, you can use the Post Integration Transactions (tfgld4282m000) session to create the postings in the General Ledger.

245678910Last

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

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories