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: Inventory Stocking Levels – Warehouses, Locations and Lots…Oh My!

The Infor LX system supports 4 levels of inventory. You can view summaries of stock at each level through the Material Status Inquiry program or through reports. Below are the 4 levels:

  • Item
  • Item + warehouse
  • Item + warehouse + location
  • Item + warehouse + location + lot

The lot number level and/or container of inventory can cross multiple warehouses and locations, for example, item + lot or item + lot + container. Locations exist within warehouses. There is no limit on the number of warehouses, locations, or lots that you can assign to an item.

Multiple Warehouses
You can assign as many warehouses as needed for any item. You can designate each warehouse as allocatable, allowed for order processing, or non-MRP, not used in the MRP netting logic. This allows your business to set up staging areas and quarantined warehouses. The warehouses can be physical or logical warehouses.

Multiple Locations
You can assign as many inventory locations as needed for any item. The location number is six characters long. This allows you to define sub-locations within a location, which can be an aisle, bin, or row.

The system stores item-warehouse combination inventory and allocation data. Optionally, sales history is available by item and warehouse in sales by units for the past twelve months. Total monetary amounts of sales by warehouse are also available in year-to-date, the last twelve months individually, and previous year-to-date.

Lot Inventory
On an item-by-item basis, the system requires the input of and performs tracking of lot numbers by inventory transaction. The system supports forward and backward lot traceability. The system provides inquiries and reports for the stock, allocation, and movement of inventory by lot. The system also automatically supports shelf life, expiration date, and reject data for each lot. The system automatically uses the expiration date in this allocation logic and MRP logic.

Previous Article Need Knowledgeable ERP Staff Quickly?
Next Article Tim Baker – Infor LX User Group’s Newest Board Member!
Print
24347 Rate this article:
4.0

Contact

George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Tips: LN | Baan

Use this session to define simulated purchase prices for purchased items per site.

Field Information:

  • Cost Calculation Code - price calculation code
  • Item

The raw materials, subassemblies, finished products, and tools that can be purchased, stored, manufactured, and sold.

An item can also represent a set of items handled as one kit, or which exist in multiple product variants.

You can also define nonphysical items, which are not retained in inventory but can be used to post costs or to invoice services to customers. The examples of nonphysical items:

  • Cost items (for example, electricity)
  • Service items
  • Subcontracting services
  • List items (menus/options)
     
  • ​Site - The site for which the purchase price is simulated.
  • Purchase Currency - The currency of the simulated purchase price.
  • Simulated Price - Purchase price

The simulated purchase price and currency are recorded twice.

  • Simulated Price Multi Currency - The purchase price in multiple currencies.

The simulated purchase price and currency are recorded twice. The amount in this field is related to the price of the supplier.

  • Unit - Purchase price unit
  • Cost Component - The cost component that must be of the type Material Costs.

Note: The cost component specified in this field does not become part of the standard cost detail structure if it is part of the cost component scheme of the selected item. If calculations are performed with a calculation code not used for actualization (simulations only), the simulated purchase price is mapped to the cost component defined in the records for this session.

Categories