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 EXECUTIVES:

George Moroses 0 17129 Article rating: 5.0

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Security Manager

George Moroses 0 15835 Article rating: 5.0

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

VJES (Visual Job Execution Software) for Infor LN & Baan

Kathy Barthelt 0 10582 Article rating: 5.0

​Every manufacturer relies on a few core metrics to manage operations: efficiency, productivity, capacity, and labor and equipment utilization. These benchmarks are used worldwide to assess performance and process effectiveness.

What if you could integrate quality control into every operation at every work center to ensure high-quality finished goods and simultaneously train high-quality operators? Manufacturing quality can be achieved using documented, repeatable, and measurable processes.

Introducing Crossroads RMC's ERP-independent solution, VJES (Visual Job Execution Software). VJES is an electronic work instruction interface that bridges engineering and the paperless manufacturing floor. VJES ensures that only one version of the work instructions is available—the correct one. By deploying up-to-date, visually rich work instructions, images, and videos, VJES provides personnel the best opportunity to build it right the first time and tracks worker productivity throughout the build process.

VJES achieves RESULTS:

  • Turn new hire welders into specialized welders in 2 weeks
  • Improve quality scores from 68/100 to 93/100 in 12 months
  • Reduce employee training time from 1 week to 3 days within the first month of use
  • Maintain a first-pass yield percentage of 100% for 8 consecutive months this year
  • Incorporate a quality cell after productivity increases due to the bandwidth gained from adopting VJES
     

Contact us to learn more, or Request a Demo today!

800.762.2077

Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression

Kathy Barthelt 0 22928 Article rating: 5.0

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.
  • The destination financial company.
  • The transaction type and series.
  • The ledger account and dimensions.
  • The transaction currency.
  • The fiscal year and the financial period, the tax period, and the reporting period.
  • The integration document type and the Debit/Credit indicator.
  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

Infor LX/BPCS Tips & Tricks for FINANCE: Default Billing Reason Code from User Order Class

George Moroses 0 16590 Article rating: 5.0

This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

Infor LN & Baan Tips & Tricks for OPERATIONS: Order Quantity Dependent Routings vs Default Routings

Kathy Barthelt 0 18530 Article rating: 5.0

Order quantity-dependent routings

An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

Infor LX/BPCS Tips & Tricks for OPERATIONS: Track all order holds added & released

George Moroses 0 14480 Article rating: 5.0

Enhancement: Order Hold Audit Functionality

This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

First910111214161718Last

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

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories