Identifies the Item, displayed as Item ID: Item Description.  This is a multi-select standard lookup that is required to return results. It defaults as blank.

Item IDs are the unique identifier for Items. 

The lookup contains a list of all Items in the Items master file.

Used to select one or more Sites. This is a multi-select standard lookup that is required to return results. It defaults as blank.

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 Sites.

 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 - Opens the Item Record View, in a new tab, for a selected Item. 
• RV: Production Batch - Opens the Production Batch Record View, in a new tab, filtered for the selected record's Production Batch.
• RV: Transaction - Opens the appropriate transaction record view, in a new tab, for a selected record with a Transaction Type of: Adjustment, Production, Production Order, Receipt, Transfer, Transfer Receipt, Purchase Order, Sales Order, or Sales Return.

 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.

Displays the allocated quantity to be added to the Available balance for an Inventory Lot or Item.

The Allocated (+) balance is the quantity, that has been allocated, on an open transaction containing incoming product. The Allocated (+) balance increases the Available balance. Unlike Committed (+) which represents "requested" balances, Allocated (+) represents "assigned" balances. For example, a Customer may order 15 Cases and only be shipped 10. The 10 Cases would signify what was actually shipped. The Allocated (+) balance is comprised of:

• Inventory transactions where the quantity of a Lot Tracked line item where the item has been saved with a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Receipt line item and either the Production Batch or Warehouse Lot was assigned, the Allocated (+) balance for that transaction would be 10.
• Production Orders where the quantity of an Output line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Allocated (+) balance for that transaction would be 10.
• Sales Returns where the line item has an allocated quantity.

Note: each of the Inventory Transactions can be conditionally included/excluded from the Allocated balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Allocated balances and used to update the Available balances, if they are set to "No", they will not be included in Allocated so they will not update Available balances.

Additionally, for Production Order Outputs, these can be conditionally included/excluded from the Allocated balances based on the "First status to include Production Order Outputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Allocated balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Allocated so they will not update Available balances. 

Database Fields: ERPx_IMTransactionDetail.EffectOnInventoryUnits or ERPx_IMTransactionDetail.EffectOnInventoryWeight

Displays the allocated quantity to be subtracted from the Available balance for an Inventory Lot or Item.

The Allocated (-) balance is the quantity, that has been allocated, on an open transaction containing outgoing product. The Allocated (-) balance reduces the Available balance. Unlike Committed (-) which represents "requested" demand on product, Allocated (-) represents the quantity that has been "assigned" and has/will ship. For example, if a Customer orders 15 cases and only 10 are allocated, the Available balance will be reduced by 15 made up of Allocated (-) of 10 cases and Committed (-) of 5 cases.  The Allocated (-) balance is comprised of:

• Inventory transactions where the quantity of a Lot Tracked line item where the item has been saved with a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Production Input line item and either the Production Batch or Warehouse Lot was assigned, the Allocated (-) balance for that transaction would be 10.
• Production Orders where the quantity of an Input line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Allocated (-) balance for that transaction would be 10.
• Sales Transactions where a line item has been allocated. 

Note: Each of the Inventory Transactions can be conditionally included/excluded from the Allocated balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Allocated balances and used to update the Available balances, if they are set to "No", they will not be included in Allocated so they will not update Available balances.

Additionally, for Production Order Inputs, these can be conditionally included/excluded from the Allocated balances based on the "First status to include Production Order Inputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Allocated balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Allocated so they will not update Available balances. 

Database Fields: ERPx_IMTransactionDetail.EffectOnInventoryUnits or ERPx_IMTransactionDetail.EffectOnInventoryWeight

 Displays the requested quantity to be added to the Available balance for an Inventory Lot or Item.  

The Committed (+) balance is the ordered (requested) quantity, that has not yet been allocated, on an open transaction containing incoming product. The Committed (+) balance increases the Available balance. The Committed (+) balance is comprised of:

• Inventory transactions where the quantity of a line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Receipt line item and either the Production Batch or Warehouse Lot was unassigned, the Committed (+) balance for that transaction would be 10.
• Open Production Orders where the quantity of an Output line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Committed (+) balance for that transaction would be 10.
• Open Purchase Orders where the quantity of an inventory item has been saved and not yet received (on a Posted Receipt transaction). For example, if the inventory item on the Purchase Order is for 100lbs and has not yet been received, the Committed (+) balance for that item would be 100lbs.  If a Receipt is then Posted with 60lbs of that item, the Committed (+) balance would be 40lbs. 
• Sales Returns: Items on Sales Order Shipments, where the Requested Returned quantity is greater than the Allocated quantity. When this occurs, it is calculated as [Requested] - [Allocated]. For example, if 15 Cases were being returned and 3 have been allocated, the Committed (+) balance would be 12. Note, this amount cannot be negative. For example, if there were 5 Cases requested for return and 7 Allocated, the Committed (+) balance would be 0 not -2.

Note: Each of the Inventory Transactions can be conditionally included/excluded from the Committed balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Committed balances and used to update the Available balances, if they are set to "No", they will not be included in Committed so they will not update Available balances.

Additionally, for Production Order Outputs and unreceived Purchase Order quantities, these can be conditionally included/excluded from the Committed balances based on the "First status to include ##### in Available balances" Inventory Preferences. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", they will be included in Committed balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, they will not be included in Committed so they will not update Available balances. 

Database Fields: ERPx_IMTransactionDetail.EffectOnInventoryUnits or ERPx_IMTransactionDetail.EffectOnInventoryWeight

Displays the requested quantity to be subtracted from the Available balance for an Inventory Lot or Item.  

The Committed (-) balance is the ordered (requested) quantity, that has not yet been allocated, on an open transaction containing outgoing product. The Committed (-) balance reduces the Available balance. The Committed (-) balance is comprised of:

• Inventory transactions: where the quantity of a Lot Tracked line item where the item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Production Input line item and either the Production Batch or Warehouse Lot was unassigned, the Committed (-) balance for that transaction would be 10.
• Open Production Orders where the quantity of an Input line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Committed (-) balance for that transaction would be 10.
• Open Purchase Orders where a negative quantity of an inventory item has been saved and not yet received (on a Posted Receipt transaction). For example, if the inventory item on the Purchase Order is for -100lbs and has not yet been received, the Committed (-) balance for that item would be -100lbs.  If a Receipt is then Posted with -60lbs of that item, the Committed (-) balance would be -40lbs.
• Sales Transactions: Items on Sales Order Shipments, where the Shipment has not been Shipped, where the Ordered quantity is greater than the Allocated quantity. When this occurs, it is calculated as [Ordered] - [Allocated]. For example, if 15 Cases were ordered and 3 have been allocated, the Committed (-) balance would be 12. Note, this amount cannot be negative. For example, if there were 5 Cases ordered and 7 Allocated, the Committed (-) balance would be 0 not -2.

Note: Each Inventory Transaction can be conditionally included/excluded from the Committed balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Committed balances and used to update the Available balances, if they are set to "No", they will not be included in Committed so they will not update Available balances.

Additionally, for Production Order Inputs, these can be conditionally included/excluded from the Committed balances based on the "First status to include Production Order Inputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Committed balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Committed so they will not update Available balances. 

Database Fields: ERPx_IMTransactionDetail.EffectOnInventoryUnits or ERPx_IMTransactionDetail.EffectOnInventoryWeight

Identifies the name of the Customer record or for the Customer assigned to a transaction. Identifies the name of the customer assigned to the sales transaction. This field comes from the 'Customer Name' property on the Properties tab of the Customer record view.

Note: This is only displayed for Transaction Types 'Order' and 'Return'.

Database Fields: ERPx_ARCustomer.CustomerName, ERPx_SOOrderHeader.CustomerSK

Identifies the number of days before a Lot "expires". This is calculated using the 'Batch Expiration Date' on the Properties tab of the Production Batch Record View and subtracting the current date. This can be edited by changing the 'Batch Expiration Date' field on the Properties tab of the Production Batch record view. This is not stored in the database.

If the Batch Expiration Date is:

• Blank, then this will be blank.
• In the future, then this will be a positive value indicating how many days are left until the Batch is "expired". 
• In the past, then this will be a negative value indicating how many days have passed since the Batch "expired".

Identifies the Item, displayed as Item ID: Item Description.  This comes from and can be edited from the 'Item Description' field on the Properties tab of the Item record view.  

Database Fields: ERPX_IMItem.ItemID, ERPX_IMItem.ItemDescription, ERPx_IMTransactionDetail.ItemSK, ERPx_SOOrderItem.ItemSK

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. Displays the Purchase Order number that was entered on the Inventory Receipt transaction or Sales transaction. This field comes from and can be edited from the 'Purchase Order' field on the Home tab of the Receipt transaction record view or Sales Order record view while the transaction is in a Status of 'New'.

Note: This is only displayed for Transaction Type 'Receipt' or 'Order'.

Database Field: ERPx_IMTransactionHeader.PONumber, ERPx_SOOrderHeader.PurchaseOrder

Identifies the Production Batch ID of the Lot. This value defaults from the 'Production Batch' value specified on the Inventory transaction that created the Production Batch. This can be edited from the 'Production Batch' field on the Properties tab of the Production Batch record view. If the inventory lot is committed and the item is not lot tracked, this value will display as "Item Tracked". If the inventory lot is committed and the item is not tracked, this value will display as "Commitments".

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.

An Inventory Lot is the most granular level that item balances (quantities of Units and/or Weight) are stored within NorthScope. Inventory Lots are created for all Inventory Items assigned an Item Type of “Inventory', regardless of whether the Item is Lot Tracked (i.e., balances are maintained by Production Batch) or the Site containing the product is 'Warehouse Lot' tracked or not. 

An Inventory Lot is unique by combination of:

• Item: The Item ID (required for all Inventory Lots)
• Site: The Site/Warehouse that contains the inventory (required for all Inventory Lots)
• Production Batch: The date code or other traceability reference that stays with product and never changes. It is required for Items with a 'Lot Tracked' property of "Yes" and will be blank for Items with a 'Lot Tracked' property of "No"
• Warehouse Lot: The identifier or location within a Site/Warehouse, this is most typically used for 3rd party distribution sites. It is required for 'Inventory Lots' in a Warehouse Lot tracked Site and will be blank for 'Inventory Lots' in a non Warehouse Lot tracked Site. This has nothing to do with whether the Item is 'Lot Tracked' or not. 
• Owner: Identifies who owns the product. This is required for all Inventory Lots.

Database Field: ERPx_IMProductionLot.ProductionLotID

Identifies the Inside Salesperson associated with the transaction. This can be edited from the 'Salesperson - Inside Sales' field on the Properties tab of the transaction record view.

Salespeople are individuals that sell goods and services to other entities. Inside Salespeople typically work in the office and are involved with sales over the telephone, email, or other cyber communication methods.

Database Fields: ERPx_SOSalesperson.SalespersonName,  ERPx_SOOrderHeader.InsideSalespersonSK

Identifies the Outside Salesperson associated with the transaction. This can be edited from the 'Salesperson - Outside Sales' field on the Properties tab of the transaction record view.

Salespeople are individuals that sell goods and services to other entities. Outside Salespeople typically work outside the office and are involved with face to face meetings with active and prospective customers.

Database Fields: ERPx_SOSalesperson.SalespersonName,  ERPx_SOOrderHeader.OutsideSalespersonSK

Identifies the unique Site ID (warehouse ID) of the Site the transaction, shipment, item, or lot is associated with. This defaults from the 'Site' field on the 'Home' tab of the Inventory transaction or the 'Default Site' field on the 'Home' tab of the Sales Order/Return transaction. This is not editable after the transaction has been Saved.

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

Database Fields: ERPx_MFSite.SiteID, ERPx_IMTransactionHeader.SiteSK, ERPx_SOOrderHeader.SiteSK

Identifies the unique Transaction ID for each transaction. This value is system generated when the transaction is created 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_SOOrderHeader.OrderID

Identifies the Status of the transaction. This can be edited from the 'Status' field on the 'Home' tab of the inventory transaction record view or the sales order record view. This is always editable while the inventory transaction or sales order/return has not been posted.

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 inquiry 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.  

Released: This status is used to signify that the transaction is ready to be released to production. While in the Status of 'Released', all editable fields are open for edit. 

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.

Database Fields: ERPx_IMTransactionStatus.TransactionStatusName, ERPx_IMTransactionHeader.TransactionStatusSK, ERPx_SOOrderStatus.OrderStatusName, ERPx_SOOrderHeader.OrderStatusSK

Identifies the Transaction Type for each transaction. This comes from the 'Transaction Type' property on the 'Properties' tab of the Transaction Class Record View for the associated transaction. This is not editable after the Transaction Class has been saved.

Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type.

Database Fields: ERPx_IMTransactionType.TransactionTypeDescription, ERPx_SOOrderType.OrderTypeName, ERPx_IMTransactionHeader.TransactionTypeSK, ERPx_SOOrderHeader.OrderTypeSK

Identifies the default reporting unit of measure that the weight (Lbs, Kg, Oz, Ton, etc.) or units (boxes, Bags, Cases, Totes, etc.) of the item is stored in. This field comes from and can be edited from the 'Default Reporting UOM' property on the 'Properties' tab of the Item record view.

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 Field: ERPx_IMItem.DefaultReportingUOMSK

Identifies the Warehouse Lot to which the selected item or inventory lot belongs. This value defaults from the 'Warehouse Lot' value specified on the Inventory transaction that created the Inventory Lot. This can be edited from the 'Warehouse Lot' field on the Warehouse Lots list view.

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.

An Inventory Lot is the most granular level that item balances (quantities of Units and/or Weight) are stored within NorthScope. Inventory Lots are created for all Inventory Items assigned an Item Type of “Inventory', regardless of whether the Item is Lot Tracked (i.e., balances are maintained by Production Batch) or the Site containing the product is 'Warehouse Lot' tracked or not. 

An Inventory Lot is unique by combination of:

• Item: The Item ID (required for all Inventory Lots)
• Site: The Site/Warehouse that contains the inventory (required for all Inventory Lots)
• Production Batch: The date code or other traceability reference that stays with product and never changes. It is required for Items with a 'Lot Tracked' property of "Yes" and will be blank for Items with a 'Lot Tracked' property of "No"
• Warehouse Lot: The identifier or location within a Site/Warehouse, this is most typically used for 3rd party distribution sites. It is required for 'Inventory Lots' in a Warehouse Lot tracked Site and will be blank for 'Inventory Lots' in a non Warehouse Lot tracked Site. This has nothing to do with whether the Item is 'Lot Tracked' or not. 
• Owner: Identifies who owns the product. This is required for all Inventory Lots.

Database Fields: ERPx_IMWarehouseLot.WarehouseLotID, ERPx_IMTransaction.WarehouseLotSK