The Infor Development Framework (IDF) is a significant component of Infor's efforts to modernize its Infor LX application. IDF aims to enhance the user experience by introducing a task-oriented approach to accessing information within Infor LX. It is designed to replace LX Inquiry screens. Here are some key points about IDF:

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.

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)

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:

• The source financial company.
• The destination financial company.
• The transaction type and series.
• The ledger account and dimensions.
• The transaction currency.
• The fiscal year and the financial period, the tax period, and the reporting period.
• The integration document type and the Debit/Credit indicator.
• If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.