Infor ERP Tips and Infor ERP News for Infor LX, BPCS, Infor ERP LX, Infor LN, Infor ERP LN, Baan, Infor M3, and Movex

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

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 158692 Article rating: 5.0

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning
    (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: Cycle Counting Part 1

Anthony Etzel 0 86713 Article rating: No rating

Understanding: The Cycle Count Transaction

If you rely on BPCS to provide you with a cycle count list, the number of items could vary from day to day from a few items to count, to several. So the person doing the cycle counting may spend a few minutes to a few hours counting items. After the cycle count is complete, the balances are not changed until the reconciliation is complete. This process could take some time before the balances are changed.

The cycle count transaction process is similar to the physical inventory transaction process.

Baan/LN Tip of the Week: GRINYA

Kathy Barthelt 0 177432 Article rating: 3.0
GRINYA is one of the more complex issues in ERP Finance. GRINYA is the tracking via ledger account of the value of items received on a purchase order that have not been matched to a supplier invoice.

Baan solutions for Baan IV and V were incomplete. To take full advantage of the current GRINYA reconciliation process, check Infor solution #107147, which contains the GRINYA user manual and a link to download the software for your version of Baan. For ERP LN, look at Document Code U8942C US.

It is called User Guide for Reconciliation and Analysis. If you are not running the latest GRINYA solutions, patching will require a good amount of time in filling the Interim tables this solution runs from. Infor has posted several procedural write ups, so check the Support Site and read up before tackling this for the first time.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 86469 Article rating: No rating
For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

BPCS/LX Tip of the Week: The Item Master Requirements Code

Anthony Etzel 0 82779 Article rating: No rating

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).
 

Other options for the field are:


1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.

Grindmaster Cecilware Selects Crossroads RMC For Baan IV / Davisware Integration

Crossroads RMC 0 42942 Article rating: No rating

Grindmaster Cecilware, a leader in the development of products for the food and beverage industry, has selected Crossroads RMC to integrate their Baan IV system to Davisware Global Warranty. Davisware is an electronic customizable online solution that fits almost any warranty process. Grindmaster’s customers will be able to access the Davisware software online and process warranty claims which will then automatically feed back into the Baan IV system for further review and processing. The integration is expected to go live in Q1 of 2015.

First128129130131133135136137Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

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.

Print
27961 Rate this article:
4.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

x

Categories