This enhancement makes the control number field in the purchase order file available for macros. Previously, the POCNO field (control number) in the purchase order was not available for macros. This enhancement allows the user to create macros that use this field. This enhancement provides the user with the ability to keep track of control numbers in their journal entries.

The programs impacted include:

• CEA502B1, ACP Engine Resolution Program
• CGL091B, ERPLX ACP File I/O Program

Field expansion can impact programs, integrations, reports, forms and more! Take a look at the chart below to see what fields are expanded in LX 8.4.

To discuss your upgrade to the latest version of Infor LX, contact Frank Petrasio.

In LX 8.4, an enhancement has been included to allow for the expanded Company fields to have the leading zero truncated.

To trim leading zeros, CEA515B is called during macro resolution to trim the leading zero based on the position in the Zero Trim file (GZT). The Zero Trim file contains all the company number fields currently defined in the CEA Cross Reference fie (GXM).

This enhancement provides year over year comparison in financial reports and eliminates the need to setup new companies in programs such as Alias Definition. Financial programs trim the leading zero on Company fields, such as Company 010, on subsystem transactions to process as Company 10 during CEA macro resolution. Clients who prefer to retain the Company value as 010 on financial reports can clear the GZT file.

Pick Release by Line has been modified to prevent Line Splitting for warehouse orders. This preserves the quantity integrity between what the customer ordered on the original customer order line and what will be shipped on the warehouse order line.

To discuss your upgrade to the latest version of Infor LX, contact Frank Petrasio.

For various month/period end programs, the purge function is now optional.

Scope:

INV903, Inventory Month End Close, optionally purges both inventory records as well as customer invoices. Some applications already have a flag or option for purging (for example, ACP900) and other applications are stand-alone. If you do not want to purge, do not run these programs: Order Purge and Close, ORD900, Close Quotes, ORD930, and Delete RMAs, ORD935. Now there are options on whether to purge records during the month end or period end programs.

The Benefits include:

• Flag or option added to allow the user to decide whether to perform month-end function with or without purge.

• Allows for month-end processing without purge.

• Improves efficiency of month-end processing.

Impact:

This enhancement includes these programs or areas:

• INV903, Inventory Month End Close

• ACR900, A/R Period Close

• CST900, PRF900, SFC900 Shop Order Close

The final step in Cycle Count processing is to maintain the (ICY) Cycle Count file. This history file increases in size with each posting session. It is up to users to purge the historical data that you no longer need. Previously, INV015 Cycle Count Purge by date only allowed users to purge the cycle count file by date. Now, additional selection criteria have been added that allows users improved ways to control records they may want to purge.

In addition to assigning lot numbers in Shop Order Entry/Maintenance (SFC500) after the shop orders have been released, users can now pre-assign lot numbers during the Multi-level Shop Order Release process (SFC530) and the Multi-Level Backflush process (LMP600) for sub-assemblies that are lot controlled items. The user has the choice of using the parent lot ID, the next sequential generated lot ID, or not pre-assigning lot IDs. Multiple items per lot must be installed to use the parent lot number option.