The Inventory Receipt Transaction Record View allows users to record the receipt of inventory from an outside entity. This transaction allows multiple line items to be received into a single site. The 'Include open Receipt transactions in Available balances' preference will determine whether Available balances are updated before the transaction is posted. Once the transaction is posted, it will update the On Hand lot balance of the item(s).

To view the help page for the NorthScope 2.0 IM Receipt Record View, please click here: Receipt Transaction Record View

Software Version: 2023.11.30 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!} If the Receipt Transaction was linked to a PO #, the PO will be updated to reflect the changes.
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: IQ: PO Linked Transactions - Opens the "PO Linked Transactions" inquiry showing the Purchase Order and all AP Invoices, AP Credit Memos, and Inventory Receipts associated with it. Change Ship To - Opens the 'Change Ship To' window allowing users to change the Ship To address for this Purchase Order.
New	Allows users to select the type of transaction or record they want to add. The list contains all the 'Active' Receipt Transaction Class IDs displayed as [TransactionType] - [ClassID]. For example: "Receipt - Packaging". Note: The Transaction Class will not display after the Transaction Type if the Class ID is named "Default"
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
REC#: [TransID] PO#: [PO] REQ#: [REQ#] [Received From]
Comment	Identifies the header comment/description of the transaction or batch. This is text box is not required but if entered, it must be <=150 characters. This defaults as follows: From the 'Comment' on the source AP Invoice/Credit memo for Receipts auto-created from a source AP Transaction. From the 'Comment' on the source PO # if one exists. As blank for manually entered Receipts that are not linked to a PO #. 'Created from Grower Ticket' when a Receipt transaction is created from linked inventory items on a posted Grower Accounting ticket. The 'Comment' can be overwritten and is always editable even after the transaction is posted Database Field: ERPx_IMTransactionHeader.Description
Date	Identifies the date of the transaction. This is a date picker that defaults to today's date for manually entered transactions or from the source AP Transaction for transactions created from an AP Invoice/Credit Memo. This is required and if missing, the message "Transaction Date is required." will be displayed on Save. The Date must be on or before the GL Date when Approving or Posting the transaction. If not, the message "The GL Date must be on or after the Transaction Date." will be displayed on Save. This is editable while the transaction is in a Status of "New". Database Field: ERPx_IMTransactionHeader.TransactionDate
PO #	A Purchase Order # (aka PO #) is the unique identifier of a Purchase Order. This is a text box that is not required and is editable when the transaction is in a Status of "New". If a valid PO# is not entered, the 'PO # lookup' will open to provide a way to search for "valid" PO's. Once a valid PO# has been selected, or manually entered, all the Purchase Order line items (with a remaining quantity) that are not already on the transaction will be auto-added to the transaction and both the 'PO #' and 'Rec. From' values will be set and disabled. A 'PO #' is considered valid for Receipts based on: The 'PO Type' of the Purchase Order PO Type of "Multiple Invoices and Receipts" are always considered PO Type of "Single Invoice and Receipt" are considered if the Purchase Order has not been assigned to an IM Receipt The 'Status' of the Purchase Order New - Only if the 'First Status POs can be Received or Invoiced' property on the Purchase Order Class is set to "New". Released - always considered valid Closed - Never considered valid Database Fields: ERPx_APPoHeader.PurchaseOrderID, ERPx_IMTransactionHeader.POHeaderSK
Rec. From	Identifies the name of the entity (Vendor, Fisherman, Grower, etc.) the product was received from. This is text box that is only required if a PO # has been entered and it defaults as: Blank for manually entered Receipts The 'Vendor Name' from the source AP Invoice/Credit Memo if the receipt was auto created. The 'Vendor Name' from the source PO # if a valid PO # is assigned. The 'Farmer Name' from the source Grower Accounting Ticket if the ticket contained line items that have linked inventory items assigned. This is editable when the transaction is in a Status of "New" for Receipts that are not linked to a PO #. For Receipts that are linked to a PO #, this is not editable. This value will be stamped on the Production Batch for all lot tracked items when the transaction is saved as Ready to Post/Posted. Database Fields: Database Field: ERPx_IMTransactionHeader.RecFrom
Reference	Identifies the Reference entered for the transaction. This is text box that defaults to blank and is not required, but if entered, it must be <=100 characters. This is always editable even after the transaction is posted. If the Receipt transaction is created as a result of a Grower Accounting ticket that has linked inventory items, this value will default as the Ticket # of the corresponding posted Grower ticket. The Reference will not default from the Reference on a linked Purchase Order. These are treated as separate reference fields. A Reference number is used to record an additional tracking number that associates this transaction to another system. For example, if a transaction was imported from a 3rd party system this could be used to store the unique identifier from that system's transaction. Database Field: ERPx_IMTransactionHeader.Reference
Site Name	Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is single select lookup that is required and defaults in the following sequence: From the Site assigned to the linked PO (if a PO # is entered for this transaction) From the Site assigned to the linked Grower Accounting ticket (if the ticket contained items that have linked inventory items assigned). Otherwise, blank for the user to select the required value. This is editable while the transaction is in a Status of "New" and until a line item (with full lot information) is saved. The Site can be changed; it is not restricted to the Site on the linked Purchase Order. Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. This lookup contains a blank value, the current assigned value, and a list of all active Sites. Database Fields: ERPx_IMTransactinHeader.SiteSK, ERPx_MFSite.SiteID
Status	Identifies the Status of the transaction. This is a single-select lookup that is required. It defaults as "New" and is always editable. The Statuses that apply to transactions in this Record 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_IMTransactionHeader.TransactionStatusSK

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 defaults as blank and is required to Approve or Post the transaction. If it has not been manually assigned, it will be automatically set to match the transaction's 'Date' when the transaction is saved with a Status of either Approved or Ready to Post. The GL Date must be on or after the transaction's 'Date' when Approving or Posting the transaction. If not, the message "The GL Date must be on or after the Doc Date." will be displayed on Save. This is always editable while the transaction is in a Status of New. Database Field: ERPx_IMTransactionHeader.GLDate
Transaction Date	This is a non-editable control that shows the 'Transaction Date' from the Home Tab. This is informational only from here. Database Field: ERPx_IMTransactionHeader.TransactionDate
Auto-Create New Lots	Identifies whether inventory lots can be auto-created if they do not already exist. This is a single-select 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 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.* Database Field: ERPx_IMTransactionHeader.NegativeBalancesEN
Group: 2
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. 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 Last Updated Date & Time of the Transaction, 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 required. Database Field: ERPx_IMTransactionHeader.LastUser
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
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
Group: 4
Transaction Class ID	The unique identifier of the Transaction Class. This is required and comes from the 'Receipt Class' selected when the transaction was initially created or from the Receipt Class set as the Receipt 'Transaction Default' for Receipts that were auto created. This is not editable. Transaction Classes are used to categorize transactions within transaction types and assign specific default values and business rules for each. Database Field: ERPx_IMTransactionHeader.TransactionClassSK, ERPx_IMTransactionClass.TransactionClassID
Linked AP Transaction ID	Identifies the transaction ID for the AP Invoice/Credit Memo transaction that is linked to this transaction. This is not required and not editable. This will be populated if a Receipt was created from the AP Invoice/Credit Memo or if the AP Invoice/Credit Memo was created from the Receipt. If a Receipt was linked but was either deleted or voided, the link will be removed.
Transaction SK	Identifies the SK value of the Transaction. This is a non-editable text box that is informational only. Database Field: ERPx_IMTransactionHeader.TransactionHeaderSK

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 - Receipt).
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. This is editable if the Transaction Class property 'Allow Attribute Edit After Approval' is set to "Yes".

Page Details

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.
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 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 Warehouse Lot Properties Storage Begin Date - This is a date picker field that the user can select or enter a valid date. Storage Renewal Day - This must be a number between 1 - 31 that represents the day of the 'Storage Begin Date'. If a Storage Begin Date is provided and the Storage Renewal Day is blank, we will automatically calculate and assign the value. For example, if the Storage Begin Date = 02/26/2022, the Storage Renewal Day would be 26. Users cannot enter 0 as a value, but the property is not required and may be blank. Warehouse Lot Attributes Each Warehouse Lot Attribute will be available
More Actions	Displays a drop down menu of related actions. The list of options includes: IQ: PO Linked Lines - Opens the "PO Linked Lines" inquiry showing the Purchase Order and all the AP Invoices, AP Credit Memos, and Inventory Receipt lines associated with this Purchase Order Item. 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
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.
Item	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. Items represent objects that you sell, produce, and/or purchase that are tracked within the system. They are used on Sales, Inventory, Fisherman Accounting and Purchasing transactions. 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:ItemDescription, ERPX_IMTransactionDetail.ItemSK
Line Comment	Identifies an alternate comment/description for a line item. This is most commonly used to either identify the Vendor's Item ID or to add more clarity to a generic/bulk Item ID. This is text box that is not required. For transactions that are not linked to a Purchase Order this defaults as blank. For transactions that were auto created from an AP transaction this defaults from the source transaction lines 'Line Comment'. For manually entered transactions that are assigned with a PO #, this will default from 'Line Comment' on the PO Line Item. This value can always be overwritten. This is not required and is always editable, even after the transaction is posted. If entered, it must be <=100 characters. When Receipts are loaded from a PO, this will default as the 'Line Comment' on those transactions. Database Fields: ERPX_IMTransactionDetail.LineComment, ERPx_APPoLine.LineComment
Line Description	Identifies an alternate item description for a line item. This is most commonly used to either identify the Vendor's Item Description or to add more clarity to a generic/bulk Item ID. This is not required, is always editable until the transaction is Approved or Posted, and defaults as follows: For line items that are manually added this default as blank. Database Fields: ERPX_IMTransactionDetail.LineDescription, ERPx_APPoLine.LineDescription
Ln.	Identifies the Line # for each Transaction Line Item. The Line # sets the sort of the items on grids, list views, inquiries, and reports. This is an editable text box that defaults to the next available base-10 number. It is required, and is editable while the transaction is in a Status of "New". To re-sequence the lines, edit one or more lines with a new positive number that would put the line item where you want it sorted, and click the Save button. On save, the line items will be resorted, and the Ln. values will be re-set to base-10 values. For example, if you had line items 10, 20, and 30 and you wanted the last one (Ln. 30) to be second, you could edit the value to any number between 10 and 20 (i.e., 15) and on save the lines would be sorted in the new sequence (10, 15, and 30) and then all Ln.'s would be re-set to base 10 numbers (10, 20, 30). Database Field: ERPx_IMTransactionDetail.LineNumber
Market Cost	Displays the Market Cost assigned to the item or lot. This is the Market base cost when the the Source is Base and Market layer cost when the source is Layer. This is an editable numeric textbox formatted to 2 decimals that is not required. If entered it must be >=0 else the message "Market Cost must be greater than or equal to 0." will be displayed on Save. It defaults based on the following: If the Lot has cost history the value will display the most recent Market Cost for the lot. If it is a new Lot and the corresponding Item has a Market Cost set on the Item master file, it will default this value. Else, it will be blank. The Market Cost reflects the estimated "market" value for the inventory. Market Costs are typically set by taking Actual costs and adding additional components such as delivered freight, brokerage/rebate amounts, and desired profit margin. For each individual LotSK, this is calculated as the [Market Base Cost Rate] + sum of all the [Market Cost Layer Rates]. Market Costs are typically maintained in companies where costs and/or margin needs to be shown/used in Sales Order based on the current market value of the item, not the Actual costs.
PO Ln.	Identifies the Purchase Order line item that the Receipt line item is linked to. This is a single-select lookup that is not required. If a 'PO #' is entered/selected for this transaction, as line items are added to the Receipt, if they are also on the Purchase Order, this will default from the Purchase Order's 'Ln.' as [PO#]: [Ln]. This is editable while the transaction is in a Status of "New". The lookup contains a blank value, the current assigned value, and a list of all the Purchase Order Line Numbers (from the PO # assigned to this transaction) that matches the selected Item ID. When AP Invoices, Credit Memos, and IM Receipts are loaded from a PO, this will default from the 'Ln.' of the Purchase Order Item. Database Field: ERPx_IMTransactionDetail.PoLnSK
Owner	Identifies a the Lot Owner for a line item. This is a single-select lookup that is enabled and required for all Lot Tracked Items. It defaults from the 'Default Owner' preference on the Inventory Preferences page. This field is editable until a line item has been saved. If the transaction was created as a result of a Grower Accounting ticket that has linked inventory items, this value will default from the 'Default Lot Owner' property on the associated Grower Accounting Ticket Class record. 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
Production Batch	Identifies the Production Batch ID of the Lot. This is a text box that is only required and editable for line items that are Lot Tracked. It defaults as blank and if missing the message "Complete lot information is required to save item: [ItemID]." is displayed on Save. It is editable on transactions 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
Site	Identifies the name of the Site (Warehouse) that the transaction, shipment, receipt, item, or lot is associated with. This is a single select lookup that defaults to the Site Name from the Home Tab but can be changed while the transaction is in a Status of 'New'. It is required else the message "Site is required." will be displayed on Save. The lookup contains a blank value, the current assigned value and all 'Active' Sites. Database Fields: ERPx_MFSite.SiteName, ERPx_IMTransactionDetail.SiteLineSK
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 required and editable only if the item is managed by 'Units Only' or 'Units and Weight'. This defaults to 0 and is always editable while the transaction is in a Status of 'New'. This can be positive or negative. This 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
Units 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 lookup. This field will be disabled if the item is managed by 'Weight Only' otherwise it will be enabled and is required to save a line item on transactions with a Status of 'Approved' or greater. This defaults as follows: For manually entered line items that are not linked to a PO Line Item, this defaults from the 'Inventory Unit UOM' property on the 'Properties' tab of the Item Record View for the selected Item. For manually entered line items that are linked to a PO #, this defaults from the UOM on the Purchase Order line item. For line items that were auto created from transactions, this defaults to the UOM on the source transaction line 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
Warehouse Lot	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. This is a text box that is only required and editable on transactions where the 'Site' is Warehouse Lot Tracked. This defaults as blank and if missing the message "Complete lot information is required to save item: [ItemID]." is displayed on Save. It is editable while the transaction is in a Status of 'New'. This must be <= 50 characters. If the transaction was created as a result of a Grower Accounting ticket that has linked inventory items, this value will default from the 'Create Warehouse Lot As' property on the associated Grower Accounting Ticket Class record. Database Field: ERPx_IMWarehouseLot.WarehouseLotID
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 required and editable only if the item is managed by 'Weight Only' or 'Units and Weight'. This defaults to 0 and is always editable while the transaction is in a Status of 'New'. This can be positive or negative. This will display the number of decimals set for the selected item on 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
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 lookup. This field will be disabled if the item is managed by 'Units Only' otherwise it will be enabled and is required to save a line item on transactions with a Status of 'Approved' or greater. This defaults as follows: For manually entered line items that are not linked to a PO Line Item, this defaults from the 'Inventory Weight UOM' property on the 'Properties' tab of the Item Record View for the selected Item. For manually entered line items that are linked to a PO #, this defaults from the UOM on the Purchase Order line item. For line items that were auto created from transactions, this defaults to the UOM on the source transaction line 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

Page Header

Header Toolbar

Home Tab

Properties Tab

Attributes Tab

Page Details

Related Topics

Page Definitions

Technical Details

Browser not supported