Deletes the transaction or master file record. When clicked, users will be prompted with: "Are you sure you want to delete this record?". Click "OK" to confirm, or "Cancel" to return without deleting. 

_{WARNING: Records cannot be recovered once they are deleted!}

Allows the user to create a new master file record or transaction by opening a blank record view page. This icon is always enabled.  The drop-down displays all active Receipt type transaction classes configured in the system.

Identifies the date of the transaction. This is a date picker that is required. If missing, the message "Transaction Date is required" will be displayed on Save. It defaults to the current date, formatted from the users 'Date Format' preference. This field is always editable while the transaction is in a Status of 'New'. 

Database Field: ERPx_IMTransactionHeader.TransactionDate

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This is a text box that is not required. It defaults as blank. If entered, this field must be <= 100 characters. This field is always editable while the transaction is in a Status of 'New'. 

Database Field: ERPx_IMTransactionHeader.PONumber

Identifies the Reference entered for the transaction.  This is a text box that is not required. It defaults as blank. If entered, this field must be <= 100 characters. This field is always editable while the transaction is in a Status of 'New'. 

Database Field: ERPx_IMTransactionHeader.Reference

Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is a single-select standard lookup that is required. If missing, the message "Site is required." will be displayed on Save. This defaults as blank and is not editable after initial Save. 

Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances.

The lookup contains a list of all the 'Active' Inventory Sites.

Database Fields: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.SiteSK

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 Fields: ERPx_IMTransactionStatus.TransactionStatusName, ERPx_IMTransactionHeader.TransactionStatusSK

Identifies whether inventory lots can be auto-created if they do not already exist. This is a single-select load on demand lookup that is required. It defaults from the 'Auto-Create New Lots' property in the 'Properties' tab of the associated Transaction Class Record View. This field is always editable while the transaction is in a Status of 'New'. If set to "Not Allowed" and the transaction would result in the creation of a new inventory lot, the message "Lots would be created when Auto-Create Lots is Not Allowed" will be displayed on Save.

This lookup contains the values in the IMAutoCreateNewLots Enumeration Class.

Database Field: ERPx_IMTransactionHeader.AutoCreateLotsEN

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. This is a non-editable text box that is required.

Database Field: ERPx_IMTransactionHeader.CreatedBy

Identifies the date the transaction posted (or will post) to the general ledger.  This is a date picker that is required. It defaults from the 'Date' field on the 'Home' tab and is always editable while the transaction is in a Status of 'New'. This field must be on or after the 'Date' field on the 'Home' tab of the Receipt Record View. Else, the message "The GL date must occur on or after the Transaction Date" will be displayed on Save. Additionally, if the GL Date is not within an open Fiscal Period for Inventory, the message "The Fiscal Period is not open. The GL Date must be in a Fiscal Period that is open for Inventory." will be displayed on Save for statuses of 'Approved' or greater.

Database Field: ERPx_IMTransactionHeader.GLDate

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. This is a non-editable text box that is required.

Database Field: ERPx_IMTransactionHeader.LastUser

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. This is a system assigned value and is never editable by a user.  This is a non-editable text box that is required.

Database Field: ERPx_IMTransactionHeader.LastUpdated

Identifies whether the transaction allows lots to be left with negative available balances. This is a single-select load on demand lookup that is required. It defaults from the 'Negative Available Balances' property in the 'Properties' tab of the associated Transaction Class Record View. This field is always editable while the transaction is in a Status of 'New'. If set to "Not Allowed" and the transaction would result in an inventory lot with a negative available balance, the message "Lot balances would be negative when set to Not Allowed" will be displayed on Save.

This lookup contains the values in the IMAllowNegativeAvailableBalances Enumeration Class.

 If Sales Order allocation preferences are set to either “Available Only” or “Available and On Hand” and a Sales order has been allocated prior to a user updating the Inventory “Negative Available Balances” property, it is possible to draw the lots negative.   

A message will be displayed to the user if lot balances are negative and a new transaction is created which would impact those balances positively, however the overall balances would still be negative.  For example, if the lot balance is -10 Cases and a Receipt transaction adds 5 Cases, the overall lot balance would still be negative. The following options are possible workarounds: 

•  Change the Receipt transaction's "Negative Available Balances" property to "Allowed"
•  Change the Receipt transaction to result in a zero or greater inventory balance.
•  Use Cycle Count feature to change inventory balance to zero or greater.

Database Field: ERPx_IMTransactionHeader.NegativeBalancesEN

A non editable text box that shows the name of the Attribute. Attributes are user-definable fields that are used on master files and transactions and are editable from the Attributes List View. The Attribute will only be displayed if the Applies property on the Assign Attribute Rules by page is set to either "Yes - Required" or "Yes - Not Required". Attributes set to "No" will not be displayed. The Attributes displayed here are setup and assigned in the Attributes section of the Company module (Company → Setup → Attributes → Inventory). 

A non editable text box that shows whether the Attribute Value is required or not. If the Attribute Value is required it will display "Yes - Required" if it is optional it will display "Yes - Not Required". This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → Inventory → Transactions hyperlink). 

Identifies the value assigned to the corresponding attribute.

Because Attributes are configurable as either Text, List, Date, or Date/Time the data entry is either a text box, lookup, or date picker. The value defaults to blank and is only required if the Attribute's 'Applies' property is set to "Yes - Required" in the Assign Attribute Rules page. Attribute Values for Master Flies are always editable. Attribute Values for transactions are always editable for unposted transactions.

 Deletes the selected line(s) from the transaction. When clicked, you are prompted with the message "Are you sure you want to delete n item(s)? Okay or Cancel". This icon is only enabled for transactions with a Status of 'New'. This toolbar icon is only enabled when the transaction is in a Status of 'New'.