This enhancement prevents users from voiding invoices after they have been selected for payment. If a user selects an invoice for payment and another user voids the invoice during the payment process, it can produce erroneous and duplicate records. The ACP500 programs were modified to check the status of an invoice before it can be voided. If the invoice has been selected for payment, a message is generated, and the invoice cannot be voided.

Automatically synchronize security changes from LX to IDF, replacing CPYSECIDF. This new process synchronizes users in IDF with those in core LX security whenever a user’s security settings are changed. When a user is deleted from an LX environment, they can also be automatically removed from the IDF environment. Changes to a user’s access to programs in LX are mirrored in IDF. Access to Companies, Facilities, and Warehouses are also synchronized. Additionally, when Business Roles or Business Units access is changed, all users assigned to those roles or units are updated in IDF security.

In the Shop Order Selection program, action 3=Copy is available. This action allows copying any shop order except for flow orders or campaign orders. Instead of copying from the parent item's bill of material and routing, the new shop order’s materials and operations will be copied from the selected shop order. Note that if the existing shop order is linked to a customer order or line, this linkage will not be copied to the new shop order.

Unlock industry capabilities

The latest version of Infor LX, release 8.4.2, provides core enhancements, an expanded database, and global modernization to meet market changes.

• IDF serves as a rapid development platform with extensibility that enables release transparency and allows your IT team to eliminate legacy queries and custom reports

• Advanced functions like embedded warehouse management, collaboration with logistics server providers and suppliers, and vendor-managed inventory are all included as standard and designed to support all of your supply chain needs

• Embedded tools like document management, notifications, and workflows improve collaboration and productivity across teams

Finance: Propagating Unused Sub-Accounts

You can use this procedure to find accounts that have a valid sub-accounts group but no corresponding general ledger chart account records. This action creates the general ledger chart account record for the account and sub-account combination. This action does not add the accounts to charts.

1. Select Financials > Global Ledger > Setup > Finance Enterprise Group > Maintenance.
2. Open the finance enterprise group and click the Sub Account tab.
3. Select Actions > Propagate Unused Sub Accounts.
4. Select the finance enterprise group and click OK.

Sub-accounts are added according to group if they have been defined on the accounts. The resulting account can be added to the charts.

Operations: Best Practices for Purchase Order Archiving / Deleting

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:

• The linked warehouse order is closed but cannot be removed.
• The purchase order is linked to a PCS pr

 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).

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.