Global Settings

Specifies whether to email the APInvoice Creator when one or more lines from their APInvoice has been denied during the approval process.

Yes

Global setting to control notifications sent in APInvoice workflow.

Yes

When this is set to Yes, the job [Sync Invoiced Receipts From Backend] can be triggered to run manually. Note that this job should be run for the first time when ARM is connected to the Epicor back-end system and then turned off.

No

The OCR solution being employed for AP Invoice.

None

Specifies the AP Invoices worklist folder for ARM to monitor.

Select a Storage Type (Provider) which is used to store attachments for documents in ARM.

There are three storage type systems to choose from, and the settings that go with each of these. For more details, see Setting the Attachment Storage Type.

LocalFileSystem

Specifies the text that appears on the Apply button throughout the application (Max length 12).

Save

Specifies the Budget Indicator text used to warn when a Requisition Line goes over budget.

Budget

Specifies the text that appears on the Cancel button throughout the application (Max length 12).

Close

Specifies the text that appears on the OK button throughout the application (Max length 12).

Save & Close

Specifies the text that appears on the Post button on the Receiving screen.

Receive

Specifies which of the buttons (OK, Apply and Cancel) to show throughout the application.

OKApplyCancel

Add from catalogue behaviour on change page.

If a user makes changes to a requisition and then navigates to another page, the changes are lost, saved, or the user is prompted - depending on this setting selection.

Options are:

See Requisition Page Navigation

Ignore entered values.

The maximum number of records Inventory Item job imports from the Epicor back-end to ARM on each run.

100

When set to "Yes": Part Classes not flagged for Requisitions shall not be integrated to ARM.

Any Part with no Part Class specified, or belonging to Part Classes not flagged for Requisitions, shall be considered a restricted Part.

Restricted Parts shall not be integrated to ARM.

Note: If a Part Class was originally flagged for "Requisitions" and then subsequently changed to not be flagged for Requisitions, any of the above data may have already integrated into ARM and will have records in the database which may be visible in the ARM user interface.

No

A flag to indicate that the page load times are displayed in the footer of each page.

No

A flag to indicate that the search times are displayed when performing searches.

No

Specifies whether to attach a copy of the PO to the PO Creation Notification Email.

Yes

Specifies the Maximum size, in Megabytes(Mb), of a file that can be loaded as an Attachment. This must be a numeric value.

10

Specifies the default value for automatically creating Purchase Orders from Requisitions that contain non-catalogue items

Yes

Select to preload search results on Add Catalogue Items search screen.

Yes

Default value for the Active flag on the ARM search screens.

Yes

Specifies the default value for the Allow Auto Send check box in a Requisition created from Change Order.

On

Specifies the default value for Allow Auto Send check box in new Requisitions.

On

Defaults the Requisition Line Type from the selected option. Options are:

Location

Specifies the way a search is performed. This applies to input fields on all Search pages. The options are:

Contains

Specifies the default sort order to be used when searching for Catalogue items. Valid values are:

PartNo

Default view mode for catalogue search screen. Options are:

table

The Requisition Due Date field defaults to today’s date plus Due Date Days from Today.

7

Enable On-charge Mark-up

A series of new fields has been introduced in the Requisition Line screen that enables Mark Up details to be captured at the time of Requisition request. Select Yes to utilize On-charge Mark-up.

No

The maximum number of records returned in one search result set.

25

Specifies whether Extended Cost is displayed on Requisition, PFO, and PO lines. (Extended Cost = Quantity x Unit Cost).

No

Specifies whether, across the ARM application, the Vendor Description is displayed. If you select No the Vendor Code will be used for display in ARM.

No

If Yes, the Vendor Group Description is displayed in ARM. If No, the Vendor Group Code is displayed instead.

No

Specifies where the Delivery Contact information will default from. Options are:

From Inventory Location

Specifies whether Delivery Contact information is recorded against the PO and displayed on the printed PO forms.

Yes

Category required on miscellaneous Draft Invoice lines.

No

Location required on miscellaneous Draft Invoice lines.

No

The message channel type which is being used. Possible value is Email, InApp

Notes:

Email,InApp

When set to Yes, any PO that is emailed to a supplier will also be CC’d to the email address configured on the PO Creator ARM User.

No

When set to Yes, any PO that is emailed to a supplier will also be CC’d to the email address of the Requisitioners.

No

Specifies whether the System Administrator Email Address will be copied in on the Delegation Email.

No

Notify Approvers on Auto-Advance Approval.

No

When set to Yes, integration errors will be sent to users defined in Email Integration Errors To.

Yes

The list of users who will receive emails when there are integration errors.

The name of Integration Manager Server.

'http://arm-integration-manager-api:8080'

Encrypted API Login for use in IM Controller Service.

abcdefg

Encrypted API Passwd for use in IM Controller Service.

abcdefg

Binding type of Integration Manager Service.

NetTcp

Port Number of Integration Manager Service.

17100

Specifies whether inventory transfers will be allowed.

Yes

Determines when validation of the Supply Location should occur.

Submit

Specifies whether the Auto Send check box in Requisitions is displayed.

Enabled

Purchase Order lines are ordered by PO Line Display Order on the screen and on the Print View.

Order by options are:

Select the option that makes it easiest to match items on the PO with goods received from the Vendor.

NOTES:

When the PO is integrated into Kinetic Purchasing, the PO Lines will be in line number order; this is not affected by the PO Line Display Order setting.

Line Number

Specifies whether the Destination Stock column is displayed on Documents.

No

Specifies whether the GL Account Code column is displayed on Documents.

Yes

Specifies whether the GL Account Description column is displayed on Documents.

No

Specifies whether item descriptions are displayed on requisition lines.

Yes

Specifies whether the On Order column is displayed on Documents.

No

Specifies the default whether the Source Stock column is displayed on Documents.

No

Specifies whether the UOM Code column is displayed on Documents.

No

Specifies whether the UOM description column is displayed on Documents.

No

Specifies whether the vendor currency is displayed on the requisition line.

No

Specifies whether Requisitions support line level locations. Also controls whether the Set Location button is displayed on Requisitions.

When this setting is enabled, the Receiving Location on each Requisition line is used to determine the approval chain. Combined with security based on Locations on User Profiles, this setting will affect search screen results and will also affect whether a user can view or perform functions on lines on a Requisition, PFO and PO.

Possible problem scenarios include:

Enabled

Defines how requisition lines are combined into PFOs. The options are:

If set to Vendor and Location, Requisition lines for the same Vendor with different receiving locations will be split out into separate PFOs.

If set to Vendor Only, all Requisition lines for the same Vendor will be combined onto a single PFO (regardless of different Receiving locations on each line).

If set to Do Not Combine, new PFOs will be created based on Requisition ID. PFOs will be split if there are different vendors on different lines but they will not be combined with existing PFOs.

Vendor Only

Timeout in seconds for sending email via SmtpClient or SendGridClient or MSGraphClient

60

The default Mailer system uses to send email.

The Global Setting Maintenance > Mail Settings Maintenances page opens. See Mail Settings Maintenance.

Global settings to control notification send in OCR Document workflow.

Yes

To trigger the resend of Draft Invoice validation notifications have been sent to users after the n day(s) set in this setting.

10000

Global settings to control notification send in RequestForQuote workflow.

Yes

Path to the root folder where all ARM reports are stored.

Reports

Specifies the full path of the email export directory, in which to place the Purchase Order files to email. Used with the Auto Email option. Ensure that the path ends with a backslash (\).

C:\Inetpub\ARM\Api\Content\EmailOut\

Specifies the default value for automatically emailing and printing (if configured) Transfer Orders by ARM Integration Manager.

No

Specifies the full path of the auto fax directory on the server, in which to place the faxable Purchase Order files. Used with the Auto Fax option. Ensure that the path ends with a backslash (\).

Select Yes to automatically print picking slip report when a new Transfer is created in ARM.

No

If Yes is selected, a Receipt Docket will be automatically sent to the specified printer when a PO is marked as Received.

No

Automatically print the Pick Slip Report for each open transfer order that has a part that was received in a Purchase Order.

Yes = On receipt of a PO, a check is performed to find any Open Transfer Orders containing a line for the parts/items that were just received. A pop-up dialog will inform the user that 'Open Transfer Orders containing parts in this Purchase Order receipt were identified. Related Transfer Orders will be automatically printed.'

Note: If a Transfer Order is identified more than once it may print multiple times. A print request will be sent to the ARM Print Server for each identified Transfer Order. The request will send the Crystal report defined in the Auto Print Picking Slip Printer setting. (If left blank, the Print Server will use the default printer configured on the ARM Application server for the user profile that the PBS ARM Task Agent runs under.)

No = No automatic Picking Slip printing will occur on receipt of a PO.

No

Automatically print the Pick Slip Report for each open transfer order that has a part that was received in a Transfer Order.

Yes = On receipt of a Transfer Order a check is performed to find any Open Transfer Orders containing a line for the parts/items that were just received. A pop-up dialog will inform the user that 'Open Transfer Orders containing parts in this Transfer Order receipt were identified. Related Transfer Orders will be automatically printed.'

Note: If a Transfer Order is identified more than once it may print multiple times. A print request will be sent to the ARM Print Server for each identified Transfer Order. The request will send the Crystal report defined in the Auto Print Picking Slip Printer setting. (If left blank the Print Server will use the default printer configured on the ARM Application server for the user profile that the PBS ARM Task Agent runs under.)

No = No automatic Picking Slip printing will occur on receipt of a Transfer Order.

Default is No.

No

The reporting service engine used to render report and PDF export. For on-premise value is default to SSRS. For SASS value is default to HTML.

HTML

The data model version to be used to generate PDF report from the HTML template (i.e PurchaseOrder).

Model version 1 is used by default.

Model version 2 is supported starting from ARM 2025.2.2 and is suitable for new implementations.

Customized PurchaseOrder report which uses model version 1 requires a technical upgrade if model version 2 is used.

1

Reporting Service Account

administrator

Reporting Service Domain

e102300rd

Reporting Service Password

abcdefg

Always copy tax information of the lines

Yes

Only copy data in Requisition header and ignore the lines.

No

A flag used to indicate that quantities are copied from Templates and Requisitions when using copy/template functionality.

Yes

Copy Requisition lines without recalculating their default values.

Notes:

No

Include attachments from the existing Requisition when copying.

This applies to both header and line level attachments.

Yes

Include custom data from the existing Requisition when copying.

This applies to both header and line level custom UDF field values.

No

Copy the [Use Default] value for both the main date fields and the requisition line date fields; otherwise, the requisition line dates will be recalculated with the default value.

No

Include notes from the existing Requisition when copying.

This applies to both header and line level notes.

Yes

Include recurring setting from the existing Requisition when copying.

No

Specifies whether an email notification should be sent to the Requisitioner each time a Requisition moves from one Approver to another. The default setting is Yes.

Emails are sent via the local mail server which is configured at installation time. Email details include a link to the actual requisition, PFO, or PO.

Yes

Specifies whether an email notification should be sent to the Requisitioner whenever lines are denied. The default setting is Yes.

Yes

Specifies whether an email notification should be sent to the Requisitioner when a Pro Forma Order is Created or Rejected. The default setting is Yes.

Yes

Specifies whether an email notification should be sent to the Requisitioner each time the Requisition’s status changes.

No

Specifies whether to email the next Reviewer when a Requisition is sent for Review.

Yes

Specifies whether a Requisition Requester will be notified each time one or more of the lines from their Requisition has been Approved.

Yes

Specifies whether a Requisition Requester will be notified when one or more lines from their Requisition has been denied during the approval process.

Yes

Specifies whether a Requisition Requester will be notified when a user submits a Requisition for them.

Yes

Specifies whether a Requisition Requester will be notified when the approved requisition is added to a Pro-Forma Order and when that Pro-Forma Order is created as a Purchase Order.

Yes

Specifies whether a Requisition Requester will be notified each time the status of their Requisition changes.

No

New users can self-register upon their first login to the ARM system.

No

If set to Yes then Blanket Order Releases will be received automatically.

If set to No then releases can be manually received at any time after their creation in the Blanket Purchase Order screen.

Yes

Specify whether ARM uses the backend ERP system or works as a standalone system.

Options are:

Kinetic

If set to Yes then the Due Date field on a Requisition will be mandatory and will default to blank.

If set to No the Due Date field will still be displayed but will default to the current date and will not be mandatory, i.e. the user can clear it.

No

The AP Payment Methods are automatically imported from Epicor. This setting controls whether or not they are to be used in ARM.

Yes

Enable specific buyer mapping when creating Purchase Orders.

Yes

Allow raising requisition with community care visit link.

No

Allow user to upload files to the OCR worklist folder from browser.

Yes

Enable discount on purchases.

No

Export system users to a file.

Yes

Enable bulk user creation by importing users from a template file.

Yes

Determines the sequence to apply GL Account Masks. Note that if a User has the option User Segments Override Defaults then the User Mask always takes precedence regardless of how it is set up here. For User Segments Override Defaults, see Maintaining Users - Assigned GL Accounts Tab.

See how to select the settings: Setting the GL Account Mask Sequence.

Vendor,User,Catalogue Item Location,Category,Location,Inventory Item Posting Code,Natural Account Options

Determines the sequence to apply GL References. Values to be sequenced are: User, Location, Category, Vendor, Natural Account Options.

Note: GL Account Mask Sequence and GL Reference Sequence are independent of each other. The GL Account Mask sequence will be added first and then ARM will attempt to add the Reference. If the Reference does not match, the GL Account Mask Sequence validation will fail and the user will be required to add a GL Reference manually on the Requisition line.

See how to select the settings: Setting the GL Reference Sequence.

Natural Account Options,Location,Category,Vendor,User

Enable Intercompany GL mode. Set by enabling or disabling this functionality during ARM Installation.

This field is read-only.

No

Main Menu ID of Epicor Kinetic.

See how to select the settings: Setting the Kinetic Main Menu ID.

MAINMENU

Enable Non-inventory mode. Set by enabling or disabling this functionality during ARM Installation.

No

Display and enable inline editing of Job information on Requisition Lines.

Yes

Automatically log user out after the specified System idle time. The default value is 20 minutes.

20

Specifies whether the Activity Code '1099' customisation is used. Used when the backoffice system is Epicor 7 only.

No

The full name of an existing NT group that will hold all eReq users. Format: YourDomain\YourNTGroupName eg: PRECISE\eReqCommonGroup.

The name of the company where the installation of ARM is located.

Specifies the Session Locale setting for the date and currency format eg: 3081.

0

The setting to turn on/off fast user switching for debugging purpose.

Yes

An encryted string that holds the current license information for this ARM installation.

abcdefg

The customer’s unique key for retrieving license information from the encrypted license.

The text description of the field displayed on RequisitionLine detail form.

Number Of Months Apportionment

The default value of the NoOfMonthsApportionment field. This must be a numeric value. For example: 12.

1

Run Password Encryption During Installation or Upgrade.

No

Specifies whether to use the field NoOfMonthsApportionment in RequisitionLine detail form.

No

Specifies which file types can be uploaded to ARM (extensions only and comma seperated eg: txt,doc,pdf,jpg).

png,jpg,jpeg,bmp,gif,csv,txt,log,lic,doc,docx,xls,xlsx,ppt,pptx,pdf,pfx,json

When Enabled, APM Project Cost Codes are visible on the purchasing line.

Enabled

Log system notifications

No

When Enabled, Requisition lines that have Project information are validated against a project budget.

Disabled

The banner text that displays on the top navigation bar of application. Usually to indicate the current application environment. Tip: Leave the value empty to indicate this is a production environment.

The banner image that displays on the login screen.

See Setting the Environment Login Banner.

Defines whether the budget is being checked as a total for the Project Phase or Cost Code, or if the budget is being compared for the Cost Type.

Total Budget

Defines if budgets for comparison will be: the standard Epicor Project Costs, the Precise APM Project Analysis, or the Precise APM Project Budget Spread.

Project Costs

Specifies which users will be available in the Reviewer List.

Options are: Requisition Related Users, All Reviewers.

All Reviewers

When a review is complete, these are the approvers who are notified.

Options are: All Approvers, Current Approver(s) Only, Current and Future Approver(s).

All Approvers

Specifies whether Custom Forms are enabled on the Requisition Line.

Options are:

Optional

Specifies whether Requisition Types are used within the Application.

No

Specifies whether the system integrates with the user information from Active Directory.

Off

The base URL for web api url. User should not change this value.

'http://qaarm2024-jsm:8040'

The full file system path on the Web Site directory e.g. C:\Program Files (x86)\Precise Business Solutions\ARM\Web Site\.

C:\Inetpub\ARM\

The base URL of ARM e.g. 'http://myserver/ARM/'.

'http://qaarm2024-jsm:8040'

Optionally override the default attachment file location to a specified network path.

Specifies whether or not to close the Purchase Order when lines are received (E9 and above only).

Yes

The name of the domain that ARM uses to interact with Active Directory.

The range to calculate project budget check for requisition line.

Full Budget

Enable old notifications to be cleared out after days set in 'Overdue Notification Period'

Yes

Specifies the time period to run the Clean Up of Notifications (in Days)

15

If this setting is set to Yes then the user will be required to enter the PO received date when posting.

No

Specifies whether a warning message should be displayed to a Purchase Order Creator when vendor minimum orders are not reached.

Yes

Specifies whether a warning message should be displayed to a Requisitioner when vendor minimum orders are not reached.

Yes