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
22999 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

This is a simple way to go from the customer order to making the order and shipping the order. It involves a few simple steps:

  1. Receive and enter the customer order
  2. Automatic credit review
  3. Automatic release of the shop order tied to the customer order
  4. Issue material, report labor to the production order receipt
  5. Pick the order, ship the order, invoice the customer


With lean, you can skip processing the demand through MRP. You can go directly from the customer order to the shop order creation.

Define Inventory transactions for issuing components to the shop and receiving finished items. See the Inventory help text for examples of transactions.

  • Transaction type I - Single Issue to Shop Order. Use this transaction type to issue one component at a time. Use this for high-value items that are marked as Must Single Issue on the Item Master file.
  • Transaction type M - Multiple Issue to Shop Order. Use this transaction type to issue all the components as listed in the Shop Order, in one transaction. Note that this transaction type does not issue Must Single Issue items.
  • Transaction type S - Receipt from shop. Use this transaction type to receive the finished item into stock and update the shop order accordingly. 

The Shop Order Lot/Location Allocation program is an alternative to using the above Inventory transactions. Use this when the item is finished, and you want to review exactly what was used to make it. You can review the components as allocated, make any changes, and finally accept the finished order.

First132133134135137139140141Last

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:

1345678910Last

Theme picker

Categories