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

BPCS/LX Tip of the Day: Inventory Management

Anthony Etzel 0 73224 Article rating: No rating

Establishing the Quantity On-Hand and the Quantity Available.

LX maintains buckets for information associated with the following inventory transactions for each item:

  • Opening Balance
  • Issues
  • Receipts
  • Adjustments
  • Allocations for the Customer
  • Allocations for Manufacturing


The on hand quantity does not include any allocations. To arrive at the on hand quantity, start with the opening balance, less any issues, plus any receipts, then add or subtract any adjustments. Available inventory is the on-hand less any allocations.

 

 

Baan/LN Tip of the Day: Chart of Accounts

Kathy Barthelt 0 106311 Article rating: No rating

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.

BPCS/LX Tip of the Day: Cycle Counting Part 2

Anthony Etzel 0 74872 Article rating: No rating

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/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 103023 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 81609 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 108959 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 81233 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.
First116117118119121123124125Last

Tips:  LX | BPCS | M3

Improves control over PO costing changes during invoice entry by replacing passive warnings with an intentional override action.

  • In ACP500D3 (Invoice Entry PO Costing), users previously could unintentionally accept changes by pressing ENTER, even when quantity to cost or amount to cost values had changed.

  • A new “F14 to Override” warning message replaces the old message:
    “Details have changed. Press enter again to accept data.”
    This ensures users acknowledge and confirm significant changes explicitly.

New System Parameter:

  • “Apply GRN Costing Tolerance for PO Costing” (optional):

    • Within tolerance: Displays the original message —
      “Details have changed. Press enter again to accept data.”

    • Outside tolerance: Triggers the new override requirement —
      “F14 to Override”

Benefits:

  • Enhances oversight and reduces unintentional cost acceptance.

  • Enables better control of PO costs when invoice details differ from expectations.

Last

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Defining “Unavailability” in Infor LN

This topic describes the definition of temporary unavailability for resources in a calendar.

Use one of the following sessions:

  • Recurring unavailability
    For recurring unavailability, such as national holidays, define the recurrence in the Recurrences (tcccp0143m000) session. Add that recurrence to the applicable calendar and availability type in the Calendar Recurrences (tcccp0144m000) session, and clear the Available check box for the unavailable days.
    With calendar recurrences you define recurring exceptions in a calendar, and set a time schedule for daily, weekly, monthly, or yearly unavailable time in one action.
  • Unavailable days for all availability types
    To define occasional unavailability, such as a department trip, use the Calendar Non-Available Days (tcccp0119m000) session. What you define here applies to all availability types.
     
  • Unavailable days for a specific availability type
    To define unavailability for a single day, complete the following steps:
  1. Start the Calendar Working Hours (tcccp0120m000) session.
  2. Find the applicable calendar and availability type, and clear the Available check box for a working hours type on the relevant date.
  • Unavailable during a part of a day
    To indicate that part of a day is unavailable, use the Calendar Recurrences (tcccp0144m000) or the Calendar Working Hours (tcccp0120m000) session to specify the time intervals that are available. All other times are considered unavailable. You cannot directly specify an unavailable time interval.

If you defined unavailable dates in the Calendar Non-Available Days (tcccp0119m000) or the Calendar Recurrences (tcccp0144m000) session, in the Calendar Working Hours (tcccp0120m000) session, click Update Calendar.

Note:

  • Unavailability always applies to entire days. If the Calendar Working Hours (tcccp0120m000) session contains multiple time intervals for a single date, and the Available check box is cleared for some intervals and selected for other intervals on the same day, the entire day is unavailable.
  • A calendar recurrence that makes a day unavailable has no effect on the availability of that day in the parent calendar.


It is not useful to define a special availability type for unavailability, because Infor LN does not maintain and update the working hours and the capacity data of a calendar in the Calendar Working Hours (tcccp0120m000) session based on non-available availability types.

Previous Article Infor LN & Baan Tip: Porting Set Issues
Next Article Infor ERP Tip of the Week: 5 Steps to Managing Sales Tax
Print
28306 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories