Add function key / action code security to control who is authorized to create/revise/delete functions in ILM501 Inbound Delivery Maintenance.  With added Group Security, managers can control which users are authorized to create, change and delete deliveries in ILM501 Inbound Delivery Maintenance.

Finance: Cost Rollup by Effective Date
Allow the load standard cost from routing and cost rollup programs to process as of a specified effective date.  With the addition of an optional effective date parameter to prompt screens for cost rollup CST500 and load standards from routing CST600. If entered, only consider bill of material components and routing operations with effective and discontinue dates that make them effective as of the entered parameter effective date.

Operations: Outside Operation Purchase Order Include Vendor Item Number
Copy the vendor item number from the vendor quote to purchase orders created automatically from outside operations of shop orders. During the process of automatically creating purchase orders from outside operations of shop orders, copy the vendor item number from the vendor quote to the purchase order line. With this change, looking at a purchase order that was created automatically for an outside operation of a shop order, the vendor item number from the vendor quote will be visible on the purchase order line.

Technology: Group Security for ILM501 Inbound Delivery Maintenance
Add function key / action code security to control who is authorized to create/revise/delete functions in ILM501 Inbound Delivery Maintenance.  With added Group Security, managers can control which users are authorized to create, change and delete deliveries in ILM501 Inbound Delivery Maintenance.

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.