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 Week: Using Pre-Assigned Lot Numbers

Anthony Etzel 0 55806 Article rating: No rating

Some items in the manufacturing process may require a lot number. A quick and easy way to release the Shop Orders with lot numbers is by using the Multi-Level Shop Order Release.

Simply select the end item from the selection screen and use action 10 for the multi-level order release. At the bottom of the release screen is the field “Pre-Assign a Lot Number to Shop Orders”. Select 1 for the pre-assigned lot number assignment option.

This option will use the pre-assigned lot number on the shop order, if the lot number exists. If the lot number does not exist, the system will automatically create a lot number and assign it to the shop order for all items that are lot-controlled.

CST Adds Warranty Service Claim System to Dealer Portal for LN

Crossroads RMC 0 32582 Article rating: No rating

Crossroads RMC has once again partnered with Xenitel Managed Service Solutions and CST Industries to create a warranty service claim system for CST’s dealers. The project will provide a way for dealers to create a “warranty request claim” from within the dealer portal, defining the customer and product, and parts that failed, and selecting what parts they are claiming for replacement to install the replacement part. This service will be offered in addition to the parts online ordering system previously developed for CST. 

 

CST is a global leader in the manufacture and construction of factory coated metal storage tanks, aluminum domes and specialty covers.

Baan/LN Tip of the Week: How Accurate is Your Inventory?

Kathy Barthelt 0 52684 Article rating: No rating

Just a refresher on a tip I’ve shared previously from Supply Chain Technology Bulletin regarding how to attain greater inventory accuracy. I thought it would be worthwhile to share again:

  1. Record data regarding your inventory as soon as the items arrive at your door / receiving dock. With information, you can make decisions. Without it, you waste money, time, and effort.
  2. Leverage data collection, label generation, and RFID solutions to make your life easier.
  3. Set inventory accuracy goals for the business and for employees.
  4. Train your employees so they know what is expected of them, and how to best perform their job and therefore how best to maintain accurate inventory counts.
  5. Count the inventory – and do it regularly. Find a method that works best for your employees, and for your business.

BPCS/LX Tip of the Week: How Accurate is Your Inventory?

Anthony Etzel 0 67389 Article rating: No rating

Just a refresher on a tip I’ve shared previously from supply Chain Technology Bulletin regarding how to attain greater inventory accuracy. I thought it would be worthwhile to share again:

  1. Record data regarding your inventory as soon as the items arrive at your door / receiving dock. With information, you can make decisions. Without it, you waste money, time, and effort.
  2. Leverage data collection, label generation, and RFID solutions to make your life easier.
  3. Set inventory accuracy goals for the business and for employees.
  4. Train your employees so they know what is expected of them, and how to best perform their job and therefore how best to maintain accurate inventory counts.
  5. Count the inventory – and do it regularly. Find a method that works best for your employees, and for your business.

BPCS/LX Tip of the Week: User Defined Transactions

Anthony Etzel 0 57590 Article rating: No rating

When to use a user-defined inventory transaction

ERP LX (BPCS) provides you with the flexibility to create inventory transactions without program modifications. The typical transaction types are defined with effects set on how the transaction will impact inventory balances.

Perhaps you want to process a customer return and don’t want the inventory to be impacted. You can create a user define transaction effect to allow the customer receipt and not update the inventory balance.

Baan/LN Tip of the Week: Month End – Miscellaneous To-Do’s

Kathy Barthelt 0 54845 Article rating: No rating
  • Print Sales Order History Information
    • all invoices processed through sales
  • Check Inventory Valuation
    • this should tie out to your inventory accounts
  • Print Integration Information
    • see all postings from WIP to finished goods
  • Print G/L Transaction Information
    • print specific transaction types for any GL account
  • Print Lot Control Information
    • will show where serial numbers were used

Baan/LN Tip of the Week: GRINYA Reconciliation – What Could Go Wrong?

Kathy Barthelt 0 57041 Article rating: No rating

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or Infor LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

BPCS/LX Tip of the Week: Inventory Control

Anthony Etzel 0 57829 Article rating: 1.0

Is Lot Control necessary?

Certain industries require lot control, where others may find it an option based on how they want to trace the material used in a product in the event of a defect, or recall.

LX provides tight lot controls and flexibility with lot number assignments. Shop orders can have a pre-assigned lot number, or a lot number can be automatically assigned when the item is produced. You can also assign a specific lot number for the entire shop order, or for each item/quantity reported against a shop order.

First105106107108110112113114Last

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

Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for OPERATIONS: Using Country of Origin for Purchase Orders
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28393 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories