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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

If you have a parts warehouse and prefer to use SIC for planning (re-order point) but need to use MRP/MPS planning for production, create a non-nettable warehouse for the parts warehouse and run the SIC plan against that warehouse.

When running the SIC plan, be sure to set the Order System to “MPS to MRP” for Baan IV and to “Planned to Planned” for Baan V and LN.

Using this method you keep the parts inventory out of the production planning and in the hands of the parts warehouse planner.

In Baan IV, a distinction is made between the actual ERP system and a separate planning tool which contains the Constraint Planning package. This tool was intended to work with any ERP system, not just with Baan IV. The Enterprise Planning package is now considered to be a package like any other package in Infor LN.

Users of Baan IV could choose whether they wanted to plan their supply in one of the following ways:

  • By using the MPS and MRP modules in the Manufacturing package.
  • By using the RPD and RMP modules in the Constraint Planning package.

Users of Infor LN can only use the Enterprise Planning package. The distinction between the MPS items and MRP items has been abandoned. In Infor LN, all items can be planned by using a combination of master-based planning methods and order-based planning methods.

First134135136137139141142143Last

Theme picker

Categories