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 Week: Transaction Accounts – Commissions

Kathy Barthelt 0 38960 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.

BPCS/LX Tip of the Week: Vendor Maintenance Security Option for Company or Program

Anthony Etzel 0 27533 Article rating: No rating

The Vendor Maintenance Security option is in the Purchasing System Parameters program(PUR820D). The purpose of this program is to provide an additional security option for VendorMaster Maintenance. To access this program, the user selects the Parameters Generation option from the System Functions menu, SYS500. The user can modify the Vendor Maintenance Security parameter from PUR820D-04 in the Purchasing System Parameters program.This feature provides an additional security parameter for Vendor Master Maintenance.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: 6 Powerful Steps to Win With Automation

Anthony Etzel 0 25386 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.

Optimize Your Manufacturing Today!

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

Kathy Barthelt 0 40719 Article rating: No rating

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or 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.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: Purchase Order Receive All Processing

Anthony Etzel 0 23697 Article rating: No rating

With this enhancement, the Purchase Receipts screens are optionally shown with the quantity and weight fields populated with the open value on the purchase order.

Previously the user had tomanually enter the quantity received or, for a dynamic weight and measure items, the weightreceived for each line on the purchase order.

Now the screens are populated with the open valueand if the open value is the same as the value received, the user can simply accept the line.

Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: 4 Reasons You Need Timely & Accurate Data

Kathy Barthelt 0 39410 Article rating: No rating

Seems obvious – you want real time data and you want it to be accurate. Do you have the systems in place to allow for this?

Here are 4 reasons you need a data collection system:

  1. See the differences between actuals and standards
  2. Determine the source of project overruns
  3. Prevent mis-shipments to customers
  4. Avoid unnecessary reordering of parts

An automated data collection system will analyze your current data, allowing you to efficiently optimize your manufacturing and the benefits will be huge and far reaching.

Optimize Your Manufacturing Today!

RSS
First8283848587899091Last

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.

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.

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
45378 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories