> Continuous Process Improvement > Inventory Management > NetSuite > Data Template

Your Inventory Management Data Template

NetSuite

Inventory Management Attributes (24) Inventory Management Activities (15) Extraction Guides (3)

Your Inventory Management Data Template

This template provides a clear roadmap for collecting the necessary data to analyze and optimize your inventory management process. It outlines the essential attributes to gather, the critical activities to track, and provides guidance for extracting this information from your source systems. By following these recommendations, you can build a robust event log ready for powerful process mining analysis.

Recommended attributes to collect
Key activities to track
Extraction guidance for NetSuite

New to event logs? Learn how to create a process mining event log.

Download Template

Inventory Management Attributes

These are the recommended data fields to include in your event log for comprehensive analysis of your inventory management processes.

3 Required 7 Recommended 14 Optional

	Name	Description
	Inventory Batch/Lot InventoryBatchLotNumber	The unique identifier for a specific batch or lot of an inventory item, serving as the case ID for tracking its lifecycle.
Description The Inventory Batch or Lot number is the primary case identifier, grouping all activities related to a specific quantity of a product. This enables tracking the complete lifecycle of a distinct stock quantity, from its receipt into inventory through its various movements and eventual issue or consumption. In process analysis, each unique InventoryBatchLotNumber represents a single process instance. Analyzing cases based on this identifier allows for a detailed view of how different batches are handled, identifying variations, delays, and exceptions in the inventory management process from receiving to shipping. Why it matters This is the essential key for tracing the end-to-end journey of a specific stock quantity, enabling analysis of its entire lifecycle and process variations. Where to get This identifier is found on transaction lines for lot or batch numbered inventory items in NetSuite. It is managed as part of the item's inventory detail. Examples LOT-202405-001B-FG-10984A2303-4CBATCH-001298
	Activity Name ActivityName	The name of the business activity that occurred at a specific point in the inventory lifecycle.
Description This attribute describes a specific event or step in the inventory management process, such as 'Goods Receipt Recorded' or 'Picking Completed'. It is fundamental for constructing the process map and understanding the sequence of operations. Analyzing the ActivityName allows for the visualization of the process flow, identification of process steps, and calculation of transition times between activities. It forms the backbone of process discovery and conformance checking by defining what happened to the inventory batch at a given time. Why it matters Defines the steps in the process, allowing for the visualization and analysis of the inventory batch's journey and any deviations from the standard flow. Where to get This is a conceptual attribute derived from NetSuite data. It is typically mapped from the 'Transaction Type' (e.g., 'Item Receipt') or the status of a transaction (e.g., 'Work Order - Built'). Examples Goods Receipt RecordedQuality Inspection PerformedPut-away CompletedInventory Discrepancy AdjustedGoods Issue Recorded
	Event Time TransactionDate	The timestamp indicating when the inventory activity occurred.
Description This attribute records the precise date and time of an activity, such as when goods were received or an adjustment was posted. This timestamp is essential for sequencing events correctly and calculating durations between process steps. In analysis, the Event Time is used to build the chronological event log for each case. It is the basis for all time-based analysis, including cycle time calculation, bottleneck identification, and performance monitoring over time. Why it matters Provides the chronological order of events, which is essential for calculating cycle times, analyzing process performance, and identifying bottlenecks. Where to get The standard 'Date' field on NetSuite transactions like Item Receipt, Inventory Adjustment, and Item Fulfillment. For more precision, system notes may provide a timestamp. Examples 2023-10-26T09:00:00Z2023-10-26T14:30:15Z2023-10-27T08:22:05Z2023-10-28T11:59:59Z
	End Time EndTime	The timestamp indicating when an activity was completed.
Description This attribute records the completion time of an activity. For many inventory transactions that are recorded instantaneously, the End Time may be the same as the Start Time. However, for activities that have a measurable duration, like a quality inspection or a put-away task, this attribute is crucial. It is primarily used in conjunction with the Start Time to calculate the Processing Time for individual activities. This enables a more granular analysis of bottlenecks, identifying not just delays between steps but also which specific steps are taking the longest to complete. Why it matters Enables the calculation of the exact duration of each activity, which is crucial for identifying inefficient steps and analyzing resource performance. Where to get This may need to be derived. For some records, it could be the 'Last Modified Date'. In other cases, it may be the timestamp of a subsequent, related event. Examples 2023-10-26T09:05:10Z2023-10-26T15:00:00Z2023-10-27T08:22:05Z
	Movement Reason Code MovementReasonCode	A code explaining the reason for an inventory movement or adjustment.
Description This attribute provides context for certain inventory transactions, particularly adjustments. It clarifies why a change to stock levels was made, for example, 'Damaged Goods', 'Cycle Count Adjustment', or 'Return to Vendor'. This is critical for the 'Inventory Adjustment Frequency & Value' dashboard, as it helps categorize adjustments to identify root causes of discrepancies. It is also used in compliance analysis to ensure that all adjustments have a valid, documented reason. Why it matters Explains the 'why' behind inventory adjustments, helping to identify root causes of stock discrepancies such as damage, theft, or data entry errors. Where to get This is typically implemented as a custom transaction body or line field in NetSuite, as there is no standard field for this purpose on all transaction types. Examples ADJ_CYCLE_COUNTDMG_IN_TRANSITRECLASS_SKUEXPIRED_STOCK
	SKU Item	The unique identifier for the specific product or material.
Description The SKU (Stock Keeping Unit) is the specific identifier for a product, such as a part number or item name. It is the most granular level of product identification. Analyzing by SKU allows for a deep dive into the performance and handling of individual products. It can reveal that certain items have longer put-away times, higher adjustment rates, or are more prone to damage, providing actionable insights for item-specific process improvements. Why it matters Provides the most granular level of product detail, allowing for precise analysis of how different products move through the inventory process. Where to get This is the standard 'Item' field on all transaction lines in NetSuite. It references a record from the Items list. Examples SKU-001-REDPN-987654RAW-STEEL-COILWIDGET-ASSY-A
	Stock Value StockValue	The financial value of the inventory involved in a transaction.
Description Stock Value represents the monetary worth of the inventory quantity being moved, adjusted, or sold. It is typically calculated by multiplying the transaction quantity by the item's current cost price. This attribute is essential for understanding the financial impact of process activities. For instance, the 'Inventory Adjustment Frequency & Value' dashboard uses Stock Value to quantify the cost of inventory discrepancies, helping to prioritize issues with the largest financial impact. Why it matters Quantifies the financial impact of inventory movements and adjustments, allowing analysis to focus on high-value transactions and prioritize cost-saving opportunities. Where to get Derived by multiplying the transaction 'Quantity' by the item's cost. The cost can be sourced from the associated Item record (e.g., 'Average Cost', 'Last Purchase Price'). Examples 1250.75500.0025.50-150.25
	Transaction Type TransactionType	The specific type of NetSuite transaction record that generated the event.
Description This attribute indicates the native NetSuite transaction type, such as 'Item Receipt', 'Inventory Adjustment', 'Work Order Close', or 'Item Fulfillment'. It provides direct traceability back to the source record in the ERP. While the 'Activity Name' provides a business-friendly label, the Transaction Type is crucial for data validation and for creating detailed analyses that require understanding the specific accounting or operational context of an event. For example, it helps differentiate between a customer return ('Return Authorization') and a vendor return. Why it matters Provides a direct link to the source record type in NetSuite, which is vital for data validation, detailed drill-downs, and understanding the technical context of an event. Where to get This is the standard 'Type' of any transaction record in NetSuite. Examples Item ReceiptInventory AdjustmentBin Putaway WorksheetItem Fulfillment
	User Performing Action User	The employee who created or last modified the transaction related to the inventory activity.
Description This attribute identifies the user responsible for executing a specific process step. This could be the warehouse operator who received the goods, the inventory manager who approved an adjustment, or the picker who fulfilled an order. Analyzing activities by user helps in understanding workload distribution, identifying training needs, and investigating compliance issues. For example, the 'Compliance of Inventory Adjustments' dashboard uses this attribute to flag adjustments made by unauthorized personnel. Why it matters Provides accountability by linking process activities to specific individuals, enabling performance analysis, compliance checks, and identification of training needs. Where to get Available in the 'Created By' or 'Last Modified By' fields on standard NetSuite transactions. The System Notes subtab also provides a detailed history of user changes. Examples John SmithJane DoeWarehouse.Operator1Admin
	Warehouse Location Location	The physical warehouse or location where the inventory activity took place.
Description This attribute specifies the warehouse, distribution center, or other physical location associated with an inventory event. NetSuite's 'Location' field is a standard way to segment inventory and operations. This is a critical dimension for comparative analysis. Dashboards like 'Put-away Cycle Time by Warehouse' and 'Warehouse Activity Heatmap' rely on this attribute to compare performance across different sites, identify regional bottlenecks, and understand geographic patterns in inventory movement. Why it matters Allows for performance comparison and resource planning across different physical locations, helping to identify site-specific bottlenecks or best practices. Where to get This is the standard 'Location' field, which is available on nearly all inventory-related transactions in NetSuite. Examples WH-EASTWH-WEST-01Main Distribution CenterRetail Store #105
	Adjustment Compliance Flag AdjustmentComplianceFlag	A calculated flag indicating if an inventory adjustment is non-compliant.
Description This is a boolean attribute that flags inventory adjustments that violate defined business rules. For example, it could be set to 'true' if an 'Inventory Discrepancy Adjusted' activity is performed by an unauthorized user or is missing a 'Movement Reason Code'. This flag is specifically designed for the 'Compliance of Inventory Adjustments' dashboard. It simplifies the analysis by creating a simple binary dimension to filter and count non-compliant events, making it easy to track and report on process deviations and policy violations. Why it matters Simplifies compliance monitoring by flagging transactions that violate business rules, making it easy to quantify and investigate policy breaches. Where to get Calculated attribute. This is derived using logic that checks other fields, for example, `IF(MovementReasonCode IS NULL) THEN true ELSE false`. Examples truefalse
	Expiration Date ExpirationDate	The date on which the inventory batch or lot is set to expire.
Description This attribute stores the expiration date for perishable or time-sensitive goods. It is a key piece of information managed at the lot or batch number level. This data is fundamental for the 'Expiring & Obsolete Stock Overview' dashboard. By analyzing the Expiration Date, businesses can proactively identify stock at risk of expiring, implement strategies like FEFO (First-Expired, First-Out), and minimize losses due to spoilage or obsolescence. Why it matters Crucial for managing perishable goods, enabling proactive identification of at-risk stock to reduce waste and financial loss from expired inventory. Where to get Available on the inventory detail of a transaction line for lot-numbered items where expiration date tracking is enabled. Examples 2024-12-312025-06-302024-08-01
	Internal Transfer Lead Time InternalTransferLeadTime	The calculated time taken to move stock between two internal locations or bins.
Description This metric measures the duration of internal stock movements. It is calculated as the time elapsed from the initiation of a transfer activity to its completion, specifically for 'Stock Moved Internally' events. Used in the 'Internal Transfer Lead Time Analysis' dashboard, this attribute helps assess the efficiency of warehouse logistics. High lead times can indicate inefficient travel paths, resource shortages, or systemic delays in the process of moving goods within the same facility. Why it matters Highlights inefficiencies in internal warehouse logistics. Long transfer times can delay fulfillment even when stock is physically present in the building. Where to get Calculated attribute. It is the time difference between the completion and start of a 'Stock Moved Internally' activity sequence. Examples 18003600900
	Last Data Update LastDataUpdate	The timestamp of the most recent data refresh from the source system.
Description This attribute indicates the date and time when the data was last extracted from NetSuite and updated in the process mining tool. It provides context for the freshness of the analysis and the data being viewed. This is a critical piece of metadata for any dashboard or analysis, as it informs the user about the recency of the insights. It helps users understand if they are looking at real-time information or a snapshot from a specific point in time. Why it matters Informs users about the freshness of the data, ensuring they understand the time frame of the analysis and make decisions based on up-to-date information. Where to get This timestamp is generated by the ETL (Extract, Transform, Load) process during data ingestion. Examples 2024-05-21T02:00:00Z2024-05-20T02:00:00Z2024-05-19T02:00:00Z
	Picking & Packing Lead Time PickingAndPackingLeadTime	The calculated time from the start of picking to the completion of packing.
Description This metric measures the efficiency of the outbound fulfillment process. It is the total time elapsed from when an item is first designated for picking ('Picking Initiated' or 'Picking Wave Created') until it has been fully packed and is ready for shipment ('Packing Completed'). This is a critical KPI for the 'Picking & Packing Completion Rate' dashboard. It directly impacts order fulfillment speed and customer satisfaction. Analyzing this lead time helps identify bottlenecks in the picking or packing stages of the outbound process. Why it matters Measures the speed of the outbound fulfillment process. Reducing this lead time is key to faster shipping and improved customer satisfaction. Where to get Calculated attribute. It is the time difference between the timestamp of the 'Packing Completed' activity and the 'Picking Initiated' activity. Examples 3600540018000
	Processing Time ProcessingTime	The duration of an individual activity, calculated from its start and end times.
Description Processing Time measures how long it took to complete a single event in the process. It is calculated as the difference between the End Time and Start Time for an activity. Analyzing Processing Time helps pinpoint inefficiencies within specific tasks. For example, a long processing time for 'Quality Inspection Performed' indicates that the inspection itself is slow, rather than there being a long wait time before the inspection begins. This allows for targeted improvements at the activity level. Why it matters Measures the duration of individual tasks, helping to distinguish between waiting time and actual work time to pinpoint specific operational inefficiencies. Where to get This is not a field in NetSuite. It is calculated by subtracting the StartTime from the EndTime during data preparation. Examples 300180086400
	Put-away Cycle Time PutAwayCycleTime	The calculated time from goods receipt to the completion of the put-away process.
Description This metric measures the total duration from the moment goods are officially received ('Goods Receipt Recorded') until they are successfully stored in their final destination bin ('Put-away Completed'). It represents the efficiency of the receiving and put-away workflow. This is a key performance indicator used in the 'Put-away Cycle Time by Warehouse' dashboard. Analyzing this cycle time helps identify delays in making new inventory available for fulfillment, highlighting bottlenecks in the receiving dock, staging areas, or in the put-away tasks themselves. Why it matters Directly measures the efficiency of making newly received stock available for sale or use. Long cycle times indicate bottlenecks that delay inventory availability. Where to get Calculated attribute. It is the time difference between the timestamp of the 'Put-away Completed' activity and the 'Goods Receipt Recorded' activity for the same case. Examples 72001440086400
	Quantity Quantity	The number of units of the item involved in the transaction.
Description This attribute represents the quantity of the stock item being moved, received, adjusted, or shipped in a given transaction. The quantity can be positive or negative, for example in the case of a stock deduction. Quantity is a fundamental metric for understanding the scale of operations. It is used to weigh the importance of certain activities, calculate throughput, and assess the volume of stock being adjusted or scrapped. It provides context to nearly every inventory analysis. Why it matters Provides the volume for each transaction, which is essential for understanding throughput, calculating the value of adjustments, and prioritizing high-volume activities. Where to get This is the standard 'Quantity' field on all transaction lines in NetSuite. Examples 100501000-10
	SKU Category ItemCategory	A classification or category for the inventory item (SKU).
Description The SKU Category is a higher-level grouping for products, such as 'Electronics', 'Apparel', or 'Raw Materials'. This allows for aggregated analysis across similar types of items. In NetSuite, this might be represented by standard fields like 'Class' or a custom item field. It is used in dashboards like 'Expiring & Obsolete Stock Overview' to analyze trends and issues affecting entire product groups rather than just individual SKUs, providing a more strategic view. Why it matters Allows for aggregated analysis by product group, helping to identify systemic issues or trends that affect entire categories of items. Where to get This could be the standard 'Class' or 'Department' fields on the Item record in NetSuite, or a custom item field created for categorization. Examples Finished GoodsRaw MaterialsElectronicsApparel
	Source System SourceSystem	The system from which the data was extracted.
Description This attribute identifies the origin of the event data. For this process view, the value will consistently be 'NetSuite', indicating that all inventory management activities are being sourced from this ERP system. While it may seem static, this attribute is crucial in environments where data from multiple systems might be combined. It ensures clarity on data provenance and helps in troubleshooting data extraction and integration issues. Why it matters Confirms the origin of the data, which is essential for data governance, validation, and in scenarios where data from multiple systems is merged. Where to get This is a static value ('NetSuite') added during the data extraction and transformation process. Examples NetSuite
	Storage Bin BinNumber	The specific bin or storage area within a warehouse where the item is located.
Description The Storage Bin identifies the most granular storage unit within a warehouse, such as a specific shelf, rack, or pallet location. This is used in environments where precise tracking of inventory placement is required. Analyzing by Storage Bin is key for understanding internal warehouse logistics. It supports the 'Internal Transfer Lead Time Analysis' by tracking movements between bins and the 'Warehouse Activity Heatmap' by showing which bins are most frequently accessed for put-away or picking activities. Why it matters Provides granular detail on inventory placement, which is essential for analyzing internal warehouse movements, optimizing layout, and tracking picking efficiency. Where to get Found in the 'Bin Number' field on transaction lines. This requires the 'Advanced Bin/Numbered Inventory Management' feature to be enabled in NetSuite. Examples A-01-01-AB-05-03-CRECEIVING-DOCK-01PICK-FACE-12
	Supplier SupplierName	The name of the supplier or vendor providing the inventory item.
Description This attribute identifies the vendor from whom the goods were procured. This information is typically captured during the goods receipt process and is linked from the corresponding purchase order. Analyzing by supplier is important for procurement and supply chain performance management. The 'Returns Processing Cycle Time' dashboard uses this attribute to identify if returns from certain suppliers are processed more slowly, which could indicate issues with product quality or documentation from that supplier. Why it matters Links inventory to its source supplier, enabling analysis of supplier performance, quality issues, and return rates. Where to get The 'Entity' field on Purchase Orders and Item Receipts, which references a Vendor record in NetSuite. Examples Global Electronics Inc.Bulk Goods Co.Component Suppliers LLCOffice Mart
	Transaction ID TransactionId	The unique identifier for the source transaction record in NetSuite.
Description This attribute is the unique system ID or document number for the NetSuite transaction that generated the event in the process mining log. Examples include the Item Receipt number or the Inventory Adjustment document number. Having the Transaction ID is invaluable for operational use cases. It allows users to easily drill down from an interesting or problematic case discovered in the process mining tool directly to the specific source record in NetSuite for further investigation or corrective action. Why it matters Provides a direct link back to the specific transaction in NetSuite, enabling users to easily investigate anomalies or audit process steps in the source system. Where to get This can be the 'Transaction Number' (the user-facing ID) or the 'Internal ID' (the system's unique primary key) of a transaction record. Examples IR-001234ADJ-00056WO-00987IF-004321
	Unit of Measure Units	The unit of measure for the transaction quantity (e.g., Each, Kg, Box).
Description The Unit of Measure (UoM) provides context for the 'Quantity' attribute. It specifies whether the quantity is in individual units, cases, kilograms, liters, or another measurement. This attribute is crucial for ensuring accurate interpretation of quantity-based metrics, especially in environments with diverse product types. It prevents misinterpretation, for example, comparing a quantity of 10 pallets to a quantity of 10 individual items, and is vital for accurate value calculations. Why it matters Provides essential context to the 'Quantity' field, ensuring that analyses and comparisons are accurate when items are tracked in different units like pieces, boxes, or kilograms. Where to get Available as the 'Units' field on transaction lines if the 'Multiple Units of Measure' feature is enabled in NetSuite. Examples EachCase (24)kgL

Required Recommended Optional

Inventory Management Activities

These are the key process steps and milestones to capture in your event log for accurate discovery and analysis of inventory flows.

6 Recommended 9 Optional

	Activity	Description
	Goods Issue Recorded	Marks the final step where an inventory batch is shipped to a customer, officially leaving the warehouse. This is captured when the status of an Item Fulfillment transaction is set to 'Shipped' in NetSuite.
Why it matters As the primary successful end event, it is essential for analyzing the end-to-end inventory lifecycle, from receipt to shipment, and measuring overall order fulfillment time. Where to get Captured from the status change date when an Item Fulfillment record is updated to 'Shipped'. This action decrements inventory. Capture Event is logged when the status of the Item Fulfillment transaction becomes 'Shipped'. Event type explicit
	Goods Receipt Recorded	Marks the official arrival of an inventory batch into the warehouse. This event is captured when an Item Receipt transaction is created in NetSuite, often linked to a Purchase Order.
Why it matters This is the primary start event for the inventory lifecycle, crucial for measuring supplier lead times and the overall inbound processing time. Where to get Captured from the creation date of the Item Receipt transaction record. The transaction logs the user, date, items, and quantities received. Capture Event is logged upon creation of an Item Receipt transaction. Event type explicit
	Inventory Discrepancy Adjusted	Occurs when a difference between physical and system inventory is corrected. This is explicitly recorded in NetSuite through an Inventory Adjustment transaction, which increases or decreases the quantity on hand.
Why it matters This is a critical event for analyzing inventory accuracy, identifying root causes of discrepancies, and ensuring financial compliance. Where to get Captured from the creation of an Inventory Adjustment transaction record. The transaction includes details like the adjustment account, reason, and quantity change. Capture Event is logged upon the creation of an Inventory Adjustment transaction. Event type explicit
	Picking Completed	Represents the completion of the physical picking of an inventory batch from its storage bin for an order. This is often inferred from a status change on the Item Fulfillment record from 'Picking' to 'Packed' or a similar status.
Why it matters This is a key milestone for measuring picker efficiency and the overall picking and packing lead time, a critical component of order fulfillment speed. Where to get Inferred from a status change on the Item Fulfillment record (e.g., to 'Picked') or the completion of all picking tasks associated with the fulfillment. Capture Inferred from a status change on the Item Fulfillment transaction to 'Picked'. Event type inferred
	Put-away Completed	Confirms that the inventory batch has been successfully placed into its designated storage bin. This event is captured when a Bin Transfer or Bin Putaway Worksheet is marked as complete, updating the item's bin location.
Why it matters This milestone is critical for tracking inventory availability for fulfillment and calculating the total put-away cycle time. Delays here directly impact order processing capabilities. Where to get Captured from the completion or transaction date of a Bin Transfer record or a completed Bin Putaway Worksheet. This action updates the bin location for the lot number. Capture Event logged upon completion of a Bin Transfer or Bin Putaway Worksheet transaction. Event type explicit
	Stock Scrapped/Disposed	Represents the final removal of an inventory batch from stock due to damage, expiration, or obsolescence. This is captured using an Inventory Adjustment transaction with a negative quantity and a specific reason code.
Why it matters This alternative end event is critical for analyzing inventory write-offs, understanding the financial impact of obsolete stock, and improving inventory lifecycle management. Where to get Captured from an Inventory Adjustment transaction where the adjustment account is designated for scrap or disposal, or a custom field indicates the reason. Capture Event is logged via an Inventory Adjustment transaction with a specific account or reason code for scrap. Event type explicit
	Inventory Count Approved	Represents the official approval of the results from a physical inventory count, preceding any adjustments. This event is inferred from the status of the Inventory Count record changing to 'Approved'.
Why it matters This approval step can be a bottleneck in the inventory reconciliation process. Analyzing its duration helps streamline operations and improve data accuracy speed. Where to get Inferred from the system notes or audit trail when the status on the Inventory Count record is updated to 'Approved' by an authorized user. Capture Inferred from a status field change on the Inventory Count record to 'Approved'. Event type inferred
	Inventory Count Initiated	Marks the beginning of a physical inventory count for a specific batch or location. This activity is captured when an Inventory Count record is created in NetSuite, scheduling the stock take.
Why it matters This event starts the clock for measuring the discrepancy resolution cycle time, highlighting how long it takes to perform counts and correct stock levels. Where to get Captured from the creation date of the Inventory Count transaction record, which defines the items and locations to be counted. Capture Event is logged upon the creation of an Inventory Count record. Event type explicit
	Packing Completed	Signals that the picked items for an order have been packed and are ready for shipment. This is typically inferred from a status change on the Item Fulfillment record from 'Picked' to 'Packed'.
Why it matters This activity marks the end of the internal warehouse processing for an order and is the final step before shipping begins. Where to get Inferred from a status change on the Item Fulfillment record to 'Packed'. The timestamp of this change would be captured from the system notes. Capture Inferred from a status change on the Item Fulfillment transaction to 'Packed'. Event type inferred
	Picking Wave Created	Initiates the outbound process by grouping multiple orders into a single picking task or wave. This is typically captured by the creation of a wave record within NetSuite WMS or a related fulfillment module.
Why it matters This marks the start of the fulfillment cycle, enabling analysis of the time from order allocation to the start of physical picking. Where to get Captured from the creation date of a picking wave or consolidated fulfillment record in NetSuite WMS. This may not exist in non-WMS implementations. Capture Event logged upon the creation of a fulfillment wave record. Event type explicit
	Put-away Initiated	Signals the start of the process to move a received inventory batch from the receiving dock to its final storage bin. This can be inferred from the creation of a Bin Putaway Worksheet or a similar task record in NetSuite's WMS module.
Why it matters This activity provides the starting point for measuring put-away cycle time, a key metric for warehouse efficiency, and helps analyze the time stock spends in staging areas. Where to get Inferred from the creation date of a Bin Putaway Worksheet or a task assignment in a WMS extension. This is most relevant for environments using NetSuite WMS. Capture Derived from the creation of a Bin Putaway Worksheet record for the specific item receipt. Event type inferred
	Quality Inspection Performed	Represents the completion of a quality check on the received inventory batch. This is often inferred from a status change on the inventory lot record or a related custom record, as standard NetSuite may not have a discrete event for this.
Why it matters Analyzing the time between receipt and inspection helps identify bottlenecks in the quality assurance process that delay stock availability. Where to get Likely inferred from a timestamp on a custom field or a status change on the Lot/Batch record, or a related Quality custom record. Requires analysis of the specific NetSuite configuration. Capture Inferred from a status change (e.g., 'Pending Inspection' to 'Available') on the inventory record. Event type inferred
	Return Authorization Created	Represents the official start of the returns process, where a request to return goods is approved and documented. This is captured by the creation of a Return Authorization (RMA) transaction in NetSuite.
Why it matters This activity initiates the reverse logistics flow, allowing for the analysis of return reasons, frequency, and subsequent processing times. Where to get Captured from the creation date of the Return Authorization transaction record. This record precedes the physical return of goods. Capture Event logged upon the creation of a Return Authorization transaction. Event type explicit
	Return Goods Received	Confirms the physical receipt of returned goods back into the warehouse. This event is captured by the creation of an Item Receipt transaction that is linked to a Return Authorization.
Why it matters Tracking this event is crucial for measuring the full cycle time of returns processing and ensuring returned inventory is accurately accounted for and dispositioned promptly. Where to get Captured from the creation date of an Item Receipt transaction where the 'Created From' field links to a Return Authorization. Capture Event logged upon creation of an Item Receipt against a Return Authorization. Event type explicit
	Stock Moved Internally	Represents the movement of an inventory batch between two different storage bins or locations within the same warehouse. This is explicitly captured by an Inventory Transfer or Bin Transfer transaction in NetSuite.
Why it matters Tracking internal movements helps analyze warehouse layout efficiency, identify excessive handling, and optimize stock placement strategies. Where to get Captured from the transaction date of an Inventory Transfer (between locations) or Bin Transfer (within one location) record. Capture Event is logged upon creation of an Inventory Transfer or Bin Transfer transaction. Event type explicit

Recommended Optional

Extraction Guides

How to get your data from NetSuite

Steps

Log into NetSuite: Access your NetSuite account with a role that has permissions to create and run 'Transaction' type Saved Searches and view all relevant inventory records.
Navigate to Saved Search Creation: Go to Reports > Saved Searches > All Saved Searches > New. Select 'Transaction' from the list of available search types. This will be the base record for all our searches.
Create a Search for 'Goods Receipt': Begin with the first activity. On the Saved Search setup page, set the criteria. Filter 'Type' to 'Item Receipt' and 'Main Line' to 'false' to get item-level detail. Add a 'Date' filter for your desired analysis period, for example, the last 3 months.
Define Results Columns: Click the 'Results' subtab. Add the necessary fields. You will need to use formulas to create a standardized ActivityName column. For this search, add a 'Formula (Text)' column and set the formula to 'Goods Receipt Recorded'. Add 'Inventory Detail Fields...Lot/Serial Number' for the case ID, 'Date' for the timestamp, 'Created By' for the user, and so on, for all required attributes. Use 'Custom Label' to rename columns to match the event log schema, for example, InventoryBatchLotNumber.
Repeat for All Activities: Save the first search. Then, create separate Saved Searches for each of the 15 required activities, adjusting the 'Type' filter and 'Formula (Text)' for the ActivityName accordingly. For example, for 'Goods Issue Recorded', you will filter by 'Type' is 'Item Fulfillment' and 'Status' is 'Shipped'. For some activities like 'Quality Inspection Performed', you may need to filter on a custom field or status specific to your organization's workflow.
Save and Run Each Search: Save each configured search with a clear name (e.g., 'ProcessMind - Goods Receipts'). Run each search from the saved search list page. The results will display on the screen.
Export Results to CSV: For each search result page, click the 'Export - CSV' icon. This will download a separate CSV file for each of the 15 activities.
Combine the CSV Files: Open the downloaded CSV files in a spreadsheet program like Microsoft Excel or use a scripting tool. Copy and paste the data from each file into a single master file, one after the other. Ensure the column headers are identical across all files before combining.
Finalize the Event Log: Review the combined master CSV file. Check that the column headers are named correctly (InventoryBatchLotNumber, ActivityName, TransactionDate, etc.). Ensure the date format is consistent and remove any duplicate header rows from the copy-pasting process. The file is now ready for upload.

Configuration

Prerequisites: User role must have permissions to create and execute Saved Searches on the 'Transaction' record type. Access to view Item Receipts, Item Fulfillments, Inventory Adjustments, and other relevant inventory records is required.
Search Type: Always use the 'Transaction' search type as the foundation for extracting inventory events.
Date Range: It is recommended to filter searches on the 'Date' field for a specific period, such as the last 3 to 6 months, to keep the dataset manageable. For very high volumes, consider running the searches in monthly or weekly batches.
Key Criteria Filters: The primary filters will be 'Type' (to isolate specific transactions like Item Receipt) and 'Main Line' set to 'No' (to get individual item lines). Additional filters on 'Status', 'Location', or custom fields will be necessary to distinguish different activities within the same transaction type.
Results Columns and Formulas: The 'Results' subtab is critical. Use the 'Inventory Detail Fields...' option to access the Lot/Serial Number. Use 'Formula (Text)' to hardcode the ActivityName for each search, for example, 'Goods Receipt Recorded'. Use 'Custom Label' on every column to define the final header for the CSV file.
Handling Lot Numbers: Ensure you add the 'Inventory Detail Fields...Lot/Serial Number' column to the results. Transactions that do not use lot numbers will not appear if you filter for this field being non-empty.

a Sample Query config

The following represents the configuration for 15 separate NetSuite Saved Searches. The results of these searches must be exported to CSV and combined into a single file.

**Search 1: Goods Receipt Recorded**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Receipt'; Main Line is false; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Goods Receipt Recorded' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Created From.Date (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 2: Quality Inspection Performed**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Receipt'; Main Line is false; [Your Custom Inspection Status Field] is '[Completed Status]'; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Quality Inspection Performed' (Custom Label: ActivityName), Last Modified Date (Custom Label: TransactionDate), null (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), null (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 3: Put-away Initiated**
*   **Search Type**: Transaction
*   **Criteria**: Type is '[Your Bin Putaway Worksheet Type]'; Main Line is false; Status is '[Initiated Status]'; Date Created is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Put-away Initiated' (Custom Label: ActivityName), Date Created (Custom Label: TransactionDate), null (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), null (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 4: Put-away Completed**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Bin Transfer' or '[Your Bin Putaway Worksheet Type]'; Main Line is false; Status is '[Completed Status]'; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Put-away Completed' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Date (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 5: Stock Moved Internally**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Inventory Transfer' or 'Bin Transfer'; Main Line is false; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Stock Moved Internally' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Date (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 6: Inventory Count Initiated**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Inventory Count'; Main Line is false; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Inventory Count Initiated' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), null (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 7: Inventory Count Approved**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Inventory Count'; Main Line is false; Status is 'Approved'; Last Modified Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Inventory Count Approved' (Custom Label: ActivityName), Last Modified Date (Custom Label: TransactionDate), Last Modified Date (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 8: Inventory Discrepancy Adjusted**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Inventory Adjustment'; Main Line is false; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Inventory Discrepancy Adjusted' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Date (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Est. Extended Cost (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 9: Picking Wave Created**
*   **Search Type**: Transaction
*   **Criteria**: Type is '[Your Wave Transaction Type]'; Main Line is false; Date Created is within [Start Date] and [End Date]
*   **Results**: Formula (Text): 'Extract Lot Number from Memo or Custom Field' (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Picking Wave Created' (Custom Label: ActivityName), Date Created (Custom Label: TransactionDate), null (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), null (Custom Label: MovementReasonCode), null (Custom Label: StockValue), Type (Custom Label: TransactionType), null (Custom Label: Item)

**Search 10: Picking Completed**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Fulfillment'; Main Line is false; Status is 'Picked' or 'Packed'; Last Modified Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Picking Completed' (Custom Label: ActivityName), Last Modified Date (Custom Label: TransactionDate), Last Modified Date (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), null (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 11: Packing Completed**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Fulfillment'; Main Line is false; Status is 'Packed' or 'Shipped'; Last Modified Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Packing Completed' (Custom Label: ActivityName), Last Modified Date (Custom Label: TransactionDate), Last Modified Date (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), null (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 12: Goods Issue Recorded**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Fulfillment'; Main Line is false; Status is 'Shipped'; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Goods Issue Recorded' (Custom Label: ActivityName), Actual Ship/Receipt Date (Custom Label: TransactionDate), Actual Ship/Receipt Date (Custom Label: EndTime), Last Modified By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)
	
**Search 13: Return Authorization Created**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Return Authorization'; Main Line is false; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Return Authorization Created' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), null (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 14: Return Goods Received**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Item Receipt'; Main Line is false; Created From.Type is 'Return Authorization'; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Return Goods Received' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Date (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Amount (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

**Search 15: Stock Scrapped/Disposed**
*   **Search Type**: Transaction
*   **Criteria**: Type is 'Inventory Adjustment'; Main Line is false; Quantity is negative; [Your Reason Code Field] is '[Scrap Reason]'; Date is within [Start Date] and [End Date]; Inventory Detail.Lot/Serial Number is not empty
*   **Results**: Inventory Detail.Lot/Serial Number (Custom Label: InventoryBatchLotNumber), Formula (Text): 'Stock Scrapped/Disposed' (Custom Label: ActivityName), Date (Custom Label: TransactionDate), Date (Custom Label: EndTime), Created By (Custom Label: User), Location (Custom Label: Location), Memo (Custom Label: MovementReasonCode), Est. Extended Cost (Custom Label: StockValue), Type (Custom Label: TransactionType), Item (Custom Label: Item)

Steps

Prerequisites: Ensure that the SuiteAnalytics Connect add-on module is enabled for your NetSuite account. You will also need a NetSuite user role with sufficient permissions to access the required data tables, such as Transaction, TransactionLine, and InventoryNumber.
Obtain Connection Details: In NetSuite, navigate to the Settings portlet on your home dashboard and click Set Up SuiteAnalytics Connect. Note your Account ID, Role ID, and the correct Service Host for your account.
Install the Driver: Download and install the appropriate driver for your operating system and SQL client. NetSuite provides ODBC, JDBC, and ADO.NET drivers.
Configure Your SQL Client: Set up a new connection or DSN using the details from step 2. You will use your NetSuite username and password for authentication. For the database name, use NetSuite.com or NetSuite2.com, depending on your account's data source.
Connect to NetSuite: Launch your preferred SQL client, such as DBeaver, Microsoft Excel, or Tableau, and establish a connection to the NetSuite data warehouse using your configured settings.
Prepare the Query: Open a new query editor in your SQL client and copy the complete SQL script provided in the Query section of this document.
Customize Placeholders: In the query, locate the WHERE clause in the initial Common Table Expression (CTE). Modify the date placeholders, such as 'YYYY-MM-DD', to define the desired date range for the extraction. Add any other company-specific filters if needed, for example, on a specific subsidiary.
Execute the Extraction Query: Run the complete SQL query. The execution time will vary depending on the date range and the volume of data in your NetSuite account.
Review the Data: Once the query completes, briefly inspect the results to ensure that rows are returned and that columns like InventoryBatchLotNumber, ActivityName, and TransactionDate are populated as expected.
Export to CSV: Export the entire result set to a CSV file. Ensure the file is saved with UTF-8 encoding to prevent any character issues.
Final Formatting: Open the CSV file and verify that the column headers match the names required for ProcessMind ingestion (CaseId, Activity, EventTime). Adjust the date format if necessary to conform to the required standard, for example, YYYY-MM-DD HH:MI:SS.

Configuration

SuiteAnalytics Connect Access: A valid license for the SuiteAnalytics Connect module is required. Without it, you cannot establish a direct database connection.
User Permissions: The NetSuite role used for the connection must have permissions to view the records and fields being queried. This includes Transactions, Items, Locations, Employees, and Inventory Numbers.
Date Range Filtering: It is critical to apply a date filter on the Transaction.trandate field to limit the data volume. We recommend starting with a recent period of 3 to 6 months to ensure manageable query performance.
Data Freshness: The SuiteAnalytics Connect data source is a replica of the production database. Be aware that there can be a replication lag, so the data may not be real-time. The lag is typically between one to three hours.
Customizations: The provided query assumes a standard NetSuite configuration. If your organization uses custom fields to track key events like 'Quality Inspection Performed' or 'Stock Scrapped', you must modify the query to include logic for those custom fields or records.
WMS Module: Some activities, like 'Picking Wave Created', are specific to the NetSuite Warehouse Management System (WMS) module. If you do not use NetSuite WMS, these parts of the query will not return any data.

a Sample Query sql

WITH EventData AS (
  SELECT
    T.tranid AS TransactionId,
    T.trandate AS TransactionDate,
    T.id AS TransactionInternalId,
    T.lastmodifieddate AS LastModifiedDate,
    BUILTIN.DF(T.type) AS TransactionType,
    BUILTIN.DF(T.status) AS TransactionStatus,
    T.memo AS TransactionMemo,
    TL.id AS TransactionLineId,
    IA.inventorynumber AS InventoryNumberId,
    INUMB.inventorynumber AS InventoryBatchLotNumber,
    I.itemid AS Sku,
    E.entityid AS UserName,
    L.fullname AS LocationName,
    TL.quantity AS Quantity,
    TL.rate AS Rate,
    T.createdfrom AS CreatedFromId,
    INUMB.custitemnumber_quality_status AS QualityStatus -- Placeholder for a custom quality status field
  FROM
    Transaction AS T
    JOIN TransactionLine AS TL ON T.id = TL.transaction
    JOIN InventoryAssignment AS IA ON TL.id = IA.transactionline
    JOIN InventoryNumber AS INUMB ON IA.inventorynumber = INUMB.id
    LEFT JOIN Item AS I ON TL.item = I.id
    LEFT JOIN Employee AS E ON T.lastmodifiedby = E.id
    LEFT JOIN Location AS L ON TL.location = L.id
  WHERE
    T.trandate >= '2023-01-01' AND T.trandate < '2024-01-01' -- Define your date range here
    AND T.type IN ('ItemRcpt', 'InvTrnfr', 'BinTrnfr', 'InvCount', 'InvAdjst', 'ItemShip', 'RtnAuth')
    AND IA.inventorynumber IS NOT NULL
)
SELECT
  InventoryBatchLotNumber,
  'Goods Receipt Recorded' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Item Receipt'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Quality Inspection Performed' AS ActivityName,
  LastModifiedDate AS TransactionDate, -- Using last modified as a proxy for this custom event
  LastModifiedDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  'Quality Status set to ' || QualityStatus AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE QualityStatus = 'Approved' -- This condition requires customization based on your quality process
UNION ALL
-- NetSuite WMS activities often use separate tables. The following are placeholders if not using EventData.
-- If not using WMS, these activities might be inferred from status changes on other transactions.
SELECT
  NULL AS InventoryBatchLotNumber, -- This information needs to be joined from your WMS implementation
  'Put-away Initiated' AS ActivityName,
  trandate AS TransactionDate,
  trandate as EndTime,
  BUILTIN.DF(lastmodifiedby) AS User,
  BUILTIN.DF(location) AS Location,
  memo AS MovementReasonCode,
  NULL AS StockValue,
  'Bin Putaway Worksheet' AS TransactionType,
  NULL AS Item
FROM Transaction
WHERE type = 'BinWksht' AND status = 'A' -- Status for 'Pending'
UNION ALL
SELECT
  NULL AS InventoryBatchLotNumber, -- This information needs to be joined from your WMS implementation
  'Put-away Completed' AS ActivityName,
  lastmodifieddate AS TransactionDate,
  lastmodifieddate as EndTime,
  BUILTIN.DF(lastmodifiedby) AS User,
  BUILTIN.DF(location) AS Location,
  memo AS MovementReasonCode,
  NULL AS StockValue,
  'Bin Transfer' AS TransactionType,
  NULL AS Item
FROM Transaction
WHERE type = 'BinTrnfr' AND BUILTIN.DF(status) = 'Completed'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Stock Moved Internally' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType IN ('Inventory Transfer', 'Bin Transfer')
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Inventory Count Initiated' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  NULL AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Inventory Count'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Inventory Count Approved' AS ActivityName,
  LastModifiedDate AS TransactionDate,
  LastModifiedDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  NULL AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Inventory Count' AND TransactionStatus LIKE '%Approved%'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Inventory Discrepancy Adjusted' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Inventory Adjustment'
UNION ALL
-- Picking Wave is a WMS-specific record. This query assumes a 'Wave' table exists.
SELECT
  NULL AS InventoryBatchLotNumber, -- Requires joining WaveTransaction and other tables to get lot numbers
  'Picking Wave Created' AS ActivityName,
  W.trandate AS TransactionDate,
  W.trandate AS EndTime,
  BUILTIN.DF(W.lastmodifiedby) AS User,
  BUILTIN.DF(WT.location) AS Location,
  W.memo AS MovementReasonCode,
  NULL AS StockValue,
  'Wave' AS TransactionType,
  NULL AS Item
FROM Wave AS W
JOIN WaveTransaction AS WT ON W.id = WT.wave
WHERE W.trandate >= '2023-01-01' AND W.trandate < '2024-01-01' -- Define your date range here
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Picking Completed' AS ActivityName,
  LastModifiedDate AS TransactionDate,
  LastModifiedDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Item Fulfillment' AND TransactionStatus LIKE '%Picked%'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Packing Completed' AS ActivityName,
  LastModifiedDate AS TransactionDate,
  LastModifiedDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Item Fulfillment' AND TransactionStatus LIKE '%Packed%'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Goods Issue Recorded' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Item Fulfillment' AND TransactionStatus LIKE '%Shipped%'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Return Authorization Created' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Return Authorization'
UNION ALL
SELECT
  ED.InventoryBatchLotNumber,
  'Return Goods Received' AS ActivityName,
  ED.TransactionDate,
  ED.TransactionDate as EndTime,
  ED.UserName AS User,
  ED.LocationName AS Location,
  ED.TransactionMemo AS MovementReasonCode,
  (ED.Quantity * ED.Rate) AS StockValue,
  ED.TransactionType,
  ED.Sku AS Item
FROM EventData ED
JOIN Transaction T_RMA ON ED.CreatedFromId = T_RMA.id
WHERE ED.TransactionType = 'Item Receipt' AND T_RMA.type = 'RtnAuth'
UNION ALL
SELECT
  InventoryBatchLotNumber,
  'Stock Scrapped/Disposed' AS ActivityName,
  TransactionDate,
  TransactionDate as EndTime,
  UserName AS User,
  LocationName AS Location,
  TransactionMemo AS MovementReasonCode,
  (Quantity * Rate) AS StockValue,
  TransactionType,
  Sku AS Item
FROM EventData
WHERE TransactionType = 'Inventory Adjustment' AND Quantity < 0 AND (LOWER(TransactionMemo) LIKE '%scrap%' OR LOWER(TransactionMemo) LIKE '%dispose%');

Steps

Prerequisites and Environment Setup: Ensure you have Python 3.6 or newer installed. Install the necessary Python libraries by running pip install requests requests-oauthlib pandas in your command line terminal. Confirm you have a NetSuite role with 'REST Web Services' permissions and access to the required transaction records (Item Receipt, Item Fulfillment, Inventory Adjustment, etc.).
Configure NetSuite Authentication: Log in to NetSuite and navigate to Setup > Integration > Manage Integrations. Create a new integration, enable Token-Based Authentication, and save the Consumer Key and Consumer Secret. Then, navigate to Setup > Users/Roles > Access Tokens > New. Select the integration, user, and role you configured, and save the Token ID and Token Secret. Note your Account ID, which can be found at Setup > Integration > Web Services Preferences.
Prepare the Python Script: Copy the complete Python script provided in the 'query' section of this document into a new file, for example, extract_netsuite_inventory.py.
Enter Credentials and Parameters: Open the script and replace the placeholder values for ns_account_id, ns_consumer_key, ns_consumer_secret, ns_token_id, and ns_token_secret with the credentials you obtained in step 2. Adjust the start_date and end_date variables to define the desired extraction period.
Customize the SuiteQL Query: Review the SuiteQL query within the script. Pay close attention to any placeholders, such as [Your Custom Field for QA Status] or [Your Scrap Account ID]. Modify these parts of the query to match your specific NetSuite configuration and custom fields.
Execute the Extraction Script: Run the script from your command line using the command python extract_netsuite_inventory.py. The script will connect to the NetSuite API, execute the query, and handle pagination automatically.
Monitor Script Execution: The script will print progress updates to the console, showing which page of data it is currently fetching. If any errors occur related to authentication or permissions, they will be displayed here. Execution time will vary depending on the date range and data volume.
Review the Output Data: Once the script completes successfully, it will create a file named netsuite_inventory_event_log.csv in the same directory. Open this CSV file with a spreadsheet program to review the extracted data.
Prepare Data for ProcessMind: Before uploading, ensure the column headers in the CSV file match the required attributes for your ProcessMind project. Rename columns if necessary. For example, InventoryBatchLotNumber should map to your case ID, ActivityName to the activity, and TransactionDate to the timestamp.

Configuration

NetSuite Role Permissions: The NetSuite role associated with the access token must have permissions for 'REST Web Services' and 'SuiteAnalytics Connect'. It also requires 'View' level access to all transaction types being queried, including Item Receipt, Item Fulfillment, Inventory Adjustment, Inventory Transfer, and any relevant custom records.
Token-Based Authentication (TBA): This script exclusively uses TBA for security. Ensure TBA is enabled in your NetSuite account (Setup > Company > Enable Features > SuiteCloud tab) and that you have generated the necessary consumer keys and access tokens.
Date Range: The script requires a start_date and end_date in 'YYYY-MM-DD' format. For initial testing, use a small date range, such as one week. For a full analysis, a period of 3 to 6 months is typically recommended to capture sufficient process variations without excessive data volume.
Subsidiary Filtering: For NetSuite OneWorld accounts, it is critical to add a filter for the specific subsidiary to avoid pulling data from all entities. This can be done by adding AND Transaction.subsidiary = [Your Subsidiary ID] to the WHERE clause of each SELECT statement in the query.
Custom Fields: The query contains placeholders for activities that often rely on custom fields or records, such as 'Quality Inspection Performed'. You must identify the correct custom field names in your system and update the query accordingly for these activities to be extracted.
API Governance: NetSuite enforces API governance limits on concurrency and total execution time. For very large datasets, the script may time out. It is advisable to run the extraction during off-peak hours and consider breaking up very large date ranges into smaller, sequential runs.

a Sample Query python

import requests
from requests_oauthlib import OAuth1
import json
import pandas as pd
import sys

class=class="hl-string">"hl-comment"># --- Configuration: Replace with your NetSuite Credentials and Parameters ---
ns_account_id = class="hl-string">"[Your NetSuite Account ID]"  class=class="hl-string">"hl-comment"># e.g., class="hl-string">"1234567_SB1"
ns_consumer_key = class="hl-string">"[Your Consumer Key]"
ns_consumer_secret = class="hl-string">"[Your Consumer Secret]"
ns_token_id = class="hl-string">"[Your Token ID]"
ns_token_secret = class="hl-string">"[Your Token Secret]"

class=class="hl-string">"hl-comment"># --- Date Range for Extraction ---
start_date = class="hl-string">"2023-01-01"
end_date = class="hl-string">"2023-06-30"

class=class="hl-string">"hl-comment"># --- SuiteQL Query ---
class=class="hl-string">"hl-comment"># This query unions data from multiple transaction types to build a comprehensive event log.
class=class="hl-string">"hl-comment"># Each SELECT block corresponds to a specific inventory activity.
suiteql_query = fclass="hl-string">"""
SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Goods Receipt Recorded' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    NULL AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'ItemRcpt' AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

-- Note: Quality Inspection is often a custom process. This is a placeholder.
-- You may need to join to a custom record or check a custom field on the InventoryNumber record.
SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Quality Inspection Performed' AS ActivityName,
    InventoryNumber.lastModifiedDate AS TransactionDate, -- Using last modified date as event time
    InventoryNumber.lastModifiedDate AS EndTime,
    (SELECT employee.entityId FROM employee WHERE employee.id = InventoryNumber.lastModifiedBy) AS User,
    BUILTIN.DF(InventoryNumber.location) AS Location,
    'QA Completed' AS MovementReasonCode,
    NULL AS StockValue,
    'Custom QA Process' AS TransactionType,
    BUILTIN.DF(InventoryNumber.item) AS Item
FROM
    InventoryNumber
WHERE
    InventoryNumber.custitemnumber_qa_status = 'Approved' -- Placeholder: [Configure based on your system]
    AND InventoryNumber.lastModifiedDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Put-away Completed' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Put-away' AS MovementReasonCode,
    NULL AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'BinTrnfr' AND TransactionLine.quantity > 0 AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Stock Moved Internally' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    Transaction.memo AS MovementReasonCode,
    NULL AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type IN ('InvTrnfr', 'BinTrnfr') AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

-- Note: Capturing multiple events from InventoryCount record (creation, approval)
SELECT
    InventoryDetail.inventoryNumber AS InventoryBatchLotNumber,
    'Inventory Count Initiated' AS ActivityName,
    InventoryCount.tranDate AS TransactionDate,
    NULL AS EndTime,
    BUILTIN.DF(InventoryCount.createdBy) as User,
    BUILTIN.DF(InventoryCount.location) as Location,
    'Count Creation' as MovementReasonCode,
    NULL as StockValue,
    'InvCount' as TransactionType,
    BUILTIN.DF(InventoryDetail.item) as Item
FROM
    InventoryCount
    INNER JOIN TransactionLine InventoryDetail ON InventoryCount.id = InventoryDetail.transaction
WHERE
    InventoryCount.tranDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryDetail.inventoryNumber AS InventoryBatchLotNumber,
    'Inventory Count Approved' AS ActivityName,
    NoteSystem.noteDate AS TransactionDate, -- Using system note date for accuracy
    NoteSystem.noteDate AS EndTime,
    NoteSystem.author AS User,
    BUILTIN.DF(InventoryCount.location) as Location,
    'Count Approval' as MovementReasonCode,
    NULL as StockValue,
    'InvCount' as TransactionType,
    BUILTIN.DF(InventoryDetail.item) as Item
FROM
    InventoryCount
    INNER JOIN TransactionLine InventoryDetail ON InventoryCount.id = InventoryDetail.transaction
    INNER JOIN SystemNote NoteSystem on InventoryCount.id = NoteSystem.recordId
WHERE
    NoteSystem.field = 'TRANSTATUS' AND NoteSystem.newvalue = 'Approved'
    AND NoteSystem.noteDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Inventory Discrepancy Adjusted' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    Transaction.memo AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'InvAdjst' AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Goods Issue Recorded' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.actualShipDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Shipment' AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'ItemShip' AND Transaction.status = 'ItemShip:G' -- G = Shipped
    AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    NULL AS InventoryBatchLotNumber, -- Batch not known at time of authorization
    'Return Authorization Created' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.createdby) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    Transaction.memo AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
WHERE
    Transaction.type = 'RtnAuth' AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Return Goods Received' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Return' AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'ItemRcpt' AND Transaction.createdFrom IS NOT NULL AND BUILTIN.DF(Transaction.createdFrom.type) = 'Return Authorization'
    AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Stock Scrapped/Disposed' AS ActivityName,
    Transaction.trandate AS TransactionDate,
    Transaction.lastModifiedDate AS EndTime,
    BUILTIN.DF(Transaction.lastModifiedBy) AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Scrap/Disposal' AS MovementReasonCode,
    (TransactionLine.quantity * TransactionLine.rate) AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
WHERE
    Transaction.type = 'InvAdjst' AND TransactionLine.quantity < 0 AND Transaction.account = [Your Scrap Account ID] -- Placeholder: [Configure based on your system]
    AND Transaction.trandate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

-- Note: Activities like Picking/Packing/Wave Creation often require the WMS module.
-- The following are common representations but may need adjustment for your specific configuration.

UNION ALL

SELECT
    NULL AS InventoryBatchLotNumber, -- Batch is assigned during picking, not wave creation
    'Picking Wave Created' as ActivityName,
    Wave.creationDate as TransactionDate,
    Wave.lastModifiedDate as EndTime,
    BUILTIN.DF(Wave.createdBy) as User,
    BUILTIN.DF(Wave.location) as Location,
    NULL as MovementReasonCode,
    NULL as StockValue,
    'Wave' as TransactionType,
    NULL as Item
FROM Wave
WHERE Wave.creationDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

-- Picking/Packing are often status changes on the Item Fulfillment
SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Picking Completed' as ActivityName,
    NoteSystem.noteDate as TransactionDate, -- Use system note date for status change time
    NoteSystem.noteDate as EndTime,
    NoteSystem.author AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Picking for Shipment' as MovementReasonCode,
    NULL AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
    INNER JOIN SystemNote NoteSystem on Transaction.id = NoteSystem.recordId
WHERE
    Transaction.type = 'ItemShip' AND NoteSystem.field = 'TRANSTATUS' AND NoteSystem.newvalue = 'Packed'
    AND NoteSystem.noteDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

UNION ALL

SELECT
    InventoryNumber.inventoryNumber AS InventoryBatchLotNumber,
    'Packing Completed' as ActivityName,
    NoteSystem.noteDate as TransactionDate, -- Use system note date for status change time
    NoteSystem.noteDate as EndTime,
    NoteSystem.author AS User,
    BUILTIN.DF(TransactionLine.location) AS Location,
    'Packing for Shipment' as MovementReasonCode,
    NULL AS StockValue,
    BUILTIN.DF(Transaction.type) AS TransactionType,
    BUILTIN.DF(TransactionLine.item) AS Item
FROM
    Transaction
    INNER JOIN TransactionLine ON Transaction.id = TransactionLine.transaction
    INNER JOIN InventoryAssignment ON Transaction.id = InventoryAssignment.transaction AND TransactionLine.id = InventoryAssignment.transactionline
    INNER JOIN InventoryNumber ON InventoryAssignment.inventorynumber = InventoryNumber.id
    INNER JOIN SystemNote NoteSystem on Transaction.id = NoteSystem.recordId
WHERE
    Transaction.type = 'ItemShip' AND NoteSystem.field = 'TRANSTATUS' AND NoteSystem.newvalue = 'Packed'
    AND NoteSystem.noteDate BETWEEN TO_DATE('{start_date}', 'YYYY-MM-DD') AND TO_DATE('{end_date}', 'YYYY-MM-DD')

-- Put-away Initiated is not included as Bin Putaway Worksheet is not available in standard SuiteQL at this time.

"""

class=class="hl-string">"hl-comment"># --- Main Script Logic ---
def main():
    class=class="hl-string">"hl-comment"># Construct the URL for the SuiteQL endpoint
    base_url = fclass="hl-string">"https://{ns_account_id.lower().replace('_', '-')}.suitetalk.api.netsuite.com"
    suiteql_url = fclass="hl-string">"{base_url}/services/rest/query/v1/suiteql"

    class=class="hl-string">"hl-comment"># Set up OAuth1 authentication
    auth = OAuth1(
        client_key=ns_consumer_key,
        client_secret=ns_consumer_secret,
        resource_owner_key=ns_token_id,
        resource_owner_secret=ns_token_secret,
        realm=ns_account_id
    )

    headers = {
        class="hl-string">'Content-Type': class="hl-string">'application/json',
        class="hl-string">'Prefer': class="hl-string">'transient'
    }

    offset = 0
    limit = 1000  class=class="hl-string">"hl-comment"># NetSuite's max limit per page
    all_data = []

    print(class="hl-string">"Starting NetSuite data extraction...")

    while True:
        payload = json.dumps({
            class="hl-string">'q': suiteql_query,
            class="hl-string">'offset': offset,
            class="hl-string">'limit': limit
        })

        try:
            print(fclass="hl-string">"Fetching data page with offset: {offset}")
            response = requests.post(suiteql_url, headers=headers, data=payload, auth=auth)
            response.raise_for_status()  class=class="hl-string">"hl-comment"># Raises an HTTPError for bad responses (4xx or 5xx)

            result = response.json()
            
            if class="hl-string">'items' in result and result[class="hl-string">'items']:
                all_data.extend(result[class="hl-string">'items'])
            
            has_more = result.get(class="hl-string">'hasMore', False)
            if not has_more:
                print(class="hl-string">"All pages have been fetched.")
                break
            
            offset += limit

        except requests.exceptions.HTTPError as e:
            print(fclass="hl-string">"HTTP Error: {e}")
            print(fclass="hl-string">"Response body: {response.text}")
            sys.exit(1)
        except Exception as e:
            print(fclass="hl-string">"An unexpected error occurred: {e}")
            sys.exit(1)

    if not all_data:
        print(class="hl-string">"No data found for the specified criteria.")
        return

    class=class="hl-string">"hl-comment"># Convert the list of dictionaries to a pandas DataFrame
    df = pd.DataFrame(all_data)

    class=class="hl-string">"hl-comment"># Save the DataFrame to a CSV file
    output_file = class="hl-string">'netsuite_inventory_event_log.csv'
    df.to_csv(output_file, index=False)
    print(fclass="hl-string">"Extraction complete. Data saved to {output_file}")

if __name__ == class="hl-string">"__main__":
    main()

Your Inventory Management Data Template

Your Inventory Management Data Template

Inventory Management Attributes

Inventory Management Activities

Extraction Guides

NetSuite Saved Search and CSV Export for Inventory

Steps

Configuration

a Sample Query config

Direct Database Query via SuiteAnalytics Connect

Steps

Configuration

a Sample Query sql

Python Script using SuiteQL via NetSuite REST API

Steps

Configuration

a Sample Query python

Ready to Get Started?

Transform Your NetSuite Inventory Management Now!

Your Inventory Management Data Template

Your Inventory Management Data Template

Inventory Management Attributes

Inventory Management Activities

Extraction Guides

NetSuite Saved Search and CSV Export for Inventory

Steps

Configuration

a Sample Query config

Direct Database Query via SuiteAnalytics Connect

Steps

Configuration

a Sample Query sql

Python Script using SuiteQL via NetSuite REST API

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Transform Your NetSuite Inventory Management Now!