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
15802 Rate this article:
4.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.

123578910Last

Theme picker

Tips: LN | Baan

When attempting to post to a ledger account, users may occasionally encounter an error indicating that the ledger account is blocked. To resolve this issue, navigate to the Chart of Accounts session (tfgld0508m000) and select the Miscellaneous tab. Once there, review the Blocking field. The available settings are:

  1. Free
  2. Blocked for manual input (integration transactions and other automatic transactions can be posted with this setting)
  3. Blocked for all purposes.

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...


TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

123578910Last

Theme picker

Categories