Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Sales functional area is used to store all Customer data and The Sales functional area is used to store all Customer data and record all Sales transactions. The main tasks performed include maintaining customer data, manage customer price lists, importing and/or entering Sales Orders, and receiving and applying customer payments. The Sales functional area integrates with the Financial, Fisherman Accounting, Inventory, Load Management, and Sales Program functional areas. The purpose of the Sales Preference Page is to configure how these features work. From here, users can set defaults, identify which features are used, and how the enabled features perform.

...

identify during integration host specify . This This lookup contains all the values to specify which non lot tracked items to over allocateEnumeration ClassThis lookup contains all the values in the MFNegativeInventoryLevel  specify the priority items are Auto Allocated
Toolbar IconsDescription
Excel
Insert excerpt
Excel - Global (old)
Excel - Global (old)
nopaneltrue
Favorites
Insert excerpt
Favorites Add/Remove - Global
Favorites Add/Remove - Global
nopaneltrue
Grid Layout
Insert excerpt
Grid Layout - Global
Grid Layout - Global
nopaneltrue
Help
Insert excerpt
Help - Global
Help - Global
nopaneltrue
Save
Insert excerpt
Save - Global
Save - Global
nopaneltrue
FieldsDescription
Preference NameIdentifies the Preference that is being setup.
Value A text box or lookup to set the value of the preference. Preference values are always editable and can be changed at any time, unless otherwise specified. 
PreferencesDescription
Contract Defaults
Next Contract NumberA text box to assign the next Contract Number that will be auto assigned to new customer contracts. This defaults to 1000 and is required. If not assigned, 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.
Credit Holds
When credit limits are exceeded

A single select lookup to assign how the system treats Customers that exceed their Credit Limitsreacts when a Transaction exceeds a Customer's Credit Limit. This defaults to 'Ignore' but can be changed at any time to either 'Warn' or 'Place on Credit Hold'. This field is required and always enabled. 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 alerting the user. This is just an alert, 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. 

Default code for Credit Holds on Order

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.

Default code for Credit Holds on Order

A single select standard lookup to assign the 'Hold Code' that will be automatically assigned to Orders where the Customer has exceeded their Credit Limit. This 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 lookup contains a list of all the Sales 'Hold Codes' with a 'Transaction Type' of "Order".

Default
Default Payment Receipt Checkbook

A single select lookup to assign the default Checkbook for a Payment Receipt. This defaults This field defaults to blank and is not required. This field is always enabled and can be changed at any time to any Checkbookalways enabled.

This lookup contains a list of all the Checkbooks set up in the Financial functional area. Not sure if we need (or use this preference) we should confirm before publishing.

Default Shipping UOM

A single select lookup to assign the default Weight Unit of Measure used for Sales Order Shipments. This defaults to 'Lbs' but can be changed at any time to any "Weight" unit of measure. This field is always enabled.

This lookup contains a list of all the Weight UOM's.

Default Cash payment checkbook

A single select lookup to assign the default Checkbook for a Cash payment received and entered on a Quick Sale transaction. This defaults This field defaults to blank , and is not required, and can be changed at any time to any 'Active' Checkbook. This . This field is always enabled.

This lookup contains a list of all the 'Active' Checkbooks set up in the Financial functional area.

Default Check payment checkbook

A single select lookup to assign the default Checkbook for a Check payment received and entered on a Quick Sale transaction. This defaults  This field defaults to blank , and is not required, and can be changed at any time to any 'Active' Checkbook. This . This field is always enabled.

This lookup contains a list of all the 'Active' Checkbooks set up in the Financial functional area.

Default Credit Card payment checkbook

A single select lookup to assign the default Checkbook for a Credit Card payment received and entered on a Quick Sale transaction.  This defaults This field defaults to blank , and is not required, and can be changed at any time to any 'Active' Checkbook. This . This field is always enabled.

This lookup contains a list of all the 'Active' Checkbooks set up in the Financial functional area.

Financial
Record Sales Revenue in the GL net of Delivered Freight?

A Yes/No lookup to identify whether sales revenue is recorded in the GL net of delivered freight. The value defaults to "No" and is required. This field is always enabled. 

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
Integration
Are Transaction Numbers Managed By Host

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.
EDI Duplicate PO Number Hold Code

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.

EDI Duplicate PO Number Notification ListA text box to specify the the EDI duplicate PO Number notification list for integrated transactions. This defaults to blank and is not required. This field is always editable.
Build Batches By

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. 

Item Allocation
Stop over allocating for lot tracked items based on

A single select lookup to specify which lot tracked items to over allocate. This defaults to 'Do Not Evaluate' and is required. This field is always editable.

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

Stop over allocating for non lot tracked items based on

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.

Can you ship more than the ordered quantity for a non-substitute order item?

A single select lookup to specify whether a non-substitute order item can ship more than the ordered quantity. This defaults to 'No' and is required. This field is always editable.

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

Auto Allocate by?

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.

Update Allocated from Ordered for non-Lot Tracked Items shipping from non-Whse Lot Sites

A Yes/No lookup to specify whether to update allocated from ordered for non-lot tracked items that ship from non-warehouse lot sites. The value defaults to "No" and is required. This field is always editable.

A value of "Yes" means ....

A value of "No" means ....

Item Favorites
Default Item Favorites LevelA single select lookup to specify where to default item favorites. This defaults to 'Customer' and is required. This field is always editable.
Add Item Favorites Ordered X TimesA text box to specify how many items favorites are ordered. 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.
Add Item Favorites Ordered in X DaysA text box to specify how many days item favorites are ordered. 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.
Auto Remove Item FavoritesA Yes/No lookup to identify whether to automatically remove item favorites. This value defaults to "No" and is required. This field is always editable.
Order / Invoice Approval
Require a printed BOL for all shipped OrdersA Yes/No lookup to identify whether a printed Bill of Landing is required for a shipped order. This value defaults to "No" and is required. This field is always editable.
Allow items with a zero price

A single select lookup to specify whether items with a zero price is allowed. This defaults to 'Yes' and is required. This field is always editable.

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

Order Save
Do Sales Orders Require a CarrierA Yes/No lookup to identify whether sales orders require a carrier. This value defaults to "No" and is required. This field is always editable.
Price Adjustment Approval
Require a Note for all Price Adjustment LotsA Yes/No lookup to specify whether a note for price adjustment lots is required for an adjustment transaction. This value defaults to "No" and is required. This field is always editable.
Require a Reason Code for all Price Adjustment LotsA Yes/No lookup to specify whether a reason code for price adjustment lots is required for an adjustment transaction. This value defaults to "No" and is required. This field is always editable.
Price List
Require Item Price End DateA Yes/No lookup to specify whether an item price end date is required. This value defaults to "No" and is required. This field is always editable.
Allow Price Variances

A single select lookup to specify whether price variances are allowed. This defaults to 'Yes' and is required. This field is always editable.

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

Default Customer Quick Sale Price List

A single select lookup to specify which Quick Sale price list should be defaulted. 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'.

Acceptable price variance below Price List price (%)A text box to specify the acceptable percentage of price variance below Price List. This must be a whole number between 0 and 1000 and is required. If not assigned, the message "Acceptable price variance below Price List price (%)is required" will be displayed on Save. If not between 0 and 1000, the message "Acceptable price variance below Price List price (%) must be between 0 and 1000" will be displayed on Save. This field is always editable.
Acceptable price variance above Price List price (%)A text box to specify the acceptable percentage of price variance above Price List. 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.
Date used for calculating Price List Prices

A single select lookup to specify which date should be used for calculating Price List prices. This defaults to 'Order Date' and is required. This field is always editable.

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

Return Approval
Require a Reason Code for all Returned Lots

A Yes/No lookup to specify whether a reason code for all returned lots is required for a return transaction. This value defaults to "No" and is required. This field is always editable.

Require a Note for all Returned LotsA Yes/No lookup to specify whether a note for all returned lots is required for a return transaction. This value defaults to "No" and is required. This field is always editable.
Sales Defaults
Default Employee Sale Payroll Deduction CodeA single select lookup to specify which employee sale payroll deduction code should be defaulted for a sales order. This defaults to blank is not required. This field is always editable.
Sales Tax
Enable Sales Tax on Employee Sales

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. 

A value of "Yes" means that the 'Tax Class' field on Quick Sales to Employees will be enabled. If so, the values will default from the Employee and can be edited to calculate or not calculate sales tax.

A value of "No" means that the 'Tax Class' field on Quick Sales to Employees is disabled, will not default from the Employee, and sales tax will not be calculated.

Enable Sales Tax on Customer Sales

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. 

A value of "Yes" means that the 'Tax Class' field on Quick Sales to Customers will be enabled. If so, the values will default from the Customer and can be edited to calculate or not calculate sales tax.

A value of "No" means that the 'Tax Class' field on Quick Sales to Customers is disabled, will not default from the Customer, and sales tax will not be calculated.

Transaction
Default Carrier

A single select lookup to specify the default carrier. This defaults to blank is not required. This field is always editable.

This lookup contains a list of all the active Carriers set up in the Sales functional area.

Allow Duplicate PO Numbers

A single select lookup to specify if duplicate PO Numbers are allowed. This defaults to 'Warn' and is required. This field is always editable.

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

Default Transaction Class for New Orders

A single select lookup to specify the Transaction Class that should be defaulted for new 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'.

Related Topics



Expand
titlePage Definitions

Page Definitions


...