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
11444 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
     

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

First3637383941434445Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories