Software Version: yyyy.mm.dd and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
| Edit | Opens the selected record for editing. If a record is not selected, the page will not open. |
| 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 Options | Error rendering macro 'excerpt-include' : No link could be created for 'Search Options for Kendo - Global'. |
| Help | Opens the online WIKI help page for the current page.
|
| Mass Update | Opens the mass update dialog, which allows to mass update the following properties:
|
| More Actions | Opens a drop-down menu for the user to select Void/Correct, which opens the Void/Correct page and allows the user to either Correct, Void or Void & Correct a transaction. |
| New | Allows users to select the type of transaction or record they want to add. The list contains:
|
| Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. | |
| View | Opens a drop-down menu for the user to select Shipment Details, which opens the Shipment Details Record View for the associated record. This is only applicable to Transfer type transactions. |
| Fields | Description |
| Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
| BOL | Identifies the Bill of Lading reference/ID that was entered on the corresponding Transfer transaction. If no value was entered by the user, this field is populated with the Transaction ID of the corresponding Transfer when the record is saved. This is not required and can be edited on the Home tab of the record view. This field is always editable while the transaction is in a status of New. Database Field: ERPx_IMTransactionHeader.BOL |
| Corrected From | Identifies the Transaction ID of the source transaction that was corrected. This field only displays a value when the transaction was corrected and is never editable. Database Field: ERPx_IMTransactionHeader.CorrectedFromTransactionHeaderSK |
| 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_IMTransactionHeader.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_IMTransactionHeader.CreatedBy |
| Date | Identifies the date of the transaction. This is not required and can be edited from the 'Home' tab on the record view while in the status of New. For Transfer type transactions this is the 'Transferred On' date. Database Field: ERPx_IMTransactionHeader.TransactionDate |
| GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This is required and can be edited from the 'Properties' tab on the Transfer transaction record view. If no value is specified, this field will be populated with the transaction date on save. Database Field: ERPx_IMTransactionHeader.GLDate |
| Reference | Identifies the Reference entered for the transaction. This is not required and can be edited from the 'Home' tab on the record view while in the status of New. Database Field: ERPx_IMTransactionHeader.Reference |
| Site | Error rendering macro 'excerpt-include' : No link could be created for 'Site'. This is required and can be edited from the 'Home' tab on the record view while in the status of New prior to Save. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Fields: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.SiteSK |
| Status | Identifies the Status of the transaction. This is required and can be edited from the 'Status' on the 'Home' tab of the Adjustment, Production, Receipt and Transfer Record View and represents the status of the transaction. This is always editable while the transaction is in a Status of 'New' or 'Approved'. Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type. The Statuses that apply to transactions in this List View include: New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist. Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted". Database Field: ERPx_IMTransactionStatus.TransactionStatusName, ERPx_IMTransactionHeader.TransactionStatusSK |
| To Site | Error rendering macro 'excerpt-include' : No link could be created for 'To Site'. This is required and can be edited from the 'Home' tab on the record view while in the status of New prior to Save. This field is only visible on Transfer type transactions. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Field: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.ToSiteSK |
| Transaction Class | The unique identifier of the Transaction Class. This is required and is a system assigned value based on which transaction class the user created the transaction in. It is never editable by a user. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPX_IMTransactionClass.TransactionClassID,ERPx_IMTransactionHeader.TransactionClassSK |
| Trans Type | Identifies the Transaction Type for each transaction. This is a system assigned value and is never editable by a user. The transaction types are: Adjustment, Production, Receipt and Transfer. 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_IMTransactionType.TransactionTypeDescription, ERPx_IMTransactionHeader.TransactionTypeSK |
| Transaction | Identifies the unique Transaction ID for each transaction. Clicking on the link opens the corresponding transaction record view. This is a system assigned value and is never editable by a user. 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_IMTransactionHeader.TransactionID |
| Via Site | Error rendering macro 'excerpt-include' : No link could be created for 'Via Site'. This is not required and can be edited from the 'Home' tab on the record view while in the status of New prior to Save. This field is only visible on Transfer type transactions. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. Database Field: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.ViaSiteSK |
Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab.