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: Operational Inefficiencies

Anthony Etzel 0 42337 Article rating: No rating

Two big sources of inefficiencies in manufacturing are paper and spreadsheets. I know that you love ‘em, but they are the cause of more problems than you probably realize. Think of how long it takes you to get paper based data into the hands of those who can do something valuable with the data.

  • Is the information captured correctly?
  • Can everyone access the information?
  • Is this an accurate representation of what’s going on across all operations?

Make your shop floor paperless and put systems in place that talk to one another and automatically pull and push data to and from your ERP so that you can look in one place for all the information you need to run your business effectively.

If you’re not doing this today, you might as well be burning money.
 
Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: Operational Inefficiencies

Kathy Barthelt 0 81168 Article rating: No rating
Two big sources of inefficiencies in manufacturing are paper and spreadsheets. I know that you love ‘em, but they are the cause of more problems than you probably realize. Think of how long it takes you to get paper based data into the hands of those who can do something valuable with the data.
  • Is the information captured correctly?
  • Can everyone access the information?
  • Is this an accurate representation of what’s going on across all operations?

Make your shop floor paperless and put systems in place that talk to one another and automatically pull and push data to and from your ERP so that you can look in one place for all the information you need to run your business effectively.

If you’re not doing this today, you might as well be burning money.
 
Optimize Your Manufacturing Today!

BPCS/LX TIP OF THE WEEK: REGULATORY ENHANCEMENTS

Anthony Etzel 0 44741 Article rating: No rating

In LX 8.3.5, a new report has been added that meets the regulatory reporting requirement for purchase and sales transactions (invoices, debit notes, credit notes) of a company. The report refers to transactions from the previous year (January – December). The report is available in an eFile layout.

The enhancement provides a new display and batch programs to extract the data and format the reports. New logs are provided in addition to the extraction report.

This enhancement will assist the user in meeting the regulatory requirement for reporting transactions.

Baan/LN Tip of the Week: Restricted User Access

Kathy Barthelt 0 97623 Article rating: No rating

Administrators are able to restrict access in Baan in several ways – including Companies, Packages, Modules, Sessions, and Tables – using the Authorization capabilities of the system.

In Baan IV, access can be given or denied on a user by user basis.

In Baan V and LN, the Authorization Management System can provide or deny access based upon roles to which users are assigned.

BPCS/LX TIP OF THE WEEK: INVENTORY MANAGEMENT

Anthony Etzel 0 35252 Article rating: No rating

Establishing the Quantity On-Hand and the Quantity Available.

LX maintains buckets for information associated with the following inventory transactions for each item:

  • Opening Balance
  • Issues
  • Receipts
  • Adjustments
  • Allocations for the Customer
  • Allocations for Manufacturing

The on hand quantity does not include any allocations. To arrive at the on hand quantity, start with the opening balance, less any issues, plus any receipts, then add or subtract any adjustments. Available inventory is the on-hand less any allocations.

Baan/LN Tip of the Week: Old Porting Set

Kathy Barthelt 0 134970 Article rating: No rating

Here are some issues that you might run into if you stay on an old porting set too long:

  • Incompatibility because of operating system patches
  • Printing issues because of out-of-date libraries
  • Potential performance issues if binaries are not updated
  • Updating third party products may not be possible because of dependencies
  • Limited support from Infor
  • Issues with updating database software/patches because of dependencies (if database is also running on same server as application)

Need help getting on a newer porting set? Let us know! We’d be happy to help.

Crossroads RMC Moves Arrowhead from 4.0.05CD to Infor LX

Crossroads RMC 0 34098 Article rating: 5.0

Arrowhead Products, a world leader in the design, development and manufacture of ducting systems for aircraft and propulsion lines for rocks, has partnered with Crossroads RMC to move from BPCS 4.0.05CD to Infor LX. Crossroads RMC is providing financial business consulting as part of this project. Go live is expected in Q4 of 2017.

First8485868789919293Last

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

Kathy Barthelt

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

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:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Using Country of Origin for Purchase Orders
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28195 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories