> Continuous Process Improvement > Inventory Management > Oracle Fusion SCM > Data Template

Your Inventory Management Data Template

Oracle Fusion SCM

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

Your Inventory Management Data Template

This template provides a comprehensive guide for extracting and structuring your Inventory Management data from Oracle Fusion SCM. It outlines the essential attributes and activities needed to create an effective event log. Use this resource to accurately analyze your inventory processes and identify areas for optimization.

Recommended attributes to collect
Key activities to track for process discovery
Guidance on data extraction from Oracle Fusion SCM

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

Download Template

Inventory Management Attributes

These are the essential data fields recommended for inclusion in your event log, allowing for comprehensive analysis of your inventory management processes.

5 Required 5 Recommended 11 Optional

	Name	Description
	Activity Name ActivityName	The name of the specific inventory management activity that was performed.
Description The Activity Name describes a single step or event that occurred within the inventory management process for a specific batch or lot. These events form the sequence of the process flow. Examples of activities include 'Goods Receipt Recorded', 'Quality Inspection Performed', 'Stock Moved Internally', and 'Goods Issue Recorded'. Analyzing the sequence and frequency of these activities is the core of process mining, allowing for the visualization of process maps, identification of deviations, and analysis of transition times between steps. Why it matters This attribute is fundamental for constructing the process map, as it defines the distinct steps and events that make up the inventory lifecycle. Where to get This is often derived by mapping transaction types or event codes from source tables (e.g., INV_MATERIAL_TXNS) to user-friendly activity names. Examples Goods Receipt RecordedPut-away CompletedInventory Discrepancy AdjustedPicking Initiated
	Event Start Time EventStartTime	The timestamp indicating when the inventory activity began.
Description This attribute captures the precise date and time that an activity started. It is the primary temporal element used to order events chronologically and build the process flow. In analysis, the Event Start Time is critical for calculating durations and waiting times between activities. It enables the identification of bottlenecks, the measurement of cycle times for KPIs like 'Average Put-away Cycle Time', and the analysis of process performance over different time periods (e.g., shifts, days, or months). Why it matters This timestamp is essential for ordering events, calculating cycle times and waiting times, and understanding process bottlenecks. Where to get Typically sourced from a transaction date or creation date field in inventory transaction tables, such as TRANSACTION_DATE in INV_MATERIAL_TXNS. Examples 2023-10-01T08:05:21Z2023-11-15T14:30:00Z2024-01-20T21:00:15Z
	Inventory Batch/Lot InventoryBatchLot	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 mining analysis, this attribute is fundamental. It connects disparate events like receiving, quality inspection, internal transfers, and goods issue into a single, coherent process instance. Analyzing processes by Inventory Batch/Lot allows for the calculation of end-to-end cycle times, identification of common pathways, and discovery of bottlenecks affecting specific stock groups. Why it matters This is the essential case identifier that links all related inventory activities together, making it possible to trace the full journey of a stock batch from receipt to issue. Where to get This information is typically found in the inventory transaction tables, such as INV_MATERIAL_TXNS, associated with lot or batch control details. Examples LOT2024-A01134BATCH-US-00582LPN-493820-202405
	Last Data Update LastDataUpdate	Timestamp indicating the last time the data for this record was refreshed from the source system.
Description This attribute records when the data was last extracted from the source system and loaded into the process mining tool. It reflects the freshness of the data being analyzed. This timestamp is vital for understanding the recency of the process insights. It allows users to know if they are looking at near real-time data or a snapshot from a previous period, which is crucial for making timely and informed decisions based on the analysis. Why it matters Indicates the freshness of the data, ensuring users understand how current the process analysis is and when the next data refresh is expected. Where to get This is a metadata field generated during the data extraction, transformation, and loading (ETL) process. Examples 2024-05-21T02:00:00Z2024-05-20T02:00:00Z2024-05-19T02:00:00Z
	Source System SourceSystem	Identifies the system from which the data was extracted.
Description This attribute specifies the source application where the inventory transaction was recorded. In a large enterprise, inventory data might originate from multiple systems or modules. Specifying the source system is crucial for data governance and for understanding the context of the data. It helps in troubleshooting data extraction issues and can be used to compare processes that span different systems or instances, for example, comparing inventory management processes across different regional ERPs. Why it matters Provides essential context for data origin, which is important for data validation, governance, and analyzing processes that may span multiple systems. Where to get This is typically a static value added during the data extraction and transformation process to label the origin of the data. Examples Oracle Fusion SCMOracle SCM Cloud-PRODFusion-ERP-US
	Event End Time EventEndTime	The timestamp indicating when the inventory activity was completed.
Description The Event End Time marks the completion of an activity. While many inventory transactions are recorded as single-point-in-time events, some activities like 'Quality Inspection' or 'Picking' have a distinct duration. For instantaneous events, the End Time is often the same as the Start Time. This attribute is used in conjunction with the Event Start Time to calculate the processing time of individual activities. This is crucial for performance analysis, resource utilization studies, and identifying activities that take longer than expected, contributing to overall process delays. Why it matters Enables the calculation of the processing time for individual activities, helping to pinpoint which specific steps are time-consuming. Where to get May be the same as the start time for instantaneous transactions. For activities with duration, it would be a separate completion timestamp field in the relevant source table. Examples 2023-10-01T08:05:21Z2023-11-15T15:00:00Z2024-01-20T21:05:45Z
	Item Number ItemNumber	The unique identifier for the product or material being handled.
Description The Item Number, often referred to as a Stock Keeping Unit (SKU), identifies the specific product involved in an inventory transaction. This allows for analysis to be filtered or segmented by product. In process mining, this attribute is essential for product-centric analysis. It helps answer questions like, 'Which products have the longest put-away times?' or 'Which items are most frequently adjusted?'. This enables targeted improvements for specific product lines or categories. Why it matters Allows for filtering and analysis by specific products, helping to identify which items are associated with process delays or issues. Where to get This is a core field in inventory transaction tables, typically named INVENTORY_ITEM_ID, which links to the item master table (EGP_SYSTEM_ITEMS_B) for details. Examples AS54888CPU-INT-i9MEM-DDR5-32GB
	Movement Reason Code MovementReasonCode	A code that explains the business reason for an inventory movement or adjustment.
Description The Movement Reason Code provides context for why an inventory transaction occurred. This is particularly important for non-standard movements like scrap, cycle count adjustments, or returns. This attribute is critical for root cause analysis. For instance, the 'Inventory Adjustment Frequency And Reasons' dashboard uses this code to categorize adjustments, helping to distinguish between damage, theft, or data entry errors. Analyzing these reasons helps prioritize and focus improvement efforts on the most significant problems. Why it matters Explains the 'why' behind inventory adjustments and movements, which is crucial for root cause analysis of issues like discrepancies or scrap. Where to get Found in transaction tables as a reason code field, such as REASON_ID in INV_MATERIAL_TXNS, which links to a reason code master data table. Examples DAMAGED IN TRANSITCYCLE COUNT ADJEXPIRED STOCK
	User Performing Action UserPerformingAction	The user ID or name of the person who executed the inventory transaction.
Description This attribute identifies the specific user responsible for performing a given activity, such as a warehouse operator who completed a put-away task or an inventory manager who approved an adjustment. Analyzing by user is critical for understanding workload distribution, identifying training needs, and ensuring compliance. For instance, the 'Inventory Adjustment Frequency And Reasons' dashboard uses this attribute to see who performs adjustments most often, which can highlight top performers or individuals who may require additional training on inventory control procedures. Why it matters Attributes actions to specific individuals, enabling analysis of user performance, workload, training needs, and process compliance. Where to get Typically found in transaction tables as a 'USER_ID' or 'CREATED_BY' field, such as CREATED_BY in INV_MATERIAL_TXNS. Examples JSMITHAMARTINWAREHOUSE.OPERATOR
	Warehouse Location WarehouseLocation	The specific location within the warehouse where the activity occurred, such as a bin or zone.
Description This attribute specifies the physical location within the warehouse, like a specific aisle, rack, or bin, related to the inventory transaction. It provides granular detail on where stock is stored or moved. Analyzing by warehouse location helps identify logistical inefficiencies. For example, the 'Internal Stock Movement Lead Time' dashboard can use this to show if transfers between certain zones are consistently slow. It can also reveal if specific locations are prone to inventory discrepancies. Why it matters Provides geographical context within the warehouse, enabling analysis of movement efficiency and location-specific issues like bottlenecks or frequent adjustments. Where to get Sourced from fields like LOCATOR_ID in inventory transaction tables, which can be joined with location master data (INV_ITEM_LOCATIONS) for descriptive names. Examples A1-R4-S3-B2RECEIVING-DOCK-01QC-INSPECT-AREA
	Activity Processing Time ActivityProcessingTime	The duration of a single activity, calculated as the difference between its end and start times.
Description This metric measures the time spent actively working on a task, calculated as 'EventEndTime' minus 'EventStartTime'. For instantaneous events, this duration is zero. For activities with a defined start and finish, like a quality inspection, it represents the actual processing time. Analyzing processing time helps identify which specific steps in the process are the most time-consuming. This is different from cycle time, which includes waiting periods. High processing time for certain activities might indicate a need for better tools, automation, or more staff. Why it matters Measures the actual work duration of an activity, helping to pinpoint inefficient steps that require optimization, separate from waiting time. Where to get Calculated during data transformation: EventEndTime - EventStartTime. Examples 0 00:30:000 02:00:000 00:00:00
	Inventory Holding Days InventoryHoldingDays	The total time an inventory batch remains in stock, from first receipt to final issue or disposal.
Description This is a case-level KPI that calculates the total duration a specific batch or lot of inventory is held. It is measured from the timestamp of the first 'Goods Receipt Recorded' activity to the timestamp of the final 'Goods Issue Recorded' or 'Stock Scrapped/Disposed' activity for that case. This metric is crucial for managing working capital and storage costs. A high value for Inventory Holding Days indicates slow-moving stock, which can lead to increased costs, risk of obsolescence, and inefficient use of warehouse space. Analyzing this KPI helps in optimizing inventory levels and improving turnover. Why it matters A critical KPI for financial and operational efficiency, it measures how long capital is tied up in inventory and helps identify slow-moving stock. Where to get This is a case-level metric calculated within the process mining tool by taking the difference between the timestamp of the last relevant event and the first. Examples 30 days 10:05:0095 days 04:00:0015 days 12:30:00
	Inventory Organization InventoryOrganization	The specific organization (e.g., warehouse, manufacturing plant) where the inventory is held.
Description An Inventory Organization represents a distinct facility or entity that holds stock, such as a distribution center or a factory. It is a key organizational data element in Oracle Fusion SCM. This attribute is used to filter and compare processes across different physical sites. It helps answer questions like, 'Which warehouse has the fastest put-away time?' or 'Is the inventory discrepancy rate higher in our European or North American facilities?'. This enables benchmarking and the sharing of best practices across the organization. Why it matters Allows for process comparison and benchmarking across different facilities like warehouses or plants, helping to identify site-specific performance. Where to get A core field in transaction tables, such as ORGANIZATION_ID, which links to an organization master data table for the name. Examples US1 Distribution CenterSeattle ManufacturingEU Central Warehouse
	Inventory Transaction ID InventoryTransactionId	The unique system-generated identifier for a single inventory event.
Description The Inventory Transaction ID is the primary key for a single, atomic inventory transaction record in the source system. Each row in the event log corresponds to one such ID. While not typically used directly in high-level process maps, this ID is invaluable for data validation, auditing, and drill-down analysis. It provides a direct link back to the specific record in Oracle Fusion SCM, allowing analysts to investigate anomalies or specific events in the source system itself. Why it matters Provides a unique key for each event, which is essential for data validation, traceability, and allowing users to drill down to the source system record. Where to get This is the primary key of the main inventory transaction table, typically TRANSACTION_ID in INV_MATERIAL_TXNS. Examples 987654321123456789555444333
	Is Cycle Count Adjustment IsCycleCountAdjustment	A boolean flag that is true if an inventory adjustment directly follows a cycle count activity.
Description This derived attribute is a boolean flag (True/False) that identifies 'Inventory Discrepancy Adjusted' activities that occur shortly after a 'Cycle Count Performed' activity for the same item and location. This helps isolate adjustments that are a direct result of the counting process. This flag is used for the 'Post-Cycle Count Adjustment Rate' KPI. It allows analysts to measure the effectiveness of the cycle counting program by highlighting how often counts lead to adjustments. A high rate of such adjustments may indicate systemic issues in inventory record accuracy. Why it matters Helps to specifically measure the effectiveness of the cycle counting process by isolating adjustments that are a direct result of a physical count. Where to get This is a derived attribute created during data transformation by checking the sequence of activities for a given item or batch. Examples truefalse
	Item Status ItemStatus	Indicates the current status of the inventory item, such as Active, Inactive, or Obsolete.
Description The Item Status reflects the lifecycle stage of the product itself. For example, an item can be 'Active' for normal transactions, 'Hold' for quality review, or 'Obsolete' if it is no longer in use. This attribute can provide valuable context for analyzing certain activities. For example, a high rate of scrapping for items with an 'Obsolete' status is expected, but scrapping of 'Active' items may indicate a serious issue. It helps in segmenting the analysis to focus on relevant and active inventory. Why it matters Provides context on the product lifecycle, helping to differentiate between expected actions (e.g., scrapping obsolete items) and unexpected process issues. Where to get This information comes from the item master table (e.g., EGP_SYSTEM_ITEMS_B) and must be joined to the transaction data. Examples ActiveInactiveObsolete
	Quantity Quantity	The quantity of the item involved in the transaction.
Description This attribute represents the number of units of an item that were moved, adjusted, counted, or otherwise transacted. It provides a measure of the magnitude of each event. Quantity is a fundamental metric for many analyses. It is used to calculate the volume of goods processed, the size of inventory discrepancies, and the amount of scrap. When combined with cost data, it allows for the financial impact of process inefficiencies to be quantified, as seen in the 'Cycle Count Discrepancy Analysis' dashboard. Why it matters Quantifies the volume of each transaction, allowing for analysis of throughput, discrepancy sizes, and the financial impact of inventory activities. Where to get A standard field in inventory transaction tables, such as PRIMARY_QUANTITY or TRANSACTION_QUANTITY in INV_MATERIAL_TXNS. Examples 100-105000
	SKU Category SKUCategory	The category or family to which the product (SKU) belongs.
Description The SKU Category is a classification used to group similar products together. Examples include 'Electronics', 'Raw Materials', 'Finished Goods', or categories based on value (e.g., A, B, C items). This attribute enables high-level analysis by product group, which is often more insightful than looking at thousands of individual items. It is used in dashboards like 'Scrap And Obsolescence Rate Analysis' to identify which categories of products are most prone to being scrapped, helping to focus inventory policy and demand forecasting improvements. Why it matters Allows for aggregation and comparison of process performance across different product groups, revealing trends that may not be visible at the individual item level. Where to get This information is typically stored in the item master data (EGP_SYSTEM_ITEMS_B) and needs to be joined with the transaction data. Examples Fast MovingHigh ValueSpare Parts
	Subinventory Code SubinventoryCode	A subdivision of an inventory organization, representing a specific storage area or type.
Description A subinventory is a logical or physical grouping of items within a larger inventory organization (e.g., warehouse). Examples include 'Receiving', 'Finished Goods', 'Quality Hold', or 'Defective Material'. This attribute allows for a higher-level location analysis than the specific bin location. It's useful for tracking the flow of materials between different functional areas, such as the time it takes for items to move from the 'Receiving' subinventory to the 'Finished Goods' subinventory after quality inspection. Why it matters Enables analysis of inventory movement and holding times between different functional areas within a warehouse, like receiving, quality, and main storage. Where to get A standard field in inventory tables, often named SUBINVENTORY_CODE. Examples RECEIVINGFGISTORES
	Transaction Type TransactionType	The system-defined type of the inventory transaction.
Description This attribute is the raw, system-level classification of an inventory event, such as 'PO Receipt', 'Subinventory Transfer', or 'Cycle Count Adjustment'. It is often a more technical classification from which the user-friendly Activity Name is derived. While the Activity Name is used for high-level process maps, the Transaction Type can be valuable for detailed technical analysis or for validating the mapping to activities. It can help identify specific sub-processes or system behaviors that are grouped under a single activity. Why it matters Provides the raw system classification of an event, which is useful for detailed analysis and for validating the derivation of the 'Activity Name'. Where to get A standard field in inventory transaction tables, typically joined from a transaction type master table like MTL_TRANSACTION_TYPES. Examples PO ReceiptSubinventory TransferWIP Component Issue
	Unit Of Measure UnitOfMeasure	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, specifying what the numerical value represents. For example, a quantity of '10' could mean 10 individual items, 10 boxes, or 10 kilograms. This attribute is essential for accurate interpretation of quantity-based analysis. Without the UOM, it's impossible to compare transactions for different items or to accurately aggregate quantities. It ensures that analyses are performed on a consistent and meaningful basis. Why it matters Provides essential context to the 'Quantity' attribute, ensuring that values are interpreted correctly and comparisons are meaningful. Where to get Typically found alongside the quantity field in transaction tables, such as TRANSACTION_UOM in INV_MATERIAL_TXNS. Examples EAKGBOX

Required Recommended Optional

Inventory Management Activities

These are the crucial process steps and milestones to capture in your event log, ensuring accurate and detailed process discovery for inventory operations.

7 Recommended 8 Optional

	Activity	Description
	Goods Issue Recorded	Marks the final exit of an inventory lot from the warehouse, either through shipment to a customer, issuance to a production job, or transfer to another facility. This is a definitive, explicit material transaction that decrements inventory.
Why it matters This is a primary end point for the inventory lifecycle, crucial for calculating inventory turnover and holding days. It confirms the fulfillment of demand for the specific lot. Where to get Recorded as a material transaction in INV_MATERIAL_TXNS with types such as 'Sales Order Issue', 'WIP Component Issue', or 'Transfer Order Shipment'. Capture Logged when the ship confirmation or component issue transaction is processed. Event type explicit
	Goods Receipt Recorded	Marks the initial physical arrival of an inventory batch or lot into the warehouse, typically against a purchase order or return material authorization. This is an explicit transaction logged in the system when goods are received, creating the first record of the inventory lot.
Why it matters This activity serves as the primary start point for the inventory lifecycle analysis. Tracking the time from this event to others like put-away or quality inspection is critical for measuring inbound efficiency. Where to get Recorded as a material transaction in the INV_MATERIAL_TXNS table with transaction types such as 'PO Receipt', 'RMA Receipt', or 'Intransit Shipment Receipt'. The creation date of this transaction serves as the event timestamp. Capture Event is logged upon execution of a receipt transaction. Event type explicit
	Inventory Discrepancy Adjusted	An explicit transaction to correct the system's on-hand quantity for an inventory lot to match the physical count or to account for other discrepancies like damage. This transaction formally recognizes a gain or loss of inventory.
Why it matters Tracking adjustment frequency and reasons is crucial for identifying root causes of inventory inaccuracy, such as theft, damage, or process errors. It directly impacts financial records and stock reliability. Where to get Recorded as a material transaction in INV_MATERIAL_TXNS with a specific type like 'Cycle Count Adjustment' or 'Miscellaneous Issue/Receipt', often accompanied by a reason code. Capture Logged upon approval and posting of an inventory adjustment transaction. Event type explicit
	Picking Completed	Signifies that the inventory lot has been physically picked from its storage location and moved to a staging area. This is an explicit transaction where the picker confirms the completion of the pick task in the system.
Why it matters This is a key milestone in order fulfillment. The duration from 'Picking Initiated' to this event measures picker efficiency and the performance of the picking process. Where to get Captured via a pick confirmation transaction, which updates the status of the move order line or warehouse task to 'Completed' or triggers a 'Subinventory Transfer' transaction in INV_MATERIAL_TXNS. Capture Logged when a user confirms the pick transaction in the system, often via a mobile RF device. Event type explicit
	Put-away Completed	Represents the completion of moving the inventory lot into its designated storage bin or subinventory, making it officially part of available stock. This is captured by an explicit material transaction that updates the lot's location from receiving to a storage location.
Why it matters This milestone marks the end of the inbound process. The cycle time from 'Goods Receipt Recorded' to this event is a key KPI for measuring put-away efficiency. Where to get Recorded as a material transaction, often a 'Subinventory Transfer' or 'Put Away', in the INV_MATERIAL_TXNS table. This transaction moves the lot from a receiving subinventory to a storage subinventory. Capture Event is logged when the transaction confirming the move to a storage location is completed. Event type explicit
	Quality Inspection Performed	Signifies the completion of the quality inspection process, where a decision is made to accept or reject the inventory lot. This event is typically inferred from the final status update on the quality inspection record.
Why it matters This is a critical milestone that determines the availability of stock for downstream processes. Analyzing inspection outcomes and duration helps optimize quality control and supplier performance. Where to get Inferred from the timestamp when the quality inspection record in QA_RESULTS is updated with a final status like 'Accepted' or 'Rejected', or when the lot's material status is changed from 'QA' to 'Active'. Capture Derived from the completion date of the quality inspection record associated with the inventory lot. Event type inferred
	Stock Scrapped/Disposed	Represents the formal removal of an inventory lot from stock due to it being expired, damaged, obsolete, or otherwise unusable. This is an explicit transaction that writes off the inventory value.
Why it matters This is an end point for inventory that does not get sold or used. Tracking scrap helps identify issues with inventory aging, demand forecasting, or handling processes, and it has a direct financial impact. Where to get Recorded as a material transaction in INV_MATERIAL_TXNS, typically a 'Miscellaneous Issue' or a specific 'Scrap' transaction type, linked to a scrap-specific account and reason code. Capture Logged when the scrap transaction is executed and approved. Event type explicit
	Cycle Count Performed	Indicates that an inventory lot has been physically counted as part of a cycle counting or physical inventory program. This is an explicit action where a user enters the counted quantity into the system.
Why it matters This activity is central to analyzing inventory accuracy programs. It provides the basis for identifying discrepancies and measuring the effectiveness of the counting process. Where to get Recorded in the INV_CYCLE_COUNT_ENTRIES table when a count quantity is entered and saved by a user. The timestamp of the count entry serves as the event time. Capture Logged when a user submits a count for a specific item and lot in a cycle count task. Event type explicit
	Item Status Changed	Represents a change in the usability or restriction status of an inventory lot, such as placing it on hold, restricting it from sale, or releasing it. This is typically inferred from changes to the lot's status attribute.
Why it matters Monitoring status changes helps understand inventory availability and control. Frequent holds might indicate quality issues, while tracking releases is important for process flow. Where to get Inferred by tracking changes to the 'LOT_STATUS_CODE' or similar fields in inventory tables like INV_LOT_NUMBERS. Audit history or database logs may be required to capture the timestamp of the change. Capture Captured by comparing the current and previous values of the lot status field over time. Event type inferred
	Packing Completed	Represents the completion of the packing process where the picked lot is placed into a shipping container and the container is sealed. This can be an explicit station scan or inferred from a shipment status change.
Why it matters Marks the end of physical warehouse processing before shipment. Analyzing the time between picking and packing helps identify inefficiencies in the packing station. Where to get Inferred from a status change on the delivery detail or shipment record (e.g., in WSH_DELIVERY_DETAILS) to 'Packed'. In some configurations, this might be an explicit transaction at a packing station. Capture Derived from a shipment status update timestamp or a specific packing transaction log. Event type inferred
	Picking Initiated	Marks the start of the order fulfillment process where a task is created to pick an inventory lot from its storage location for a sales order, work order, or transfer. This is inferred from the creation of a pick wave or move order line.
Why it matters This event starts the clock on picking cycle time. Delays between order allocation and pick initiation can reveal bottlenecks in order processing or warehouse task assignment. Where to get Inferred from the creation timestamp of a record in WMS tables for a pick task or a status update on a move order line (e.g., Mtl_Txn_Request_Lines) to 'Released to Warehouse'. Capture Identified by the creation of a pick task or move order associated with the inventory lot. Event type inferred
	Put-away Initiated	Marks the start of the process to move received goods from a staging or receiving area to their final storage location. This is usually inferred from the creation of a system-directed task or move request for the put-away operation.
Why it matters Initiating the put-away process quickly is key to clearing receiving docks and making inventory available. This event helps measure the delay between receipt and the start of put-away activities. Where to get Inferred from the creation timestamp of a move request or warehouse task in the Warehouse Management System (WMS) module related to the received lot. Capture Identified by the creation of a put-away task associated with the inventory transaction or lot. Event type inferred
	Quality Inspection Initiated	Represents the moment an inventory lot is designated for quality control inspection before being made available for use. This is often inferred from the creation of an inspection plan record associated with the received lot or a status change placing the lot in a 'QA' hold status.
Why it matters Identifies the start of the quality assurance process. The duration between this and 'Quality Inspection Performed' reveals the lead time and potential bottlenecks in the QC department. Where to get Inferred from the creation of a quality inspection record in the Quality Management module (e.g., QA_RESULTS) or by tracking a change in the lot's material status to a designated inspection status. Capture Inferred from the creation timestamp of a quality inspection plan or a lot status change to 'Awaiting Inspection'. Event type inferred
	Return Goods Processed	Captures the receipt and processing of a returned inventory lot from a customer via a Return Material Authorization (RMA). This activity re-introduces the lot into the inventory system, often triggering inspection and disposition processes.
Why it matters Analyzing the returns process is key to understanding product quality issues and improving reverse logistics efficiency. It can be a starting point for a separate returns sub-process. Where to get Recorded as an 'RMA Receipt' material transaction in the INV_MATERIAL_TXNS table. The transaction details link back to the original sales order and customer. Capture Logged upon execution of the RMA receipt transaction in the system. Event type explicit
	Stock Moved Internally	Captures the movement of an inventory lot between different storage locations, such as bins or subinventories, within the same warehouse. These movements are recorded as explicit material transactions for purposes like replenishment or consolidation.
Why it matters Analyzing internal movements helps identify inefficient warehouse layouts, excessive handling, and opportunities to optimize stock placement. High frequency may indicate poor initial put-away logic. Where to get Recorded as a material transaction in INV_MATERIAL_TXNS with a type such as 'Subinventory Transfer' or 'Locator Transfer' that does not involve an external party. Capture Logged upon completion of an internal transfer transaction. Event type explicit

Recommended Optional

Extraction Guides

How to get your data from Oracle Fusion SCM

Steps

Access Oracle BI Publisher: Log in to your Oracle Fusion SCM instance. Navigate to the Reports and Analytics work area through the Navigator menu. From there, select 'Browse Catalog' to open the Oracle BI Publisher interface.
Create a New Data Model: Inside the catalog, choose a suitable folder to store your extraction assets. Click the 'New' dropdown and select 'Data Model'.
Define the SQL Data Set: In the Data Model editor, click the '+' icon to add a new data set and select 'SQL Query'.
Configure the Data Source: In the new data set dialog, provide a name, for example, 'InventoryManagementEventLog'. Select 'ApplicationDB_FSCM' as the data source. Set the 'Type of SQL' to 'Standard SQL'.
Enter the SQL Query: Copy the complete SQL query provided in the 'query' section of this document and paste it into the SQL Query text area.
Define Parameters: The query uses parameters for the date range (p_start_date, p_end_date) and the organization code (p_organization_code). BI Publisher will automatically detect these. You can set default values or mark them as mandatory for users running the report.
Save and View Data: Save the data model. You can go to the 'Data' tab, enter parameter values, and click 'View' to see a sample of the extracted data and confirm the query works as expected.
Create a Report: Navigate back to the catalog. Click the 'New' dropdown and select 'Report'. In the report creation wizard, select the data model you just created.
Configure the Report Layout: Proceed through the wizard. When prompted for the layout, choose a simple 'Table' layout. Drag and drop all columns from the data set into the table. You do not need to apply complex formatting, as the goal is a raw data export.
Schedule the Report for Automated Extraction: Save the report. Use the 'Schedule' option for the report. Create a new schedule job. In the 'Output' tab of the schedule configuration, specify the output format as CSV. In the 'Destination' tab, configure the delivery to a content server directory or an external SFTP server where you can retrieve the files.
Retrieve the Event Log: Once the scheduled job runs, navigate to the specified destination (e.g., download from the content server or access the SFTP server) to retrieve the generated CSV file. This file is the event log, ready for upload into a process mining tool.

Configuration

Prerequisites: A user account with the necessary BI Administrator and data access roles to query inventory management tables like INV_MATERIAL_TXNS, RCV_TRANSACTIONS, and WSH_DELIVERY_DETAILS.
Data Source: Use the standard 'ApplicationDB_FSCM' data source in BI Publisher, which connects to the main Fusion SCM transactional database.
Report Parameters: It is critical to filter the data to manage performance. The provided query is parameterized for:
- p_start_date: The start date of the reporting period.
- p_end_date: The end date of the reporting period.
- p_organization_code: The specific inventory organization (warehouse) code to extract data for.
Date Range: For initial extractions, start with a limited historical period, such as the last 3 to 6 months, to ensure the job completes in a reasonable time. For ongoing extractions, schedule daily or weekly runs covering the recent period.
Output Format: Configure the BI Publisher report job to generate output in CSV format. Ensure the CSV delimiter and character encoding are compatible with your process mining tool.
Scheduling: Schedule the report to run during off-peak hours to minimize the impact on system performance. Large data volumes can consume significant system resources during execution.

a Sample Query sql

WITH EventData AS (
-- 1. Goods Receipt Recorded (PO & RMA)
SELECT
    IMT.TRANSACTION_ID,
    'Goods Receipt Recorded' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation, -- Using Org Code for warehouse level
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_TRANSACTION_TYPES_VL ITT ON IMT.TRANSACTION_TYPE_ID = ITT.TRANSACTION_TYPE_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON IMT.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND ITT.TRANSACTION_TYPE_NAME IN ('PO Receipt', 'RMA Receipt')

UNION ALL

-- 2. Quality Inspection Initiated (Move to QA subinventory)
SELECT
    IMT.TRANSACTION_ID,
    'Quality Inspection Initiated' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_SUBINVENTORIES_VL ISV ON IMT.SUBINVENTORY_CODE = ISV.SUBINVENTORY_CODE AND IMT.ORGANIZATION_ID = ISV.ORGANIZATION_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON IMT.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND IMT.TRANSACTION_ACTION_ID = 27 -- Subinventory Transfer
    AND ISV.SUBINVENTORY_TYPE = 'QA' -- This is a placeholder, adjust based on your system's QA subinventory naming convention

UNION ALL

-- 3. Quality Inspection Performed (Move out of QA subinventory)
SELECT
    IMT.TRANSACTION_ID,
    'Quality Inspection Performed' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_SUBINVENTORIES_VL ISV ON IMT.TRANSFER_SUBINVENTORY = ISV.SUBINVENTORY_CODE AND IMT.ORGANIZATION_ID = ISV.ORGANIZATION_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON IMT.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND IMT.TRANSACTION_ACTION_ID = 27 -- Subinventory Transfer
    AND ISV.SUBINVENTORY_TYPE <> 'QA' -- Moved out of a QA-type subinventory
    AND IMT.SUBINVENTORY_CODE IN (SELECT SUB.SUBINVENTORY_CODE FROM INV_SUBINVENTORIES_VL SUB WHERE SUB.ORGANIZATION_ID = IMT.ORGANIZATION_ID AND SUB.SUBINVENTORY_TYPE = 'QA')

UNION ALL

-- 4. Put-away Initiated (Modeled by Move Order Creation for received items)
SELECT
    MOL.MOVE_ORDER_LINE_ID AS TRANSACTION_ID,
    'Put-away Initiated' AS ActivityName,
    MOL.CREATION_DATE AS EventStartTime,
    MOL.CREATION_DATE AS EventEndTime,
    MOL.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    NULL AS MovementReasonCode,
    MOL.ORGANIZATION_ID
FROM
    INV_MOVE_ORDER_LINES MOL
JOIN INV_MOVE_ORDERS_V MOH ON MOL.HEADER_ID = MOH.HEADER_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON MOL.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND MOL.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON MOL.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON MOL.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
WHERE
    MOL.LOT_NUMBER IS NOT NULL
    AND MOH.MOVE_ORDER_TYPE = 6 -- Put Away

UNION ALL

-- 5. Put-away Completed (Subinventory transfer from Receiving)
SELECT
    IMT.TRANSACTION_ID,
    'Put-away Completed' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_SUBINVENTORIES_VL ISV ON IMT.SUBINVENTORY_CODE = ISV.SUBINVENTORY_CODE AND IMT.ORGANIZATION_ID = ISV.ORGANIZATION_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON IMT.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND IMT.TRANSACTION_ACTION_ID = 27 -- Subinventory Transfer
    AND IMT.TRANSACTION_SOURCE_TYPE_ID = 1 -- Purchase Order
    AND ISV.SUBINVENTORY_TYPE = '[Your Receiving Subinventory Type]' -- Adjust based on configuration

UNION ALL

-- 6. Stock Moved Internally
SELECT
    IMT.TRANSACTION_ID,
    'Stock Moved Internally' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    IMT.SUBINVENTORY_CODE || ' -> ' || IMT.TRANSFER_SUBINVENTORY AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_TRANSACTION_TYPES_VL ITT ON IMT.TRANSACTION_TYPE_ID = ITT.TRANSACTION_TYPE_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND ITT.TRANSACTION_TYPE_NAME = 'Subinventory Transfer'

UNION ALL

-- 7. Cycle Count Performed & 8. Inventory Discrepancy Adjusted
SELECT
    IMT.TRANSACTION_ID,
    CASE 
        WHEN ITT.TRANSACTION_TYPE_NAME = 'Cycle Count Adjustment' THEN 'Cycle Count Performed'
        ELSE 'Inventory Discrepancy Adjusted'
    END AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    IMT.SUBINVENTORY_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_TRANSACTION_TYPES_VL ITT ON IMT.TRANSACTION_TYPE_ID = ITT.TRANSACTION_TYPE_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND ITT.TRANSACTION_TYPE_NAME IN ('Cycle Count Adjustment', 'Miscellaneous issue', 'Miscellaneous receipt')

UNION ALL

-- 9. Item Status Changed
SELECT 
    ILN.LOT_NUMBER_ID AS TRANSACTION_ID,
    'Item Status Changed' AS ActivityName,
    ILN.LAST_UPDATE_DATE AS EventStartTime,
    ILN.LAST_UPDATE_DATE AS EventEndTime,
    ILN.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    ILN.STATUS_CODE AS MovementReasonCode,
    ILN.ORGANIZATION_ID
FROM 
    INV_LOT_NUMBERS ILN
JOIN EGP_SYSTEM_ITEMS_B ESIB ON ILN.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND ILN.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON ILN.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON ILN.LAST_UPDATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
WHERE 
    ILN.LOT_NUMBER IS NOT NULL

UNION ALL

-- 10. Picking Initiated (From Pick Wave Move Order)
SELECT
    MOL.MOVE_ORDER_LINE_ID AS TRANSACTION_ID,
    'Picking Initiated' AS ActivityName,
    MOL.CREATION_DATE AS EventStartTime,
    MOL.CREATION_DATE AS EventEndTime,
    MOL.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    OOD.ORGANIZATION_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    NULL AS MovementReasonCode,
    MOL.ORGANIZATION_ID
FROM
    INV_MOVE_ORDER_LINES MOL
JOIN INV_MOVE_ORDERS_V MOH ON MOL.HEADER_ID = MOH.HEADER_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON MOL.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND MOL.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN INV_ORG_PARAMETERS OOD ON MOL.ORGANIZATION_ID = OOD.ORGANIZATION_ID
JOIN PER_USERS PU ON MOL.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
WHERE
    MOL.LOT_NUMBER IS NOT NULL
    AND MOH.MOVE_ORDER_TYPE = 1 -- Pick Wave

UNION ALL

-- 11. Picking Completed (Transfer to Staging)
SELECT
    IMT.TRANSACTION_ID,
    'Picking Completed' AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    IMT.TRANSFER_SUBINVENTORY AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_TRANSACTION_TYPES_VL ITT ON IMT.TRANSACTION_TYPE_ID = ITT.TRANSACTION_TYPE_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND ITT.TRANSACTION_TYPE_NAME = 'Staging Transfer'

UNION ALL

-- 12. Packing Completed (Inferred from Ship Confirm)
-- 13. Goods Issue Recorded (Sales Order Issue)
-- 14. Return Goods Processed (RMA Issue - though this is usually a receipt)
-- 15. Stock Scrapped/Disposed
SELECT
    IMT.TRANSACTION_ID,
    CASE
        WHEN ITT.TRANSACTION_TYPE_NAME = 'Sales order issue' AND IMT.TRANSACTION_ACTION_ID = 1 THEN 'Goods Issue Recorded'
        WHEN ITT.TRANSACTION_TYPE_NAME = 'Sales order pick' THEN 'Packing Completed' -- Using Pick as a proxy for packing start/completion
        WHEN ITT.TRANSACTION_TYPE_NAME = 'RMA Receipt' THEN 'Return Goods Processed' -- This is a receipt, not an issue.
        WHEN ITT.TRANSACTION_TYPE_NAME = 'Miscellaneous issue' AND MTR.REASON_NAME LIKE '%Scrap%' THEN 'Stock Scrapped/Disposed'
        ELSE 'Other'
    END AS ActivityName,
    IMT.TRANSACTION_DATE AS EventStartTime,
    IMT.TRANSACTION_DATE AS EventEndTime,
    IMT.LOT_NUMBER AS InventoryBatchLot,
    ESIB.ITEM_NUMBER AS ItemNumber,
    IMT.SUBINVENTORY_CODE AS WarehouseLocation,
    PUN.DISPLAY_NAME AS UserPerformingAction,
    MTR.REASON_NAME AS MovementReasonCode,
    IMT.ORGANIZATION_ID
FROM
    INV_MATERIAL_TXNS IMT
JOIN INV_TRANSACTION_TYPES_VL ITT ON IMT.TRANSACTION_TYPE_ID = ITT.TRANSACTION_TYPE_ID
JOIN EGP_SYSTEM_ITEMS_B ESIB ON IMT.INVENTORY_ITEM_ID = ESIB.INVENTORY_ITEM_ID AND IMT.ORGANIZATION_ID = ESIB.ORGANIZATION_ID
JOIN PER_USERS PU ON IMT.CREATED_BY = PU.USERNAME
JOIN PER_USER_NAMES_F PUN ON PU.PERSON_ID = PUN.PERSON_ID AND PUN.NAME_TYPE = 'GLOBAL' AND SYSDATE BETWEEN PUN.EFFECTIVE_START_DATE AND PUN.EFFECTIVE_END_DATE
LEFT JOIN MTL_TRANSACTION_REASONS MTR ON IMT.REASON_ID = MTR.REASON_ID
WHERE
    IMT.LOT_NUMBER IS NOT NULL
    AND ITT.TRANSACTION_TYPE_NAME IN ('Sales order issue', 'Sales order pick', 'RMA Receipt', 'Miscellaneous issue')
)
SELECT
    ED.InventoryBatchLot,
    ED.ActivityName,
    ED.EventStartTime,
    'Oracle Fusion SCM' AS SourceSystem,
    SYSDATE AS LastDataUpdate,
    ED.EventEndTime,
    ED.UserPerformingAction,
    ED.ItemNumber,
    ED.WarehouseLocation,
    ED.MovementReasonCode
FROM
    EventData ED
JOIN INV_ORG_PARAMETERS OOD ON ED.ORGANIZATION_ID = OOD.ORGANIZATION_ID
WHERE
    ED.EventStartTime BETWEEN :p_start_date AND :p_end_date
    AND OOD.ORGANIZATION_CODE = :p_organization_code
    AND ED.ActivityName <> 'Other' -- Exclude unmapped transactions
ORDER BY
    ED.InventoryBatchLot, ED.EventStartTime

Steps

Log into your Oracle Fusion Cloud Applications environment with a user assigned the BICC administrator role.
Navigate to the Business Intelligence Cloud Connector (BICC) console by selecting it from the main navigator menu under Tools.
From the BICC console, select 'Manage Offerings and Data Stores'. Search for and ensure the 'Supply Chain Management' offering is enabled. This makes all SCM-related data stores (PVOs) available for extraction.
Navigate to 'Manage Extract Schedules' and create a new schedule dedicated to the inventory management process.
Within the new schedule, search for and add the necessary Public View Objects (PVOs) to extract the required data. Key PVOs include FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO, FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.LotControlExtractPVO, FscmTopModelAM.ScmExtractAM.QaBiccExtractAM.InspectionResultExtractPVO, and FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryDetailExtractPVO.
For each selected PVO, navigate to the 'Configure Columns' tab. Select all columns required for the event log, such as lot numbers, item details, timestamps, user identifiers, and transaction types. Deselect any columns that are not needed to optimize the extract size.
Define filters to manage data volume. On the 'Manage Filters' tab, set a global filter to enable incremental data loads. The standard filter expression is LAST_UPDATE_DATE >= '#BI_LAST_EXTRACT_DATE'. This ensures each run only extracts data that has changed since the previous run.
Configure the external storage for data delivery. Under 'Configure External Storage', choose 'Cloud Storage Service' and provide the connection credentials for your target storage, such as Oracle Cloud Infrastructure (OCI) Object Storage.
Save the schedule configuration and submit it to run. You can monitor the job's progress from the 'Manage Extract Schedules' screen.
Once the BICC job completes, the raw data files (in CSV format) will be available in your configured cloud storage location.
Implement a post-processing script or ETL workflow to download these CSV files. This script will need to transform and combine the data from multiple files according to the logic outlined in the query section to create the final event log.
The script should produce a single CSV file with the precise columns (InventoryBatchLot, ActivityName, EventStartTime, etc.) required for upload into ProcessMind.

Configuration

Offerings: The 'Supply Chain Management' offering must be enabled in BICC to access inventory, shipping, and quality management PVOs.
Key PVOs (Data Stores): A comprehensive extraction requires multiple PVOs. At a minimum, include:
- FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO: The primary source for most material movements like receipts, issues, transfers, and adjustments.
- FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.LotControlExtractPVO: Provides details on lot statuses.
- FscmTopModelAM.ScmExtractAM.QaBiccExtractAM.InspectionResultExtractPVO: Captures the outcomes of quality inspections.
- FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryDetailExtractPVO: Contains information related to picking and shipping processes.
Incremental Extract Configuration: Always use the incremental extract functionality for ongoing data loads. Configure a filter on the LastUpdateDate column using the #BI_LAST_EXTRACT_DATE variable. For the initial historical load, you may choose to run a full extract for a defined period, for example, the past 6 to 12 months.
PVO-Level Filters: To improve performance and reduce file sizes, apply additional filters directly on the PVOs. Common filters include OrganizationId to limit data to specific warehouses or TransactionTypeId to exclude irrelevant movements.
Prerequisites: The process requires a user account with the BICC_ADMINISTRATOR_JOB role. You must have access to and credentials for a supported cloud storage service (e.g., OCI Object Storage) where BICC can deliver the extracted files.

a Sample Query config

-- This is a conceptual query representing the logic to be applied in a post-processing script
-- after extracting raw data from the specified PVOs using BICC.

-- Activity: Goods Receipt Recorded (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Goods Receipt Recorded' AS "ActivityName", TransactionDate AS "EventStartTime", NULL AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode || ' / ' || LocatorName AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName IN ('PO Receipt', 'Transfer Receipt')

UNION ALL

-- Activity: Quality Inspection Initiated (Source PVO: FscmTopModelAM.ScmExtractAM.QaBiccExtractAM.InspectionPlanExtractPVO)
SELECT trx.LotNumber AS "InventoryBatchLot", 'Quality Inspection Initiated' AS "ActivityName", insp.CreationDate AS "EventStartTime", NULL AS "EventEndTime", insp.CreatedBy AS "UserPerformingAction", insp.ItemNumber AS "ItemNumber", insp.OrganizationCode AS "WarehouseLocation", NULL AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", insp.LastUpdateDate AS "LastDataUpdate"
FROM InspectionPlanExtractPVO_output.csv insp JOIN MaterialTransactionExtractPVO_output.csv trx ON insp.SourceTransactionId = trx.TransactionId

UNION ALL

-- Activity: Quality Inspection Performed (Source PVO: FscmTopModelAM.ScmExtractAM.QaBiccExtractAM.InspectionResultExtractPVO)
SELECT trx.LotNumber AS "InventoryBatchLot", 'Quality Inspection Performed' AS "ActivityName", res.TransactionDate AS "EventStartTime", res.TransactionDate AS "EventEndTime", res.CreatedBy AS "UserPerformingAction", res.ItemNumber AS "ItemNumber", res.OrganizationCode AS "WarehouseLocation", res.InspectionResultStatus AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", res.LastUpdateDate AS "LastDataUpdate"
FROM InspectionResultExtractPVO_output.csv res JOIN MaterialTransactionExtractPVO_output.csv trx ON res.SourceTransactionId = trx.TransactionId

UNION ALL

-- Activity: Put-away Initiated (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Put-away Initiated' AS "ActivityName", TransactionDate AS "EventStartTime", NULL AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName IN ('PO Receipt', 'RMA Receipt')

UNION ALL

-- Activity: Put-away Completed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Put-away Completed' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode || ' / ' || LocatorName AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName = 'Subinventory Transfer' AND SourceSubinventoryCode LIKE '%RECEIVING%'

UNION ALL

-- Activity: Stock Moved Internally (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Stock Moved Internally' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode || ' / ' || LocatorName AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName = 'Subinventory Transfer' AND SourceSubinventoryCode NOT LIKE '%RECEIVING%'

UNION ALL

-- Activity: Cycle Count Performed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.CycleCountEntriesExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Cycle Count Performed' AS "ActivityName", CountDate AS "EventStartTime", CountDate AS "EventEndTime", CountedByEmployeeName AS "UserPerformingAction", ItemNumber AS "ItemNumber", Subinventory AS "WarehouseLocation", NULL AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM CycleCountEntriesExtractPVO_output.csv
WHERE CountedByEmployeeName IS NOT NULL

UNION ALL

-- Activity: Inventory Discrepancy Adjusted (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Inventory Discrepancy Adjusted' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName IN ('Cycle Count Adjustment', 'Physical Inventory Adjustment')

UNION ALL

-- Activity: Item Status Changed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.LotControlExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Item Status Changed' AS "ActivityName", LastUpdateDate AS "EventStartTime", NULL AS "EventEndTime", LastUpdatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", NULL AS "WarehouseLocation", 'New Status: ' || LotStatusCode AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM LotControlExtractPVO_output.csv

UNION ALL

-- Activity: Picking Initiated (Source PVO: FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryDetailExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Picking Initiated' AS "ActivityName", CreationDate AS "EventStartTime", NULL AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", Subinventory AS "WarehouseLocation", NULL AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM DeliveryDetailExtractPVO_output.csv
WHERE ReleasedStatus = 'R'

UNION ALL

-- Activity: Picking Completed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Picking Completed' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", TransferSubinventory || ' / ' || TransferLocatorName AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName = 'Sales Order Pick'

UNION ALL

-- Activity: Packing Completed (Source PVO: FscmTopModelAM.ScmExtractAM.WshBiccExtractAM.DeliveryExtractPVO)
SELECT dd.LotNumber AS "InventoryBatchLot", 'Packing Completed' AS "ActivityName", d.ConfirmedDate AS "EventStartTime", d.ConfirmedDate AS "EventEndTime", d.LastUpdatedBy AS "UserPerformingAction", dd.ItemNumber AS "ItemNumber", dd.Subinventory AS "WarehouseLocation", NULL AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", d.LastUpdateDate AS "LastDataUpdate"
FROM DeliveryExtractPVO_output.csv d JOIN DeliveryDetailExtractPVO_output.csv dd ON d.DeliveryId = dd.DeliveryId
WHERE d.StatusCode = 'CL'

UNION ALL

-- Activity: Goods Issue Recorded (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Goods Issue Recorded' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName IN ('Sales Order Issue', 'Work Order Issue')

UNION ALL

-- Activity: Return Goods Processed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Return Goods Processed' AS "ActivityName", TransactionDate AS "EventStartTime", NULL AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName = 'RMA Receipt'

UNION ALL

-- Activity: Stock Scrapped/Disposed (Source PVO: FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.MaterialTransactionExtractPVO)
SELECT LotNumber AS "InventoryBatchLot", 'Stock Scrapped/Disposed' AS "ActivityName", TransactionDate AS "EventStartTime", TransactionDate AS "EventEndTime", CreatedBy AS "UserPerformingAction", ItemNumber AS "ItemNumber", SubinventoryCode AS "WarehouseLocation", ReasonName AS "MovementReasonCode", 'Oracle Fusion SCM' AS "SourceSystem", LastUpdateDate AS "LastDataUpdate"
FROM MaterialTransactionExtractPVO_output.csv
WHERE TransactionTypeName IN ('Scrap Transaction', 'Inventory Write-Off')

Steps

Prerequisites: Ensure you have Python 3.6 or newer installed on your system. Install the requests library, which is necessary for making HTTP API calls, by running the command pip install requests in your terminal.
Obtain API Credentials: Secure the necessary credentials for accessing the Oracle Fusion SCM REST API. This includes the base URL for your Oracle Fusion instance (e.g., https://your-fusion-instance.oraclecloud.com), a username, and a password for an account with sufficient privileges to read inventory data.
Configure the Python Script: Download the provided Python script. Open the file in an editor and locate the configuration section at the top. Fill in the placeholder values for BASE_URL, USERNAME, PASSWORD, START_DATE, END_DATE, and ORGANIZATION_ID.
Understand API Endpoints: The script primarily uses the inventoryTransactions REST API endpoint. This endpoint provides a comprehensive log of all material movements and adjustments, which will be translated into the process mining event log.
Review Activity Mapping Logic: Examine the map_transaction_to_activity function within the script. This function contains the core logic that translates Oracle's TransactionTypeName into the standardized ActivityName required for the event log. You may need to adjust this mapping based on the specific transaction types used in your organization.
Execute the Script: Run the script from your terminal using the command python your_script_name.py. The script will authenticate with the API, fetch transaction data page by page, process it, and print status updates to the console.
Handle Pagination and Data Fetching: The script automatically handles API pagination by making sequential requests using offset and limit parameters until all data within the specified date range is retrieved. This ensures the complete dataset is extracted without overloading the server or the script's memory.
Data Transformation: For each transaction retrieved, the script restructures the JSON response into a flat record. It maps fields like LotNumber, TransactionDate, and CreatedBy to the required event log attributes InventoryBatchLot, EventStartTime, and UserPerformingAction.
Generate the CSV Output: Once all data is fetched and processed, the script will write the results into a CSV file named oracle_fusion_inventory_log.csv in the same directory where the script is located.
Review and Upload: Open the generated CSV file in a spreadsheet application to verify its contents. Check for correct data population, complete date ranges, and the presence of all expected activities. Once validated, the file is ready to be uploaded to ProcessMind.

Configuration

API Credentials: A valid username and password for an Oracle Fusion user is required. The user must have a role with permissions to read inventory transaction data, such as Inventory Manager or a custom integration role.
Base URL: The root URL of your Oracle Fusion SCM instance (e.g., https://your-instance.oraclecloud.com) must be correctly specified.
Date Range: Set the START_DATE and END_DATE parameters in YYYY-MM-DD format to define the extraction window. It is recommended to start with a 3 to 6 month period to manage data volume.
Organization ID: Specify the ORGANIZATION_ID to restrict the extraction to a single inventory organization or warehouse. This is critical for performance and data relevance.
Page Size (Limit): The LIMIT variable in the script controls how many records are fetched per API call. A value between 100 and 500 is generally effective, balancing performance and API load.
API Version: The script assumes a specific REST API version (11.13.18.05). You may need to update the URL path if your Oracle Fusion environment uses a different version.

a Sample Query python

import requests
import json
import csv
from datetime import datetime

class=class="hl-string">"hl-comment"># --- Configuration Settings ---
class=class="hl-string">"hl-comment"># Replace with your Oracle Fusion SCM instance details
BASE_URL = class="hl-string">"https://[your-fusion-instance.oraclecloud.com]"
USERNAME = class="hl-string">"[your_api_user]"
PASSWORD = class="hl-string">"[your_api_password]"

class=class="hl-string">"hl-comment"># --- Extraction Parameters ---
class=class="hl-string">"hl-comment"># Define the date range for the extraction (YYYY-MM-DD)
START_DATE = class="hl-string">"2023-01-01"
END_DATE = class="hl-string">"2023-06-30"
class=class="hl-string">"hl-comment"># Specify the Inventory Organization ID to filter results
ORGANIZATION_ID = class="hl-string">"[your_organization_id]"
LIMIT = 500  class=class="hl-string">"hl-comment"># Number of records to fetch per API call
OUTPUT_FILE = class="hl-string">"oracle_fusion_inventory_log.csv"

class=class="hl-string">"hl-comment"># --- API Endpoint ---
API_ENDPOINT = fclass="hl-string">"{BASE_URL}/fscmRestApi/resources/11.13.18.05/inventoryTransactions"

def map_transaction_to_activity(transaction_type_name):
    class="hl-string">"""Maps Oracle Fusion transaction type names to standardized activity names."""
    mapping = {
        class=class="hl-string">"hl-comment"># Goods Receipt & Returns
        class="hl-string">"PO Receipt": class="hl-string">"Goods Receipt Recorded",
        class="hl-string">"RMA Receipt": class="hl-string">"Return Goods Processed",
        class=class="hl-string">"hl-comment"># Put-away & Internal Moves
        class="hl-string">"Subinventory Transfer": class="hl-string">"Stock Moved Internally",
        class="hl-string">"WMS Putaway": class="hl-string">"Put-away Completed", class=class="hl-string">"hl-comment"># Assuming WMS module is used
        class="hl-string">"Move Order Transfer": class="hl-string">"Stock Moved Internally",
        class=class="hl-string">"hl-comment"># Adjustments & Counts
        class="hl-string">"Cycle Count Adjustment": class="hl-string">"Inventory Discrepancy Adjusted",
        class="hl-string">"Physical Inventory Adjustment": class="hl-string">"Inventory Discrepancy Adjusted",
        class=class="hl-string">"hl-comment"># Note: Cycle Count Performed is often the same transaction as the adjustment.
        class=class="hl-string">"hl-comment"># We can create a dedicated activity for the adjustment itself.
        class=class="hl-string">"hl-comment"># Picking, Packing, Shipping (Goods Issue)
        class="hl-string">"Sales Order Pick": class="hl-string">"Picking Completed",
        class="hl-string">"Sales Order Issue": class="hl-string">"Goods Issue Recorded",
        class="hl-string">"Movement Request Issue": class="hl-string">"Goods Issue Recorded",
        class="hl-string">"WIP Component Issue": class="hl-string">"Goods Issue Recorded",
        class=class="hl-string">"hl-comment"># Disposals
        class="hl-string">"Miscellaneous Issue": class="hl-string">"Stock Scrapped/Disposed", class=class="hl-string">"hl-comment"># Often used for scrap with a reason code
        class="hl-string">"Account Alias Issue": class="hl-string">"Stock Scrapped/Disposed",
        class=class="hl-string">"hl-comment"># Status Changes (often handled outside material transactions, placeholder)
        class="hl-string">"Lot Status Update": class="hl-string">"Item Status Changed",
    }
    return mapping.get(transaction_type_name, None)

def fetch_inventory_transactions():
    class="hl-string">"""Fetches and processes all inventory transactions within the specified date range."""
    event_log = []
    offset = 0
    has_more = True

    class=class="hl-string">"hl-comment"># Use a session for persistent authentication
    session = requests.Session()
    session.auth = (USERNAME, PASSWORD)

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

    while has_more:
        params = {
            class="hl-string">'finder': class="hl-string">'TransactionDateFinder',
            class="hl-string">'q': fclass="hl-string">'OrganizationId={ORGANIZATION_ID};TransactionDate between \'{START_DATE}\class="hl-string">' and \'{END_DATE}\class="hl-string">'',
            class="hl-string">'onlyData': class="hl-string">'true',
            class="hl-string">'limit': LIMIT,
            class="hl-string">'offset': offset,
            class="hl-string">'fields': class="hl-string">'TransactionId,TransactionDate,TransactionTypeName,LotNumber,ItemNumber,CreatedBy,SubinventoryCode,LocatorId,TransactionReasonId,LastUpdateDate'
        }

        try:
            response = session.get(API_ENDPOINT, params=params)
            response.raise_for_status()  class=class="hl-string">"hl-comment"># Raises an exception for bad status codes (4xx or 5xx)
            data = response.json()
            items = data.get(class="hl-string">'items', [])

            if not items:
                print(class="hl-string">"No more items found. Ending extraction.")
                has_more = False
                continue

            print(fclass="hl-string">"Fetched {len(items)} records. Processing offset {offset}...")

            class=class="hl-string">"hl-comment"># Process each transaction from the API response
            for item in items:
                if not item.get(class="hl-string">'LotNumber'):
                    continue class=class="hl-string">"hl-comment"># Skip transactions without a lot number as it's the case ID
                
                activity_name = map_transaction_to_activity(item.get(class="hl-string">'TransactionTypeName'))
                
                class=class="hl-string">"hl-comment"># If the transaction type doesn't map to a relevant activity, skip it
                if not activity_name:
                    continue

                class=class="hl-string">"hl-comment"># Create the event log entry
                event = {
                    class="hl-string">'InventoryBatchLot': item.get(class="hl-string">'LotNumber'),
                    class="hl-string">'ActivityName': activity_name,
                    class="hl-string">'EventStartTime': item.get(class="hl-string">'TransactionDate'),
                    class="hl-string">'EventEndTime': item.get(class="hl-string">'TransactionDate'), class=class="hl-string">"hl-comment"># End time is often same as start for transactions
                    class="hl-string">'UserPerformingAction': item.get(class="hl-string">'CreatedBy'),
                    class="hl-string">'ItemNumber': item.get(class="hl-string">'ItemNumber'),
                    class="hl-string">'WarehouseLocation': item.get(class="hl-string">'SubinventoryCode'), class=class="hl-string">"hl-comment"># Using Subinventory as location
                    class="hl-string">'MovementReasonCode': item.get(class="hl-string">'TransactionReasonId'),
                    class="hl-string">'SourceSystem': class="hl-string">'Oracle Fusion SCM',
                    class="hl-string">'LastDataUpdate': datetime.now().isoformat()
                }
                event_log.append(event)

            class=class="hl-string">"hl-comment"># Check if there are more pages
            has_more = data.get(class="hl-string">'hasMore', False)
            offset += LIMIT

        except requests.exceptions.HTTPError as http_err:
            print(fclass="hl-string">"HTTP error occurred: {http_err} - {response.text}")
            break
        except Exception as err:
            print(fclass="hl-string">"An error occurred: {err}")
            break
    
    return event_log

def write_to_csv(data):
    class="hl-string">"""Writes the processed data to a CSV file."""
    if not data:
        print(class="hl-string">"No data to write to CSV.")
        return

    print(fclass="hl-string">"Writing {len(data)} records to {OUTPUT_FILE}...")
    
    class=class="hl-string">"hl-comment"># Define the headers based on the keys of the first dictionary
    headers = [
        class="hl-string">'InventoryBatchLot', class="hl-string">'ActivityName', class="hl-string">'EventStartTime', class="hl-string">'EventEndTime',
        class="hl-string">'UserPerformingAction', class="hl-string">'ItemNumber', class="hl-string">'WarehouseLocation',
        class="hl-string">'MovementReasonCode', class="hl-string">'SourceSystem', class="hl-string">'LastDataUpdate'
    ]

    with open(OUTPUT_FILE, class="hl-string">'w', newline=class="hl-string">'', encoding=class="hl-string">'utf-8') as csvfile:
        writer = csv.DictWriter(csvfile, fieldnames=headers)
        writer.writeheader()
        writer.writerows(data)
    
    print(class="hl-string">"CSV file has been created successfully.")

if __name__ == class="hl-string">"__main__":
    all_transactions = fetch_inventory_transactions()
    write_to_csv(all_transactions)

Your Inventory Management Data Template

Your Inventory Management Data Template

Inventory Management Attributes

Inventory Management Activities

Extraction Guides

Oracle BI Publisher for Inventory Management Extraction

Steps

Configuration

a Sample Query sql

Oracle BI Cloud Connector (BICC) Bulk Data Export

Steps

Configuration

a Sample Query config

Python Script Extraction via Oracle Fusion SCM REST APIs

Steps

Configuration

a Sample Query python

Ready to Get Started?

Transform Inventory Management: Start Optimizing Today

Your Inventory Management Data Template

Your Inventory Management Data Template

Inventory Management Attributes

Inventory Management Activities

Extraction Guides

Oracle BI Publisher for Inventory Management Extraction

Steps

Configuration

a Sample Query sql

Oracle BI Cloud Connector (BICC) Bulk Data Export

Steps

Configuration

a Sample Query config

Python Script Extraction via Oracle Fusion SCM REST APIs

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Transform Inventory Management: Start Optimizing Today