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: How Items Are Selected for a Cycle Count

The Cycle Counting Sub-System Within Inventory Management

The system uses the following information as the basis for cycle counting selection:

  • Cycle Counts/Year: The system calculates the time between cycle counts based on your entry in this Item Master file field for each item (optional).
  • Last Cycle Count Date: This date is in the Location Inventory file, ILI, if you use locations, or in the Warehouse Inventory file, IWI, if you don't.

The system adds the time between cycle counts (calculated as described above) to this date. If the result is less than or equal to today's date, the item is selected for cycle counting. If it is greater than today's date, the item is not selected, it is not due yet for cycle counting.

There is another special condition that causes an item to be selected for cycle counting. If the ILI/IWI record of the item has a Y in the Cycle Flag field, the item is selected automatically. This flag indicates that the item's on-hand balance has gone to a negative value sometime since the last cycle count. That applies even if the value is not negative at selection time. The programs that can set this field are INV500D, INV510, and BIL540.

You can also limit the items selected for counting by specifying limits of the item numbers or warehouses to be searched.

Previous Article Mitigating Risk With Your Infor ERP
Next Article Infor LN & Baan Tip: Project Status Options
Print
15039 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

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

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:

1345678910Last

Theme picker

Categories