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

BPCS / LX Tip of the Week: Purchase Order Print Security Validation

Anthony Etzel 0 53678 Article rating: 5.0

This enhancement allows users to restrict access to purchase order print programs. The purchase order print programs were updated to provide security validation for the user who selects the purchase orders to print. The security validation is controlled by the PO Print Security Validation flag on the Purchasing System Parameters screen, PUR820D-04. This enhancement gives users the option to restrict access to purchase order print programs, providing additional security at the company and warehouse levels.

Infor LN & Baan: Need Accurate Inventory?

Kathy Barthelt 0 62260 Article rating: 5.0

Automate & Streamline Your Current Processes

We know that efficiency is the name of the game and Crossroads RMC has helped manufacturers achieve real results:

  • Better inventory management
  • Increased visibility
  • Reduced operational costs
  • Increased accuracy and much more

Crossroads RMC has solutions to automate and streamline your current processes from receiving all the way through shipping. Work with Crossroads RMC and realize greater benefits from your CURRENT ERP version.

Get Started

Crossroads RMC to integrate their Baan IV system with all Subway Restaurants and Moe’s Southwest Grill locations nationwide to provide streamlined parts and machine ordering capability

Kathy Barthelt 0 32307 Article rating: 5.0
Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to provide streamlined parts and machine ordering capability for all Subway Restaurants and Moe’s Southwest Grill locations nationwide. The integration will allow for orders to automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q2 of 2019.

Baan / LN tip of the Week: approving a new tax code

Kathy Barthelt 0 81740 Article rating: 5.0

Prior to approving a new tax code, the system displays a message, “An approved tax code cannot be changed anymore. Continue?” This is concerning to end users if they take the message literally. The user can answer “Yes” to the question as it refers to the tax details, not the rates or ledger accounts. A user can always change the tax rate and ledger accounts after it has been approved. All taxing authorities change rates periodically, so it is logical that these could be updated as needed.

OTTO: Making plans happen isn't just about material

Anthony Etzel 0 27539 Article rating: 5.0

Making plans happen isn't just about material. Other things can be the real cause of delays.

OTTO provides the ability to proactively manage the entire customer order backlog from top to bottom. It begins monitoring orders as soon as they’re booked and identifies and prioritizes those critical events that must happen every day so they can be managed and get orders produced and shipped on time.  Learn more

BPCS / LX Tip of the Week: Facility Security Ranges

Anthony Etzel 0 53412 Article rating: 5.0

Previously, a user was able to complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings that were set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and complete the cost transfer process. After the user enters a range in the CST920 screen that is outside of their authority set up in SYS600, a message is displayed that explains they are not authorized to all facilities. Before the enhancement was applied, a user could enter any range in CST920 and it would transfer the costs, regardless of their security level. This enhancement provides security in CST920 that prevents incorrect cost transfers from being processed. 

First6869707173757677Last

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

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories