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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

EGLi provides Infor LX Configurable Enterprise Accounting (CEA) functionality including Advanced Transaction Processing (ATP), a configurable ledger, and batch transaction processing in the IDF architecture.

EGLi is a complete replacement for CEA. Infor LX applications integrate with EGLi, and subsystem transactions generated in Infor LX are used to create journal entries in EGLi. The Infor LX integration system parameters allow you to specify whether CEA or EGLi is your primary financial product.

We recommend that you select CEA while you test the integration. The primary financial product flag and the CEA migration programs are designed to assist existing CEA clients with their implementation of EGLi. Journals are produced in both GL systems so you can verify that the data in both GL systems are the same. This integration includes migration programs that copy your existing CEA files to corresponding EGLi files. After you run the migration programs, EGLi should be configured and ready to use. If you are already running IDF via Ming.le or SiW, before you install EGLi, you will need to see the Ming.le integration guide for instructions on how to export EGLi tasks from IDF to SiW/Ming.le.

Learn More > Infor LX Integration Guide for Enterprise General Ledger

  • Control Date Lead Times – LX provides five separate Control Date Lead Time fields so you can specify additional lead time values for Shop Orders, Purchase Orders and Planned and Firm Planned orders. Each Control Lead Time Date represents additional time (days) required at each step in the process that needs more time (Quarantine, Stabilize), that is to say, when a component is due, and when it can be used. (working with an aerospace  precision bearing manufacturer, I had to account for the QA requirement that no measurements could be taken until the parts had been “soaked” (stored) in an atmospheric controlled environment (72 degrees, and controlled humidity) for 24 hours. This requirement added one full day of lead time between each machining operation) The MPS/MRP Generation program, as well as programs that Shop Order Material Allocation records use the five control date lead times to adjust component required dates to function in the same way as the BOM Offset Lead Time.
     
  • All programs that create MRP Planned Orders, MRP Firm Planned Orders, Shop Orders, and Purchase Orders call the Control Date Calculation program (MRP515B) to establish all five control dates. A Control Lead Time Date is used to adjust the component Required Dates data in the Material Requirements file (KMR), based on planned orders for a parent, and the FMA Required Dates data, based on shop order release dates for a parent.
First5859606163656667Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories