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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

Fiscal, Reporting and Tax Periods can have status Open, Closed or Final Closed. If a period is Closed or Final Closed, you cannot post entries to those periods. If a period is Closed, you can re-set it to Open and post entries. If a period is Final Closed, you cannot post and you cannot set it back to Closed or Open.

A Provisional Close is run at year-end to bring the balances forward for the new year without having to close the previous year. A Provisional Close can be run as many times as you like. After a Final Close, a Provisional Close cannot be run.

The Provisional Close allows you to continue into the new year with all financial reporting and not have to rush with the Final Close until all adjusting entries are made and any final signoffs have been completed.

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

First157158159160162164165166

Theme picker

Categories