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: GETTING A HANDLE ON DOWNTIME

Anthony Etzel 0 48099 Article rating: No rating

It is essential to capture a reason and duration for each downtime incident to enable the team to effectively prioritize and focus.

Start simple, and make sure every reason is clear (when compared with other reasons) and describes symptoms (as opposed to attempting to diagnose root causes). Remove reasons that aren’t regularly used and add reasons.

 

Baan/LN Tip of the Week: Getting a Handle on Downtime

Kathy Barthelt 0 84961 Article rating: No rating

It is essential to capture a reason and duration for each downtime incident to enable the team to effectively prioritize and focus.

Start simple, and make sure every reason is clear (when compared with other reasons) and describes symptoms (as opposed to attempting to diagnose root causes). Remove reasons that aren’t regularly used and add reasons.

BPCS/LX Tip of the Week: What Should I Consider When Analyzing my Sales?

Anthony Etzel 0 50834 Article rating: No rating

From a recent article published by M4B Marketing:

When analyzing your sales performance consider the following: 

  • Pricing changes eg. price increases or discounting
  • Competitors – competitors entering or exiting the market
  • New product or service launch growing sales
  • New product or service cannibalizing existing product or service sales
  • Customers moving between products or services
  • Changes in customer demand eg. increasing or decreasing
  • The segments and distribution channels you operate in
 

Baan/LN Tip of the Week: What Should I Consider When Analyzing My Sales?

Kathy Barthelt 0 2760431 Article rating: No rating

From a recent article published by M4B Marketing:

When analyzing your sales performance consider the following: 

  • Pricing changes eg. price increases or discounting
  • Competitors – competitors entering or exiting the market
  • New product or service launch growing sales
  • New product or service cannibalizing existing product or service sales
  • Customers moving between products or services
  • Changes in customer demand eg. increasing or decreasing
  • The segments and distribution channels you operate in

Crossroads MES – The Shining Star of Hoffmaster’s Move to LX

Anthony Etzel 0 36752 Article rating: No rating

When Hoffmaster finally flipped the switch on its ERP migration at the end of February, the IT director was nervous. Not only was the paper-goods supplier consolidating a manufacturing site on Infor ERP LX, but it was also replacing an old shop floor reporting system with a new one from Crossroads RMC. There was a lot that could go wrong for the IBM i shop.

"When we weighed all of our products, Crossroads RMC pretty much convinced us their product was plug and play and their integration back to LX was solid as a rock, and they were right..." the IT director says.

Click Here to Learn about Hoffmaster’s move to Infor LX and their implementation of the Crossroads MES solution.

Tip of the Week: Operational Inefficiencies

Anthony Etzel 0 55676 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.
First9899100101103105106107Last

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
28318 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories