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

George Moroses
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: Infor LX & BPCS Cycle Counting Selection Process

The cycle counting sub-system in Inventory Management determines which items are selected for cycle counting based on the following criteria:

  1. Cycle Counts/Year: The system calculates the cycle count frequency for each item using the "Cycle Counts/Year" field in the Item Master file (optional).

  2. Last Cycle Count Date: If you use locations, this date is found in the Location Inventory file (ILI), and if you don't, it's in the Warehouse Inventory file (IWI).

The system adds the calculated cycle count frequency to the last cycle count date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it's greater, the item is not due for cycle counting yet.

Additionally, an item is automatically selected for cycle counting if the Cycle Flag field in the ILI/IWI record contains 'Y.' This flag indicates that the item's on-hand balance has gone negative since the last cycle count, even if it's not negative at the time of selection. The programs INV500D, INV510, and BIL540 can set this flag.

You can further narrow down the selection of items by specifying item number or warehouse limits.

Previous Article "Apologies, boss, but at the moment, we are unable to contribute to advancing the business."
Next Article Infor LX & BPCS Tip: How to handle “ZERO COST” items
Print
23115 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

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.

Last

Tips: LN | Baan

Categories