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

Eliminating ERP Customizations: Key Considerations and Modern Solutions

Transitioning away from customizations can indeed pose challenges, but it's not insurmountable with the right approach. Here’s a look at the real issues and solutions that can pave the way for a streamlined, up-to-date ERP.


Common Challenges:

  1. Dependency on Custom Processes
    Custom processes become ingrained, and removing them disrupts established workflows. However, business processes often evolve over time, as do best practices incorporated into modern ERP systems.

  2. Cost and Time Constraints
    Testing, retraining, and hiring consultants for an upgrade are valid concerns. Yet, consider the efficiency gains and reduced maintenance costs over time by utilizing standard ERP features.

  3. User Resistance
    Change management is critical, as employees can be skeptical of losing tools they’re familiar with. Effective communication about the benefits of standardized, future-ready tools can help ease the transition.


The Reality Check: Has Your Organization Changed?

Evaluate how much your business needs have shifted, how user expectations have evolved, and if any workarounds or interim solutions are now adding unnecessary complexity. Many companies discover that industry-standard ERP features can replace outdated customizations.


Did You Know?

  • ERP Upgrades Can Eliminate 25% - 50% of Customizations
    Modern ERP systems incorporate industry best practices as core features, allowing you to rely less on customizations and more on robust, standardized solutions.

  • Extensibility & Reporting Solutions
    Extensibility tools in Infor LN or Baan let users add last-mile functionality without modifying the core ERP. Reporting tools allow custom insights while keeping ERP data intact.


Solutions to Reduce Customization Dependency:

  1. Rewrite Customizations to Use Standard APIs and Libraries
    This ensures seamless interaction with core ERP features without modifying underlying code.

  2. Utilize Infor Extensibility and LN Studio
    Smaller tweaks can be handled with Extensibility; larger needs can leverage LN Studio for custom apps without touching the ERP's foundation.

  3. Incorporate Infor ION for External Integrations
    If customizations primarily manage integrations, Infor ION can connect and streamline external systems effectively.

  4. RMCgen for Custom Components
    RMCgen allows for custom development without altering standard programs, offering flexibility without compromising core stability.

  5. Analytics Dashboards for ERP Insights
    Dashboards offer tailored views and insights without requiring customizations in the ERP itself.

  6. Leverage Built-in Reporting Tools
    Infor Report Designer, Document Management, and BIRST can provide custom reporting, avoiding custom coding altogether.

  7. Assess Your Custom Components
    A thorough assessment of your customizations—internally or with Crossroads RMC consultants—can reveal areas for potential standardization and streamlining.

Let’s Talk Solutions

If customizations are standing in the way of your ERP’s full potential, Crossroads RMC can help. Connect with us at 800.762.2077, solutions@crossroadsrmc.com, or request a consultation to start your path towards a flexible, future-proof ERP.
 

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Use of Electronic Bank Statements
Next Article News You Can Use - Infor: What's new with LX 8.4.2
Print
10589 Rate this article:
5.0

Contact

Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories