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

David Dickson

If ERP is plumbing for the Enterprise - How do we unplug it and keep it from making a huge mess?

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 300 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

What has surely changed is how we use these systems. Back when I started we used them because we could process more transactions more accurately and faster with a computer, than with the otherwise necessary roomful of clerks. Those clerks, schedulers, and various other clerical employees were the first generation of jobs computers rendered obsolete. Strangely, I do not remember anyone bemoaning those lost jobs. I will let others speculate on the reasons for that.

Individual companies could and did debate the decision about how much they automated. Yes, in retrospect, it is pretty clear that choosing not to automate was to accept a long, slow death for the business, but it is not that long ago when there were still lots of manufacturing managers and business owners who did not use, or like, computers.

Competition Changes Everything

Today a business system is just another piece of necessary infrastructures like an office, a phone, a lawyer, a bank account, and an accountant. The system remains the transaction processing backbone for the organization, but the way in which we use the information that flows from those transactions has changed drastically in this interconnected world. Back in the heady days when ERP was new, the focus was all internal, inside the four walls. Today that seems quaint – the Internet connects all systems and much of the unique incremental benefits (or competitive advantage, if you prefer) come from two deceptively simple concepts – how you connect with the rest of the world from your business systems, and how you monitor your business’s performance in real-time and adapt to what you learn.

I still remember a kickoff meeting twenty years ago for what was then a pretty large ERP implementation at an automotive supplier. Two comments struck me – the first was public. “I like to think of our business as a boat, and we have been steering it by looking out the back. This project will at least let us see out the sides.” The other was in a private meeting when we were discussing change management, and how they would deal with the resistance that would surely come. This same manager said simply, “I guess we will have to fire someone for it, and then the rest will get religion.”

Not terribly ambitious goals, but I give him credit for honesty.

Things have certainly changed a lot in terms of our expectations for the systems, and our approach to implementation, but despite these systems have become an integral and necessary part of the infrastructure of every business, they remain infuriatingly complex and the benefits we expect are often difficult to achieve.

Illusive Benefits = Bad Form

That should not be the case. My goal is to be your guide and share my insights and other good ideas, found across the web, as to how to make business system selection easier and how to get the most benefit from those systems. Because in spite of all the marketing folderol, it seems pretty clear that your friendly software vendor and expert implementation consultants are not going to do that for you. Not because they are stupid or evil people, of course, quite the contrary. They just cannot and will not make the decisions for us that need to be made.

Systems should work for us. Choosing and implementing a system should not be a high-risk proposition for a business, or the individuals doing the work.

The common elements made simple, efficient, and effortless with returns.

My entire career has been dedicated to those goals.

What do you consider yourself to be?

  • internal expert?
  • someone beginning the search and implementation process?
  • an executive looking for a competitive advantage?
  • an industry insider?
  • or someone who finds this amusing for some reason?

All of the above? There is a better way to choose and use software and as someone who could fit into any and all of the categories listed (yes, I really do find business software entertaining in some weird way), I have some ideas I’d love to share with you, so feel free to ask questions.

About the author:

David Dickson is an itinerant generalist; his path to partner and CFO of Crossroads RMC has had its twists and turns. His first twist occurred when an employer needed a business system and picked him because he had three semesters of computer programming in engineering school -- an “expert” born. Somewhere along the line he helped to build and sell a company, which he bought back a couple of years later. Add in another acquisition, a merger, and about 30 years in manufacturing systems in various roles, and you might get a sense from where his real expertise might arise.

Previous Article Accelerating Change: How Innovation Is Driving Digital, Always-On Supply Chains
Next Article Crossroads RMC to Exhibit at Inforum 2016
Print
30394 Rate this article:
5.0
David Dickson

David DicksonDavid Dickson

Other posts by David Dickson

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

Customer Defined Fields (CDFs) can be added to tables, screens, reports and BODs and validation and calculation logic can be defined around those fields.

Use the CDF concept to store additional data in the standard Infor LN tables. The CDF definitions are stored separately from the table definitions in the Data Dictionary. For the end user, the CDFs behave in the same way as the standard fields, if defaulting, validations, etc. are built using the CDF logic of the table extension point. The session extension point also has features for the CDFs.

CDFs are configured per package combination. This implies that when moving your companies from one package combination to another, the CDF definitions must be present in the target package combination. Otherwise you lose the data in the CDFs.

The package includes numerous reports and sessions to view the variances in a way that Finance can identify problems based on the Finance Integration Transactions in the General Ledger.

There are a few main sessions with many detailed sessions linked to them. The reports can be run from the main Print Production Order Variance Reports or in the individual detailed session.

Sessions included in the report package:

1. Print Finalized Trans – Variance Reports.

a. Financial Trans. by L/Acct – Prod. Order Variances - Recap

b. Financial Trans. by L/Acct – Prod. Order Variances – Details

2. Update Production Order Variances (updates special variance table).

3. Production Order Variance Overview – Main view

a. Production Order Variance Details

b. Price Variance Details – Material Variances

c. Price Variance Details – Operation Variances

d. Efficiency Variance Details – Material Variances

e. Efficiency Variance Details – Operation Variances

f. Efficiency Variance Details – Reject Variances

g. ACO Variance Details – Reject Variances

h. Accept Production Order Variances

i. Un-accept Production Order Variances

j. Finally Accept Production Order Variances

4. Print Production Order Variance Reports:

a. Production Order Variance – Overview

b. Production Order Price Variance – Material Revaluation

c. Production Order Price Variance – Operation Revaluation

d. Production Order Efficiency Variance – Material

e. Production Order Efficiency Variance – Operation

f. Production Order Efficiency Variance – Rejects

g. Production Order ACO Variance – Rejects-Additional Costs

5. Delete Production Order Variances (used to redo a month)

Contact Kathy Barthelt to learn more.

First5657585961636465Last

Theme picker

Categories