Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Don't laugh - the average lifespan of an ERP system is 7-10 years
Crossroads RMC
/ Categories: Infor LX & BPCS Tips, Infor LN & Baan Tips, Because I Care, Services News, Upgrade & Implementation, Integrations & Enhancements, Infor ERP Utilization Review, ERP Utilization Review & Process Improvement Consulting, Support, Training & Workshops, Consulting, Department, Finance, Manufacturing, Operations, Technology

Don't laugh - the average lifespan of an ERP system is 7-10 years

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!

Is it that black and white though? There is an ocean between “do nothing” and “replace everything”. Taking incremental steps can give your organization a tremendous amount of benefit without the tremendous price tag that often goes with ERP replacement, but you need to be willing to take the first step. Maybe there is a manufacturing ERP add-on that you know would provide tremendous benefit and improve overall efficiency, or a web portal that you log in to that allows you to communicate with your suppliers, but it has no tie to your purchase orders, or maybe your team would benefit from a review of industry best practices and how that compares to how your ERP system is currently being used. Or at the very least you need to know if your ERP system is still meeting the organization’s needs.

“Success will never be a big step in the future. Success is a small step taken just now.” – Jonatan Martensson

Crossroads RMC specializes in helping manufacturers maximize the benefit of “the small step”.  Not sure how Crossroads RMC can optimize your business?

Our Infor ERP Services can optimize your business with the following initiatives and many more:

Infor LX (ERP LX) Services>
Infor LN (ERP LN) Services>
BPCS Services>
Baan Services>

It's time to take the first step today!
800-762-2077  |  solutions@crossroadsrmc.com

Previous Article Infor LN & Baan Tip: Purchase Order Text
Next Article Are You Running Your IT Department, or is IT Running You?
Print
26999 Rate this article:
5.0
Crossroads RMC

Crossroads RMCCrossroads RMC

Other posts by Crossroads RMC
Contact author

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

Read more

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.
Read more

A cluster is a group of one or more warehouses in a particular geographical area. You can plan an item by cluster (geographical area).

To enable this, you can set up multiple plan items for one item. You always define one plan item without a cluster indication and multiple plan items with a cluster indication. A plan item with a cluster is called a clustered plan item, and a plan item without cluster is called the non-clustered plan item.

The plan items in the clusters can be supplied not only by distribution, but also through purchase and production. In this way, you can, for example, plan local purchasing in a cluster (geographical area). You can also plan supply from multiple sources.

  

Optimize Your Manufacturing Today!

Read more
First100101102103105107108109Last

Theme picker

Categories