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

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