Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Baan/LN Tip of the Week: 6 Powerful Steps to Win With Automation

Kathy Barthelt 0 39067 Article rating: No rating

1. Eliminate paper shop packet and distribution of the paperwork to the shop floor.     

2. Eliminate manual (paper-based) recording activities and the need to key in the transactions.

3. Easy electronic scheduling by sequence and changing job priorities.

4. Evaluate differences using actual times compared to standards.

5. Improve data accuracy and eliminate the need to chase and fix errors.

6. Practice Real-Time data reporting to monitor efficiencies and identify problems as they occur.

Read more

BPCS/LX Tip of the Week: Receiving to Inspection

Anthony Etzel 0 33039 Article rating: No rating

If the item being received needs to be inspected prior to being available for use, there are two schools of thought.The first is to receive the item to a QC hold location. The downside is the item will show up in on hand inventory.

A better method would be to do a PO receipt to inspection. Both Inv500 and Pur550 support this method. Now you have received the item without showing it in inventory. Only the PO quantity in inspection is updated. This method also allows you to create an Inspection Dispatch Report. After the QC process for the item is complete, then the transaction Receipt from Inspection to Stock is processed. That transaction then updates the PO quantity received field and the Item on hand field in inventory.

 

Read more

Baan/LN Tip of the Week: Transaction Accounts – Commissions

Kathy Barthelt 0 47732 Article rating: No rating

In Baan IV, if a link with Financials exists for commissions and rebates, invoices are created directly in the Commission Control System (CMS) module and posted to Financials. As a result, users must specify the ledger accounts that are used for posting commissions and rebates in the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session.

In LN, the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session is removed from the Commission Control System (CMS) module, because invoices are no longer created directly in the Commission Control System module.

Read more

Grindmaster-Cecilware Selects NextTrack Sales For Sales Analysis

Kathy Barthelt 0 31501 Article rating: No rating

Grindmaster-Cecilware (GMCW), a leading provider of products for the food and beverage industry, has selected NextTrack Sales to satisfy their sales analysis requirements. Integrated with their Baan ERP system, NextTrack Sales provides sophisticated pivot grid and charting functionality, and the ability to generate any number of views of the data, all without customizing their ERP system. Grindmaster’s VP of Sales said it was "the perfect fit for him, and covered all of his reporting needs".

Read more

Peerless Instrument Selects Crossroads RMC for Baan Data Collection

Kathy Barthelt 0 26616 Article rating: No rating

Peerless Instrument, a division of Curtiss Wright, has selected Crossroads RMC for Baan data collection. Peerless is interested in furthering the data collection partnership that Curtiss Wright began with Crossroads RMC 20 years ago. The data collection implementation will include Receiving, Material Issue, Inspection and Report Operations Complete, and is expected to be completed in July of 2016. 

Peerless Instrument provides state-of-the-art electronic components, systems, and software to the US military. Peerless' advanced instrumentation and control systems are not only used in Navy propulsion systems but provide sophisticated monitoring systems for the gas, oil, or petrochemical industries.
Read more
RSS
First120121122123125127128129Last

Theme picker

Tips:  LX | BPCS | M3

Previously, Material Requirements Planning (MRP) preferred practices meant that the component's due date was the same as the parent's shop order release date. Because MRP trends have changed, the preference for this due date is the day before the release date of the parent. Although Infor LX already has this functionality in Shop Order Maintenance programs (SFC500), users could not change how due dates were determined for lower-level shop orders in Multi-Level Shop Order Release, SFC530D.

This enhancement provides an additional parameter for Multi-Level Shop Order Release. This parameter allows the user to change how the due date of the child components is determined. The Multi-Level Shop Order Release, SFC5302, has a new parameter for shop orders. The Due Date of Children = Release Date of Prent (Due Date of Children) field allows the user to set the due date determined for multi-level shop orders.

Read more

This feature uses different exchange rates in the user's inventory processes by using new macros in Post Inventory to G/L, INV920D. INV920 used macros limited by the Override Exchange Rate parameter set on the book in Book Definition, CEA105D3. If the Override Exchange rate parameter is set to No, the macro uses the Rate Type of the Book. If the Override Exchange parameter is set to Yes, the macro uses the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Order Company. This enhancement provides macros that use the Rate Type of the Warehouse Company, Order Company, or the Book regardless of the Override Exchange Rate parameter in the Book.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Plan Codes

In Baan IV, plan items exist within the context of a plan code. A plan code includes only items of the MPS Item item type. Planned orders are independent of a plan code. Users can compare plan codes by means of the Plan Code Performance Comparison (cprmp4504m000) session.

The scenario concept in Infor LN replaces the plan code concept in Baan IV.

In Infor LN, the basic data for plan items is the same for all scenarios. However, users maintain not only the master plan within a scenario, but the planned orders as well.

For example, for each scenario, Users can specify:

  • Special demand for an item.
  • The availability of resources (in the Scenario – Availabilities (cprpd4160m000) session).
  • The sourcing strategies and supply strategies.

Users can compare scenarios by means of the Performance Indicators (cprao2201s000) session.

Previous Article Baan/LN Tip of the Week: Data Sizing Moving to LN
Next Article Baan/LN Tip of the Week: Purchase Inquiry
Print
45218 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

x

Categories