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

Infor LN & Baan Finance Tip: Unallocated Payment

How do I assign an unallocated payment to a purchase invoice when the document dates are not the same?

When trying to assign an unallocated payment, it is possible that the purchase invoice is not displayed in session Assign Unallocated / Advance Payments to Invoices (tfcmg2106s000), even though it is showing in the open entries. This can happen when the document date of the unallocated payment lies before the document date of the purchase invoice you want to assign it. There are 2 ways to handle this:

  1. Change the document date of the unallocated payment. This can be done by reversing the original document and creating a new one with a different document date.
  2. Create a new financial batch and use a transaction type of category Cashsubcategory Assign Advance/ Unallocated Payment. The date of the assignment will be the Transaction Entry Date of the batch. This way, the document dates can differ. Session Assign Advance/Unallocated Payments to invoices (tfcmg2131s000) will open. Chose the correct unallocated payment document and on top, click assign invoices to assign the correct invoice.
Previous Article Infor LX & BPCS Tip: What items should be M-P-S planned vs. M-R-P planned?
Next Article An ERP System Review is NOT a Report Card
Print
26385 Rate this article:
5.0
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.

1234567810Last

Theme picker

Tips: LN | Baan

 Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.
  • Purchase contracts must be archived before purchase orders can be archived.

You cannot delete a purchase order (line) if:

To increase the speed of sessions and processes slowed by large amounts of data, you can use table boosters. These speed up access to specific database tables by loading the table, or a specified part of it, into memory. Table boosters are defined in the Table Boosters (tcmcs0598m000) session.

Tables

Table boosters are implemented for tables. By default, table boosters are not active. When you access a table, LN builds a list of tables for which you can activate the boosters in the Table Boosters (tcmcs0598m000) session.

Note: You can only activate table boosters for tables that have been accessed at least once.

For more information, refer to the LN - Performance, Tracing, and Tuning Guide (U9357).

First567810121314Last

Theme picker

Categories