Deletes the transaction, batch, 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!}

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 reason the balances are being adjusted. This is a single-select standard lookup that is not required. It defaults as blank. This field is always editable while the transaction is in a Status of 'New'. This value will auto populate the 'Reason Code' field in the grid section when actual balances have been entered.

The lookup contains the values configured for Adjustment reason codes in the Reason Codes Master File (Company > Setup > Reason Codes).

Database Field: ERPx_MFNoteTypeReasonCode.ReasonCode, ERPx_IMTransactionHeader.ReasonCodeSK

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

Database Field: ERPx_IMTransactionHeader.CreatedDate

Identifies the date the transaction posted (or will post) to the general ledger.  This is a date picker that is required. It defaults to blank on New and from the 'Date' field on the 'Home' tab when the record is saved as Approved or greater if no value exists. It 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 Adjustment 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 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 an Adjustment transaction adds 5 Cases, the overall lot balance would still be negative. The following options are possible workarounds: 

•  Change the Adjustment transaction's "Negative Available Balances" property to "Allowed"
•  Change the Adjustment 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". If it is optional, it will display as blank. This value is only editable from the 'Assign Attribute Rules' page (Company → Setup → Attributes → Inventory → Transactions hyperlink → Inventory - Adjustment). 

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.

 Adds a blank line in the grid to allow for data entry. If a valid Item ID is entered, the line will be saved. If not, the 'Item Lookup' window will open allowing users to search for the Item. This toolbar icon is only enabled when the transaction status is New.

Opens the mass update dialog, which allows to mass update the following properties: 

•  Transaction
  • Warehouse Lot - This may only be updated if the Site is warehouse lot tracked and if the Status of the transaction is 'New'. Else the message "Warehouse Lot may only be updated for transactions in the status of New." will be displayed on Save.
• Production Batch Properties
  • Batch Class, Batch Date, Expiration Date, Production Batch Site and Status
• Production Batch Attributes
  • Each Batch Attribute will be available
• Production Batch Certifications
  • Each applicable certification will be available

This toolbar icon is always enabled.

 Removes the selected line(s). When clicked, you are prompted with the message "Are you sure you want to delete n item(s)? Okay or Cancel". This cannot be done on transactions with a Status of 'Approved', Ready to Post', 'Posted', 'Closed', 'Void', or 'Replaced'.

Identifies the Item, displayed as Item ID: Item Description.  This is a text box that is required. It defaults as blank and is not editable once the line item has been saved to the transaction.

When the 'Add Item' icon is clicked, users may enter all or part of an Item ID or Description and hit the Enter key on the keyboard. If a complete Item ID was entered, the line item will be saved, if not, the Item Lookup dialog box will open with a list of items containing the data entered. From the 'Item Lookup' dialog box, users may check the checkbox next to one or multiple item(s) to add to the transaction using the Save & Close button.

Item IDs are the unique identifier for Items. 

The lookup contains a list of all active Inventory type Items in the Items Master File.

 Selecting an Item will default the 'Inventory Unit UOM' and 'Inventory Weight UOM' properties specified on the Item Record View.

Database Fields: ERPx_IMItem.ItemID, ERPx_IMItem.ItemDescription, ERPx_IMTransactionDetail.ItemSK

Identifies whether or not item balances are maintained for "Production Batches". This is a non-editable text box that is not required. This value defaults from the 'Lot Tracked' field in the 'Properties' tab of the Item Record View. It displays as "Yes" if the line item is a lot tracked item. It displays as blank if the item is not a lot tracked item. This field is for informational use only and cannot be edited.   

Database Fields: ERPx_IMItem.TrackMethodEN, ERPx_IMTransactionDetail.ItemSK

Identifies the Production Batch ID of the Lot. This is a text box that is only required to save a line item on a transaction in 'Approved' or greater status if the item selected is Lot Tracked. It defaults as blank and is only editable if the selected item is Lot Tracked and the transaction is in a Status of 'New'. This field must be <= 50 characters.

A Production Batch is the identifier that contains all the Traceability information (Production Batch Properties and Attributes) for Lot Tracked Items. This number stays attached to the product, even if it is transferred to another Site. Production Batch is one of the 5 components that make up a unique Inventory Lot and it is required when entering a transaction line for a Lot Tracked Item. This value will be blank and/or disabled for all non-Lot Tracked items on screens that include a Production Batch field.

Database Fields: ERPx_IMProductionLot.ProductionLotID, ERPx_IMTransactionDetail.ItemSK

Identifies a the Lot Owner for a line item. This is a single-select standard lookup that is required. It defaults from the 'Default Owner' preference on the Inventory Preferences page. This field is editable until a line item has been saved.

Owners are used to identify who owns the inventory. Additional Owners are typically added for companies that do custom processing and need to keep that inventory separate from their own. Owner is one of the 5 components that make up a unique Inventory Lot and it is required on all Inventory Lots.

The lookup contains a list of all Lot Owners.

Database Field: ERPx_IMLotOwner.OwnerName

Identifies the reason the balances are being adjusted. This is a single-select standard lookup that is required to save the transaction in a Status of 'Approved' or greater if the "Require Reason Codes for all Adjustment lines" property is set to "Yes" on the Inventory Preferences page. If missing and required, the message "Reason Codes are required for all Adjustment transaction lines" will be displayed on Save. This field defaults from the 'Reason Code' field in the 'Home' tab of this Record View. This field is always editable while the transaction is in a Status of 'New'.

The lookup contains all the Adjustment Reason Codes setup in the Company→ Reason Codes Master File

Database Fields: ERPx_MFNoteTypeReasonCode.ReasonCode, ERPx_IMTransactionDetail.ReasonCodeSK

Identifies the number of units to be added or subtracted for the corresponding item in the inventory lot. This is a numeric text box that is sometimes required. This field is required and editable only if the item is managed by Units Only or Units or Weight. This field defaults to 0 and is always editable while the transaction is in a Status of 'New'. Unlike other inventory transactions, Adjustment transactions treat all items as variable weight and the require whole units property is not enforced. Adjustment transactions also allow users to set units as positive and weight as negative and vice versa. Units can be entered with 5 decimals regardless of the 'Unit Decimals' property configured in the 'Properties' tab for the selected Item on the Item Record View.

'Units' and 'Unit UOM' fields will always display as the values entered by the user. However for consistency, Units that are saved using a UOM that is different than the 'Inventory Unit UOM' will be converted and subsequently stored in the default Inventory Unit UOM.

Database Field: ERPx_IMTransactionDetail.TransactionUnits

Identifies the unit of measure that the units are stored in (Box, Bag, Case, Each, Tote, etc.) for a line item or on the transaction. This is a single-select standard lookup that is required to save a line item on transactions with a Status of 'Approved' or greater. This field will be disabled if the item is managed by Weight Only. If enabled, it will default from the 'Inventory Unit UOM' property on the 'Properties' tab of the Item Record View for the selected Item. If enabled, this field will be editable while the transaction is in a Status of 'New'.

This lookup contains all 'Active' Unit UOMs on the selected Item's UOM Schedule.

A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext.

Database Fields: ERPx_IMUOM.UOMName, ERPX_IMItem.UOMScheduleSK, ERPx_IMTransactionDetail.TransactionUnitsUOMSK

Identifies the Warehouse Lot to which the selected item or inventory lot belongs. This is a single-select standard lookup that is sometimes required to save a line item on transactions with a Status of 'Approved' or greater. It is required when the 'Site', identified on the transaction header, is a warehouse lot tracked Site and is disabled when it is not. If required and blank, the message "Warehouse Lot is required for Warehouse Lot Tracked sites when Approving or Posting." will be displayed on Save of Statuses of 'Approved' or greater. This field defaults as blank and will be disabled if the 'Site' field on the transaction is not warehouse lot tracked. If enabled, this field is editable via the Mass Update Dialog while the transaction is in a Status of 'New'. This field must be <= 50 characters.

The transaction will validate the Warehouse Lot based on the following:

• If the selected Site is warehouse lot tracked and allows multiple items, the transaction will allow multiple items to be coded to the same warehouse lot and will create the warehouse lot with the default item selection of 'All Items Selected'.
• If the selected Site is warehouse lot tracked and allows multiple items and the warehouse lot ID entered for an item on the transaction already exists, the transaction will verify the warehouse lot is either set to 'All Items Selected' or the specific item is selected.
• If the selected Site is warehouse lot tracked and only allows single items, the transaction will restrict multiple items from being coded to the same warehouse lot and it will create the warehouse lot for the first item code on the transaction and will prompt an error for the next item trying to save to the same warehouse lot.
• If the selected Site is warehouse lot tracked and only allows single item and the warehouse lot ID entered for an item on the transaction already exists, the transaction will verify the warehouse lot is set to the specific item that is selected.
• If the selected site is not warehouse lot tracked, no warehouse lots can be entered.

A Warehouse Lot (aka Storage Lot) is used by 3rd party distribution sites to identify a unique quantity of product they are storing. Unlike a Production Batch number that never changes, Warehouse Lots will change as product is transferred to other Sites and/or transferred into exiting Warehouse Lots within the same Site. The 'Warehouse Lot' is one of the 5 components that make up a unique Inventory Lot and it is required when entering a transaction line on a transaction for a Warehouse Lot Tracked Site. This value will be blank and/or disabled for all non-Warehouse Lot Tracked Sites on screens that include a Warehouse Lot field.

Database Fields: ERPx_IMWarehouseLot.WarehouseLotID, ERPx_IMLotBalance.WarehouseLotSK

Identifies the weight amount to be added or subtracted for the corresponding item in the inventory lot. This is a numeric text box that is sometimes required. This field is required and editable only if the item is managed by Weight Only or Units or Weight Only. This field defaults to "0.00" and is always editable while the transaction is in a Status of 'New'. Unlike other inventory transactions, adjustment transactions treat all items as variable weight and require whole units property is not enforced. Adjustment transaction also allow users to set units as positive and weight as negative and vice versa. Weight can be entered with 5 decimals regardless of the 'Weight Decimals' property configured on the 'Properties' tab for the selected Item on the Item Record View. 

'Weight' and 'Weight UOM' fields will always display as the values entered by the user. However for consistency, Weight that is saved using a UOM different than the 'Inventory Weight UOM' will be converted and subsequently stored in the default Inventory Weight UOM.

Database Field: ERPx_IMTransactionDetail.TransactionWeight

Identifies the unit of measure that the weight is stored in (Lbs, Kg, Oz, Ton, etc.) for a line item or on the transaction. This is a single-select standard lookup that is required to save a line item on transactions with a Status of 'Approved' or greater. This field will be disabled if the item is managed by Units Only. If enabled, it will default from the 'Inventory Weight UOM' property on the 'Properties' tab of the Item Record View for the selected Item. If enabled, this field will be editable while the transaction is in a Status of 'New'.

This lookup contains all 'Active' Weight UOMs on the selected Item's UOM Schedule.

A UOM is a quantity used as a standard of measurement. It identifies how much makes up "1" of the measurement. Examples include Bag, Box, Each, Kg, Lb, ext.

Database Fields: ERPx_IMUOM.UOMName, ERPX_IMItem.UOMScheduleSK, ERPx_IMTransactionDetail.TransactionWeightUOMSK