Cost History Inquiry
The Cost History Inquiry details all layer costs assigned to Inventory Tracked Items. The purpose of the inquiry is to display how the current cost is calculated.
This inquiry also contains columns for each Attribute that is set up for the 'Items' attribute type and the 'Production Batches' attribute type. Additionally, this inquiry also contains columns for each Lot Certification with a certification 'Type' of "Item & Site". Item attributes, Production Batch attributes and Lot Certifications are automatically included in the default view. However, because these attributes and lot certifications are user defined, they are not included in the help documentation.
Software Version: 2022.06.16 and newer
Page Header
Search
Filter Items | Description |
---|---|
Auto Hide Filters | A non-required text box that defaults as checked and is used to determine if the Search Options should be hidden when the Inquiry runs or is refreshed.
Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. If you change the default setting but do not save it in a custom search, it will only remain this way while the page is opened. Refer to this FAQ for advanced search options. |
Auto Refresh on Open | A non-required text box that defaults as checked and is used to determine if the inquiry opens with or without data in the grid.
Users can only change the default value of this setting with a custom search in the "Saved Searches" lookup. Refer to this FAQ for advanced search options. |
Costing Method | A multi-select lookup to limit the results to Lots containing Items based on the Item's 'Costing Method'. This defaults to blank (All) and if left blank, all Costing Methods will be included. The lookup contains options for:
This should be based on what we do with the same data on the Update Costs inquiry. The lookup contains the values "NON-INV', "Item" and "Lot". |
Costing Status | A single-select lookup to limit the results to Lots that are either Open or Closed for Costing. This defaults to 'Open' but can be changed to 'Closed'. Is this intended to be a single select lookup and not a multi-select lookup? This lookup contains the values in the LayerCostingStatus Enumeration Class. |
Effective Date | A text box to identify the method for selecting a date range, a specific date, or a min/max date. For help on using this control refer to the FAQ Article /wiki/spaces/HELP/pages/3108732991. This is used to limit the Cost Layers based on their Effective Data. This defaults to "last 30 Days" but can be changed.Change label to 'Cost Layer Effective Date' |
Include | |
Item | Identifies the Item, displayed as Item ID: Item Description. This is a multi-select lookup to limit the results to Lots for one or more associated Items. This defaults to blank (All) and if left blank, all Items will be included. Item IDs are the unique identifier for Items. The lookup contains a list of all Items displayed as [Item ID]: [Item Description]. |
Item Class | Used to select one or more Item Classes. This is a multi-select lookup to limit the results to Lots containing Items based on the Item's 'Item Class'. This defaults to blank (All) and if left blank, all Item Classes will be included. Item Classes are used to identify default values that will be applied to new Inventory Items and to group Items together for reporting purposes. The lookup contains a list of all Item Classes displayed as [Item Class ID]: [Item Class Description]. |
Lot Owner | Used to select one or more inventory Owners. This is a multi-select lookup to limit the results to Lots that are assigned to one or more owners. This defaults to blank (All) and if left blank, all Owners will be included. 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. |
Reason Code | Identifies the Reason Code associated with a Lot Cost Layer adjustment or addition. This is a multi-select lookup to limit the results to Cost Layers containing the Reason Code(s) selected. This defaults to blank (All) and if left blank, all Cost Layers will be selected regardless of the Reason Code. Reason Codes are used throughout the system to describe the reason a transaction or transaction line item was entered. Unlike Notes, which allow for free text edits,, Reason Codes are pre-determined and controlled by lists to ensure structure and uniformity. Reason Codes are used for things like Returns, product Adjustments, Employee Terminations, and Write Offs. The lookup contains a list of all the 'Lot Cost Adjustment' Reason Codes. |
Saved Searches | Displays the saved searches lookup and related icons. This tool allows users to select previously saved search options, create a new set of search options, save changes to existing search options, forget/delete saved search options and/or assign a saved search option as the default for the page. Once changes are made to the search options, the user can click the Save Options icon and save the changes. Saving search options will also save the preferences for 'Auto Refresh on Open' and 'Auto Hide Filters'. The new search option can also be set as the default. Default searches can be removed by clicking the 'Set as Default' button again when the current default search is selected. Refer to this FAQ for advanced search options. |
Search | A non-required text box that defaults to blank and is used to search across multiple fields. When the page is 'Refreshed', the data returned will be limited by what was included in the Search box (in addition to any other Search Options). Refer to this FAQ for advanced search options. The Search field can be used to search across the following fields:
|
Site | Identifies the Site displayed as [Site ID]: [Site Name]. This is a multi-select lookup to limit the results to Lots that are in one or more Sites. This defaults to blank (All) and if left blank, all Sites will be included. 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 displayed as [Site ID]: [Site Name]. |
Page Detail
Toolbar Icons | Description |
---|---|
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. |
Favorites | Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab. |
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. |
Help | Opens the online WIKI help page for the current page. |
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. |
Refresh | 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. |
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. |
Search Options | Toggles between displaying and hiding the Search Options portion of the page. |
Fields | Description |
Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
Actual Cost Rate | Identifies the cost rate assigned to the Actual Cost Layer. This can only be edited by adding/editing an 'Actual Cost Layer' or adding/updating an 'Actual Cost Base'. 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. Database Field: ERPx_IMLotCostHistory.Cost |
Batch Comment | 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 |
Batch Date | The Batch Date identifies the date the Production Batch, for the Item, was initially created. This is the date used to determine the age of the batch and it stays attached to the Lot, even if it is transferred to another Site. This will be blank and/or disabled for all non-Lot Tracked items on screens that include a Production Batch field. This can be edited from the 'Batch Date' field on the Properties tab of the Production Batch Record View. Database Field: ERPx_IMProductionLot.DateProduced |
Batch Site ID | 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 |
BOM ID | Displays the BOM ID of the Bill of Material record. Clicking on the link opens the corresponding Bill of Materials Record View. This field is only populated if the lot costs have been retrieved from a BOM record. This is not editable. Database Fields: ERPx_MPBOM.BOMID, ERPx_IMProductionLot.BaseCostBOMSK |
Born on Date | 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. What data field stores this value and how is it set? |
Cost Group Description | 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 |
Cost UOM | 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 |
Costing Method | Identifies which cost bucket is used to post to the General Ledger. This is a required and can be edited from the 'Costing Method' property on the 'Advanced Properties' tab of the Item Record View. Database Fields: ERPx_IMItem.ValuationMethodEN |
Costing Status | Displays whether cost changes can be made to the Lot. If the Costing Status is "Open" then cost changes can be made. If the Costing Status is "Closed" then cost changes cannot be made to the Lot. This can be edited from the 'Layer Costing Status' property on the Mass Update dialog box launched from the Lot Balances List View. Database Fields: ERPx_IMLotBalance.LayerCostingStatusEN |
Country of Origin | Displays the name of the Country that the Production Batch originated in. The value is stored in the 'Country of Origin' Tab on the Production Batch Record View. If no 'Country of Origin' has been assigned, this will be blank, if there is only one 'Country of Origin' assigned to the Production Batch then the name of that country will be displayed. If there is more than one country assigned on the 'Country of Origin' Tab then this will indicate "Multiple". This can be edited from the 'Country of Origin' field on the 'Properties' tab of the Production Batch Record View. Database Field: ERPx_IMProductionLot.CountryOfOrigin |
Days Old | Displays the calculated age (in days) of the Production Batch. It is calculated as the (Current Date) - [Batch Date]. This can be edited by changing the 'Batch Date' field on the Properties tab of the Production Batch record view. This is not stored in the database. This is a calculated field that is not stored in the database. |
Days Until Expiration | 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:
This is a calculated field that is not stored in the database. |
Effective Date | Displays the Effective date of the cost update event. If the cost event was manually set, then this field cannot be edited once the 'Effective Date' field is applied on the Mass Update dialog box launched from the Update Costs List View. If the cost was updated from BOM, then this field comes 'Effective' field on the 'Cost Inputs' tab of the Bill of Materials Record View and cannot be edited. Database Field: ERPx_IMLotCostHistory.EffectiveDate |
Expiration Date | 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 |
Inventory Balance Sheet Account | 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".
Database Fields: ERPx_GLAccount.AccountNumber, ERPx_GLAccount.Description, ERPx_IMItem.InventoryActSK |
Is Lot Expired | A Yes/No field to identify if a Lot is expired.
This is a calculated field that is not stored in the database. |
Item: Description | 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 |
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. Database Field: ERPx_IMLotCostHistory.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. Database Field: ERPx_IMLotCostHistory.LastUser |
Market Cost Rate | Identifies the cost rate assigned to the Market Cost Layer. This can only be edited by adding/editing a 'Market Cost Layer' or adding/updating a 'Market Cost Base'. 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. Database Field: ERPx_IMLotCostHistory.MarketCost |
Owner | 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 |
Production Batch | 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:
Database Field: ERPx_IMProductionLot.ProductionLotID |
Reason Code | Identifies the Reason Code associated with a Lot Cost Layer adjustment or addition. This can only be assigned when adding/editing a Cost Layer or adding/updating a Base Cost. Reason Codes are used throughout the system to describe the reason a transaction or transaction line item was entered. Unlike Notes, which allow for free text edits,, Reason Codes are pre-determined and controlled by lists to ensure structure and uniformity. Reason Codes are used for things like Returns, product Adjustments, Employee Terminations, and Write Offs. Database Fields: ERPx_MFNoteTypeReasonCode.ReasonCode, ERPx_IMLotCostHistory.ReasonCodeSK |
Received From | Identifies the name of the Vendor, Fisherman, or Grower that the product was received from. If there is only one 'Received From' identified on the Production Batch, the name will be displayed. If there is more than one 'Received from' identified on the Production Batch, the word "Multiple" will be displayed. This can be edited from the 'Rec. From' header field on the Inventory Receipt record view before the transaction is posted or from the Production Batch Record View at any time. Database Field: ERPh_IMTransactionHeader.ReceivedFrom |
Site | 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 |
Site Name | 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 |
Source | Identifies how the Cost Layer was added. This is automatically assigned based on how the costs were assigned and is not editable. The options include:
ERPx_IMLotCostHistory.LotCostTypeEN |
Standard Cost Rate | Identifies the cost rate assigned to the Standard Cost Layer. This can only be edited by adding/editing a 'Standard Cost Layer' or adding/updating a 'Standard Cost Base'. 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. Database Field: ERPx_IMLotCostHistory.StandardCost |
Storage Begin Date | 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 |
Storage Renewal Day | 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. Database Fields: ERPx_IMWarehouseLot.DtorageRenewalDay |
UOM Schedule | 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. Database Fields: ERPx_IMItem.UOMScheduleSK, ERPh_IMTransactionDetail.ItemSK |
Warehouse Lot | 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:
Database Fields: ERPx_IMWarehouseLot.WarehouseLotID, ERPx_IMLotBalance.WarehouseLotSK |