Identifies the file formats that you will allow the report to be exported in when printing from the Print Dialog. This is a single select lookup that defaults to blank on New but is required to save. If missing, the message "At least one allowed format must be specified" will be displayed on Save. This is always editable. 

The lookup contains:

• PDF
• Word
• Excel
• CSV

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReport.ReportExportTypeEN

Identifies the description of the report. This defaults to blank, is not required, and must be <= 1000 characters. This is always editable and will be visible for reports set to be located on the Reports Page.  

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReport.Description

Identifies the user-friendly name that will be displayed in the Print Dialog and on each of the Report List Views. This defaults to blank and is required and must be <= 50 characters.  If left blank, this will default to the 'Report Name' value.  This is always editable. 

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReport.DisplayName

Displays a text box and browse button for the user to upload a report. When the user clicks the 'Browse' button, the file explorer window opens allowing the user to select the .rdl (Report Definition Language) file they wish to upload/deploy.  If another file type is selected, the message "You are only allowed to upload rdl files" will be displayed on Save. This is always editable. 

  The editability rules do not apply to 'Direct Print' type reports. 

This is used to identify the page(s) you can print the report from. This is only enabled for reports that Launch From a 'Print Dialog'. This is a single select lookup that defaults to blank and is only enabled when the Launch From is set to 'Print Dialog'. If blank, the report will not be displayed in any print dialog window within the Functional Area. The lookup contains an option for ALL as well as all the available pages the report can be added to within the Functional Area. 

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReportForm.FormSK

THIS IS NOT CURRENTLY USED

Database Field: ERPx_RSReport.IsHistoryTracked

Identifies where the report is launched from. This is a single select lookup that defaults to blank on New but is required to Save. If missing, the message "Report Location is required" will be displayed. The lookup contains: 

• Print Dialog
• Reports Page
• Direct Print

Note: The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReport.ReportLocationEN

Identifies whether or not the report exists on the report server.  This displays 'Yes' when the report exists on the report server and is blank when it does not.  This is never editable. Reports that are not on the Report Server will not run.

Identifies the report file name (RDL Name) of the report installed on the Report Server. This is a text box that defaults to blank on New, this value is a reference that is not visible to the user launching the report (they see the 'Display Name'). This is required and if missing, the message "Report Name is required" will be displayed on Save. Report Names must be unique, if a duplicate name is entered the message "Report Names must be unique." will be displayed on Save. This must be <= 50 characters and is only editable on New.  

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReport.ReportName

Identifies the file system location where the report exists.  This is a text box that defaults to blank on New and allows the user to enter the path to the directory of the associated report being uploaded.  This allows users to use reports that are located on another server as opposed to the NorthScope report server.  

Database Field: ERPx_RSReport.ReportPathOverride

Identifies how the report is classified. This is a single select lookup that defaults to blank on New.  This is required else the message "Report Type is required" will be displayed on Save. The lookup contains the values in the ReportType Enumeration Class.

Report Types are used to classify Reports into one of the following report types: 

1. Aging: Aging reports identify unpaid invoice balances along with the duration for which they've been outstanding (based on the Aging Periods you have specified). These are used internally to view Customer, Vendor, and/or Fishermen Balances.
2. Analysis: Analysis reports are used to analyze historical data across a range of user specified parameters (i.e., dates, customers/vendors/fishermen/sites, transaction classes, etc.). Unlike 'Edit' reports which are often used as a file/audit copy, these are for performing analysis and are typically launched from the Reports page.
3. Billing: Billing reports are documents you send to organizations that owe you money. Examples would include the Sales Invoice, Quick Sale Invoice, and Fisherman Sale Invoice. 
4. Check: Checks are used to print payments made through Accounts Payable, Fisherman Accounting, and Grower Accounting. This report type is only used for the paper check, not any check history or ACH remittance reports. Checks are typically launched as a Direct Print report. 
5. Edit: Edit reports are used to review transactional data and/or journal details before or after posting. They are often used internally as file copy for a single transaction or batch of transactions posted together. Because these are intended to be internal reports that do not go outside the company, they do not typically contain special formatting or print with company logos. These are most often launched from the Print dialog from transaction list views, record vires, and historical inquiries. 
6. File Export: File Export reports are datasets that generate as 'txt' or other formats designed to only be exported.
7. Financial: Financial reports are designed to be printed at month-end and year-end. These are typically launched from the Reports page. Examples include Trial Balance, Balance Sheet, and Income Statement.
8. Other: The "Other" report type is used to classify reports that do not fall into any of the other Report Types.
9. Setup: Setup reports are designed to show the details for a master file. Setup reports are internal use reports that are typically launched from the reports page. 
10. Statement: Statements are used to show transaction history and outstanding balances for customers, fishermen, and/or growers. These are typically launched from the Reports page.
11. Transaction: Transaction reports are designed to be external reports sent to Customers (e.g., Order confirmation), Warehouses, (e.g., Warehouse Release and Picking Instructions), Carriers, (e.g., Warehouse Release), Brokers (e.g., Broker Settlement), Vendors (e.g., Purchase Order), Fishermen (e.g., Fish Ticket), and Growers (e.g., Grower Ticket) that show details of a single transaction. Because these are external reports, they are typically formatted to fit in a window envelope and print with a company logo. Transaction Reports are typically launched from the Print dialog from the transaction list view, record view, and/or historical inquires.   

Database Field: ERPx_RSReport.ReportType

Identifies which Company/Companies within NorthScope has access to the associated report. This is a single select lookup that defaults to *ALL* on New. This is not required, however if no company is selected the report will not be available for use within NorthScope. This is always editable. 

  The editability rules do not apply to 'Direct Print' type reports. 

Database Field: ERPx_RSReportCompany.DataEntityCompanySK