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.

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.PreferenceValue where 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. Use this setting if you are not managing Credit Limits in NorthScope.
• 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.

Note: In order to fully use this feature, Credit Limits must be setup on your Customers.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "CreditLimitExceeded"

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.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "NextContractNumber"

Identifies the cost type to be used when displaying cost and margin information on sales transactions. This is a single select lookup that is required.  It defaults to 'Market' and is always editable. The options include:

• Actual
• Market

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "

DisplayCostsandMarginFrom"

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

Identifies the default Checkbook that will be used 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. It defaults to "Ignore" is always editable. The options include:

• Ignore: Nothing happens when a customer exceeds their credit limit. Use this setting if you are not managing Credit Limits in NorthScope.
• 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.

Note: In order to fully use this feature, Credit Limits must be setup on your Customers.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultCashPaymentCheckbookCreditLimitExceeded"

Identifies the default Checkbook that will be used for a Check payment received and entered on a Quick Sale transaction'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 not required and defaults to blankrequired 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 editablealways editable.

The This lookup contains a blank value, the current assigned value, and a list of all the 'Active' CheckbooksSales 'Hold Codes' with a 'Transaction Type' of "Order".

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultCheckPaymentCheckbookDefaultCreditHold"

THIS IS NOT CURRENTLY USED

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:

Identifies the default Checkbook that will be used 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.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultCashPaymentCheckbook"

Identifies the default Checkbook that will be used 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.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "

DefaultCheckPaymentCheckbook"

Identifies the default Checkbook that will be used 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.PreferenceValue where 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.

Identifies how Sales batches are built in the host ERP/Accounting system when transactions are integrated. This is a single-select standard lookup that is required. It defaults to "Transaction Status" and is always editable.

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. 

Note: This preference is only applicable For NorthScope systems that send Sales Transactions to another ERP system (e.g. Dynamics GP) 

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 'Sales' account (effectively pulling freight dollars out of Sales Revenue).
• Credit the GL Account assigned as the Item's 'Freight Revenue (Credit)' account.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "BuildBatchesByGLSalesRevenueNetDeliveredFreight"

Identifies whether or not you allow lots to be over-allocated (e.g. are you allowed to assign more quantity from an Inventory Lot than what is 'Available' or 'On Hand')

If an EDI order comes into NorthScope with the same combination of Customer ID and PO#, NorthScope can immediately put that Order on Hold, giving someone time to investigate why a duplicate PO# was used. This preference is used to assign the 'Hold Code' that will be applied to these integrated transactions. This is a single-select standard lookup that is not required. If It defaults to "Do Not Evaluate" blank and is always editable. If an item’s ‘Manage Items By’ property is set to “Units Only” OR “Units and Weight”, NorthScope bases the over allocation validation on the quantity of allocated Units.  If the item’s ‘Manage Items By’ property is set to “Weight Only”, NorthScope bases the over allocation validation on the quantity of allocated Weight.

• 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 of the Lot.
• Available and On Hand: Users will not be able to allocate more than the On Hand quantity of the Lot. 

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

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DuplicatePONumberHoldCode"

Specifies the the EDI duplicate PO Number notification list for integrated transactions. This is a text box that is not currently used. Notifications are currently emailed to the default system administrator.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DuplicatePONumberNotification"

Identifies how Sales batches are built in the host ERP/Accounting system when transactions are integrated. This is a single-select standard lookup that is required. It defaults to "Transaction Status" and is always editable.

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. 

Note: This preference is only applicable For NorthScope systems that send Sales Transactions to another ERP system (e.g. Dynamics GP).

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "StopOverAllocateLotTrackedItemBuildBatchesBy"

Identifies whether or not you allow

lots to be over-allocated (e.g. are you allowed to assign more quantity from

an Inventory Lot than what is 'Available' or 'On Hand'). This is a single-select standard lookup that is required.

If defaults to "Do Not Evaluate" and is always editable. If an item’s ‘Manage Items By’ property is set to “Units Only”

or “Units and Weight”, NorthScope bases the over allocation validation on the quantity of allocated Units.  If the item’s ‘Manage Items By’ property is set to “Weight Only”, NorthScope bases the over allocation validation on the quantity of allocated Weight.

• 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 of the Lot.
• Available and On Hand: Users will not be able to allocate more than the On Hand quantity of the Lot. 

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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "

StopOverAllocateLotTrackedItem"

Identifies whether or not you allow Sales Inventory items that are not Lot Tracked, to be over-allocated (e.g. are you allowed to assign more quantity from a Warehouse Lot than what is 'Available' or 'On Hand'). This is a single-select standard lookup that is required. It defaults to "NoDo Not Evaluate" and is always editable.  If If an item’s ‘Manage Items By’ property is set to “Units Only” OR or “Units and Weight”, NorthScope bases the over allocation validation on the quantity of allocated Units. If the item’s ‘Manage Items By’ property is set to “Weight Only”, NorthScope bases the over allocation validation on the quantity of allocated Weight. This preference applies to Orders, Invoices, Price Adjustments, and Returns.

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

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "AllowOverAllocation"

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

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

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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "StopOverAllocateNonLotTrackedItem"

Specifies whether or not over allocation is allowed (can you ship more than what was ordered). This is a single-select standard lookup that is required. It defaults to "No" and is always editable. If an item’s ‘Manage Items By’ property is set to “Units Only” or “Units and Weight”, NorthScope bases the over allocation validation on the quantity of allocated Units. If the item’s ‘Manage Items By’ property is set to “Weight Only”, NorthScope bases the over allocation validation on the quantity of allocated Weight. This preference applies to Orders, Invoices, Price Adjustments, and Returns.

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

This lookup contains all the values in the 

YesNoWarnValue Enumeration Class.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "

AllowOverAllocation"

Determines whether or not allocated quantities for non-Lot Tracked Sales Inventory items will automatically stay in sync with the ordered quantities on Sales Orders and Invoices. This is a Yes/No lookup that is required. It defaults to "No" and is always editable.

• Yes: Allocated quantities of non-Lot Tracked Sales Inventory items, shipping from non-warehouse lot sites, will automatically be updated on Save to match the ordered quantities.
• No: Allocated quantities of non-Lot Tracked Sales Inventory items, shipping from non-warehouse lot sites, must be manually updated.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "AutoUpdateAllocated"

Specifies the default location that Item Favorites are stored (this preference sets the ‘Use Favorites for’ field on the Customer Master File for new Customers). This is a single-select standard lookup that is required. It defaults to "Customer" and is always editable.

• Address: New Customers added will default to store Item Favorites independently for each address.
• Customer: New Customers added 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.

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

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultItemFavoritesLevel"

Specifies how many times the item needs to be ordered before it gets added to the list of Item Favorites. This is a text box that is required. If missing, the message "Add Item Favorites Ordered X Times is required" will be displayed on Save. This value must be a positive, whole number. Else the message "Add Item Favorites Ordered X Times must be between 1 and 1000" will be displayed on Save. This field defaults to "1" and is always editable. The purpose of this preference is to 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. For example, if the value 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.

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "ItemFavoriteOrderCount"

Specifies the time interval used to auto-add items to the list of Item Favorites. This is a text box that is required. If missing, the message "Add Item Favorites Ordered in X Days is required" will be displayed on Save. This value must be a positive, whole number. Else the message "Add Item Favorites Ordered in X Days must be between 0 and 1000" will be displayed on Save. This field defaults to "365" and is always editable. 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. For example, 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.

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "ItemFavoriteOrderDays"

Identifies whether or not Item Favorites are removed if they no longer meet the same criteria that auto-added them. This is a text box that is required. It defaults to "No" and 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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "RemoveItemFavorites"

Determines whether or not a printed Bill of Lading is required before an Order or Invoice can have their status change to "Approved". This is a Yes/No lookup that is required. It defaults to "No" and 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.

Note: A custom BOL report is required to use this feature. 

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "IsPrintedBOLRequired"

Specifies whether or not Orders, Invoices, Price Adjustments, and Returns can be Approved if they contain 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 is a single-select standard lookup that is required. It defaults to "Yes" and is always editable.

• Yes: Users will be able to Approve and/or Post transactions that contain one or more line items with a 0.00 price. 
• No: Users will not be able to Approve and/or Post transactions that contain one or more line items with a 0.00 price.
• 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" when they Approve and/or Post transactions that contain one or more line items with a 0.00 price.

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "AllowZeroPriceItems"

Specifies whether or not users are required to enter a Note on every returned Lot, prior to Approving and/or Posting a Price Adjustment transaction. This is a Yes/No lookup field that is required. It defaults to "No" and is always editable.

• Yes: The transaction must have a Carrier in order to save it.No: Carrier is optional. If any lots are missing notes, the user is prompted to add a note before the transaction can be Approved and/or Posted. Notes may be added on the 'Allocate Item' page.
• No: Notes are not required but can be optionally added. 

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "IsSOCarrierRequiredRequireNoteForPriceAdjustments"

Specifies whether or not users are required to enter a Note on every returned Lotselect a 'Reason Code' for every Lot being adjusted, prior to Approving and/or Posting creating a Price Adjustment transaction. This is a Yes/No lookup that is required. It defaults to "No" and is always editable.

• Yes: If any lots that are missing notes, the user is prompted to add a note before the transaction can be Approved and/or Posted. Notes may be added on the 'Allocate Item' page.No: Notes being adjusted are missing a Reason Code on the 'Price Adjustment: Find an Invoice' page, the message "Reason codes are required for all price adjustment lines." will be displayed when the 'Build Price Adjustment' button is clicked. 
• No: Reason Codes are not required but can be optionally added. 

Specifies whether or not users are required to select a 'Reason Code' for every returned Lot, prior to Approving and/or Posting a Price Adjustment transaction. This is a Yes/No lookup that is required. It defaults to "No" and is always editable.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "RequireNoteForPriceAdjustments"

RequireReasonCodeForPriceAdjustments"

Specifies how Price Adjustment transactions will be created. This is a numeric textbox that is required, if missing the message "Create More than X Price Adjustments Asynchronously is required." will be displayed on Save.  The value defaults to '1' but is always editable and must be between 0 and 1000.  If Price Adjustments are set to be created Asynchronously they will be sent to the Inbound Integration queue for processing, otherwise they will be created immediately after building the Price Adjustment from the Price Adjustment: Find an Invoice page. 

For example, if this preference is set to 0, this will result in all Price Adjustments being sent to the Inbound Integration queue for processing and after that queue is successfully processed the transactions will be visible in the Sales Transactions List View as expected.  If this preference is set to 1000, any Price Adjustments made across less than 1000 different invoices will be immediately created and visible in the Sales Transactions List View. 

The message "Creation of the requested Price Adjustments has been queued.  You will be notified when processing is complete." will be displayed when price adjustments are set to be created asynchronously and are successfully sent to the queue. After successfully processing, a message will display in the bottom left hand corner of the Sales Transactions List View "[TransactionID(s)] Price Adjustment(s) have been created."

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "RequireReasonCodeForPriceAdjustmentsAsyncPriceAdjustmentCreation"

Specifies whether or not an End Date is required for each item on a price list. This is a Yes/No lookup that is required. It defaults to "No" and 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 entered, then the item's price will be effective until a new price or an End Date is entered.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "RequireEndDate"

Specifies whether or not users can override item prices on Orders, Invoices, Price Adjustments, and Returns that come in from a Price List. This is a single-select standard lookup that is required. It defaults to "Yes" and 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 above 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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "AllowPriceVariance"

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

The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Quick Sale Price Lists.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultCustomerPriceList"

Specifies the percent limit that manually entered prices can drop below the price list price if prices variances are allowed. This is a text box that is required. If missing, the message "Acceptable price variance below Price List price (%) is required" will be displayed on Save. The value must be a whole number between 0 and 1000. Else the message "Acceptable price variance below Price List price (%) must be between 0 and 1000" will be displayed on Save. This field defaults to "10" and is always editable.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "PriceVarianceMin"

Specifies the percent limit that manually entered prices can exceed the price list price if prices variances are allowed. This is a text box that is required. If missing, the message "Acceptable price variance above Price List price (%) is required" will be displayed on Save. The value must be a whole number between 0 and 1000. Else the message "Acceptable price variance above Price List price (%) must be between 0 and 1000" will be displayed on Save. This field defaults to "10" and is always editable.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "PriceVarianceMax"

Specifies which date field on sales transactions will be used for calculating prices from price list price effective dates. This is a single-select standard lookup that is required. It defaults to "Ship By Date" and is always editable.

• Order Date: The date specified as the 'Order Date' on the Sales Order will be used.
  
• Ship By Date: The date specified as the Shipments '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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "SOPriceDate"

Specifies whether or not users are required to enter a Note on every returned Lot, prior to Approving and/or Posting a Return transaction. This is a Yes/No lookup that is required. It defaults to "No" and is always editable.

• Yes: If any lots are missing notes, the user is prompted to add a note before the transaction can be Approved and/or Posted. Notes may be added on the 'Allocate Item' page.
• No: Notes are not required but can be optionally added. 

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "RequireNoteForReturns"

Specifies the default Payroll Deduction that will be used for Quick Sales entered for Employees. This is a single-select standard lookup that is not required. It defaults to blank and 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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultEmployeeSalePayrollDeduction"

Identifies whether or not Quick Sales (to Customers) support charging Sales Tax. This a Yes/No lookup that is required. It defaults to "Yes" and is always editable.

Identifies whether or not Quick Sales (to EmployeesCustomers) support charging Sales Tax. This a Yes/No lookup that is required. It defaults to "NoYes" and is always editable.

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "EnableSalesTaxEmployeeSaleEnableSalesTaxCustomerSale"

Specifies 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 is a single-select standard lookup that is not required. It defaults to blank and and is always editable. If left blank, then the Carrier will default from the address selected. If there is no default on the address, then 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.

Identifies whether or not Quick Sales (to Employees) support charging Sales Tax. This a Yes/No lookup that is required. It defaults to "No" and is always editable.

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

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "DefaultCarrierEnableSalesTaxEmployeeSale"

Specifies whether or not to allow new Orders, Invoices, Price Adjustments, and Returns Sales transactions to use PO numbers that have already been used by the customer. This is a single-select standard lookup that is required. It defaults to "Warn" and 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.
• WarnPO’s are allowed.
• No: 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.

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "AllowDuplicatePONumbers"

Specifies the Transaction Class that will default for new sales orders, for users that do not have a 'Default Transaction Class for New Orders' assigned as a User Preference. This is a single-select standard lookup that is not required. It defaults to blank and is always editable. Is this 

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

 This is only applicable to Sales Quote and Order type transactions. 

Database Field: ERPx_MFSysPreferences.PreferenceValue where ERPx_MFSysPreferences.PreferenceName = "OrderDocumentIDAllowDuplicatePONumbers"