Used to select one or more Items. This is a multi-select lookup that defaults to blank (All) and is not required. Selecting nothing assumes you want all records returned.

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 lookup that defaults to blank (All) and is not required. Selecting nothing assumes you want all records returned.

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.

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

• Lot Properties
  • Costing Status
• Set Base Costs
  • Update Method:
  • Actual Cost:
  • Market Cost:
  • Standard Cost:
  • Reason Code:
• Add Cost Layers 
  • Effective Date:
  • Actual Cost:
  • Market Cost:
  • Standard Cost:
  • Reason Code:
• Update Costs from Other Costs
  • Effective Date:
  • Source Cost:
  • Destination Cost:
  • Cost Update Method:
  • Amount:
• Post Costs to GL
  • Post Costs Through GL Period:
  • Post Costs to GL:
  • Update PO Receipts Costs:

 Displays a drop down menu of related actions. The list of options includes: 

• IQ: Cost History: opens the cost history for the selected record.
• IQ: Lot History: opens the Lot History for the selected record. 
• LV: Warehouse Lot
• RV: Production Batch

——————————————

• Update Costs from BOM: opens the Update Costs from BOM page

 Re-queries the contents of the grid/page based on the Search Options or the default values for grids that do not support Search Options. 

 This ONLY re-queries the contents of columns that are currently visible, if you add a new column the contents will be empty until you click 'Refresh' again.

The Actual Base Cost reflects the 'Base Cost' assigned within the Actual cost type. The Actual base cost is added to the Actual layer cost(s) to compute total Actual cost. This is a calculated field that can only be edited by adding/editing an 'Actual Base Cost'.

Database Fields: ERPx_IMLotCostHistory.Cost where ERPx_IMLotCostHistory.LotCostTypeEN = 3

An Actual Cost Layer reflects the 'Layer Cost' assigned within the Actual cost type. The Actual layer cost(s) are added to the Actual base cost to compute total Actual cost. This is a calculated field that can only be edited by adding/editing an 'Actual Cost Layer'.

Database Fields: ERPx_IMLotCostHistory.Cost where ERPx_IMLotCostHistory.LotCostTypeEN = 2

The Actual Cost Rate refers to the 'Rate' applied to the Inventory for determining the extended 'Actual Cost'. For a single Lot, it is the 'Rate' that is multiplied by the quantity to compute the 'Actual Cost' value of the Lot. For multiple Items and/or Lots it is the calculated value from dividing the sum of the extended 'Actual Costs' by the sum of the quantity. This is a calculated field that can only be edited by adding/editing an 'Actula Cost Layer' or adding/updating an 'Actual Base Cost'. 

Displays the batch comment assigned to the corresponding Production Batch. This is not required and is always editable from the 'Batch Comment' field on the Properties tab of the Production Batch record view.

Database Field: ERPx_IMProductionLot.LotComment

Identifies the Site where the Production Batch was born, created, or initially received. This is required and is always editable from the 'Batch Site ID' field on the Properties tab of the Production Batch Record View. 

Database Fields: ERPx_MFSite.SiteID, ERPx_MFSite.SiteName, ERPx_IMProductionLot.ManufactureSiteSK

The Born on Date identifies the date that a new Inventory Lot record was born, created, or initially received into a Site. This is not used for product aging but just a way to know when the Lot was born, created, or initially received into a Site. For example, if a Transfer transaction was physically received on 3/24, and it resulted in one or more new Inventory Lots, those new Lot's 'Born on Date' would be 3/24 even if they had different Production 'Batch Dates'.   This is a system assigned value that is not editable.

Database Field: ERPx_IMLotBalance.BornOnDate 

Identifies the description associated with the unique Cost Group ID associated with the item. This is not required and can be edited from the 'Cost Group' property on the 'Properties' tab of the Item Record View.

Cost Groups are used to associate items that share the same cost model.

Database Field: ERPx_IMCostGroup.CostGroupID, ERPx_IMCostGroup.CostGroupDescription, ERPx_IMItem.CostGroupSK

Identifies the unit of measure the item's cost is stated in terms of. This is the value assigned in the "Cost UOM" property on the Item Record View. This is required for Costing and can be edited from the 'Cost UOM' property on the 'Advanced 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 Fields: ERPx_IMItem.CostUOMSK

Identifies whether the Lot is Open or Closed for Cost changes. If a Lot is Closed for Costing, no cost changes can be made.  

This can be edited from the 'Costing Status' property on the Mass Update dialog.

Database Fields: ERPx_IMLotBalance.LayerCostingStatusEN

Displays the "Batch Expiration Date" assigned to the Production Batch. This defaults by adding the value set on the Item's 'Expiration Days' to the 'Batch Date' assigned to the Production Batch.  This is editable from the Production Batch Record View.

Database Field: ERPx_IMProductionLot.ExpirationDate

The GL Account that is used for the following Costing journal entries: This only applies to the 'Actual' cost of Items with a Costing Method of "Active". 

• Inventory Adjustments & Cycle Counts: The debit account used for item balance increases and the credit account used for item balance decreases. 
• Inventory Production (Inputs): The credit account used for the decreased value of inventory that was consumed during production.
• Inventory Production (Outputs): The debit account used for the increased value of inventory that was created during production.
• Inventory Receipts: The debit account used for the increased value of inventory that was received.
• Inventory Transfer: The debit account used to show the increased value of inventory in the receiving Site and the credit account used to show the decreased value of inventory in the sending Site.
• Sales Order: The credit account used for the decreased value of inventory that was shipped to a customer.
• Sales Return: The debit account used for the increased value of inventory that was returned by a customer.
• Inventory Valuation changes (manual changes): The debit account used for item valuation increases and the credit account used for item valuation decreases.

Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_IMItem.InventoryActSK

Identifies the Item, displayed as Item ID: Item Description.  The 'Item ID' and/or the 'Item Description' can be edited from the 'Properties' tab of the Item Record View.

Item IDs are the unique identifier for Items. 

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

Item Classes are used to identify default values that will be applied to new Inventory Items and to group Items together for reporting purposes. 

Database Fields: ERPx_IMItemClass.ID, ERPx_IMItem.ItemClassSk

A Lots 'Last Effective Actual Cost Change' identifies the last 'Effective Date' that an 'Actual' Base Cost or 'Actual' Cost Layer was applied to a Lot. For example, if the Actual Cost was updated on the 2nd and the Market Cost was updated on the 5th, this would display as the 2nd. This can only be changed by adding an Actual Cost or adding/removing an Actual Cost Layer.

A Lots 'Last Effective Market Cost Change' identifies the last 'Effective Date' that a 'Market' Base Cost or 'Market' Cost Layer was applied to a Lot. For example, if the Market Cost was updated on the 2nd and the Actual Cost was updated on the 5th, this would display as the 2nd. This can only be changed by adding a Market Cost or adding/removing a Market Cost Layer.

Identifies whether the Lot is Open or Closed. Lots are automatically set to "Closed" when all balances are 0.00 (On Hand, Committed, Allocated, and On Hold). Lots can also be manually closed even with remaining balances. This is most commonly used for Lots with small residual balances typically caused from UOM conversion rounding (e.g., a Lot shows a balance of 0.00 Units and -0.00025 lbs).  

The Market Base Cost reflects the 'Base Cost' assigned within the 'Market ' cost type. The Market base cost is added to the Market layer cost(s) to compute total Market cost. This is a calculated field that can only be edited by adding/editing a 'Market Base Cost'.

Database Fields: ERPx_IMLotCostHistory.MarketCost where ERPx_IMLotCostHistory.LotCostTypeEN = 3

A Market Cost Layer reflects the 'Layer Cost' assigned within the Market cost type. The Market layer cost(s) are added to the Market base cost to compute total Market cost. This is a calculated field that can only be edited by adding/editing a 'Market Cost Layer'.

Database Fields: ERPx_IMLotCostHistory.MarketCost where ERPx_IMLotCostHistory.LotCostTypeEN = 2

The Market Cost Rate refers to the 'Rate' applied to the Inventory for determining the extended 'Market Cost'. For a single Lot, it is the 'Rate' that is multiplied by the quantity to compute the 'Market Cost' value of the Lot. For multiple Items and/or Lots it is the calculated value from dividing the sum of the extended 'Market Costs' by the sum of the quantity. This is a calculated field that can only be edited by adding/editing a 'Market Cost Layer' or adding/updating a 'Market Base Cost'.

Displays the On Hand units of the item at the corresponding Site or Inventory Lot. This column is only populated when the inquiry is run with a value in the "GL Period Activity" Search Option Parameter.

If the item's 'Manage Items By' value is set to:

• "Units Only" or "Units and Weight", this field will be populated.
• "Weight Only", this field will be blank

Displays the On Hand weight of the item at the corresponding Site or Inventory Lot. This column is only populated when the inquiry is run with a value in the "GL Period Activity" Search Option Parameter.

If the item's 'Manage Items By' value is set to:

• "Units Only" or "Units and Weight", this field will be populated.
• "Weight Only", this field will be blank

Identifies the Lot Owner of the Inventory Lot. This cannot be edited, ownership for an existing Lot can only be changed via a Transfer Transaction.

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.

Database Field: ERPx_IMLotOwner.OwnerName

Identifies the Production Batch ID of the Lot. This can be edited from the 'Production Batch' field on the Properties tab of the Production Batch Record View. 

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

Displays the Site ID for the Site where the inventory balances are stored. This is always editable from the Sites Record View.

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_MFSite.SiteID, ERPh_IMTransactionHeader.SiteSK

Displays the Site Name for the Site where the inventory balances are stored. This is always editable from the Sites Record View.

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

Database Fields: ERPx_MFSite.SiteName, ERPx_IMLotBalance.SiteSK

The Standard Base Cost reflects the 'Base Cost' assigned within the Standard cost type. The Standard base cost is added to the Standard layer cost(s) to compute total Standard cost. This is a calculated field that can only be edited by adding/editing a 'Standard Base Cost'.

Database Fields: ERPx_IMLotCostHistory.StandardCost where ERPx_IMLotCostHistory.LotCostTypeEN = 3

A Standard Cost Layer reflects the 'Layer Cost' assigned within the Standard cost type. The Standard layer cost(s) are added to the Standard base cost to compute total Standard cost. This is a calculated field that can only be edited by adding/editing a 'Standard Cost Layer'.

Database Fields: ERPx_IMLotCostHistory.StandardCost where ERPx_IMLotCostHistory.LotCostTypeEN = 2

The Standard Cost Rate refers to the 'Rate' applied to the Inventory for determining the extended 'Standard Cost'. For a single Lot, it is the 'Rate' that is multiplied by the quantity to compute the 'Standard Cost' value of the Lot. For multiple Items and/or Lots it is the calculated value from dividing the sum of the extended 'Standard Costs' by the sum of the quantity. This is a calculated field that is not stored in the database. It can only be edited by adding/editing a 'Standard Cost Layer' or adding/updating a 'Standard Base Cost'. 

Identifies the date a cold storage began (or will begin) charging storage. This is typically set to a value of one month after the initial receipt date. Cold Storages typically charge for both "Storage" and "Handling", and this is the date the storage portion begins. Storage is typically billed monthly and is calculated by multiply a pre-determined storage rate * Lbs in the Warehouse Lot. This can only be edited on the Warehouse Lot List View.

Database Fields: ERPx_IMWarehouseLot.DtorageRenewalDate

Identifies the day of the month that the cold storage will bill for a Warehouse Lot. If there are any quantity balances remaining on that day, a new storage bill will be issued.
 This can only be edited by editing the 'Storage Begin Date' on the Warehouse Lot List View

Database Fields: ERPx_IMWarehouseLot.DtorageRenewalDay

Identifies the default inventory unit of measure that the units are stored in (boxes, Bags, Cases, Totes, etc.) for the item. This column is only populated when the inquiry is run with a value in the "GL Period Activity" Search Option Parameter.

If the item's 'Manage Items By' value is set to:

• "Units Only" or "Units and Weight", this field will be populated.
• "Weight Only", this field will be blank

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

Identifies the UOM Schedule that is used to determine what Units of Measure are to be used for specific items that are bought, sold and manufactured as well as the conversions for those Units of Measure.
This field comes from the 'UOM Schedule' property on the 'Properties' tab of the Item Record View and is not editable from here.

Database Fields: ERPx_IMItem.UOMScheduleSK, ERPh_IMTransactionDetail.ItemSK

Identifies the Warehouse Lot to which the selected item or inventory lot belongs. 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_IMLotBalance.WarehouseLotSK

Identifies the default inventory unit of measure that the weight is stored in (Lbs, Kg, Oz, Ton, etc.) for the item. This column is only populated when the inquiry is run with a value in the "GL Period Activity" Search Option Parameter.

If the item's 'Manage Items By' value is set to:

• "Weight Only" or "Units and Weight", this field will be populated.
• "Units Only", this field will be blank.
  

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