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: 3-Way Match - A validation step when paying vendor invoices in ACP500

The validation compares the order quantity and price from the purchase order, the quantity received from the ITH record, and the quantity and price on the vendor invoice. The PO, the receipt, and the invoice are the three “legs” of a 3-way match. If all three match, you have a valid invoice transaction. If the price you are about to pay does not match the price agreed on the purchase order, or if the quantity you’re about to pay for does not match what you ordered or received, the ACP500 user will want to review the discrepancy before paying the invoice. There can be legitimate reasons for a discrepancy, such as needing to prepay an invoice for an item to be received in the future. The 3-Way Match process lets the user take those extra validation steps before making the payment.

Previous Article Infor LX & BPCS Tip of the Week: Credit Card Processing Within LX
Next Article Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)
Print
23326 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

Serial and Lot are additional characteristics/properties of Items that can be used to uniquely or collectively identify and track the item along with its Item code. Any Item can be made as Serialized and/or Lot controlled by choosing options "Serialized" and "Lot Controlled" in Items-General session under traceability section on the Details tab.

Further in Items-Warehousing data under the Identification tab, you can enable "Lot Tracking", "Lot in Inventory", "Serial Tracking" and "Serial in Inventory" which enables tracking of the Items. You can also define if the Item is "Serial/Lot not in inventory" then where you want to record the serial and lot details in the transactions like "Direct Delivery", "Receipt", "Transfer", "Register during As-Built, Service and Maintenance".

Below are some topics related to Serialized and Lot Controlled Items that will be useful...

Yes, you can backflush an item with an estimated quantity = 0.00 if you haven't already backflushed the order. For example, you had an order with one component, you reported the quantity at the operation or order level and ran the backflush. Now you realize you need another component added. In this example, the order has already been backflushed, so if you were to add a second component, run backflushing, nothing would happen.

Backflushing is based on the 'quantity to backflush' in report operations or report orders complete. When the quantity is backflushed....

First4041424345474849Last

Theme picker

Categories