Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Def - Not Defined'.
 The purpose of this page is to display all outstanding transactions that have not been applied. Users will be able to select a transaction to apply to a Fish Ticket.

Software Version: YYYY.MM.DD and newer

Page Header

Toolbar IconsDescription
Apply DocumentOpens the Apply Payable Document record view. Users should select a transaction prior clicking this toolbar icon. Only one transaction can be selected at a time.
ExcelExport 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. 
Grid LayoutOpens 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).

(lightbulb) The bolded view is the default view, which will determine the view will automatically display in when opened. 

HelpOpens the online WIKI help page for the current page. 

(lightbulb) This icon is only visible on pages that are documented in the online help.

Inquiry Criteria

Opens Inquiry Criteria window where users can define the following criteria: 

  • Include transactions through: A textbox that defaults to the current date.
  • Hide fully applied transactions: A Yes/No lookup that defaults to "Yes".
RefreshRe-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. 
FieldsDescription
CheckboxUsed to select one transaction to apply a document to.
Account

Identifies the ID of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is required and comes from the 'Vendor ID' field on the Fishermen & Tenders record view. This is only editable by changing the Fisherman, Fisherman & Tender or Tender assigned to the transaction.

Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK

Account Class

Identifies the description of the Fisherman Class associated with the transaction. This is required and comes from the 'Vendor Class' field on the Fishermen & Tenders record view. This is only editable by changing the Fisherman, Fisherman & Tender or Tender assigned to the transaction.

Database Fields: ERPx_APVendor.VendorClassSK, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK

Account Name

Identifies the name of the Fisherman, Fisherman & Tender or Tender associated with the transaction. This is required and comes from the 'Vendor Name' field on the Fishermen & Tenders record view. This is only editable by changing the Fisherman, Fisherman & Tender or Tender assigned to the transaction.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK, ERPx_APTransactionLine.AccountSK, ERPx_APTransactionLine.FromDistributionAccountSK, ERPx_APTransactionLine.ToDistributionAccountSK

Distributed Description

Identifies a description of the distribution, including the name of the Vendor, Fisherman, Fisherman & Tender, Tender or Loan. This is required for Adjustment, Tender Resale, Invoice and Balance Transfer transaction types and not required for all other transaction types. For Adjustment transaction types, this field defaults from the 'Distributed To' field on the Adjustment record view. For Tender Resale transaction types, this field can be edited from the 'Tender' field on the Tender Resale record view. For Invoice transaction types, this field can be edited from the 'Vendor' field on the Invoice/Credit Memo record view. For Balance Transfer transaction types, this field can be edited from the 'Transfer Balance To - Credit' field on the Balance Transfer record view. This is only editable by changing the Tender, Vendor or Transfer Balance To fields on the associated transactions.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.FromVendorSK (Tender Resale), ERPx_APTransactionHeader.VendorSK (Invoice), ERPx_APTransactionLine.ToDistributionAccountSK (Balance Transfer)

Doc Date

Identifies the date of the transaction. This is required and can be edited from the 'Date' field on the in the associated transaction header. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.TransactionDate

Doc Description

Error rendering macro 'excerpt-include' : No link could be created for 'Description - Header'.
This is not required and can be edited from the 'Description' field on the associated transaction header. This is always editable.

Database Field: ERPx_APTransactionHeader.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 is not required and can be edited from the 'Doc No' field on the in the associated transaction header. This is always editable.

Database Field: ERPx_APTransactionHeader.DocNumber

GL Date

Identifies the date the transaction posted (or will post) to the general ledger.  This is required and can be edited from the 'GL Date' on the 'Properties' tab of the associated transaction. If not manually edited, this will be automatically set to match the 'Doc Date' when the transaction is saved with a Status of either Approved or Ready to Post. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionHeader.GLDate

GL Period

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the associated transaction. This can only be edited by changing the GL Date.

GL Year

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the associated transaction. This can only be edited by changing the GL Date.

Line Description

Identifies the Description for the line item. This is required and can be edited from the 'Description' on the Item grid of the associated transaction. This is always editable while the transaction is in a Status of New.

Database Field: ERPx_APTransactionLine.LineDescription

Original Amount

Displays the total amount of the transaction. For Invoice, Tender Resale, Adjustment and Balance Transfer transaction types, this displays the 'Extended' amount of an individual line item. This is required and can be edited by changing the Price or Quantity of line items. This can only be edited while in a Status of New.

Database Fields: ERPx_APTransactionLine.ExtendedAmount, ERPx_APTransactionheader.ExtendedAmount

Transaction

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the record view for the selected transaction. This is a system assigned number that comes from the 'Transaction Class' and is required but is not editable by users.

Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'.

Database Field: ERPx_APTransactionHeader.TransactionID

Transaction Type

Identifies the Transaction Type for each transaction. This is required and comes from the Transaction Type selected when starting a new transaction. This is never editable.

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 Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionHeader.TransactionClassSK

Unapplied Amount

Displays the amount of the transaction that is not yet applied.  This is required and updates when values are entered to the Terms Discount Taken and Applied Amount fields. This is calculated by subtracting previous applications from the original amount. This value is not stored in the database.

Related Topics



 Page Definitions

Page Definitions


 Technical Details

Technical Details

  • No labels