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

An ERP System Review is NOT a Report Card

It's a no-judgment-review - we promise!

report card C minusWe all remember our school days and the nervousness that we felt when it came time to get our grades. Even if we were doing well, we were still nervous. Sometimes we experienced that same nervousness when it came time for a performance review on our job. Nervousness…sometimes dread…knowing that our performance was not what we wanted it to be, or others expected it to be. 

Somehow I think the feelings that we felt in our past often find ways to creep into our present. I have seen this recently when I suggested an ERP system review to one of our customers. They immediately became flustered and thought about every possible problem that they knew existed within the software and how they were currently using it. I asked them to consider the purpose of the ERP system review.

An ERP Utilization Review will:

  • Document how your company is using your ERP system (or a particular aspect of the system) and to what extent the system meets the needs of the business.
  • Identify challenges encountered using the software.
  • Create opportunities for improving business processes and generating additional value.
  • Identify potential risks and areas that need improvement.


key hole to the futureSo, if the result of ERP system review is to establish a path forward for growth based on current status, then why doesn’t every company take advantage of it? I think for some, the answer lies in the feelings of nervousness and dread still stuck in the recesses of our brains.

An ERP system review or more specifically a utilization review is NOT a personal report card, or performance review showing how well a particular individual does his/hers/their job, nor is it an attack on the team that implemented the software. 

As they say, hindsight is 20/20. What we view now to be a less than ideal implementation methodology may have been absolutely appropriate at the time the software was originally deployed. The software has likely matured and the skillsets of the individuals responsible for the system have likely matured as well. In some cases, those resources are no longer with the company, leaving those that remain with no back story as to how and why implementation decisions were made.

Instead of viewing the ERP utilization review as a reason to find fault in previous decisions, think of it as discovering untapped potential – both of the ERP system and the people who use it. Viewing an ERP utilization review in this way puts a positive spin on it and allows us to challenge ourselves to identify opportunities for growth far greater than anything we imagined before. This means not only moving our businesses forward faster but also advancing the strength of the company as individuals and as a team.

What untapped potential lies within your company?

Consider a utilization review of your entire ERP system, or just a part of it like Finance, Technology, Materials Management, Order Processing, or Shop Floor Control. You just might be surprised at what greatness can be achieved… far greater than anyone could have imagined.  

Get a free phone consultation button

800.762.2077

Previous Article Infor LN & Baan Finance Tip: Unallocated Payment
Next Article Infor LN & Baan Tip: Why can’t I delete my outbound order line upon cancellation of a sales order?
Print
23102 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