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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Baan/LN Tip of the Week: Setting Up Interest Invoicing

You can set up interest invoicing in Accounts Receivable and in the General Ledger.

To set up interest invoicing, use these sessions:

Invoice-to Business Partner (tccom4112s000)
For invoice-to business partners for which you want to raise interest invoices, select the Charge Interest check box.

Mapping Scheme (tfgld4573m000)
Use this session to define the mapping of the Interest Invoice / Revenues Analysis integration document type.

Interest Percentages (tfacr5102m000)
Use this session to define the interest percentages for each financial business-partner group, and for different periods of days.

Interest Invoice Related Data (tfacr5101s000)
Use this session to define whether interest must be calculated on unpaid invoices, partly paid invoices, interest invoices, and/or fully paid invoices. You can also indicate that LN must take advance payments, unallocated payments, and credit notes into account for the generation of interest invoices.

Optionally, set conditions
Example: LN only generates an interest invoice advice entry if these conditions are met: The total of all advice entries in one currency is higher than the allowed minimum amount of an interest invoice defined in the Minimum Amount for Interest Invoice field.

The invoice is overdue for a greater number of days than the number of days defined in the Minimum Days for Interest Invoice field.

Previous Article Top Ten Proven Tips to Maximize Uptime & Boost Performance
Next Article BPCS/LX Tip of the Week: Summarize Transactions by Account or Journal Source
Print
34333 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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

No matter how large or small your manufacturing plant is, efficiency and productivity relative to your capital investment are the keys to maintaining your competitive edge. Wasting time and money is not something anyone wants to do, but manufacturers need to be especially mindful of both and actively work to address any issues that lead to productivity or financial loss.

Source: https://www.onupkeep.com/blog/improve-production-efficiency/

In previous releases of LN, the Assembly Control Bill of Material (BOM) offered limited flexibility. For each end item configuration, users were required to create unique Engineering Modules, which are used to determine the assembly parts that are consumed in a specific Line Station during a specific operation.

If LN is integrated with Design Studio, previously called Infor CPQ, BOM structures can be maintained in Design Studio for Assembly Control. These structures can include non-configurable parts that are directly linked to configurable items. When communicating these structures to LN using the Assembly Control, Product Variant Structure (tiapl3510m000) session, the structures were rejected because non-configurable parts were not supported by the session logic.

In this release, BOM structures that include non-configurable parts can now be accepted in LN. Consequently, if LN is integrated with Design Studio, it is no longer required to use the Engineering Module. Using the Engineering Module has become optional.

First5152535456585960Last

Theme picker

Categories