Page Comparison

Checkbox

Used to select one or more records for delete or mass update.

Identifies the value in the 'Document Prefix' property on the record view. This defaults to blank for new records and is not required.

The 'Document Prefix' is used in conjunction with the 'Next Document Number' to determine the system assigned Transaction ID's. Transaction ID's are created by stringing together the [Document Prefix] + [Next Ticket Number] from the applicable Transaction Class. The 'Next Document Number' is auto-incremented each time a new transaction for the selected transaction class is created. 

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

Linked Database Field: ERPx_SOOrderTypeDocument.DocumentPrefix

A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be listed as a value when the 'New' icon is clicked from Sales Transactions List View. If set to 'No' then the record is "Active" and can be freely used. 

Linked Database Field: ERPx_SOOrderTypeDocument.IsInactive

Used to display the network path for the image file used on the transaction reports for records assigned to the Transaction Class. This defaults to blank for new records and is not required. This is only used for reports and does not drive any other functionality. This field is always editable from the record view and must be <= 1000 characters. view.

This lookup contains a blank value, the current assigned value, and a list of all the Company Currencies

Linked Database Field: ERPx_SOOrderTypeDocumentARCustomer.DocumentLogoLocation

Identifies the value in the 'Next Document Number' property on the record view.

This defaults CurrencyID

Customer Class

The ‘Customer Class' property on the Customer record.

This defaults to blank for new records and is required. If missing, the message “Next Document Number is required.” will be displayed on Save. The value must be a numeric whole number. If not, the message "Next Document Number must be a number and cannot contain letters or symbols." will be displayed on Save.

The 'Document Prefix' is used in conjunction with the 'Next Document Number' to determine the system assigned Transaction ID's. Transaction ID's are created by stringing together the [Document Prefix] + [Next Document Number] from the applicable Transaction Class. The 'Next Document Number' is auto-incremented each time a new transaction for the selected transaction class is created. 

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.

Linked Database Field: ERPx_SOOrderTypeDocument.NextDocNumber

The 'Payment Terms' property on the Transaction Class record. This defaults to blank on new records and is not required. 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 Customer Classes.

Linked Database Field: ERPx_SOOrderTypeDocumentARCustomer.DefaultPaymentTermSKCustomerClassSK

Customer ID

A hyperlink that shows the value of the ‘Customer ID' Transaction Class' property on the Transaction Class recordthe Customer record. Clicking on the link opens the record view for the selected Transaction Classselected Customer. 

This defaults to blank for new records and is required. If not assigned, the message "Transaction Class Customer Processing Failed: Request 1 (#MISSING#): Customer ID is required." will be displayed on Save. This value must be unique by Transaction Type. If not unique, the message "Duplicate Transaction Classes are Customer Processing Failed: Request 1 ([CustomerID]): Duplicate Customer ID is not allowed." will be displayed on Save. This field is not always editable after the initial Save and must be <= 15 characters. from the record view.

The Customer ID is used as a short description and unique identifier of the Customer account.

Linked Database Field: ERPx_SOOrderTypeDocumentARCustomer.DocumentIDCustomerID

Identifies the value in the 'Transaction Integration to Host System' property on the record view. This defaults to "Transaction with Journal Details" for new records. This functionality is only applicable where NorthScope sales transactions are sent to a separate host system. For systems that send sales transactions, this preference describes how they are sent. The options include:

• Transaction with Journal Details: When transactions for this Transaction Class are posted, an outbound record is created so that it can be imported by the host system. This can only happen if the Outbound Transaction Type of "SO Transaction Class" is configured in the Integration Configuration master file.
• No Integration: When transactions for this Transaction Class are posted, no outbound record is created, even if the Outbound Transaction Type of "SO Transaction Class" is configured in the Integration Configuration master file to send transactions.

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

Hold

The value from the 'Hold' property on the Customer record. If set to 'Yes' then new transactions can be entered for the Customer but payments cannot be issued to them. 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 value is defaulted to ‘No’ for a new customer record is always editable.

Linked Database Field: ERPx_ARCustomer.IsOnHold

Inactive

The value from the 'Inactive' property on the Customer record. 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 value is defaulted to ‘No’ for a new customer record and is always editable.

Linked Database Field: ERPx_

ARCustomer.

IsInactive

Identifies the value in the 'Transaction Type' Invoice Delivery

The value from the ‘Invoice Delivery Method’ property on the Customer record view. This defaults to blank and is required. If . This is a required field and if not assigned, the message “Transaction Type "Customer Processing Failed: Request 1 ([CustomerID]): Invoice Delivery Method is required.” will " will be displayed on Save. This field is not editable after the initial Save. The value can be set to:

• Order: Used to track the order and shipment of items
• Invoice: Used to invoice a customer
• Return: Used to allow customers to return items
• Price Adjustment: Used to provide customers with price adjustments for items

This lookup contains all the values in ERPx_SOOrderType where IsEnabled = 1The 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

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.

Linked Database Field: ERPx_SOOrderTypeDocumentARCustomer.OrderTypeSKPaymentTermsSK