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

Baan/LN Tip of the Week: Configuring Items in Infor LN

Kathy Barthelt 0 128096 Article rating: No rating

In Infor LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 88960 Article rating: No rating
In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Shop Order Status

Anthony Etzel 0 89677 Article rating: No rating

You can see the status of the Shop Order when using SFC300 Shop Order Inquiry. You want to be sure that your shop orders are at the correct status in order to report against them.

The following are the shop order status codes:

04 = The Shop order has been entered.

05 = The Shop order has been released and printed.

14 = The Shop order has been released, but not printed. If a shop order is at this status, you have released it and it is not printed due to a system failure, or the order has been put on hold.

XX = The Shop order is closed.

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

Anthony Etzel 0 93217 Article rating: 4.0
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.

Baan/LN Tip of the Week: What could go wrong with GRINYA?

Kathy Barthelt 0 119769 Article rating: No rating
One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Baan/LN Tip of the Week: Differentiating An Item By Supplier - LN

Kathy Barthelt 0 94286 Article rating: No rating

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

BPCS/LX Tip of the Week: Inventory Control

Anthony Etzel 0 97419 Article rating: No rating

In Infor LX you need to determine how inventory will be moved in and out of warehouse storage locations, and which of the following transactions to use for inventory control:


  • A transfer transaction can be used to move inventory from one warehouse location to another warehouse location.
  • A production receipt transaction is used to add inventory to a warehouse location.
  • A material issue or backflush is used to reduce inventory from a warehouse location.

New Definition of Insanity: Collect data the same old way

Anthony Etzel 0 96541 Article rating: 5.0

Just because you've always done it this way doesn't mean it's the best way. The old way of doing things may get the job done, but is the job being performed efficiently, accurately, and on a timely basis?

People resist change because there is an element of fear behind change and having to learn something new. Sometimes it’s just that you’re comfortable with how things are done, and you don’t see the need to make any changes. 


Are you stuck in manual?

First131132133134136138139140Last

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