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
/ Categories: Infor LX & BPCS Tips

Infor LX & BPCS Tip: How to handle “ZERO COST” items

When I try to enter a 3-way match invoice with zero cost items, I get an error 'Must have value/cost entry.

Resolution
ACP500 requires a positive value to create a 'C' transaction when entering a 3-way match invoice. If you are receiving inventory items for free (no charge) and have a purchase order for it and need to include the quantity in inventory, you should first receive your items through PUR550 using something like a 'U' transaction. Then, you would enter a 'C' transaction with the quantity and zero cost through PUR550. This will change the status of the line in the HPO file to '3', fully received and costed. Once this is completed, you will be able to enter an invoice for your zero-cost item through ACP500 without getting the error message 'Must have value/cost entry.

Previous Article Infor LX & BPCS Tip: Infor LX & BPCS Cycle Counting Selection Process
Next Article Infor LN & Baan Tip: Why was the session "General Ledger Diagnostics Workbench" built?
Print
11504 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.

123578910Last

Theme picker

Tips: LN | Baan

When attempting to post to a ledger account, users may occasionally encounter an error indicating that the ledger account is blocked. To resolve this issue, navigate to the Chart of Accounts session (tfgld0508m000) and select the Miscellaneous tab. Once there, review the Blocking field. The available settings are:

  1. Free
  2. Blocked for manual input (integration transactions and other automatic transactions can be posted with this setting)
  3. Blocked for all purposes.

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:...


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value...


TECHNOLOGY: Infor LN Rest API
Frequently Asked Questions (KB2316174)

123578910Last

Theme picker

Categories