Epicor ARM 2025.1.2 Release Guide

When importing approval tree reference data, certain entities, such as Category Group and Requisition Type (Custom Form), rely on identity-based references (IDs). A common issue arises when exporting the approval tree from one environment (e.g., Pilot) and importing it into another (e.g., Live). Since Category Group IDs and Custom Form IDs may differ between environments due to variations in data creation and order, this can lead to mismatches during the import process.

This improvement aims to enhance the import experience by providing greater control over how Category Group and Custom Form references are resolved.

When exporting the approval tree to JSON, the import_options section now includes two new properties that define how Category Group and Custom Form (Requisition Type) keys are matched during import:

Import by ID (default)

Import by Name

By offering both ID-based and name-based resolution options, this enhancement ensures a smoother and more flexible import process.

To improve the approval workflow and reduce unnecessary emails, the notification logic has been refined:

These enhancements streamline communication, reduce inbox clutter, and ensure approvers receive notifications only when necessary.

ARM now supports the ability to export, import, and update Locations, enabling users to easily edit and maintain location address data.

The following additional options have been added to the Requisition Type:

Additionally, a new setting titled ‘Use Requisition Line Custom Forms’ has been introduced with these options:

ARM has introduced its own ‘Active’ flag, allowing users to mark UOMs as active or inactive within ARM if they meet specific conditions. For example, only UOMs that are active and belong to an active UOM class in Kinetic can be set as active in ARM.

Inactive UOMs are automatically filtered out from selection in new documents.

Additionally, deactivating a UOM class will automatically deactivate all of its associated UOMs.

ARM has introduced its own ‘Active’ flag, allowing users to mark Categories as active or inactive within ARM if they meet specific conditions.

Two new permissions have been added to manage Standing Orders separately:

The Released By detail is now displayed on the Blanket Order Lines.

Key Epicor Tax settings are now integrated, providing a more intuitive and streamlined tax management experience within ARM.

ARM now displays the Created Date and Entry Person on the AP Dashboard.

The main document will show the created date and created by at the bottom right, and the export file now includes the created date and Entry Person detail.

The PO Line Supplier Part Number will now be displayed alongside the Part Number in the line-level details of the PO screen.

Additionally, the EDI SupplierPartID tag now includes both the Vendor SKU and Part Number.

This enhancement allows users to efficiently cross-check and reconcile received items with system records, ensuring a more accurate and a more streamlined receipting process.

A new column titled ‘Open Balance’ has been added to the ‘Send Reminder for Overdue Purchase Order Receipt’ scheduled job notification.

Only the Requisition Owner(s) whose PO lines are overdue will receive a notification, displaying their total PO amount and the corresponding open balance.

Additional fields have been added to the User Export and Import functionality for improved data management. They include:

A new ‘Job Title’ field has been added to the User and Requester functionality.

The ERP PO Number (E9PONumberReference) and Purchase Order Line note have been added to the PO report data set (HTML), enabling improved visibility and reference within the report.

Some OCR settings have been renamed, and default values have been updated to improve clarity for users.

A new setting titled ‘Ignore Mismatch Warnings’ has been introduced on the Due Date and Payment Terms. The system will determine whether to ignore mismatch warnings here. When checked, the system will ignore warnings if the value conflicts with a calculated/default value, thus allowing automatic invoice creation.

ARM now displays both the PunchOut UOM and ARM’s UOM on requisition lines.

Additionally, the UOM mapping logic has changed to improve accuracy and user control. When a PunchOut cart is imported into ARM the following logic is applied:

When a user adds items from a configured PunchOut site to a requisition, the UOM for an item may be missing a direct mapping to an ARM UOM, or there may be an existing mapping that the user wishes to replace.

Now, users can select an ARM UOM from the lookup to use for the relevant item.

At this point, if the user has permission to maintain PunchOuts, they are provided with the following options:

If a user accepts the option to update or insert, this will only occur upon a successful final PO EDI submission.

ARM now supports a new tolerance checking criterion: Extended Cost. This applies to both AP receipts and PO receipts.

The Buyer job in ARM now includes all buyers that the ARM integration account can read, regardless of their authorization status.

Additionally, both BuyerID and BuyerCode are available within the approval tree export functionality. The approval tree import function will use BuyerCode as the key to match buyers in ARM, ignoring BuyerID, thus aligning with Kinetic’s behavior.