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

BPCS/LX Tip of the Day: Inventory Management

Anthony Etzel 0 73358 Article rating: No rating

Establishing the Quantity On-Hand and the Quantity Available.

LX maintains buckets for information associated with the following inventory transactions for each item:

  • Opening Balance
  • Issues
  • Receipts
  • Adjustments
  • Allocations for the Customer
  • Allocations for Manufacturing


The on hand quantity does not include any allocations. To arrive at the on hand quantity, start with the opening balance, less any issues, plus any receipts, then add or subtract any adjustments. Available inventory is the on-hand less any allocations.

 

 

Read more

Baan/LN Tip of the Day: Chart of Accounts

Kathy Barthelt 0 106613 Article rating: No rating

Zero sublevel accounts are posting level accounts. All others are parent accounts. Once the balances have been updated in the child ledger accounts, the parents are automatically updated.

Inquiries and reports can be printed or displayed either by child accounts or by parent accounts. On line drill-down is possible from either child or parent.

Read more

BPCS/LX Tip of the Day: Cycle Counting Part 2

Anthony Etzel 0 75111 Article rating: No rating

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

Read more

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 103398 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

Read more

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 81925 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Read more

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 109368 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.
Read more

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 81494 Article rating: No rating
For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.
Read more
First116117118119121123124125Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Read more
Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Because I Care, Services News, Infor ERP Utilization Review, ERP Utilization Review & Process Improvement Consulting

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

Print
28419 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

x

Categories