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 39220 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 27700 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 25556 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 40825 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 23882 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 39669 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
First8384858688909192Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

George Moroses

Infor LX/BPCS Tips & Tricks for EXECUTIVES:

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track All Order Holds Added & Released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

Print
6289 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

x

Categories