Journal Line History Inquiry

The purpose of the Journal Line History inquiry is to display journal lines from Posted journal entries. From this page, users can open the corresponding journal entry record view, the source transaction record view, or the Reverse/Correct window. This inquiry can be accessed from either the Inquiries page, or the GL Account Balances List View, or the GL Account Balances By Period Inquiry.

(lightbulb) This record view also contains columns for each Attribute that is set up for the 'Financial' attribute type. Because these are user defined, they are not included in the default view but can be added a saved column layout. Financial attributes are not included in the help documentation.

Software Version: 2023.08.11 and newer

Page Header

Filter ItemsDescription
Account Class

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.

Auto Hide FiltersA non-required text box that defaults as checked and is used to determine if the Search Options should be hidden when the Inquiry runs or is refreshed.
  • When checked, each time the 'Refresh' button is clicked, the search options will be hidden, allowing for more rows of data to be visible on the page. This behavior is ideal for users that have entered their search parameters and want to see the results in full-screen. 
  • When unchecked, the search options will not be hidden when the 'Refresh' button is clicked. This behavior is ideal for users that need to run several searches with different search parameters.

Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. If you change the default setting but do not save it in a custom search, it will only remain this way while the page is opened.

Refer to this FAQ for advanced search options.

Auto Refresh on OpenA non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid.
  • When checked, each time the page is opened, the search is run using the default parameters (or a 'Saved Search' if one was set as your default for the page) so the grid will be populated with data .  
  • When unchecked, the search is NOT run when the page opens and no data will be present until the 'Refresh' button is clicked. 

Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup.

Refer to this FAQ for advanced search options.

Category

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 StatementsAccount 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
Control Account Type

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.

Fiscal Period

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.

Fiscal Year

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.

GL Account

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.

GL Date

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. 

Include

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.
Search

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.
Saved Search Options

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.

  

Page Detail

Toolbar IconsDescription
Column Filter Show/Hide Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
Excel Exports the contents of the grid 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, or excluded columns, only the contents in the grid 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. 

(lightbulb) Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.

Group By Show/Hide Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total. 
Help Opens the online WIKI help page for the current page. 
More Actions

 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.
Quick Column Filter Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text.
Refresh

 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. 

(lightbulb) 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.

Saved Layouts Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific).  Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected.  

Please note that existing saved grid layouts will display the Filter Row as hidden by default.

Search Options Toggles between displaying and hiding the Search Options portion of the page.
FieldsDescription
Account

Identifies the GL Account ID of the GL Account assigned to a transaction line, journal entry line, or master file record. This field is not editable once it has been Saved.

A GL Account ID is the unique identifier for each record used to summarize transactions for each type of asset, liability, equity, revenue and expense.

Database Field: ERPx_GLAccount.AccountNumber

Account Description

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

Balance

Identifies the beginning balance amount for a Fiscal Period. This field comes from the amounts on journal line entries created from posted transactions. This field should match the 'Period Balance' column on the previous Fiscal Period. This amount cannot be edited, unless the original posted transaction is voided, reversed or corrected.  This is a calculated field and not stored in the database.


The Balance column represents the GL Account balance after the Journal Line and is calculated as [Prev Balance + Net Change].

Comment

Shows the Comment entered for the transaction or transaction line. 

Database Field: ERPx_GLJournalHeader.Comment

Created

Identifies the Created Date & Time of the record, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_GLJournalHeader.CreatedDate

Created By

Identifies the name of the user that created the record. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user.

Database Field: ERPx_GLJournalHeader.CreatedBy

Credit

Identifies the Credit amount of the journal line. This field comes from the 'Credit' column on a Journal Entry Record View with a Date that falls within the Fiscal Period. This amount cannot be edited, unless the original posted transaction is voided, reversed or corrected. This is a calculated field and not stored in the database.

Database Field: ERPx_GLJournalLine.CreditAmount

Debit

Identifies the Debit amount of the journal line, This field comes from the 'Debit' column on a Journal Entry Record View with a Date that falls within the Fiscal Period. This amount cannot be edited, unless the original posted transaction is voided, reversed or corrected. This is a calculated field and not stored in the database.

Database Field: ERPx_GLJournalLine.DebitAmount

Distributed To

Identifies the name of entity the Journal Line was Distributed to, for Journal Lines that were "Distributed To" a Project, Fisherman, or Employee.

Database Fields: ERPx_GLProject.ProjectDescription, ERPx_GLJournalLine.DistributionAccountSK

Distributed Type

Identifies the "Type" of entity the Journal Line was Distributed to, for Journal Lines that were "Distributed To" a Project, Fisherman, or Employee.

Database Field: ERPx_GLJournalLine.MFDistributionAccountTypeEN

Fiscal Period

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

Fiscal Year

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

Functional Area

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)

Host JE

Identifies the Journal ID from the Host System. This is only populated for companies that export their Journal Entries to a host system. For companies that do not, this field is blank.

Database Field: ERPx_GLJournalHeader.HostJournalID

Journal Date

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

Database Field: ERPx_GLJournalHeader.JournalDate

Journal ID

Identifies the unique Journal ID (transaction ID) for the journal entry.

Database Field: ERPx_GLJournalHeader.JournalID

Journal Type

Identifies the Journal Type assigned to the Journal Entry.

Database Field: ERPx_GLJournalHeader.JournalTransactionTypeSK

Last Updated

Identifies the Last Updated Date & Time of the Transaction, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_GLJournalLine.LastUpdated

Last Updated By

Identifies the name of the user that last updated the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user.

Database Field: ERPx_GLJournalLine.LastUser

Line Comment

Shows the Comment entered for the transaction or transaction line. 

Database Field: ERPx_GLJournalLine.Comment

Master Number

Displays the master number of the corresponding journal entry to give users the ability to audit the trail of journal history.

Database Field: ERPx_GLJournalHeader.MasterNumber

Net ChangeIdentifies the Debit or Credit amount of the line. If the Journal Line was a Debit then the amount will be display as a positive number. If the Journal Line was a Credit then the amount will be displayed as a negative (e.g. (150.25). This field is not stored in the database.
Note

Displays the first 30 characters of the Internal Note from a Manual Journal Entry.

Database Field: ERPx_GLJournalHeaderNote.NoteHTML where ERPx_GLJournalHeaderNote.JournalHeaderSK = ERPx_GLJournalLine.JournalHeaderSK

Posted

Identifies the Date & Time the transaction was posted.

Database Field: ERPx_GLJournalHeader.PostedDate

Posted By

Identifies the name of the user that Posted the Transaction. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user.

Database Field: ERPx_GLJournalHeader.PostedBy

Reference

Identifies the Reference entered for the transaction. 

Database Field: ERPx_GLJournalHeader.Reference

Segment 1

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

Segment 2

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

Segment 3

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

Source Trans Date

Identifies the GL Date of the Source Transaction that created the journal entry.

Database Field: ERPx_GLJournalHeader.SourceTransactionDate

Source Trans Detail

Identifies details of the Source Transaction. For example, if the journal entry came from an AP Invoice this specifies the [Vendor Name] ([Vendor ID]).

Database Field: ERPx_GLJournalHeader.SourceTransactionDetail

Source Trans IDIdentifies the Transaction ID of the Source Transaction that created the journal entry.
Source Trans Type

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