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

George Moroses

Infor LX & BPCS Finance Tip: AR Aging

An ACR system parameter allows you to specify whether to measure invoice age from the date on which you create the invoice, invoice date, or the date on which the invoice is due. You can set up a separate terms code for each customer on the system to set the basic terms of payment for that customer. For example, this term could specify the number of days an invoice can be due before it is considered past due and the number of days that a discount is available. The system uses the terms code data to calculate invoice due dates and uses system parameter information to age invoices. Whichever date you specify Accounts Receivable | Run Instructions | 27 ACR Overview to measure invoice age from, the age of an invoice is defined as the number of days between that date and the current processing date.

You also use the Accounts Receivable System Parameters program, ACR820D, to establish five generic aging buckets for your receivables. To determine the time length for each of these buckets, specify the number of aging days for each bucket. The number of aging days aging is the difference between the invoice aging date and the current processing date. You can set the time periods and assign names to each bucket according to your needs.

Each time you generate any of the receivable Trial Balance reports, the system recalculates the age of every invoice. If you use calendar months as financial periods, change the bucket definitions each month to reflect the appropriate 1-month bucket, 2-month bucket, and so on. If you use an aging system based on days, like the one described in the preceding paragraph, you do not need to change the bucket definitions.

Note that you can process future dated invoices if you use a negative age bucket and specify negative aging days.

Previous Article Infor LN & Baan Finance Tip: What Can You Do in the Financial Statements Module?
Next Article Infor LX & BPCS Materials Tip of the Week: Drop Shipments
Print
18923 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

Theme picker

Contact author

Please solve captcha
x

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

Ensuring access to historical logistical and financial transaction information for your employees is crucial. However, before proceeding with archiving or deletion, it's essential to evaluate the necessity of retaining this data. Baan and Infor LN (ERP LN) offer standard archiving sessions within major modules that typically handle a significant volume of historical transactions. These sessions are designed to transfer historical data to an archive company before deleting it from the operational company.

When it comes to archiving sessions, you have three primary options:

Many transactions in all kinds of modules use order numbers or serial numbers. These order numbers are most often automatically generated. In the Number Groups (tcmcs0151m000) session you can define groups of order numbers used for dedicated areas. A Number Group is a group of the first free number series that you can assign to a specific use. All the numbers that Infor LN generates in the number groups that are dedicated to the same purpose are unique.

All the first free numbers are stored in the table tcmcs050.

As many different processes can request a free number from the number groups, we often see delays in the performance, due to locking on the first free number records. This locking issue can have a severe impact on the performance of huge batch-type transactions, but also on the performance perceived by individual users in many areas in LN.

For example:

First89101113151617Last

Theme picker

Categories