Project Transaction History Inquiry
Description: The Project Transactions Inquiry details all the transactions that have been distributed to a project together with the revenue/expense distributed to the associated project.
Software Version: 2023.08.31 and newer
Page Header
Toolbar Icons | Description |
|---|---|
| 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.
|
| Inquiry Criteria | Opens Inquiry Criteria window where users can define the following criteria:
|
| Refresh | Re-queries the contents of the grid/page based on the Inquiry Criteria parameters or the default parameters for grids that do not support Inquiry Criteria. |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.Columns
Column Headers | Description |
|---|---|
| Doc No | Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This identifies the document number the Vendor assigned to the invoice/credit memo. Database Field: ERPx_APTransactionHeader.DocNumber |
| End | Displays the end date assigned to the project. The date the Project ends. If this date is empty then the Project will be open indefinitely. This value is always editable and if entered it must occur on or after the 'Start' date. Database Field: ERPx_GLProject.ProjectEndDate |
| Expense | Displays the expense amount distributed to the project on the transaction. |
| GL Period | Displays the GL period associated with the transaction’s GL Date. |
| GL Year | Displays the GL year associated with the transaction’s GL Date. |
| Module | Displays the name of the module the transaction originated in. |
| Project | Displays the ID of the project the transaction is distributed to. This field is a hyperlink, which opens the corresponding Project record. |
| Project Class | Identifies the Class that the project has been assigned to. |
| Project Description | Displays the description of the project. |
| Project GL Account | Displays the GL Account number of the GL Account associated with the transaction. This is the line item’s Purchase Account for AP Invoices and Credit Memos and the account number for manual journal entries. |
| Project GL Account Description | A GL Account Description is the name given to a GL Account ID. |
| Revenue | Displays the revenue amount distributed to the project on the corresponding transaction. |
| Start | The date the Project begins. Projects cannot be assigned to transactions that occur before this date. Database Field: ERPx_GLProject.ProjectStartDate |
| Transaction Date | Displays the Transaction Date of the source transaction. |
| Transaction ID | Identifies the unique Transaction ID for each transaction. This field is a hyperlink, which opens the corresponding transaction record. |
| Transaction Type | Displays the type of the transaction (e.g. Purchasing Invoice or GL 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. |
| Vendor ID | Identifies the ID of the Vendor account that is assigned to the transaction. This is only populated for AP Invoice and Credit Memo transactions and is blank when the transaction type is GL Journal Entry. |
| Vendor Name | Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View. This is only populated for AP Invoice and Credit Memo transactions and is blank when the transaction type is GL Journal Entry. |