Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News, Crossroads Connection

Zero sublevel accounts are posting level accounts. All others are parent accounts. Once the balances have been updated in the child ledger accounts, the parents are automatically updated.

Inquiries and reports can be printed or displayed either by child accounts or by parent accounts. On line drill-down is possible from either child or parent.

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

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.

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.

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.