The bolded view is the default view, which will determine the view will automatically display in when opened. 

Identifies the next Contract Number that will be auto assigned to new customer contracts. This is a text box that is required and defaults to 1000. If missing, the message "Next Contract Number is required" will be displayed on Save. When a new contract is added, the Contract Number is auto-assigned from this preference value and then the value is incremented by 1. This field is always enabled.

Database Field: ERPx_MFSysPreferences.PreferenceName = "NextContractNumber"

Identifies the how the system will react when a transaction exceeds a customer's credit limit. This is a single-select standard lookup that is required. It defaults to "Ignore" is always editable. The options include:

• Ignore: Nothing happens when a customer exceeds their credit limit.
• Warn: If a customer exceeds their credit limit, a warning will appear on Save. This is an alert, but it will not prevent the order from proceeding. 
• Place on Credit Hold: If a customer exceeds their credit limit, a warning will appear and the order will be placed on Credit Hold by applying the 'Hold Code' specified in the 'Default code for Credit Holds on Order' preference.

This lookup contains all the values in the SOCreditHoldOption Enumeration Class. 

Note: "When credit limits are exceeded" preference is set to "Place on Credit Hold" the preference "Default code for Credit Holds on Order" must be filled in otherwise a message “Default code for Credit Holds on Order is required.” will be displayed.

Database Field: ERPx_MFSysPreferences.PreferenceName = "CreditLimitExceeded"

Identifies the 'Hold Code' that will be automatically assigned to Orders when the Customer has exceeded their Credit Limit. This is a single-select standard lookup that is required when the 'When credit limits are exceeded' preference is set to "Place on Credit Hold". If missing and required, the message “Default code for Credit Holds on Order is required.” will be displayed on Save. This 'Hold Code' will only be applied if the 'When credit limits are exceeded' Preference is set to "Place on Credit Hold" and the transaction would put the Customer over their Credit Limit. This field is always editable.

This lookup contains a list of all the Sales 'Hold Codes' with a 'Transaction Type' of "Order".

Database Field: ERPx_MFSysPreferences.PreferenceName = "DefaultCreditHold"

Identifies the default Checkbook for a Payment Receipt when the Checkbook assigned to the Customer is not in the Customer Currency or the Home Currency. This is a single-select stand lookup that is not required and defaults as blank. This field is always editable.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Checkbooks.

Database Field: ERPx_MFSysPreferences.PreferenceName = "DefaultCustomerCheckbook"

Identifies the default Checkbook for a Cash payment received and entered on a Quick Sale transaction. This is a single-select standard lookup that is not required and defaults to blank. This field is always editable.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Checkbooks.

Database Field: ERPx_MFSysPreferences.PreferenceName = "DefaultCashPaymentCheckbook"

Identifies the default Checkbook for a Check payment received and entered on a Quick Sale transaction. This is a single-select standard lookup that is not required and defaults to blank. This field is always editable.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Checkbooks.

Database Field: ERPx_MFSysPreferences.PreferenceName = "DefaultCheckPaymentCheckbook"

Identifies the default Checkbook for a Credit Card payment received and entered on a Quick Sale transaction. This is a single-select standard lookup that is not required and defaults to blank. This field is always editable.

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Checkbooks.

Database Field: ERPx_MFSysPreferences.PreferenceName = "DefaultCreditCardPaymentCheckbook"

Identifies whether sales revenue is recorded in the GL net of delivered freight. This is a Yes/No lookup that is required. It defaults to "No" and is always editable. 

If set to "No", the journal entry to record the Delivered (Included) Freight on a Sales transaction will be calculated as follows:

• Debit the GL Account assigned as the Item's 'Freight Expense (Debit)' account for the amount of the freight.
• Credit the GL Account assigned as the Item's 'Freight Accrual (Credit)' account for the amount of the freight.

If set to "Yes", the journal entry to record the Delivered (Included) Freight on a Sales transaction will include an additional entry to reduce the Sales revenue by the freight amount and put those dollars in a Freight Revenue account as follows:

• Debit the GL Account assigned as the Item's 'Freight Expense (Debit)' account for the amount of the freight.
• Credit the GL Account assigned as the Item's 'Freight Accrual (Credit)' account for the amount of the freight.
• Debit the GL Account assigned as the Item's 'Sales' account .
• Credit the GL Account assigned as the Item's 'Freight Revenue (Credit)' account.

Database Field: ERPx_MFSysPreferences.PreferenceName = "GLSalesRevenueNetDeliveredFreight"

A Yes/No lookup to determine whether or not transaction numbers are managed by NorthScope or by the host ERP/Accounting system. The value defaults to "No" and is a required field. This field is always enabled.

• Yes: NorthScope looks to the host system tables to get the next transaction number.
• No: the next numbers come from the NorthScope tables.

A single-select lookup to specify the EDI duplicate PO number hold code for integrated transactions. This defaults to blank and is not required. This field is always editable.

This lookup contains all the values in the SOHoldType Enumeration Class.

A single-select lookup to determine how batches are built in the host ERP/Accounting system when transactions are integrated. This defaults to 'Transaction Status' and is required. This field is always editable. The available options are:

• Transaction Status
• Transaction Status and Site
• Transaction Workflow Step
• Inv. Doc ID, Order Type and Status
• Order Doc ID and Status

This lookup contains all the values in the SOBatchPreference Enumeration Class.

Note: “Ready to Post” is displayed as “RTP” in the host system batch name. 

A single-select lookup to determine whether or not you allow Lots to be over-allocated when the item is lot tracked. This defaults to "Do Not Evaluate" and is required. This field is always editable.

• Do Not Evaluate: Users can over-allocate a Lot (allocate more than is currently available).
• Available Only: Users will not be able to allocate more than the available quantity.
• Available and On Hand: Users will not be able to allocate more than the On Hand quantity. 

If an item’s ‘Manage Items By’ property is set to “Units Only” OR “Both”, NorthScope bases the over allocation validation on Units.  If the item’s ‘Manage Items By’ property is set to “Weight”, NorthScope bases the over allocation validation on Weight.

This lookup contains all the values in the MFNegativeInventoryLevel Enumeration Class.

Note: If Sales Order allocation preferences are set to either “Available Only” or “Available and On Hand” and a Sales order has been allocated prior to a user updating the Inventory “Negative Available Balances” property, it is possible to draw the lots negative.

A single-select lookup to determine whether or not you allow Lots to be over-allocated when the item is not lot tracked. This defaults to "Do Not Evaluate" and is required. This field is always editable.

• Do Not Evaluate: Users can over-allocate a Lot (allocate more than is currently available).
• Available Only: Users will not be able to allocate more than the available quantity.
• Available and On Hand: Users will not be able to allocate more than the On Hand quantity. 

If an item’s ‘Manage Items By’ property is set to “Units Only” OR “Both”, NorthScope bases the over allocation validation on Units.  If the item’s ‘Manage Items By’ property is set to “Weight”, NorthScope bases the over allocation validation on Weight.

This lookup contains all the values in the MFNegativeInventoryLevel Enumeration Class.

Note: If Sales Order allocation preferences are set to either “Available Only” or “Available and On Hand” and a Sales order has been allocated prior to a user updating the Inventory “Negative Available Balances” property, it is possible to draw the lots negative.

A single-select lookup to specify whether or not you allow over allocation. This defaults to 'No' and is always required. This field is always editable.

• Yes: Users may over-allocate and no messages will be displayed.
• No: Users will be unable to allocate more than what has been ordered.
• Warn: Users will receive a warning if they allocate more than what has been ordered but they can chose to over-allocate.

If an item’s ‘Manage Items By’ property is set to “Units Only” OR “Both”, NorthScope bases the over allocation validation on Units. If the item’s ‘Manage Items By’ property is set to “Weight”, NorthScope bases the over allocation validation on Weight. This preference applies to Orders, Invoices, Price Adjustments, and Returns.

This lookup contains all the values in the YesNoWarnValue Enumeration Class.

A single-select lookup to determine how NorthScope will auto-allocate Lots for sales order allocation.  This defaults to 'Date Produced' and is required. This field is always editable. The available options are: 

• Date Produced: NorthScope will allocate the oldest lots first based on product age.
• Smallest Quantity: NorthScope will allocate the Lots with the least amount of product in order to close them out first.

This lookup contains all the values in the SOAutoAllocatePriority Enumeration Class.

This preference determines whether or not allocated quantities for non-lot tracked items will automatically stay in sync with the ordered quantities on Sales Orders and Invoices. The value defaults to "No" and is required. This field is always editable.

• Yes: Any non-lot tracked item shipping from non-warehouse lot sites on a Sales Order transaction will automatically be updated on save to have its allocated quantities match its ordered quantities.
• No: Any non-lot tracked item shipping from non-warehouse lot sites on a Sales Order transaction must be manually updated for allocated quantities.

A single-select lookup to specify the default value for the ‘Use Favorites for’ field on the Customer Master File. This defaults to 'Customer' and is required. This field is always editable.

• Address: New Customers added in NorthScope will default to store Item Favorites independently for each address.
• Customer: New Customers added in NorthScope will default to store item Favorites at the Customer level and all Addresses will inherit their Item Favorites from the Customer.
• None: Item Favorites will not be defaulted.

Note: The most typical setting is "Address" since it provides the most granular level of detail.

A text box to specify how many times the item needs to be ordered before it gets added to the list of Item Favorites. This must be a positive, whole number and is required. If not assigned, the message "Add Item Favorites Ordered X Times is required" will be displayed on Save. This field is always editable. If it is set to 3, the Customer or Address would have to order the item at least 3 times before it will get auto-added to their list of Item Favorites. The purpose of this is provide a way to ensure the most typically ordered items are added to the Item Favorites and not items that may have been accidentally ordered or that are seldom ordered. 

Note: This preference is one of the two preferences that determine how items are automatically added to the list of Item Favorites. This preference works in conjunction with the Preference "Auto-add Item Favorites ordered in X days".

A text box to specify the time interval used to auto-add items to the list of Item Favorites. This must be a positive, whole number and is required. If not assigned, the message "Add Item Favorites Ordered in X Days is required" will be displayed on Save. This field is always editable. If it is set to 90, the Customer or Address would have to have ordered the item within the past 90 days for it to be auto-added to their list of Item Favorites. The purpose of this is provide a way to ensure that only the most typically ordered items are added to the item favorites and not items that may have been ordered a long time ago and are not currently being ordered.

Note: This preference is one of the two preferences that determine how items are automatically added to the list of Item Favorites. This preference works in conjunction with the Preference "Auto-add Item Favorites ordered X times".

A Yes/No lookup to identify whether or not Item Favorites are removed if they no longer meet the criteria that auto-adds them. This value defaults to "No" and is required. This field is always editable.

• Yes: Items that no longer meet the criteria that would auto-add them will be removed.
• No: Items that have been added as an Item Favorite can only be manually removed.

Note: The most typical setting is "Yes" since it keeps the Item Favorite list the most accurate.

This preference determines whether or not a printed Bill of Lading is required before an Order or Invoice can have their status change to "Approved". This value defaults to "No" and is required. This field is always editable.

• Yes: A BOL must be physically printed before the Order or Invoice can be Approved. If the BOL is not printed and someone tries to approve the transaction they will get a message indicating that the BOL must first be printed.
• No: Printing the BOL is optional.

Note: This should be set to ‘No’ unless you require a printed BOL for all Orders and Invoices.

A single-select lookup to specify whether or not Orders, Invoices, Price Adjustments, and Returns can be Approved if there are one or more line items with a zero price. The purpose of this preference is to prevent transactions that are missing prices from being set to a status of Approved. This defaults to "Yes" and is required. This field is always editable.

• Yes: Users will be able to set transactions to be in Approved status and no messages will be displayed.
• No: Users will be unable to set transactions to be in Approved status until the item(s) are priced or removed from the transaction.
• Warn: Users will be prompted with a message indicating there are items with missing prices and given the option to proceed by clicking "OK", or to return to the order to make changes by clicking "Cancel".

This lookup contains all the values in the YesNoWarnValue Enumeration Class.

Note: The most typical setting is "Warn". For companies that ship a lot of “Samples” with no prices they may set this to ‘Yes’.

A Yes/No lookup to identify whether sales orders and invoices require a carrier. This value defaults to "No" and is required. This field is always editable.

• Yes: The transaction must have a Carrier in order to save it.
• No: Carrier is optional.

A Yes/No lookup to specify whether or not to allow blank lot notes when moving the status to Approved on a Price Adjustment transaction. This value defaults to "No" and is required. This field is always editable.

• Yes: If any lots are missing notes, then the user is prompted to add a note before the transaction can be Approved. Notes can be added on the "Allocate Item" page.
• No: The system check for Notes will be bypassed and blank Notes will be allowed.

A Yes/No lookup to specify whether or not to allow a blank Reason Code on a Price Adjustment transaction when moving the status to Approved. This value defaults to "No" and is required. This field is always editable.

• Yes: If there is not a Reason Code then the user will be prompted to input one for each lot before the transaction can be Approved. The Reason Code can be added on the "Allocate Item" page.
• No: The system check for Reason Codes will be bypassed and blank Reason Codes will be allowed.

A Yes/No lookup to specify whether or not an End Date is required for each item on a price list. This value defaults to "No" and is required. This field is always editable.

• Yes: An End Date will be required when adding items to a price list. The End Date must be after the Start Date. The End Date will determine the last day the item's price is effective.
• No: An End Date will not be required when adding items to a price list but can still be entered. If entered, then the End Date must be after the Start Date. If no End Date is required and no End Date is entered, then the item's price will be effective until a new price or an End Date is entered.

A single-select lookup to specify whether or not users can override item prices on Orders, Invoices, Price Adjustments, and Returns that comes from a Price List. This defaults to 'Yes' and is required. This field is always editable.

• Yes: Users can make any changes to item prices that came in from a Price List. 
• No: Users are not allowed to save price overrides. 
• Warn: This preference works in conjunction with the 'Acceptable price variance below Price List price (%)' and the 'Acceptable price variance below Price List price (%)' preferences and will alert users if they are making a change that falls outside the acceptable limits. 

This lookup contains all the values in the YesNoWarnValue Enumeration Class.

Note: If the sales item is not on an assigned price list, then this preference does not apply.

A single select lookup to specify which Quick Sale Price List should be defaulted when the 'Sold To' field is populated on a new Quick Sale transaction. This defaults to blank is not required. This field is always editable.

This lookup contains all the values set up on the Price Lists List View where Price List Class = "Quick Sale".

A text box to specify the percent limit that manually entered prices can vary above the price list price if prices variances are allowed. This must be a whole number between 0 and 1000 and is required. If not assigned, the message "Acceptable price variance above Price List price (%)is required" will be displayed on Save. If not between 0 and 1000, the message "Acceptable price variance above Price List price (%) must be between 0 and 1000" will be displayed on Save. This field is always editable.

A single-select lookup to specify which date field on sales transactions will be used for calculating prices from price list price effective dates. This defaults to 'Order Date' and is required. This field is always editable.

• Order Date: Current date will be used.
  
• Ship By Date: Ship By date will be used.

This lookup contains all the values in the MFPriceListDate Enumeration Class.

Note: If the preference is set to Order Date and the Order Date is before the price's start date, then the price will not default. If the Order Date is after the price's end date, then the price will not default. The same is true for Ship By dates.

A Yes/No lookup to specify whether or not a note is required for each returned lot. This value defaults to "No" and is required. This field is always editable.

• Yes: A note will be required for each returned lot before the transaction can be saved as Approved/Ready to Post.
• No: A lot note will not be required for each returned lot.

A single-select lookup to specify the default Payroll Deduction that will be used for Employee Sales. This defaults to blank is not required. This field is always editable.

The lookup contains all the payroll deductions from the host system that are identified as 'Available to Employee Sales'. This value is required on an Employee Sale.

A Yes/No lookup to identify whether or not Quick Sales (to Employees) support charging Sales Tax. The value defaults to "No" but can be changed at anytime. 

• Yes: The 'Tax Class' field on Quick Sales to Employees will be enabled. The values will default from the Employee and can be edited to calculate or not calculate sales tax.
• No: The 'Tax Class' field on Quick Sales to Employees is disabled, will not default from the Employee, and the sales tax will not be calculated.

A Yes/No lookup to identify whether or not Quick Sales (to Customers) support charging Sales Tax. The value defaults to "No" but can be changed at anytime. 

• Yes: The 'Tax Class' field on Quick Sales to Customers will be enabled. The values will default from the Customer and can be edited to calculate or not calculate sales tax.
• No: The 'Tax Class' field on Quick Sales to Customers is disabled, will not default from the Customer, and the sales tax will not be calculated.

A single-select lookup to specify a default Carrier to be used on Orders, Invoices, Price Adjustments, and Returns when the customer address does not have a default Carrier already identified. This defaults to blank and is not required. If left blank, then the Carrier will default from the address you select and if there is no default on the address the user will need to enter it when creating a new transaction. If a Carrier is specified, then it will become the default Carrier on any Order or Invoice where the customer address does not have a default Carrier assigned. This field is always editable. 

This lookup contains a list of all the active Carriers set up in the Carrier Master File.

A single-select lookup to specify whether or not to allow new Orders, Invoices, Price Adjustments, and Returns to use PO numbers that have already been used by the customer. This defaults to 'Warn' and is required. This field is always editable.

• Yes: Duplicate PO’s are allowed.
• No: Users will receive a message that the PO has been previously used by this customer and they will not be able to re-use it.
• Warn: Users will receive a message that the PO has been previously used by this customer and can decide whether or not to re-use it.

This lookup contains all the values in the YesNoWarnValue Enumeration Class.

A single select lookup to specify the Transaction Class that should be defaulted for new sales orders. This defaults to blank and is not required. This field is always editable.

This lookup contains all the values set up in the Transaction Class LV where Transaction Type = "Order".