Customers are entities you sell things to and the Customer List View shows the list of these accounts. Customers are used in Sale and Sales Programs. The purpose of this page is to add, edit, remove, and activate/inactive these records.
This list view also contains columns for each Attribute that is set up for the 'Customers' attribute type. Because these are user defined, they are not included in the default view but can be added a saved layout. Customer attributes are not included in the help documentation.
Software Version: 2019.09.03 and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
| Excel | Export the contents of the list view to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view only the filtered contents will be exported. |
| Favorites |   Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline.
|
| Grid Layout | Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).
|
| Help | Opens the online WIKI help page for the current page.
|
| New | Opens a new blank record for data entry. |
| Fields | Description |
Checkbox | Used to select one or more records for delete or mass update. |
Currency | The 'Currency’ property on the Customer record. This defaults from the Customer Class on new records, but can be overwritten, and is required. If not assigned, the message "Customer Processing Failed: Request 1 ([CustomerID]): Currency is required." will be displayed on Save. This field is always editable from the record view. The Currency assigned identifies the transaction currency used for the customer. If a Customer is assigned a Currency of "USD", all of their transactions are stated in "USD" and their payments must be received in "USD". Changing the assigned Currency is allowed but should not be done until all the open receivable transactions are fully applied. This lookup contains a blank value, the current assigned value, and a list of all the Company Currencies. Linked Database Field: ERPx_ARCustomer.CurrencyID Error rendering macro 'excerpt-include' : No link could be created for 'HELP:Def: Currency'. This is required and is always editable from the Customer Record but should not be done until all the open receivable transactions are fully applied. Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_ARCustomer.CurrencyID |
Customer Class | The ‘Customer Class' property on the Customer record. This defaults to blank for new records and is required. If not assigned, the message "Customer Processing Failed: Request 1 ([CustomerID]): Customer Class is required." will be displayed on Save. This field is always editable from the record view. The Customer Class is used to classify customers and to set default Properties and Accounts (GL Accounts). These defaults can be overwritten for individual Customers. The lookup contains a blank value, the current assigned value, and a list of all the 'Active' Customer Classes. Linked Database Field: ERPx_ARCustomer.CustomerClassSK Error rendering macro 'excerpt-include' : No link could be created for 'HELP:Def: Customer Class'. This is required and is always editable from the Customer Record but changing it will not update any of the default customer properties or accounts that are assigned on the new Class. Customer Classes are managed in the Customer Class master file. Database Fields: ERPx_ARCustomerClass.Description, ERPx_ARCustomer.CustomerClassSK |
Customer ID | A hyperlink that shows the value of the ‘Customer ID' property on the Customer record. Clicking on the link opens the record view for the selected Customer. This defaults to blank for new records and is required. If not assigned, the message "Customer Processing Failed: Request 1 (#MISSING#): Customer ID is required." will be displayed on Save. This value must be unique. If not unique, the message "Customer Processing Failed: Request 1 ([CustomerID]): Duplicate Customer ID is not allowed." will be displayed on Save. This field is always editable from the record view. The Customer ID is used as a short description and unique identifier of the Customer account. Linked Database Field: ERPx_ARCustomer.CustomerID Error rendering macro 'excerpt-include' : No link could be created for 'HELP:Def: Customer ID'. This is required and is always editable from the Customer Record but only in systems that are not integrating Customers with a third party system. To be editable, the "Customer" 'Transaction Type on both the 'Inbound to NorthScope' and 'Outbound from NorthScope' Integration Modes must be set to "None" on the Integration Configuration page. Database Field: ERPx_ARCustomer.CustomerID |
Customer Name | The ‘Customer Name' property on the Customer record. This defaults to blank for new records and is required. If not assigned, the message "Customer Processing Failed: Request 1 ([CustomerID]): Customer Name is required." will be displayed on Save. This field is always editable from the record view. The Customer Name is used as a long description/name of the Customer account. Linked Database Field: ERPx_ARCustomer.CustomerName Error rendering macro 'excerpt-include' : No link could be created for 'HELP:Def: Customer Name'. This is required and is always editable from the Customer Record. Database Field: ERPx_ARCustomer.CustomerName |
Hold | Identifies if the Customer is "On Hold". If set to 'Yes' then new Sales Orders or Quick Sales cannot be entered but Price Adjustments, Returns and Payment Receipts are allowed. This does not currently work, as On Hold Customers are not displayed in the Payment Receipt lookup. If set to 'No' then the record is not on hold and can be freely used. 'No' values display as blank in the grid. This is always editable from the Customer Record. Database Field: ERPx_ARCustomer.IsOnHold |
Inactive | Identifies if the Customer is "Inactive". If set to 'Yes' then the record is "Inactive" and will not be included in look-ups for transactions or other master files. If set to 'No' then the record is "Active" and can be freely used. 'No' values display as blank in the grid. This is always editable from the Customer Record but only for Customers that have no 'Open Transactions'. ←This does not currently work, any customer is currently allowed to be put on hold Database Field: ERPx_ARCustomer.IsInactive |
Invoice Delivery | Identifies the default ‘Invoice Delivery Method’ for the Customer. This is a required and is always editable from the Customer Record. If not assigned, the message "Customer Processing Failed: Request 1 ([CustomerID]): Invoice Delivery Method is required." will be displayed on Save. The value is defaulted to “Print” (SOInvoiceDeliveryMethod Enumeration Class with an Enumeration Value of 1) for a new customer record and is always editable. This lookup contains all the values in the SOInvoiceDeliveryMethod Enumeration Class. Linked Database Field: ERPx_ARCustomer.InvoiceDeliveryMethodEN Identifies the default ‘Invoice Delivery Method’ for the Customer. This is a required and is always editable from the Customer Record. The applicable values are in the SOInvoiceDeliveryMethod Enumeration Class. Database Fields: ERPx_ARCustomer.InvoiceDeliveryMethodEN |
Payment Terms | The 'Payment Terms' property on the Customer record. This defaults from the Customer Class on new records, but can be overwritten, and is required. If not assigned, the message "Customer Processing Failed: Request 1 ([CustomerID]): Payment Terms is required." will be displayed on Save. This field is always editable from the record view. This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Payment Terms. Payment Terms are used to calculate Due Dates, Payment Discounts, and Customer Aging. Linked Database Field: ERPx_ARCustomer.PaymentTermsSK Error rendering macro 'excerpt-include' : No link could be created for 'HELP:Def: Payment Terms'. This is required and is always editable from the Customer Record but will only apply to new transactions, it will not update existing transactions. Database Fields: ERPx_MFPaymentTerms.PaymentTermName, ERPx_ARCustomer.PaymentTermsSK |