Used to select one or more GL Account Classes. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

GL Account Classes are used to classify one or more GL Accounts into a group with other similar behaving accounts and for organizing financial reports. For example, you may have several revenue accounts that are all classified as "Sales" Accounts. 

The lookup contains a list of all GL Account Classes.

Used to select one or more GL Account Class Categories. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

The General Ledger Account Category identifies which major section the GL Account belongs to on the Financial Statements. Account Categories can be assigned as follows:

Balance Sheet Accounts: 

• Asset
• Liability
• Equity

Income Statement Accounts:

• Income Statement

This lookup contains the values in the GLAccountClassCategory Enumeration Class.

• Asset
• Liability
• Equity
• Income Statement

Used to select one or more GL Account Control Types. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Control Account is a general ledger account containing only summary amounts. The details for control accounts are stored in a separate but related subsidiary ledger. The subsidiary ledger allows for tracking transactions within the control account in more detail. Individual transactions are posted both to the control account and the corresponding subsidiary ledger, and the totals for both are compared when preparing a trial balance to ensure accuracy. Control Accounts keep the general ledger free of details, while still maintaining correct balance for preparing the company's financial statements. The most common examples of Control Accounts include Accounts Receivable and Accounts Payable. The List of Control Account Types include:

• Brokerage: The accrued brokerage payable. The details are stored in Program Balances.  
• Checkbooks: The balance of a bank account. The details are stored in the Checkbook Transactions inquiry.
• Customers: Current Accounts Receivable. The details are stored in the custom aging.
• Fishermen: Current fishermen payable/receivable. The details are stored in the Fisherman Balances inquiry. 
• Fishermen Loans: Current Fishermen Loans Receivable. The details are stored in the Fisherman Balances inquiry.
• Freight: Current Accrued Freight (from Freight POs). The details are stored in the Purchase Order Lines List View.
• Growers: Current Grower Payable. The details are stored in the vendor aging. 
• Inventory: Current inventory valuation. The details are stored in the Inventory valuation.
• Rebates: The accrued rebates payable. The details are stored in Program Balances.
• Retained Earnings: This is posted to during a year-end close.
• Vendors: Current Accounts Payable. The details are stored in the vendor aging.

This lookup contains the values in the GLControlAcctType Enumeration Class.

Used to select one or more Fiscal Periods, as configured in the Fiscal Periods master file. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

Fiscal Periods represent budgetary or accounting periods that fall within Fiscal Years. These often match the calendar where there are 12 periods, matching the calendar months. In organization where the fiscal year does not match the calendar year, Fiscal Periods may or may not match the number of days in a calendar month. Every transaction that posts to the general ledger contains a 'GL Date' and that date identifies both the Fiscal Year and Fiscal Period the transaction was posted to the general ledger in. 

The lookup contains a list of all Fiscal Periods.

Used to select one or more Fiscal Years. This is a multi-select standard lookup that is not required to return results. It defaults as the current year.

A Fiscal Year is a one-year period that companies use for financial reporting and budgeting. A Fiscal Year is most commonly used for accounting purposes to prepare financial statements. Fiscal Years often start on January 1st and end on December 31st. However, not all Fiscal Years correspond with the calendar year. For example, a company may run their Fiscal Year from May 1st - April 30th. Once a Fiscal Year has been determined, it is unlikely to ever change outside of a company sale and/or merger.

The lookup contains a list of all Fiscal Years.

Used to select one or more GL Accounts. This is a multi-select standard lookup that is not required to return results. If the inquiry is opened from the Inquiries page, it defaults as blank. If the inquiry is opened from the GL Account Balances List View or the GL Account Balances by Period Inquiry, it defaults with the selected GL Account.

A GL Account Description is the name given to a GL Account ID.

The lookup contains a list of all GL Accounts.

Used to select a single GL Date or GL Date range. For a single GL Date, all GL Dates occurring on or before the specified date will be included. This is a date range editor that is not required to return results. It defaults as blank.

Identifies the date the transaction posted (or will post) to the general ledger. 

A lookup to assign one or more conditions you want included in your search. This lookup contains:

• Beginning Balances. If selected, a row will be inserted for each GL Account that calculates the Beginning Balance for the account.

A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). 

Refer to this FAQ for advanced search options.

The Search field can be used to search across the following fields: 

• Account. Search for all or part of a GL Account number.
• Account Description. Search for all or part of a GL Account Description.
• Natural Account Range. Search for a range of "Natural" accounts (e.g. "1000:2000” to return all GL Accounts between "1000" and "2000").
• Journal ID. Search for all or part of a Journal ID.

Displays the saved searches lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. Saving search options will also save the preferences for 'Auto Refresh on Open' and 'Auto Hide Filters'. The new search option can also be set as the default.  Default searches can be removed by clicking the 'Set as Default' button again when the current default search is selected.  

Refer to this FAQ for advanced search options.

 Displays a drop down menu of related actions. The list of options includes:

• RV: Journal. Opens the Journal Entry Record View.
• RV: Source Transaction. Opens the Record View of the Source Transaction.
• Reverse/Correct. Opens the Reverse/Correct page and allows the user to either Reverse or Reverse & Correct a journal entry.

 Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. 

 This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again.

Identifies the Description associated with the GL Account assigned to a transaction line, journal entry line, or master file record. This can be edited from the 'Account Description' field on the GL Accounts List View.

A GL Account Description is the name given to a GL Account ID.

Database Field: ERPx_GLAccount.Description

Identifies the Period on a Fiscal Calendar. This can be edited from the 'Period Name' field on the Fiscal Periods master file.

Fiscal Periods represent budgetary or accounting periods that fall within Fiscal Years. These often match the calendar where there are 12 periods, matching the calendar months. In organization where the fiscal year does not match the calendar year, Fiscal Periods may or may not match the number of days in a calendar month. Every transaction that posts to the general ledger contains a 'GL Date' and that date identifies both the Fiscal Year and Fiscal Period the transaction was posted to the general ledger in. 

Database Field: ERPx_MFFiscalPeriod.PeriodName

Identifies the Year on a Fiscal Calendar. This is a system assigned value and cannot be edited.

A Fiscal Year is a one-year period that companies use for financial reporting and budgeting. A Fiscal Year is most commonly used for accounting purposes to prepare financial statements. Fiscal Years often start on January 1st and end on December 31st. However, not all Fiscal Years correspond with the calendar year. For example, a company may run their Fiscal Year from May 1st - April 30th. Once a Fiscal Year has been determined, it is unlikely to ever change outside of a company sale and/or merger.

Database Field: ERPx_MFFiscalYear.FiscalYear

Identifies the Functional Area where the Journal ID originated.

Functional Areas represent the collection of Transactions, Master Files, Inquires, and Reports that pertain to unique areas of operations within the software. The Functional Areas include: 

• Software Application Functional Areas:
  • CO - Company
  • SY - System
• Core Functional Areas:
  • GL - General Ledger / Financial
  • A/P - Accounts Payable & Purchase Order
  • A/R - Accounts Receivable / Sales Order
  • IN - Inventory

• Specialty Functional Areas: 
  • FA - Fisherman Accounting
  • GA - Grower Accounting
  • LM - Load Management
  • PR - Payroll
  • PT - Portal
  • SP - Sales Programs (Brokerage, Rebate, Off Invoice)

Identifies the first part (segment) of the GL Account Format. It comes from the 'Number' column on the GL Account Format Record View. This field is never editable.

A GL Account Segment refers to the individual components that make up a General Ledger Account. Every GL Account contains at least on segment called the "Natural Account". Companies often add additional "Segments" to further organize and structure their chart of accounts. GL Account Segments are typically separated by a "-" within the GL Account Number (e.g. 5003-05-4). For example, a company that runs multiple Plants and produces multiple lines of product may use three GL Account Segments: [Natural Account] - [Plant ID] - [Product Line].

Database Field: ERPx_GLAccountSegmentNumber.Number, ERPx_GLAccountFormat.SegmentSK

Identifies the second part (segment) of the GL Account Format. It comes from the 'Number' column on the GL Account Format Record View. This field is never editable.

A GL Account Segment refers to the individual components that make up a General Ledger Account. Every GL Account contains at least on segment called the "Natural Account". Companies often add additional "Segments" to further organize and structure their chart of accounts. GL Account Segments are typically separated by a "-" within the GL Account Number (e.g. 5003-05-4). For example, a company that runs multiple Plants and produces multiple lines of product may use three GL Account Segments: [Natural Account] - [Plant ID] - [Product Line].

Database Field: ERPx_GLAccountSegmentNumber.Number, ERPx_GLAccountFormat.SegmentSK

Identifies the third part (segment) of the GL Account Format. It comes from the 'Number' column on the GL Account Format Record View. This field is never editable.

A GL Account Segment refers to the individual components that make up a General Ledger Account. Every GL Account contains at least on segment called the "Natural Account". Companies often add additional "Segments" to further organize and structure their chart of accounts. GL Account Segments are typically separated by a "-" within the GL Account Number (e.g. 5003-05-4). For example, a company that runs multiple Plants and produces multiple lines of product may use three GL Account Segments: [Natural Account] - [Plant ID] - [Product Line].

Database Field: ERPx_GLAccountSegmentNumber.Number, ERPx_GLAccountFormat.SegmentSK

Identifies the Transaction Type of the transaction that created the Journal Entry. 

Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type.

Database Field: ERPx_GLJournalHeader.SourceTransactionTypeName