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

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

Anthony Etzel 0 88323 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.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 184447 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.

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

Anthony Etzel 0 88956 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.

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 84025 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

Grindmaster Cecilware Selects Crossroads RMC For Baan IV / Davisware Integration

Crossroads RMC 0 43726 Article rating: No rating

Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to Davisware Global Warranty. Davisware is an electronic customizable online solution that fits almost any warranty process. Grindmaster’s customers will be able to access the Davisware software online and process warranty claims which will then automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q1 of 2015.

Huf North America Goes Lives With Next Phase of RMC3 Data Collection

Crossroads RMC 0 44558 Article rating: No rating

Huf North America, a global leader in the production of mechanical and electronic key systems, lock sets, steering locks, and remote control systems for the automotive industry, has gone live with phase 2 of their Crossroads RMC data collection implementation. This go-live included Report Orders Complete, Labor Reporting, Material Issue, Inventory Transfers, barcode label modifications, as well as custom applications for their Paint / Polishing operations. This go-live was paired with the expansion of Huf’s Plastic Injection Molding and Paint Facility in Greeneville, TN. The next phase of this project will include the extension of the Crossroads RMC solution into Huf’s facility in Mexico.

First129130131132134136137138Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Infor ERP Tips & Tricks: Gain Insight into Inventory Variances with Cycle Counting Analytics

Applies to: Infor LN Baan environments

Why this matters

Inventory discrepancies are often identified, but not fully understood. Without clear visibility into where and why variances occur, teams are left reacting instead of improving processes.

What this solves

The Cycle Counting Variances session (whinh8352m000) provides a visual way to analyze inventory discrepancies, helping teams identify patterns and root causes across warehouses and counting activities.


How it works

This session displays interactive bar charts that show:

  • Cycle counting variances by warehouse (default view)
  • Cycle counting variances by reason (drill-down view)

Users can:

  • Hover over bars to view variance details
  • Click into a warehouse to analyze variance reasons
  • Zoom and filter chart views for deeper analysis

Chart settings can be adjusted using the Cycle Counting Variances – Chart Settings session (whinh0901m500).

Variance values are calculated based on the valuation method defined in Inventory Revaluation Transactions (whina1522m000).

Key benefits

  • Visual insight into where variances are occurring
  • Root cause analysis by warehouse and reason
  • Improved inventory control through better understanding of discrepancies
  • Faster decision-making with interactive data views

Practical insight

Identifying a variance is only the first step. Understanding patterns—such as recurring issues by warehouse or reason—is what enables teams to reduce discrepancies over time.

When combined with NextTrack Insights dashboards, this data can be extended to:

  • Track variance trends over time
  • Highlight recurring problem areas
  • Provide real-time visibility beyond standard sessions

Getting started

The Cycle Counting Variances session can be accessed from the menu or your Role-Based Home Page. Crossroads RMC can help you extend this visibility with dashboards that bring together inventory, variance, and operational data into a single, actionable view.

Previous Article Infor ERP Tips & Tricks: Already Have Avalara? Integrate It with Your Infor ERP
Next Article Industry Insights: Simplifying Integration Across LN and LX with Infor ION
Print
2608 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories