The Inventory Transfer Transaction Record View allows users to record the transfer of inventory items from one site to another. In addition, the user can record the transfer of inventory items via an in transit site using the same transaction. The transfer of items using this transaction also allows the user to track warehouse lots and product ownership. The 'Include open Transfer transaction in Available balances' preference will determine whether Available balances are updated before the transaction is posted.

Software Version: 2024.01.31 and newer

Page Header

Header Toolbar

Toolbar Icons	Description
Delete	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!} This toolbar icon is enabled when the transaction status is 'New'.
Help	Opens the online WIKI help page for the current page.
More Actions	Displays a drop down menu of related actions. The list of options includes: Export Details: Opens the Export Details dialog. This toolbar icon is only enabled after the Transaction has been saved the first time and an ID has been assigned. Journal Details: Opens the Journal Details window showing the Journal Entry for this transaction. Until the transaction Approved or Posted, this is a temporary journal entry so no Journal ID will be assigned. A journal entry is only created when freight has been recorded. Reprice: Updates the item prices according to the most recent price list prices if the 'Price List' property is selected and the 'Item Price' has not previously been set. This toolbar icon is enabled when the transaction status is New. Shipment Details: Opens the Shipment Details dialog to allow for inputting freight costs and adding freight legs.
New	Allows users to select the type of transaction or record they want to add. The drop-down displays all active Transfer type transaction classes configured in the system.
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled. Notes are used throughout the application to add additional details to Master Files and Transactions. Transactions and Master Files that support Notes store the text of the note in one or more 'Note Types' as a way to classify/organize notes.
Print	Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. When clicked, all the Reports that launch from the Print Dialog that are assigned to this page, and that the user has rights to (if Report Data Access is enabled) are displayed.
Process Correction	This toolbar icon is only displayed when a correction has been processed from the Void/Correct page. Users can make any edits to the transaction prior to clicking Process Correction. When this icon is clicked, the changes displayed will be the difference between the original and the new transaction. If the transaction was not updated, the message "No changes have been made and a correction cannot be processed. Please either make changes or delete the transaction." will be displayed when the icon is clicked. Once clicked, the icon is hidden.
Save	Saves the changes made to the record.
Save & Close	Saves your changes and closes the page.

Home Tab

Fields	Description
Transfer #: [Transaction ID] For Transfer Receipts: Transfer Receipt #: [Transaction ID]
BOL	Identifies the Bill of Landing ID for the Transfer transaction. This is a text box that is not required. It defaults to blank and if entered, it must be <= 100 characters. On Save, if no value has been entered, it defaults to the transaction ID. This field is always editable while the transaction is in a Status of 'New'. A Bill of Lading (BOL) is a document of title, a receipt for shipped goods, and a contract between a carrier and shipper. This document must accompany the shipped goods and must be signed by an authorized representative from the carrier, shipper, and receiver. Database Field: ERPx_IMTransactionHeader.BOL
Carrier	Identifies the 'Leg 1' Carrier associated with the transaction. This is a single-select standard lookup that is not required. It defaults as blank and is always editable while the transaction is in a Status of 'New'. Carriers represent entities that transport goods from one location to another. They can be actual freight companies (i.e. UPS or Fed Ex) and/or they can represent a delivery method (i.e. Our Truck, Customer Pickup, Transfer in Storage, or UPS-Air). They are used on Inventory transfers and sales order shipments. The lookup contains a list of all 'Active' Carriers. Database Fields: ERPx_SOCarrier.CarrierName, ERPx_IMTransactionHeader.CarrierSK
Corrected From	Displays the Transaction ID of the source transaction the correction is being made from. This is a text box that defaults to the source transaction. This field is not visible unless the transaction is the result of a correction. It is only required on transactions that are being corrected. This field is auto populated by the system and is not editable. 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 Fields: ERPx_IMTransactionHeader.TransactionID, ERPx_IMTransactionHeader.CorrectedFromTransactionHeaderSK
From Site	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 "From Site is required." will be displayed on Save. This defaults as blank and is always editable while the transaction is in a Status of 'New'. 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. On a transfer receipt transaction, this field is disabled. Database Fields: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.SiteSK
Received On	Identifies the date the transfer items are to be delivered to the 'To Site'. This is a date picker is only enabled once a Ship Via site is selected and the transaction is saved. This field defaults to the current date and is required if displayed. The date entered in this field will serve as the transaction date for the second part of the transfer, which is from the Ship Via site and to the To Site. This field must be on or after the Transferred On date, else the message "Received On date must occur on or after the Transferred On date." will be displayed on Save. This field is always editable while the transaction is in a Status of 'New'. Database Field: ERPx_IMTransactionHeader.DeliverOnDate
Reference	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
Ship Via	Identifies the name of the Site the items are being shipped via, or were shipped via. This is a single-select standard lookup that is not required. This defaults as blank and is always editable while the transaction is in a Status of 'New'. Selecting a value for the 'Ship Via' field and saving will display the 'Received On' field . For the first part of the transfer, the Ship Via site will act as the To Site and will have it's inventory increased until the transaction is posted. Once the transaction is posted and the second half of the transfer is created, the Ship Via site will act as the From Site and will have it's inventory decreased. 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 'Active' Inventory Sites where the 'In Transit' property is set to "Yes". On a transfer receipt transaction, this field is always disabled. Database Fields: ERPx_MFSite.SiteName, ERPx_IMTransactionHeader.ViaSiteSK
Status	Identifies the Status of the transaction. This is a single-select standard lookup that defaults as 'New' and is required. 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 Fields: ERPx_IMTransactionStatus.TransactionStatusName, ERPx_IMTransactionHeader.TransactionStatusSK
To Site	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 "To Site is required." will be displayed on Save. This defaults as blank and is always editable while the transaction is in a Status of 'New'. 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.ToSiteSK
Transferred On	Identifies the date the items left the From Site. This is a date picker that is required. It defaults to current date and if missing, the message "Transferred On is required" is displayed on Save. The date entered in this field will serve as the transaction date for the first part of the transfer, if there are multiple parts. This field must be on or before the Received On date, else the message "Received On date must occur on or after the Transferred On date." will be displayed on Save. This field is always editable while the transaction is in a Status of 'New'. This field is not editable on the Transfer Receipt transaction. Database Field: ERPx_IMTransactionHeader.TransactionDate

Properties Tab

Fields	Description
Group 1
GL Date	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 'Transferred On' 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 'Transferred On' field on the 'Home' tab of the Transfer Record View. Else, the message "The GL date must occur on or after the Transferred On 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
Auto-Create New Lots	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
Negative Available Balances	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 Transfer transaction adds 5 Cases, the overall lot balance would still be negative. The following options are possible workarounds: Change the Transfer transaction's "Negative Available Balances" property to "Allowed" Change the Transfer 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
Price List	Identifies the ID of the Price List that is assigned to the transaction. This is a single-select load on demand lookup that is not required. It defaults to the Price List that has the selected transaction class assigned on the 'Transfer_Class' tab of the Price List Record View. This field is always editable while the transaction is in a Status of 'New'. Price Lists are used to store a group of Items with pre-defined prices and effective dates. The lookup contains a list of all the 'Active' Inventory Price Lists. Database Fields: ERPx_MFPriceListHeader.PriceListID, ERPx_IMTransactionHeader.PriceListHeaderSK
Freight Purchase Order	A system assigned value to identify whether a Freight Purchase Order is applicable / allowed and if it has been created or not. It is conditionally set based upon the Transaction Class property values, the Carriers assigned to all the Freight Legs that contain estimated freight, and the Status of the transaction. This is not editable and will one of the following values: Not Applicable: The Transaction's Transaction Class is not configured to create Freight Purchase Orders. Freight PO Allowed: The Transaction's Transaction Class is configured to create Freight Purchase Orders and the Transaction is not Yet Posted. Freight PO Created: A Freight Purchase Order was created for the Freight Leg(s) on this Transaction. Freight PO Not Created: The Transaction's Transaction Class is configured to create Freight Purchase Orders but no Freight Purchase Order was created because not all the Freight Legs, that contained estimated freight, were for Carriers that were configured to create a Freight Purchase Order. Database Field: ERPx_IMTransactionHeader.FreightPOEN
Group 2
Created	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
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. This is a non-editable text box that is required. Database Field: ERPx_IMTransactionHeader.CreatedBy
Last Updated	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
Last Updated By	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
Corrected From	Displays the Transaction ID of the source transaction that was corrected. This is a non-editable text box that is not required. It is only displayed on the corrected transaction and is never editable. Database Fields: ERPx_IMTransactionHeader.TransactionID, ERPx_IMTransactionHeader.CorrectedFromTransactionHeaderSK
Group 3
Void Date	Identifies the date the transaction was voided, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user. This is a non-editable text box that is not required. Database Field: ERPx_IMTransactionHeader.VoidDate
Voided By	Identifies the name of the user that voided 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 not required. Database Field: ERPx_IMTransactionHeader.VoidedBy

Attributes Tab

Fields	Description
Attributes	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).
Required	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 - Transfer).
Value	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.

Page Detail

Items Grid

Toolbar Icons	Description
Add Item	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.
Column Filter Show/Hide	Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column.
Excel	Exports the contents of the grid 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, or excluded columns, only the contents in the grid will be exported.
Find Lots	Opens Find Inventory Lots page in a new window. This feature allows users to find existing lots and view their on hand and available balances. This toolbar icon is only enabled when the transaction status is New.
Group By Show/Hide	Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total.
Mass Update	Opens the mass update dialog, which allows to mass update the following properties: Transaction To Warehouse Lot and 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.
More Actions	Displays a drop down menu of related actions. The list of options includes: LV: Warehouse Lot - Opens the Warehouse Lot List View, in a new tab, filtered for the selected record's Warehouse Lot. RV: Item - Open the item Record View for the selected item RV: Production Batch - Open the Production Batch Record View for the selected line item
Notes	Opens the Notes dialog, filtered for the appropriate Note Type(s). From here, users can add, review, or edit Notes associated with the record. This icon is always enabled.
Quick Column Filter	Used to filter across all columns in the grid. When the user types text into the Quick Column Filter text box, the grid's Filter Row will be automatically hidden. The text in the Quick Column Filter text box automatically replaces any existing Filter Row filters. The results of the data immediately refresh as you enter text.
Remove Items	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'.
Saved Layouts	Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected. Please note that existing saved grid layouts will display the Filter Row as hidden by default.
Fields	Description
Checkbox	Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete.
Gross Weight	This field is currently in development. Identifies the Gross Weight of the line item, calculated as [Net Weight] + ([Units] * [Unit Tare Weight]). This is a numeric text box that is not required. This field defaults as 0 and is auto-populated on Save if the 'Default Gross Weight from Item Setup on Transfer Transaction' Inventory preference is set to "Yes" and the item is managed by Units only or Units and Weight. This field can be both positive or negative. Additionally, this field may be populated when the 'Gross Weight' field on the Find Lots page is saved. This field is always editable while the transaction is in a Status of 'New' or 'Approved'. Database Field: ERPx_IMTransactionDetail.GrossWeight
Item: Description	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 Item 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
Item Price	Identifies the "insured" price of the line item. This is a numeric text box that is not required. This field defaults to 0 if there is no 'Price List' assigned to the 'Properties' tab or if the item is not found on the assigned price list. The number of Item Price decimals that may be entered comes from the 'Price Decimals' property on the 'Properties' tab of the Item Record View. It is always editable while the transaction is in a Status of 'New'. Database Field: ERPx_IMTransactionDetail.ItemPrice
Lot Tracked	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
Net Weight	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. This field defaults to 0 and is editable while the transaction is in a Status of 'New'. This field can be both positive or negative. Once an item has been selected, this field will display with the number of decimals set for the 'Weight Decimals' property on the 'Properties' tab of the Item Record View. If this field is editable, the following will be enforced: For an item that is fixed weight and requires whole units: When Weight is entered: the value will be rounded up to the nearest Weight that results in a whole Unit then the Units will automatically be calculated based on the Weight value. For an item that is fixed weight and does not require whole units: When Weight is entered: the Units will automatically be calculated based on the Weight value. The Weight value does not have to result in an integer Units value. However, because the Units and Weight values round to two decimal places, if the rounded Units value produced by the weight value does not convert to equal the weight value, the weight value will automatically update to equal the converted value of the units since the item is a fixed weight item. For an item that is variable weight and requires whole units: When Weight goes from empty to a value: the Units will automatically be calculated based on the Weight value and then be rounded to the next whole Unit. Weight will remain as the user entered Weight, per the Item's 'Weight Decimals'. When Weight goes from one value to another: the Units will NOT be recalculated. '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
Owner	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 Fields: ERPx_IMLotOwner.OwnerName, ERPx_IMLotBalance.LotOwnerSK
Price List Override By	Identifies the name of the user, formatted to be the "logged-in" user's [User First Name] + [User Last Name], who has updated the 'Item Price' field from the Price List Price on the transaction. This is a non-editable text box that is not required. This field defaults as blank and remains blank unless a Price List is assigned to the transaction and the user manually updates the 'Item Price' field to be different than the 'Price List Price' field. The field is for informational use only and is never editable. Database Field: ERPx_IMTransactionDetail.PriceListOverrideBy
Price List Override Date	Identifies the date when the 'Item Price' field was updated from the Price List price on the transaction record, formatted from the users 'Date Format' preference. This is a non-editable text box that is not required. This field defaults as blank and remains blank unless a Price List is assigned to the transaction and the user manually updates the 'Item Price' field to be different than the 'Price List Price' field. The field is for informational use only and is never editable. Database Field: ERPx_IMTransactionDetail.PriceListOverrideDate
Price List Price	Identifies the published "insured" price of the item, based on the Price List that is assigned to the transaction. This field is for informational use only and is never editable. This field defaults to 0 if there is no 'Price List' assigned to the 'Properties' tab or if the item is not found on the assigned price list. Price Lists are used to store a group of Items with pre-defined prices and effective dates. Database Field: ERPx_IMTransactionDetail.PriceListPrice
Price UOM	Identifies the unit of measure the price is calculated from. This is a single-select standard lookup that is required. It defaults from the 'Default Price UOM' property on the 'Properties' tab of the Item Record View when an item is selected and the transaction is saved. If a Price List is assigned to the transaction and the item is configured on the Price List, then this field defaults to the 'Price UOM' field on the 'Transfer_Items' tab of the Price List Record View. It is always editable while the transaction is in a Status of 'New'. 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_MFPriceListItemHistory.PriceUOMSK, ERPx_IMTransactionDetail.PriceListItemSK
Production Batch	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'. Once saved, this field will be disabled. 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
To Owner	Identifies the Lot Owner to which the corresponding item is being transferred to. 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 while the transaction is in a Status of 'New'. 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 Fields: ERPx_IMLotOwner.OwnerName, ERPx_IMLotBalance.LotOwnerSK
To Warehouse Lot	Identifies the Warehouse Lot to which the selected item or inventory lot is being transferred to. 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: On a one-part transfer, if the 'To Site', identified on the transaction header, is a warehouse lot tracked Site On a two-part transfer, if the 'Ship Via Site', identified on the transaction header, is a warehouse lot tracked Site On a Transfer Receipt, if the 'To Site', identified on the transaction header, is a warehouse lot tracked Site and is disabled when these conditions are not true. If required and blank, the message "To Warehouse Lot is required for Warehouse Lot Tracked sites when Approving or Posting." will be displayed on Save of Statuses of 'Approved' or greater. If the 'To Site' field (one part transfer) or the 'Ship Via' field (two part transfer) is warehouse lot tracked, then the 'Auto Generate Warehouse Lots on Transfer Receipts' property on the Site Record View will determine whether the 'To Warehouse Lot' field is defaulted. The 'Auto Generate Warehouse Lots By' property on the Site Record View will determine the default value of the 'To Warehouse Lot' field when the transaction is saved If enabled, this field is editable via the Item Grid - 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. Updating this field on the transfer receipt transaction will result in the reallocation of items to the updated Warehouse Lot when the transaction is saved. Database Fields: ERPx_IMWarehouseLot.WarehouseLotID, ERPx_IMLotBalance.WarehouseLotSK
Units	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'. This field can be both positive or negative. This field will display the number of decimals set for the selected item on the 'Unit Decimals' property on the 'Properties' tab of the Item Record View. If this field is editable, the following will be enforced: For an item that is fixed weight and requires whole units: When Units are entered: the value will be rounded up to the nearest integer then the Weight will automatically be calculated based on the Units integer value. For an item that is fixed weight and does not require whole units: When Units are entered: the Weight will automatically be calculated based on the Units value. The Units value does not have to be an integer. For an item that is variable weight and requires whole units: When Units go from empty to a value: the value will be rounded up to the nearest integer then the Weight will automatically be calculated based on the Units integer value. When Units go from one value to another: the value will be rounded up to the nearest integer but the Weight will NOT be recalculated. '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
Unit UOM	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'. 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. This lookup contains all 'Active' Unit UOMs on the selected Item's UOM Schedule. Database Fields: ERPx_IMUOM.UOMName, ERPX_IMItem.UOMScheduleSK, ERPx_IMTransactionDetail.TransactionUnitsUOMSK
Warehouse Lot	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
Weight UOM	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'. 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. This lookup contains all 'Active' Weight UOMs on the selected Item's UOM Schedule. Database Fields: ERPx_IMUOM.UOMName, ERPX_IMItem.UOMScheduleSK, ERPx_IMTransactionDetail.TransactionWeightUOMSK