> Continuous Process Improvement > Supply Chain Management > Oracle SCM Cloud > Data Template

Your Supply Chain Management Data Template

Oracle SCM Cloud

Supply Chain Management Attributes (22) Supply Chain Management Activities (14) Extraction Guides (3)

Your Supply Chain Management Data Template

This template provides a structured overview of the essential data points required for effective process mining in supply chain management. It outlines the crucial attributes to collect and the key activities to track within your event log. Additionally, it offers guidance to help you extract this vital information seamlessly.

Recommended attributes to collect
Key activities to track
Extraction guidance

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

Download Template

Supply Chain Management Attributes

These are the recommended data fields to include in your event log for comprehensive supply chain management analysis and optimization.

3 Required 9 Recommended 10 Optional

	Name	Description
	Activity Name ActivityName	The name of the specific business event or task that occurred within the logistics process, such as 'Purchase Order Issued' or 'Shipment Confirmed'.
Description This attribute describes a single step or milestone in the logistics lifecycle. Each activity represents a specific action performed, like checking inventory, producing goods, or signing a proof of delivery. The sequence of these activities forms the process flow for each logistics order. Analyzing the Activity Name is fundamental to process mining. It allows for the visualization of the process map, calculation of transition times between steps, identification of rework loops, and discovery of common or deviant process paths (variants). Why it matters It defines the steps of the process. Analyzing the sequence and frequency of activities is the core of process mining. Where to get Activity names are derived from event data captured in various Oracle SCM Cloud modules. This often requires mapping transaction statuses or event logs to a standardized list of activity names. Examples Purchase Order IssuedGoods ProducedShipment ConfirmedProof of Delivery Signed
	Event Time EventTime	The precise date and time when a specific activity occurred.
Description The Event Time is the timestamp associated with each activity in the process. It provides the chronological context necessary to order events and understand the process flow over time. This data is critical for any time-based analysis. In process mining, this attribute is used to calculate all duration-based metrics, such as cycle times, processing times, and waiting times. It is the foundation for creating the event log, identifying bottlenecks by measuring the duration between activities, and assessing performance against time-based targets or SLAs. Why it matters This timestamp is essential for ordering events chronologically and calculating all performance metrics related to time, such as cycle time and bottlenecks. Where to get Timestamp fields are typically available in transaction tables across Oracle SCM Cloud modules, such as CREATION_DATE or LAST_UPDATE_DATE fields. Examples 2023-10-26T10:00:00Z2023-10-26T14:30:15Z2023-10-27T08:05:00Z
	Logistics Order LogisticsOrder	The unique identifier for a single logistics order, serving as the case ID for tracking the end-to-end supply chain process.
Description The Logistics Order is the primary case identifier that connects all activities related to a specific demand or fulfillment request within the supply chain. This ID allows for a complete view of a product's journey, from initial customer order or demand forecast through procurement, production, and final delivery. In process mining analysis, this attribute is crucial for grouping all related events into a single case. It enables the reconstruction of the process flow for each order, making it possible to analyze cycle times, identify bottlenecks, discover process variants, and assess overall performance from a holistic, order-centric view. Why it matters This is the essential key for linking all process steps together. Without a consistent Logistics Order ID, it is impossible to trace the complete journey of an order. Where to get This identifier is typically found across multiple modules in Oracle SCM Cloud, including Order Management, Inventory Management, and Shipping. Examples LO-2024-00123LO-2024-00124LO-2024-00125
	Actual Delivery Date ActualDeliveryDate	The date when the order was actually delivered to the customer, confirmed by a proof of delivery.
Description This date marks the final completion of the logistics process when the goods have reached their destination. It is often captured from the 'Proof of Delivery Signed' activity. This attribute is essential for performance measurement. It is directly compared with the 'Requested Delivery Date' to determine if an order was on-time or late. It is also used to calculate the final end-to-end cycle time of the logistics order. Why it matters It provides the actual completion time of the process, enabling the calculation of on-time delivery rates and total cycle times. Where to get This is often the timestamp of the final delivery confirmation event, found in shipping or transportation modules like WSH_DELIVERIES. Examples 2023-11-162023-11-302024-01-12
	Item Number ItemNumber	The unique identifier, or SKU, for the specific product being processed.
Description The Item Number provides the most granular level of product identification. It allows for analysis of individual products, which is more detailed than analyzing by product category. Using the Item Number in analysis helps identify process issues tied to specific products. For example, a particular item may have a high rate of quality control failures or be associated with longer production times. This enables targeted problem-solving at the SKU level. Why it matters Enables highly detailed analysis at the individual product level, helping to pinpoint issues that may not be visible at a category level. Where to get Item identifiers are present in most transactional tables in Oracle SCM, such as DOO_FULFILL_LINES_ALL or INV_MATERIAL_TXNS, typically as INVENTORY_ITEM_ID. Examples SKU-100-ASKU-250-BPART-XYZ-01
	Logistics Order Status LogisticsOrderStatus	The final status of the logistics order, indicating whether it was successfully completed, canceled, or partially fulfilled.
Description This attribute provides the terminal state or outcome of a logistics order case. It helps differentiate between orders that proceeded through the entire process as planned versus those that were terminated prematurely. In process analysis, filtering by status is crucial. For example, cycle time analysis should typically only include 'Completed' orders to avoid skewed results from canceled ones. It also allows for root cause analysis on why orders are being canceled. Why it matters Indicates the outcome of a case, allowing for filtering of incomplete or canceled orders to ensure analysis is performed on comparable data. Where to get The final status is often derived from the status of the sales order or fulfillment line in Oracle Order Management, found in tables like DOO_HEADERS_ALL or DOO_FULFILL_LINES_ALL. Examples DeliveredCanceledPartially ShippedClosed
	Mode Of Transport ModeOfTransport	The method of transportation used for shipment, such as Air, Sea, Truck, or Rail.
Description This attribute specifies the transportation mode used to move goods between locations, for example, from the warehouse to the customer. This information is critical for logistics and transportation analysis. In process mining, filtering or segmenting by Mode of Transport helps in analyzing the efficiency of different shipping methods. The Transportation Efficiency Analysis dashboard uses this to compare the duration of transit for different modes, helping to optimize logistics costs and delivery times. Why it matters Allows for analysis of transportation efficiency and cost, helping to optimize logistics strategy based on speed and expense. Where to get This data is typically found in the Oracle Transportation Management (OTM) module or the shipping execution modules. Look for fields in tables like WSH_DELIVERY_LEGS. Examples Air FreightOcean FreightFull TruckloadLess Than Truckload
	Product Category ProductCategory	The category or family to which the product in the order belongs.
Description Product Category is a classification attribute that groups similar products together, such as 'Electronics', 'Apparel', or 'Raw Materials'. This allows for higher-level analysis than looking at individual product SKUs. In process mining, segmenting the analysis by Product Category is very powerful. It can reveal if certain types of products have longer cycle times, follow different process variants, or are more prone to delays. This helps in tailoring process improvements to specific product lines. Why it matters Allows for performance analysis to be segmented by product type, revealing patterns and issues specific to certain product families. Where to get This information is part of the item master data in Oracle SCM Cloud, accessible via tables like EGP_SYSTEM_ITEMS_B and related category tables. Examples Finished GoodsSpare PartsRaw MaterialsConsumer Electronics
	Purchase Order Number PurchaseOrderNumber	The unique identifier for a purchase order created to procure raw materials or components.
Description The Purchase Order Number is a key document ID in the procurement part of the supply chain. It links the logistics order to specific requests made to suppliers. This attribute allows for a detailed drill-down into procurement activities. It can be used to trace all events related to a specific PO and is essential for analyzing supplier performance and procurement cycle times. Why it matters Provides a direct link to procurement documents, enabling detailed analysis of the purchasing sub-process and its impact on the overall logistics flow. Where to get This ID is found in the Oracle Procurement Cloud module, primarily in the PO_HEADERS_ALL table as SEGMENT1. Examples PO-98345PO-98346PO-98347
	Requested Delivery Date RequestedDeliveryDate	The delivery date for the order as requested by the customer.
Description This date represents the customer's desired delivery timeline and serves as the primary benchmark for measuring on-time delivery performance. It is typically set when the customer order is created and is a critical component of service level agreements (SLAs). In analysis, this attribute is compared against the 'Actual Delivery Date' to calculate the On-Time Delivery Rate KPI. It helps businesses understand their ability to meet customer expectations and identify the root causes of delays. Why it matters This is the baseline for measuring on-time delivery performance, a critical KPI for customer satisfaction and supply chain efficiency. Where to get This is typically stored at the sales order or fulfillment line level in Oracle Order Management. Look for fields like REQUEST_SHIP_DATE or REQUEST_ARRIVAL_DATE. Examples 2023-11-152023-12-012024-01-10
	Supplier Name SupplierName	The name of the supplier or vendor providing the raw materials for a purchase order.
Description This attribute identifies the external party responsible for supplying components or raw materials needed for production. It is associated with procurement-related activities like 'Purchase Order Issued' and 'Raw Materials Received'. Analyzing by Supplier Name is critical for the Supplier Lead Time Performance dashboard. It helps evaluate which suppliers are reliable and deliver on time, and which are frequently late. This insight is crucial for procurement strategy, supplier relationship management, and mitigating production delays caused by material shortages. Why it matters Enables performance measurement and benchmarking of suppliers, which is key to ensuring a reliable and efficient inbound supply chain. Where to get Supplier information is located in the procurement modules of Oracle SCM Cloud, linked to purchase orders. Key tables include PO_HEADERS_ALL and POZ_SUPPLIERS. Examples Global Components Inc.Advanced Materials LLCTech Parts Direct
	User User	The user ID or name of the person who performed a specific activity.
Description This attribute identifies the employee or system user responsible for executing a task in the process. It can be used to understand workload distribution and individual performance. Analyzing by User helps in resource management and performance analysis. It can identify high-performing individuals or teams, highlight potential training needs, or reveal automation opportunities for tasks that are consistently slow when performed manually. Why it matters Enables analysis of resource performance, workload distribution, and helps identify opportunities for training or automation. Where to get User information is typically stored in 'Created By' or 'Last Updated By' columns in most Oracle SCM transaction tables. Examples JSMITHALOGANSYSTEMBATCH_USER
	Carrier Name CarrierName	The name of the third-party logistics company or carrier responsible for transporting the goods.
Description The Carrier Name identifies the specific transportation provider used for a shipment. This is a key piece of information for evaluating the performance of logistics partners. This attribute is used in the Transportation Efficiency Analysis dashboard to compare the performance of different carriers. It helps answer questions like which carriers have the shortest transit times, which are most reliable for specific routes, and which offer the best value. Why it matters Allows for performance benchmarking of transportation partners, which is crucial for optimizing shipping costs and reliability. Where to get This information is stored in Oracle Transportation Management or Shipping modules. It is typically linked to a specific trip or delivery leg in tables like WSH_TRIPS. Examples FedExDHLUPSMaersk
	Customer Name CustomerName	The name of the customer who placed the order.
Description This attribute identifies the recipient of the goods and services. It is a fundamental dimension for any customer-centric analysis. Segmenting process analysis by customer can reveal important patterns. For instance, certain high-value customers may experience more delays, or different customer segments might follow different process paths. This information is vital for improving customer service and managing key accounts effectively. Why it matters Allows for a customer-centric view of the process, helping to understand if certain customers or customer types face unique process challenges. Where to get Customer information is stored in the order management modules, linked to the sales order. It can be found in tables related to DOO_HEADERS_ALL by joining with customer account tables (HZ_CUST_ACCOUNTS). Examples Retail CorpManufacturing SolutionsMegaStore Inc.
	End To End Cycle Time EndToEndCycleTime	The total time elapsed from the creation of the customer order to the final proof of delivery.
Description This calculated metric measures the total duration of the entire logistics process for a single order. It is computed as the difference between the timestamp of the very first activity (e.g., 'Customer Order Created') and the very last activity (e.g., 'Proof of Delivery Signed'). This is one of the most important KPIs for understanding overall process efficiency. It provides a high-level measure of performance and is used in dashboards to track trends over time and identify long-running orders that may require investigation. Why it matters Provides a holistic measure of process performance from start to finish, helping to identify long-running cases and track overall efficiency improvements. Where to get This is calculated in the process mining tool or during data preparation by subtracting the start time of the first event from the start time of the last event for each case. Examples 15 days 4 hours22 days 8 hours10 days 2 hours
	Is On Time Delivery IsOnTimeDelivery	A boolean flag that indicates whether the order was delivered on or before the requested delivery date.
Description This is a calculated attribute that simplifies performance analysis. It is derived by comparing the 'Actual Delivery Date' to the 'Requested Delivery Date'. If the actual date is on or before the requested date, the value is true, otherwise it is false. This flag makes it easy to create KPIs and dashboards, like the Customer Delivery Performance dashboard. It allows for quick filtering and aggregation to calculate the overall On-Time Delivery Rate and enables root cause analysis to find the common characteristics of late orders. Why it matters Directly measures performance against customer expectations and simplifies the creation of key performance indicators related to delivery timeliness. Where to get This attribute is not in the source system. It is calculated during the data transformation process by comparing 'ActualDeliveryDate' <= 'RequestedDeliveryDate'. Examples truefalse
	Is Rework IsRework	A boolean flag indicating if a logistics order has undergone rework, such as a repeated activity or a loop in the process.
Description This calculated attribute identifies cases that deviate from a linear, efficient flow. It is typically determined by detecting sequences where an activity is repeated or a later activity is followed by an earlier one, indicating a process loop (e.g., 'Goods Picked' -> 'Quality Control Failed' -> 'Goods Picked'). This flag is crucial for quantifying process inefficiency. It helps calculate the Order Rework Rate KPI and allows analysts to filter for and investigate cases with rework to understand the root causes, such as data entry errors, quality issues, or incorrect initial processing. Why it matters Helps quantify and isolate process inefficiencies, such as loops and repeated steps, which are often sources of delays and increased costs. Where to get This is not available in the source system. It is calculated by the process mining tool by analyzing the sequence of activities for each case to detect patterns indicative of rework. Examples truefalse
	Last Data Update LastDataUpdate	The timestamp indicating when the data for this event was last refreshed or extracted from the source system.
Description This attribute marks the most recent time the event data was updated in the process mining dataset. It is essential for understanding the freshness of the data and the time period covered by the analysis. It is used for data governance and to inform users about the recency of the insights presented in dashboards. It helps answer questions like 'How up-to-date is this process view?'. Why it matters Provides crucial context about the timeliness of the data, ensuring users understand the period of analysis. Where to get This timestamp is generated and added during the data extraction, transformation, and loading (ETL) process. Examples 2024-01-15T02:00:00Z2024-01-16T02:00:00Z
	Order Value OrderValue	The total monetary value of the logistics order.
Description This attribute represents the financial value associated with a single logistics order. It is a critical business metric for prioritizing analysis and understanding the financial impact of process inefficiencies. In process mining, Order Value can be used to correlate process performance with financial outcomes. For example, analysis might show that high-value orders experience longer delays, representing a significant risk to revenue. It also allows for prioritizing improvements on processes that handle the most value. Why it matters Provides financial context to process performance, helping to prioritize improvements based on monetary impact. Where to get Order value is typically stored at the sales order header level in Oracle Order Management. Consult tables like DOO_HEADERS_ALL for total amount fields. Examples 5250.7512300.00950.20
	Source System SourceSystem	Identifies the information system from which the data was extracted.
Description This attribute specifies the origin of the event data, which in this case is Oracle SCM Cloud. It is useful in environments where data from multiple systems is combined, providing clarity on data provenance. In analysis, it helps differentiate processes or activities that might span multiple systems. For a single-system view like this one, it serves as a standard data governance attribute. Why it matters Ensures data provenance and helps distinguish data origins in multi-system environments. Where to get This is typically a static value ('Oracle SCM Cloud') added during the data extraction and transformation process. Examples Oracle SCM CloudOracle Fusion SCM
	Transportation Duration TransportationDuration	The time taken for goods to travel from the point of loading to the destination.
Description This is a calculated metric that measures the 'in-transit' portion of the overall cycle time. It is calculated as the time difference between the 'Goods Loaded for Transport' activity and the 'Goods Unloaded at Destination' activity. This attribute is used to power the Transportation Efficiency Analysis dashboard. It helps isolate delays that occur specifically during the transportation phase, and can be analyzed by carrier and mode of transport to optimize shipping performance. Why it matters Isolates the in-transit time, allowing for focused analysis on transportation efficiency independent of warehouse or production delays. Where to get This metric is calculated during data transformation by finding the time difference between the timestamps of the 'Goods Loaded for Transport' and 'Goods Unloaded at Destination' events for a case. Examples 2 days 3 hours5 days 1 hour12 hours
	Warehouse Location WarehouseLocation	The warehouse or distribution center from which the goods are picked and shipped.
Description This attribute specifies the physical location or facility involved in a particular logistics activity. It is essential for location-based performance analysis. Analyzing by Warehouse Location can reveal significant performance differences between facilities. For example, one warehouse might have a much shorter pick-and-pack cycle time than another. These insights help identify best practices that can be shared across locations or highlight facilities that require process improvements. Why it matters Enables performance comparison across different physical locations, helping to identify high-performing facilities and areas for improvement. Where to get Warehouse or inventory organization information is a fundamental data element in Oracle Inventory Management. It is often found as ORGANIZATION_ID in tables like INV_MATERIAL_TXNS. Examples WH-NORTHWH-WESTDC-CENTRAL

Required Recommended Optional

Supply Chain Management Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery and performance evaluation.

6 Recommended 8 Optional

	Activity	Description
	Customer Order Created	This activity marks the creation of a sales order in Oracle Order Management, representing a customer's formal request for goods. This event is captured explicitly when a new sales order record is saved in the system, initiating the logistics order lifecycle.
Why it matters As the primary start event, it allows for the measurement of the end-to-end logistics cycle time. It is the baseline for analyzing order processing efficiency and customer demand patterns. Where to get Captured from the creation timestamp of the sales order record in the Order Management module, typically from the DOO_HEADERS_ALL table. Capture Use the creation date of the sales order header. Event type explicit
	Goods Loaded for Transport	The packed goods are loaded onto the carrier's vehicle, and the shipment officially departs from the warehouse. This is recorded by the 'Ship Confirm' transaction in Oracle Shipping.
Why it matters This event marks the beginning of the transportation leg of the journey. It is the start point for the 'Transportation Cycle Time' KPI and 'Transportation Efficiency Analysis' dashboard. Where to get An explicit event captured by the 'Ship Confirm' transaction in Oracle Shipping. This updates the status of the delivery details to 'Shipped'. Capture Use the transaction timestamp of the Ship Confirm action. Event type explicit
	Goods Picked and Packed	Warehouse personnel pick the items for an order from inventory and pack them for shipment. This process involves several system transactions, culminating in a packed status.
Why it matters This marks the start of the physical shipping process. The time from order creation to this point, covered by the 'Inventory Check-to-Fulfillment Time' KPI, measures internal fulfillment efficiency. Where to get Inferred from the status of shipment lines or delivery details in Oracle Shipping. This is often an aggregation of multiple events like pick wave creation, pick confirmation, and pack confirmation. Capture Use the timestamp of the final pick confirm or pack confirm transaction associated with the sales order line. Event type inferred
	Goods Produced	The manufacturing process for the goods is completed, and the finished product is moved into inventory. This is captured when the work order is reported as complete in the system.
Why it matters Marks the end of the production phase and the availability of the product for fulfillment. The duration from 'Production Scheduled' to this event is a critical measure of manufacturing efficiency. Where to get Captured from the completion transaction of a work order in Oracle Manufacturing Cloud. This updates the work order status to 'Complete'. Capture Use the timestamp of the work order completion transaction or the status change to 'Complete'. Event type inferred
	Production Scheduled	For items that are manufactured, a work order is scheduled, defining the production timeline and resource allocation. This event is captured when the work order status is updated to 'Scheduled' or 'Released'.
Why it matters This activity is a key milestone for the 'Production & Shipment Stage Delays' dashboard. It marks the start of the production cycle, and any delays here cascade through the entire fulfillment process. Where to get Inferred from the status change of a work order in Oracle Manufacturing Cloud. Relevant data is stored in tables like WIP_DISCRETE_JOBS. Capture Use the timestamp when the work order status changes to 'Released' or a similar state indicating production can begin. Event type inferred
	Proof of Delivery Signed	The customer provides a signed confirmation of receipt for the goods, formally closing the delivery process. This is often recorded by updating the order or shipment with a proof of delivery date and document.
Why it matters This is the definitive end event for a successful logistics order, crucial for the 'End-to-End Logistics Cycle Time' KPI. It also supports compliance and dispute resolution processes. Where to get Often a manual or semi-automated update to the shipment or sales order record. The system may have a specific field for the POD date which can be used as the event timestamp. Capture Use the timestamp from a 'Proof of Delivery Date' field on the shipment or order record. Event type explicit
	Goods Unloaded at Destination	The shipment arrives at the customer's location or destination port and is unloaded. This information is often updated based on data from the transportation carrier or a transport management system.
Why it matters This activity marks the end of the in-transit period. The duration from 'Goods Loaded for Transport' is crucial for analyzing carrier performance and transportation efficiency. Where to get This may be an explicit event if a Transportation Management System is integrated, or it might be inferred. It could be based on carrier status updates or manual entry upon delivery confirmation. Capture Use the timestamp from an integrated TMS or a manually updated 'Delivered' status on the shipment record. Event type explicit
	Inventory Availability Checked	The system checks if the requested items are available in stock to fulfill the customer order. This is often an automated step within the order processing workflow, but its outcome is logged as a status or a timestamp.
Why it matters This activity is critical for the 'Inventory Fulfillment Efficiency' dashboard and the 'Inventory Availability Impact Rate' KPI. Delays here indicate potential stockout issues or inefficient inventory management. Where to get Inferred from status changes on the sales order line or from records in Oracle Inventory Management (INV) tables related to reservations or available-to-promise checks. Capture Inferred from a sales order line status change, such as 'Awaiting Fulfillment' or a reservation creation timestamp. Event type inferred
	Order Canceled	The customer order is canceled before fulfillment is completed. This is captured when the status of the sales order header or line is changed to 'Canceled'.
Why it matters This represents an alternative, unsuccessful endpoint for the process. Analyzing canceled orders helps identify reasons for sales falling through, such as long lead times or stockouts. Where to get Inferred from a status change on the sales order record in Oracle Order Management to a terminal 'Canceled' status. Capture Use the timestamp of the status change to 'Canceled' on the sales order header or line. Event type inferred
	Purchase Order Issued	The purchase requisition is converted into a legally binding purchase order and sent to the supplier. This event is explicitly captured when the PO is approved and its status is updated to 'Open' or 'Sent'.
Why it matters This marks the official start of the supplier lead time. It is essential for measuring the 'Supplier Lead Time Performance' dashboard and the 'Supplier On-Time Delivery Rate' KPI. Where to get Captured from the approval or submission date of the purchase order in Oracle Procurement Cloud, stored in tables such as PO_HEADERS_ALL. Capture Use the timestamp when the purchase order status changes to an approved or open state. Event type explicit
	Purchase Requisition Created	A formal request is created to procure materials from a supplier, typically triggered when inventory is insufficient to fulfill a sales order. This is an explicit transaction within the Oracle Procurement module.
Why it matters This activity highlights dependencies on procurement and external suppliers. Analyzing the time from this event to material receipt is key for understanding supplier-related delays. Where to get Recorded from the creation timestamp of a purchase requisition in Oracle Procurement Cloud, found in tables like POR_REQUISITION_HEADERS_ALL. Capture Use the creation date of the purchase requisition record. Event type explicit
	Quality Control Performed	Finished goods undergo a quality inspection before being made available for shipping. This is recorded as a quality inspection result in the Oracle Quality Management module.
Why it matters This is a critical step for compliance and customer satisfaction. Analyzing this activity helps ensure adherence to quality standards and identifies bottlenecks in the inspection process, supporting compliance audits. Where to get Captured from transaction records in Oracle Quality Management Cloud when an inspection plan is executed and results are entered. Capture Use the timestamp when the quality inspection result is recorded as 'Pass' or 'Fail'. Event type explicit
	Raw Materials Received	The ordered raw materials or goods arrive from the supplier and are formally received into inventory. This is recorded as a receipt transaction in Oracle Inventory Management.
Why it matters This event concludes the supplier lead time measurement. Delays at this stage directly impact production schedules and final customer delivery dates. Where to get Captured from the transaction date of the receipt in Oracle Inventory Management, typically from the RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS tables. Capture Use the transaction date of the material receipt record. Event type explicit
	Shipment Confirmed	All items for a shipment are staged, packed, and ready for handover to the carrier. This activity updates the shipment status to 'Confirmed' or 'Ready to Ship' in the system.
Why it matters This is a critical milestone before the goods physically leave the warehouse. It separates internal warehouse processing time from external transportation time. Where to get Inferred from a status change on the shipment or delivery record in Oracle Shipping, found in tables like WSH_DELIVERIES or WSH_NEW_DELIVERIES. Capture Use the timestamp when the shipment status is updated to 'Confirmed'. Event type inferred

Recommended Optional

Extraction Guides

How to get your data from Oracle SCM Cloud

Steps

Access Oracle BI Publisher: Log in to your Oracle SCM Cloud instance. Navigate to the Reports and Analytics work area by clicking the Navigator icon, then selecting Tools > Reports and Analytics.
Create a Data Model: In the Reports and Analytics work area, click 'Browse Catalog'. In the catalog, click 'New' and select 'Data Model'.
Define the SQL Query Dataset: In the Data Model editor, click the '+' icon to add a new data set and select 'SQL Query'.
Enter Query Details: Give the data set a name, for example, 'SCM_LOGISTICS_EVENT_LOG'. Select the appropriate Data Source, which is typically 'ApplicationDB_SCM' or a similar application database connection. Copy the complete SQL query provided in the 'query' section below and paste it into the SQL Query text area.
Define Parameters: The query uses parameters :P_START_DATE and :P_END_DATE to filter the date range. Oracle BI Publisher will automatically detect these. You can set their data type to 'Date' and configure default values if needed.
View and Save Sample Data: Go to the 'Data' tab. You can enter values for the parameters and click 'View' to see a sample of the extracted data. This helps verify the query is working correctly. Once satisfied, click 'Save' and give your data model a descriptive name, such as 'SCM Logistics Process Data Model'.
Create a BI Publisher Report: Click the 'Create Report' button directly from the data model editor. The report creation wizard will launch.
Configure the Report Layout: Select the 'Use Data Model' option. The wizard will guide you through layout creation. For a simple CSV export, you can select the 'Table' layout. Drag and drop all columns from the data set into the table layout.
Save the Report: After configuring the layout, save the report in a suitable catalog folder. Name it something like 'SCM Logistics Event Log Report'.
Schedule the Report Job: To automate the extraction, schedule the report. Open the saved report and click 'Actions' > 'Schedule'.
Configure Schedule and Output: In the 'General' tab, set the schedule trigger (e.g., daily, weekly). In the 'Output' tab, select CSV as the output format. Configure the destination, such as sending it to a specific content server location, FTP server, or object storage from where it can be retrieved for process mining analysis.
Submit and Monitor: Submit the scheduled job. You can monitor its execution from the 'Job History' page to ensure it runs successfully and delivers the CSV file to the configured destination.

Configuration

Prerequisites: Access to Oracle Fusion Applications with a user role that has permissions to create data models and BI Publisher reports, such as 'BI Administrator' or 'Application Developer'.
Data Source: The SQL query should be run against the main application database, typically named 'ApplicationDB_SCM' or similar in the BI Publisher data source list.
Date Range Parameters: It is critical to use date range filters (:P_START_DATE, :P_END_DATE) to limit the data volume. Extracting 3 to 6 months of data is a good starting point for analysis. Avoid running the query for very large date ranges (e.g., multiple years) in a single execution to prevent performance degradation or timeouts.
Filtering: Consider adding filters to the main sales_orders clause in the query to narrow the scope. You can add WHERE conditions for specific Business Units (BU_NAME), Order Types (ORDER_TYPE_CODE), or Item Categories to focus the analysis on a particular part of the supply chain.
Performance: The provided query uses standard Oracle SCM Cloud views (DOO_HEADERS_ALL, PO_HEADERS_ALL, etc.), which are generally optimized for reporting. However, for extremely large datasets, performance can be a concern. Ensure the database has up-to-date statistics for the underlying tables.
Output Format: Configure the BI Publisher report to generate the output in CSV (Comma-Separated Values) format. Ensure the CSV properties are set correctly, such as using a comma delimiter, UTF-8 encoding, and including a header row.

a Sample Query sql

WITH sales_orders AS (
  SELECT
    dha.order_number,
    dha.header_id,
    dha.source_doc_id,
    dha.creation_date
  FROM
    doo_headers_all dha
  WHERE
    dha.creation_date BETWEEN TO_DATE(:P_START_DATE, 'YYYY-MM-DD') AND TO_DATE(:P_END_DATE, 'YYYY-MM-DD')
    -- Optional: Add filters for specific Business Units or Order Types
    -- AND dha.org_id = [Your Organization ID]
)
-- 1. Customer Order Created
SELECT
  so.order_number AS "LogisticsOrder",
  'Customer Order Created' AS "ActivityName",
  dha.creation_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  mc.category_name AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  dha.status_code AS "LogisticsOrderStatus",
  dha.created_by AS "User",
  NULL AS "PurchaseOrderNumber",
  msi.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN doo_fulfill_lines_all dfla ON dha.header_id = dfla.header_id
  LEFT JOIN egp_system_items_b msi ON dfla.inventory_item_id = msi.inventory_item_id AND dfla.inventory_organization_id = msi.organization_id
  LEFT JOIN egp_item_cat_assign_b mca ON msi.inventory_item_id = mca.inventory_item_id
  LEFT JOIN egp_categories_tl mc ON mca.category_id = mc.category_id
WHERE mc.language = 'US'

UNION ALL

-- 2. Inventory Availability Checked
SELECT
  so.order_number AS "LogisticsOrder",
  'Inventory Availability Checked' AS "ActivityName",
  dfla.last_update_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  dha.status_code AS "LogisticsOrderStatus",
  dfla.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  msi.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN doo_fulfill_lines_all dfla ON so.header_id = dfla.header_id
  LEFT JOIN egp_system_items_b msi ON dfla.inventory_item_id = msi.inventory_item_id AND dfla.inventory_organization_id = msi.organization_id
WHERE
  dfla.status_code = 'AWAIT_SHIP'

UNION ALL

-- 3. Purchase Requisition Created
SELECT
  so.order_number AS "LogisticsOrder",
  'Purchase Requisition Created' AS "ActivityName",
  prh.creation_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  prh.document_status AS "LogisticsOrderStatus",
  prh.created_by AS "User",
  NULL AS "PurchaseOrderNumber",
  prl.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN por_requisition_lines_all prl ON so.source_doc_id = prl.doo_source_doc_id
  JOIN por_requisition_headers_all prh ON prl.requisition_header_id = prh.requisition_header_id

UNION ALL

-- 4. Purchase Order Issued
SELECT
  so.order_number AS "LogisticsOrder",
  'Purchase Order Issued' AS "ActivityName",
  pha.approved_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  pv.vendor_name AS "SupplierName",
  NULL AS "ModeOfTransport",
  pha.document_status AS "LogisticsOrderStatus",
  pha.created_by AS "User",
  pha.segment1 AS "PurchaseOrderNumber",
  pla.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN por_requisition_lines_all prl ON so.source_doc_id = prl.doo_source_doc_id
  JOIN po_distributions_all pda ON prl.requisition_line_id = pda.requisition_line_id
  JOIN po_lines_all pla ON pda.po_line_id = pla.po_line_id
  JOIN po_headers_all pha ON pla.po_header_id = pha.po_header_id
  JOIN poz_suppliers_v pv ON pha.vendor_id = pv.vendor_id
WHERE
  pha.approved_date IS NOT NULL

UNION ALL

-- 5. Raw Materials Received
SELECT
  so.order_number AS "LogisticsOrder",
  'Raw Materials Received' AS "ActivityName",
  rt.transaction_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  pv.vendor_name AS "SupplierName",
  NULL AS "ModeOfTransport",
  pha.document_status AS "LogisticsOrderStatus",
  rt.created_by AS "User",
  pha.segment1 AS "PurchaseOrderNumber",
  pla.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_fulfill_lines_all dfla ON so.header_id = dfla.header_id
  JOIN po_distributions_all pda ON dfla.fulfill_line_id = pda.fulfill_line_id
  JOIN po_lines_all pla ON pda.po_line_id = pla.po_line_id
  JOIN po_headers_all pha ON pla.po_header_id = pha.po_header_id
  JOIN poz_suppliers_v pv ON pha.vendor_id = pv.vendor_id
  JOIN rcv_transactions rt ON pha.po_header_id = rt.po_header_id AND rt.transaction_type = 'RECEIVE'

UNION ALL

-- 6. Production Scheduled
SELECT
  so.order_number AS "LogisticsOrder",
  'Production Scheduled' AS "ActivityName",
  wdj.scheduled_start_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  wdj.status_type_disp AS "LogisticsOrderStatus",
  wdj.created_by AS "User",
  NULL AS "PurchaseOrderNumber",
  msi.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN wip_discrete_jobs wdj ON so.source_doc_id = wdj.source_header_id
  JOIN egp_system_items_b msi ON wdj.primary_item_id = msi.inventory_item_id AND wdj.organization_id = msi.organization_id
WHERE
  wdj.status_type IN (3, 4) -- Released, Complete

UNION ALL

-- 7. Goods Produced
SELECT
  so.order_number AS "LogisticsOrder",
  'Goods Produced' AS "ActivityName",
  wdj.completed_quantity_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  wdj.status_type_disp AS "LogisticsOrderStatus",
  wdj.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  msi.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN wip_discrete_jobs wdj ON so.source_doc_id = wdj.source_header_id
  JOIN egp_system_items_b msi ON wdj.primary_item_id = msi.inventory_item_id AND wdj.organization_id = msi.organization_id
WHERE
  wdj.status_type = 4 -- Complete
  AND wdj.completed_quantity_date IS NOT NULL

UNION ALL

-- 8. Quality Control Performed
SELECT
  so.order_number AS "LogisticsOrder",
  'Quality Control Performed' AS "ActivityName",
  qir.creation_date AS "EventTime",
  NULL AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  qi.validation_result_code AS "LogisticsOrderStatus",
  qir.created_by AS "User",
  NULL AS "PurchaseOrderNumber",
  msi.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN wip_discrete_jobs wdj ON so.source_doc_id = wdj.source_header_id
  JOIN egp_system_items_b msi ON wdj.primary_item_id = msi.inventory_item_id AND wdj.organization_id = msi.organization_id
  JOIN qa_inspection_results_v qir ON wdj.work_order_id = qir.work_order_id
  JOIN qa_inspections_b qi ON qir.inspection_id = qi.inspection_id

UNION ALL

-- 9. Goods Picked and Packed
SELECT
  so.order_number AS "LogisticsOrder",
  'Goods Picked and Packed' AS "ActivityName",
  wdd.last_update_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  wnd.shipping_method_code AS "ModeOfTransport",
  wdd.released_status_name AS "LogisticsOrderStatus",
  wdd.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  wdd.item_number AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN wsh_delivery_details wdd ON dha.header_id = wdd.source_header_id
  JOIN wsh_delivery_assignments wda ON wdd.delivery_detail_id = wda.delivery_detail_id
  JOIN wsh_new_deliveries wnd ON wda.delivery_id = wnd.delivery_id
WHERE
  wdd.released_status = 'Y' -- 'Ready to Release', can be adjusted to 'S' for 'Released to Warehouse'

UNION ALL

-- 10. Shipment Confirmed
SELECT
  so.order_number AS "LogisticsOrder",
  'Shipment Confirmed' AS "ActivityName",
  wnd.confirmed_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  wnd.shipping_method_code AS "ModeOfTransport",
  wnd.status_code_name AS "LogisticsOrderStatus",
  wnd.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  NULL AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN wsh_delivery_details wdd ON dha.header_id = wdd.source_header_id
  JOIN wsh_delivery_assignments wda ON wdd.delivery_detail_id = wda.delivery_detail_id
  JOIN wsh_new_deliveries wnd ON wda.delivery_id = wnd.delivery_id
WHERE wnd.confirmed_date IS NOT NULL

UNION ALL

-- 11. Goods Loaded for Transport
SELECT
  so.order_number AS "LogisticsOrder",
  'Goods Loaded for Transport' AS "ActivityName",
  wts.actual_departure_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  wt.mode_of_transport AS "ModeOfTransport",
  wts.status_code_name AS "LogisticsOrderStatus",
  wts.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  NULL AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN wsh_delivery_details wdd ON dha.header_id = wdd.source_header_id
  JOIN wsh_delivery_assignments wda ON wdd.delivery_detail_id = wda.delivery_detail_id
  JOIN wsh_new_deliveries wnd ON wda.delivery_id = wnd.delivery_id
  JOIN wsh_delivery_legs wdl ON wnd.delivery_id = wdl.delivery_id
  JOIN wsh_trip_stops wts ON wdl.pick_up_stop_id = wts.stop_id
  JOIN wsh_trips wt ON wts.trip_id = wt.trip_id
WHERE wts.actual_departure_date IS NOT NULL

UNION ALL

-- 12. Goods Unloaded at Destination
SELECT
  so.order_number AS "LogisticsOrder",
  'Goods Unloaded at Destination' AS "ActivityName",
  wts.actual_arrival_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  wts.actual_arrival_date AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  wt.mode_of_transport AS "ModeOfTransport",
  wts.status_code_name AS "LogisticsOrderStatus",
  wts.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  NULL AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN wsh_delivery_details wdd ON dha.header_id = wdd.source_header_id
  JOIN wsh_delivery_assignments wda ON wdd.delivery_detail_id = wda.delivery_detail_id
  JOIN wsh_new_deliveries wnd ON wda.delivery_id = wnd.delivery_id
  JOIN wsh_delivery_legs wdl ON wnd.delivery_id = wdl.delivery_id
  JOIN wsh_trip_stops wts ON wdl.drop_off_stop_id = wts.stop_id
  JOIN wsh_trips wt ON wts.trip_id = wt.trip_id
WHERE wts.actual_arrival_date IS NOT NULL

UNION ALL

-- 13. Proof of Delivery Signed
SELECT
  so.order_number AS "LogisticsOrder",
  'Proof of Delivery Signed' AS "ActivityName",
  wnd.pod_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  wnd.pod_date AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  wnd.shipping_method_code AS "ModeOfTransport",
  wnd.status_code_name AS "LogisticsOrderStatus",
  wnd.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  NULL AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
  JOIN wsh_delivery_details wdd ON dha.header_id = wdd.source_header_id
  JOIN wsh_delivery_assignments wda ON wdd.delivery_detail_id = wda.delivery_detail_id
  JOIN wsh_new_deliveries wnd ON wda.delivery_id = wnd.delivery_id
WHERE wnd.pod_flag = 'Y' AND wnd.pod_date IS NOT NULL

UNION ALL

-- 14. Order Canceled
SELECT
  so.order_number AS "LogisticsOrder",
  'Order Canceled' AS "ActivityName",
  dha.last_update_date AS "EventTime",
  dha.request_ship_date AS "RequestedDeliveryDate",
  NULL AS "ActualDeliveryDate",
  NULL AS "ProductCategory",
  NULL AS "SupplierName",
  NULL AS "ModeOfTransport",
  dha.status_code AS "LogisticsOrderStatus",
  dha.last_updated_by AS "User",
  NULL AS "PurchaseOrderNumber",
  NULL AS "ItemNumber"
FROM
  sales_orders so
  JOIN doo_headers_all dha ON so.header_id = dha.header_id
WHERE
  dha.cancelled_flag = 'Y'

Steps

Log in to Oracle BI Cloud Connector (BICC): Access the BICC console using your Oracle Cloud Applications credentials. You must have the necessary BI Administrator role to perform data extractions.
Navigate to Offerings: From the BICC home page, select the 'Manage Offerings' or a similar navigation link to view the available Oracle Cloud applications data sources.
Select the SCM Offering: Choose the 'Supply Chain Management' offering. This action loads all the Public View Objects, or PVOs, related to SCM modules like Order Management, Procurement, and Inventory.
Create a New Job: Navigate to the 'Manage Extract Jobs' section. Create a new job and provide a descriptive name, for example, 'ProcessMind_Logistics_Order_Extraction'.
Select PVOs for Extraction: In the job configuration, use the search function to find and add each of the required PVOs to your extraction set. The PVOs are listed in the query section below. You will add each PVO as a separate data store to the job.
Configure PVO Columns and Filters: For each PVO added, click 'Configure' to select the specific columns needed for the event log. It is critical to apply date filters, for instance, on creation date or last update date, to limit the data volume to a manageable range, like the last 3 to 6 months.
Configure External Storage: In the 'Configure External Storage' section, provide the connection details for your target cloud storage, such as Oracle Cloud Infrastructure (OCI) Object Storage. This is where BICC will deliver the extracted data files.
Schedule the Extraction Job: Set a schedule for the job to run. For the initial extraction, you can run it manually. For ongoing monitoring, you can schedule it to run daily or weekly during off-peak hours.
Run and Monitor the Job: Save and submit the job. Monitor its progress from the 'Manage Extract Jobs' dashboard. Check the job history for any errors or warnings.
Combine and Transform Data: After the job completes successfully, BICC will deliver a separate CSV or DAT file for each PVO to your cloud storage. You must use a separate ETL tool or script to download these files, union them into a single event log table, and map the columns to the required format (LogisticsOrder, ActivityName, EventTime).
Final Formatting for Upload: Ensure the final combined file is a single CSV. The columns must match the required and recommended attributes. Check that the EventTime column is in a consistent timestamp format, such as YYYY-MM-DD HH:MI:SS.

Configuration

BICC Offering: Select 'Supply Chain Management' to access the necessary data objects.
PVO Selection: You must select multiple PVOs covering Order Management, Procurement, Inventory, Manufacturing, and Shipping to capture the full end to end process. A list is provided in the query section.
Incremental vs. Full Extract: For the initial load, a full extract with a specific date range is recommended. For subsequent runs, configure incremental extracts based on the 'Last Update Date' column available in most PVOs to reduce data volume and processing time.
Date Range Filter: Always apply a date filter on a relevant date column like 'CreationDate' or 'LastUpdateDate' for each PVO. A range of 3 to 6 months is typical for an initial analysis.
Column Selection: To improve performance, do not extract all columns from a PVO. Select only the columns required for the event log attributes. This minimizes the payload size and extraction duration.
Prerequisites: The user running the extraction requires a role with BICC access, such as 'BIACM_ADMIN'. The relevant SCM modules, including Order Management, Procurement, and Shipping, must be provisioned and in use.

a Sample Query config

The following Public View Objects (PVOs) must be selected and configured within the BI Cloud Connector extraction job. This is not a runnable script but a list of objects to add to the extraction configuration.

**Order Management PVOs:**
*   `FscmTopModelAM.DooTopAM.Header` (For Customer Order Created, Order Canceled)
*   `FscmTopModelAM.DooTopAM.FulfilledLine` (For Inventory Availability Checked)

**Procurement PVOs:**
*   `FscmTopModelAM.ScmPoTopAM.ReqHeader` (For Purchase Requisition Created)
*   `FscmTopModelAM.ScmPoTopAM.PoHeader` (For Purchase Order Issued)

**Inventory and Receiving PVOs:**
*   `FscmTopModelAM.ScmRcvTopAM.RcvTransaction` (For Raw Materials Received)

**Manufacturing PVOs:**
*   `FscmTopModelAM.WisTopAM.WorkOrderHeader` (For Production Scheduled, Goods Produced)

**Quality Management PVOs:**
*   `FscmTopModelAM.ScmQamTopAM.QualityInspectionResult` (For Quality Control Performed)

**Shipping and Warehouse Management PVOs:**
*   `FscmTopModelAM.ScmWmsShippingTopAM.ShipmentLine` (For Goods Picked and Packed)
*   `FscmTopModelAM.ScmWmsShippingTopAM.ShipmentHeader` (For Shipment Confirmed)
*   `FscmTopModelAM.ScmWmsShippingTopAM.DeliveryTrip` (For Goods Loaded for Transport)
*   `FscmTopModelAM.ScmWmsShippingTopAM.DeliveryHeader` (For Goods Unloaded at Destination, Proof of Delivery Signed)

Steps

Prerequisites: Ensure you have Python 3.6+ installed on your system, along with the requests and pandas libraries. You can install them using pip: pip install requests pandas.
Authentication Setup: Obtain user credentials (username and password) for an Oracle SCM Cloud user account that has the necessary permissions to access the required REST APIs, such as Sales Orders, Purchase Orders, Shipments, and Work Orders.
Configure the Script: Open the provided Python script in a text editor or IDE. Fill in the placeholder variables at the top of the script, including ORACLE_SCM_HOST, USERNAME, PASSWORD, START_DATE, and END_DATE.
Understand API Endpoints: The script is pre-configured to query multiple REST API endpoints corresponding to different supply chain activities. Review the endpoints dictionary in the script to understand which Oracle SCM objects are being queried.
Execute the Script: Run the script from your command line using python your_script_name.py. The script will begin authenticating and making sequential API calls for each defined activity.
API Pagination Handling: The script includes a function to handle API pagination automatically. It will make subsequent requests if the hasMore flag in the API response is true, ensuring all records within the specified date range are retrieved.
Data Transformation: As data is fetched for each activity, the script transforms the JSON response into a standardized format. It extracts key fields, maps them to the event log columns (LogisticsOrder, ActivityName, EventTime, etc.), and appends them to a master list of events.
Handling Missing Data: The script uses .get() with default None values to safely access nested JSON fields that may not be present in every record, preventing errors and resulting in null values in the output where data is missing.
Output Generation: Once all API calls are complete, the script consolidates the collected events into a pandas DataFrame.
Export to CSV: The final DataFrame is exported to a CSV file named oracle_scm_event_log.csv in the same directory where the script is run. This file is formatted for direct upload into a process mining tool.
Review and Upload: Open the generated CSV file to review the data for completeness and correctness. Once validated, upload the event log to your process mining platform.

Configuration

Credentials: A dedicated API user with roles like Order Manager, Procurement Manager, Warehouse Manager, and Shipping Manager is required to access all necessary API resources.
Date Range: Set the START_DATE and END_DATE variables in the script. It is recommended to start with a smaller range, such as 3-6 months, to manage the volume of data and API rate limits.
API Version: The script uses API version 11.13.18.05. Ensure this version is consistent with your Oracle SCM Cloud instance, or update the endpoint URLs if necessary.
Pagination Limit: The limit parameter in the API requests is set to 100 to control the number of records returned per call. This can be adjusted based on performance and API server constraints.
Filters: The script primarily filters by date (CreationDate, LastUpdateDate). Additional filters, such as by BusinessUnitName or OrganizationCode, can be added to the q parameter in the API calls to narrow the scope of the extraction for specific business units or legal entities.
Custom Fields: If your organization uses Descriptive Flexfields (DFFs) to store critical process data, you may need to customize the script to include those fields in the API query and data extraction logic.

a Sample Query python

import requests
import pandas as pd
from datetime import datetime

class=class="hl-string">"hl-comment"># --- Configuration Settings ---
class=class="hl-string">"hl-comment"># Replace with your Oracle SCM Cloud instance details
ORACLE_SCM_HOST = class="hl-string">"[Your Oracle SCM Host e.g., xyz.fa.us2.oraclecloud.com]"
USERNAME = class="hl-string">"[Your Username]"
PASSWORD = class="hl-string">"[Your Password]"

class=class="hl-string">"hl-comment"># --- Date Range for Extraction ---
class=class="hl-string">"hl-comment"># Format: YYYY-MM-DD
START_DATE = class="hl-string">"2023-01-01"
END_DATE = class="hl-string">"2023-12-31"

class=class="hl-string">"hl-comment"># --- API Request Helper Function ---
def make_api_request(endpoint, params={}):
    class="hl-string">"""Handles authentication and pagination for Oracle SCM REST API calls."""
    all_items = []
    session = requests.Session()
    session.auth = (USERNAME, PASSWORD)
    url = fclass="hl-string">"https://{ORACLE_SCM_HOST}{endpoint}"

    class=class="hl-string">"hl-comment"># Set default limit and offset for pagination
    params.setdefault(class="hl-string">'limit', 100)
    params.setdefault(class="hl-string">'offset', 0)
    params.setdefault(class="hl-string">'onlyData', class="hl-string">'true')

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

            if not data.get(class="hl-string">'hasMore', False):
                break
            
            params[class="hl-string">'offset'] += params[class="hl-string">'limit']

        except requests.exceptions.RequestException as e:
            print(fclass="hl-string">"Error fetching data from {url}: {e}")
            break

    return all_items

class=class="hl-string">"hl-comment"># --- Main Extraction Logic ---
def extract_scm_event_log():
    events = []
    date_filter = fclass="hl-string">"LastUpdateDate between '{START_DATE}' and '{END_DATE}'"
    creation_date_filter = fclass="hl-string">"CreationDate between '{START_DATE}' and '{END_DATE}'"

    print(class="hl-string">"Fetching Sales Orders for 'Customer Order Created' and 'Order Canceled'...")
    so_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub", {class="hl-string">'q': date_filter})
    for so in so_data:
        order_number = so.get(class="hl-string">'OrderNumber')
        if not order_number: continue

        class=class="hl-string">"hl-comment"># Activity: Customer Order Created
        events.append({
            class="hl-string">'LogisticsOrder': order_number,
            class="hl-string">'ActivityName': class="hl-string">'Customer Order Created',
            class="hl-string">'EventTime': so.get(class="hl-string">'CreationDate'),
            class="hl-string">'RequestedDeliveryDate': so.get(class="hl-string">'RequestShipDate'),
            class="hl-string">'ActualDeliveryDate': None,
            class="hl-string">'ProductCategory': so.get(class="hl-string">'lines', [{}])[0].get(class="hl-string">'ProductGroup'),
            class="hl-string">'SupplierName': None,
            class="hl-string">'ModeOfTransport': so.get(class="hl-string">'ShippingMethodCode'),
            class="hl-string">'LogisticsOrderStatus': so.get(class="hl-string">'Status'),
            class="hl-string">'User': so.get(class="hl-string">'CreatedBy'),
            class="hl-string">'PurchaseOrderNumber': None,
            class="hl-string">'ItemNumber': so.get(class="hl-string">'lines', [{}])[0].get(class="hl-string">'ProductNumber')
        })

        class=class="hl-string">"hl-comment"># Activity: Order Canceled
        if so.get(class="hl-string">'Status') == class="hl-string">'CANCELED':
            events.append({
                class="hl-string">'LogisticsOrder': order_number,
                class="hl-string">'ActivityName': class="hl-string">'Order Canceled',
                class="hl-string">'EventTime': so.get(class="hl-string">'LastUpdateDate'),
                class="hl-string">'RequestedDeliveryDate': so.get(class="hl-string">'RequestShipDate'),
                class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None,
                class="hl-string">'ModeOfTransport': so.get(class="hl-string">'ShippingMethodCode'),
                class="hl-string">'LogisticsOrderStatus': so.get(class="hl-string">'Status'), class="hl-string">'User': so.get(class="hl-string">'LastUpdatedBy'),
                class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
            })

    print(class="hl-string">"Fetching Purchase Requisitions for 'Purchase Requisition Created'...")
    pr_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/purchaseRequisitions", {class="hl-string">'q': creation_date_filter})
    for pr in pr_data:
        class=class="hl-string">"hl-comment"># Note: Linking PR to a specific sales order requires custom logic or configuration.
        class=class="hl-string">"hl-comment"># Here we assume a link can be inferred or is not strictly required for this event.
        events.append({
            class="hl-string">'LogisticsOrder': pr.get(class="hl-string">'SourceOrderNumber', class="hl-string">'[Not Linked]'), class=class="hl-string">"hl-comment"># Placeholder if no direct link
            class="hl-string">'ActivityName': class="hl-string">'Purchase Requisition Created',
            class="hl-string">'EventTime': pr.get(class="hl-string">'CreationDate'),
            class="hl-string">'RequestedDeliveryDate': None, class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None,
            class="hl-string">'SupplierName': None, class="hl-string">'ModeOfTransport': None, class="hl-string">'LogisticsOrderStatus': pr.get(class="hl-string">'RequisitioningBU'),
            class="hl-string">'User': pr.get(class="hl-string">'CreatedBy'),
            class="hl-string">'PurchaseOrderNumber': None,
            class="hl-string">'ItemNumber': pr.get(class="hl-string">'lines', [{}])[0].get(class="hl-string">'ItemNumber')
        })

    print(class="hl-string">"Fetching Purchase Orders for 'Purchase Order Issued'...")
    po_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/purchaseOrders", {class="hl-string">'q': fclass="hl-string">"ApprovedDate between '{START_DATE}' and '{END_DATE}'"})
    for po in po_data:
        events.append({
            class="hl-string">'LogisticsOrder': po.get(class="hl-string">'SourceOrderNumber', class="hl-string">'[Not Linked]'), class=class="hl-string">"hl-comment"># Placeholder if no direct link
            class="hl-string">'ActivityName': class="hl-string">'Purchase Order Issued',
            class="hl-string">'EventTime': po.get(class="hl-string">'ApprovedDate'),
            class="hl-string">'RequestedDeliveryDate': None, class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None,
            class="hl-string">'SupplierName': po.get(class="hl-string">'Supplier'),
            class="hl-string">'ModeOfTransport': None,
            class="hl-string">'LogisticsOrderStatus': po.get(class="hl-string">'DocumentStatus'),
            class="hl-string">'User': po.get(class="hl-string">'Buyer'),
            class="hl-string">'PurchaseOrderNumber': po.get(class="hl-string">'OrderNumber'),
            class="hl-string">'ItemNumber': po.get(class="hl-string">'lines', [{}])[0].get(class="hl-string">'ItemNumber')
        })

    print(class="hl-string">"Fetching Receipts for 'Raw Materials Received'...")
    rcv_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/receivingReceipts", {class="hl-string">'q': fclass="hl-string">"ReceiptDate between '{START_DATE}' and '{END_DATE}'"})
    for rcv in rcv_data:
        events.append({
            class="hl-string">'LogisticsOrder': rcv.get(class="hl-string">'OrderNumber'), class=class="hl-string">"hl-comment"># Assuming PO is the key link
            class="hl-string">'ActivityName': class="hl-string">'Raw Materials Received',
            class="hl-string">'EventTime': rcv.get(class="hl-string">'ReceiptDate'),
            class="hl-string">'RequestedDeliveryDate': None, class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None,
            class="hl-string">'SupplierName': rcv.get(class="hl-string">'SupplierName'), class="hl-string">'ModeOfTransport': None, 
            class="hl-string">'LogisticsOrderStatus': class="hl-string">'Received', class="hl-string">'User': rcv.get(class="hl-string">'CreatedBy'),
            class="hl-string">'PurchaseOrderNumber': rcv.get(class="hl-string">'POHeaderNumber'),
            class="hl-string">'ItemNumber': rcv.get(class="hl-string">'ItemNumber')
        })
        
    print(class="hl-string">"Fetching Work Orders for 'Production Scheduled' and 'Goods Produced'...")
    wo_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/workOrders", {class="hl-string">'q': date_filter})
    for wo in wo_data:
        class=class="hl-string">"hl-comment"># Activity: Production Scheduled
        if wo.get(class="hl-string">'ReleasedDate'):
            events.append({
                class="hl-string">'LogisticsOrder': wo.get(class="hl-string">'SalesOrderNumber', wo.get(class="hl-string">'WorkOrderNumber')), 
                class="hl-string">'ActivityName': class="hl-string">'Production Scheduled',
                class="hl-string">'EventTime': wo.get(class="hl-string">'ReleasedDate'),
                class="hl-string">'RequestedDeliveryDate': None, class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None,
                class="hl-string">'ModeOfTransport': None, class="hl-string">'LogisticsOrderStatus': wo.get(class="hl-string">'WorkOrderStatus'),
                class="hl-string">'User': wo.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': wo.get(class="hl-string">'ProductName')
            })
        class=class="hl-string">"hl-comment"># Activity: Goods Produced
        if wo.get(class="hl-string">'CompletedDate'):
            events.append({
                class="hl-string">'LogisticsOrder': wo.get(class="hl-string">'SalesOrderNumber', wo.get(class="hl-string">'WorkOrderNumber')),
                class="hl-string">'ActivityName': class="hl-string">'Goods Produced',
                class="hl-string">'EventTime': wo.get(class="hl-string">'CompletedDate'),
                class="hl-string">'RequestedDeliveryDate': None, class="hl-string">'ActualDeliveryDate': None, class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None,
                class="hl-string">'ModeOfTransport': None, class="hl-string">'LogisticsOrderStatus': wo.get(class="hl-string">'WorkOrderStatus'),
                class="hl-string">'User': wo.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': wo.get(class="hl-string">'ProductName')
            })
            
    print(class="hl-string">"Fetching Shipments for shipping activities...")
    ship_data = make_api_request(class="hl-string">"/fscmRestApi/resources/11.13.18.05/shipments", {class="hl-string">'q': date_filter})
    for ship in ship_data:
        order_number = ship.get(class="hl-string">'SourceSalesOrderNumber', ship.get(class="hl-string">'ShipmentNumber'))
        
        class=class="hl-string">"hl-comment"># Activities: Goods Picked and Packed (using shipment creation as proxy), Shipment Confirmed, Goods Loaded
        events.append({
            class="hl-string">'LogisticsOrder': order_number, class="hl-string">'ActivityName': class="hl-string">'Goods Picked and Packed',
            class="hl-string">'EventTime': ship.get(class="hl-string">'CreationDate'), class="hl-string">'RequestedDeliveryDate': None,
            class="hl-string">'ActualDeliveryDate': ship.get(class="hl-string">'ActualDeliveryDate'), class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None, 
            class="hl-string">'ModeOfTransport': ship.get(class="hl-string">'ModeOfTransport'), class="hl-string">'LogisticsOrderStatus': class="hl-string">'Packing', 
            class="hl-string">'User': ship.get(class="hl-string">'CreatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
        })
        if ship.get(class="hl-string">'ShippedDate'):
            events.append({
                class="hl-string">'LogisticsOrder': order_number, class="hl-string">'ActivityName': class="hl-string">'Shipment Confirmed',
                class="hl-string">'EventTime': ship.get(class="hl-string">'ShippedDate'), class="hl-string">'RequestedDeliveryDate': None,
                class="hl-string">'ActualDeliveryDate': ship.get(class="hl-string">'ActualDeliveryDate'), class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None, 
                class="hl-string">'ModeOfTransport': ship.get(class="hl-string">'ModeOfTransport'), class="hl-string">'LogisticsOrderStatus': class="hl-string">'Shipped', 
                class="hl-string">'User': ship.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
            })
            events.append({
                class="hl-string">'LogisticsOrder': order_number, class="hl-string">'ActivityName': class="hl-string">'Goods Loaded for Transport',
                class="hl-string">'EventTime': ship.get(class="hl-string">'ShippedDate'), class="hl-string">'RequestedDeliveryDate': None, 
                class="hl-string">'ActualDeliveryDate': ship.get(class="hl-string">'ActualDeliveryDate'), class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None, 
                class="hl-string">'ModeOfTransport': ship.get(class="hl-string">'ModeOfTransport'), class="hl-string">'LogisticsOrderStatus': class="hl-string">'In Transit', 
                class="hl-string">'User': ship.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
            })

        class=class="hl-string">"hl-comment"># Activity: Goods Unloaded at Destination (if data available)
        if ship.get(class="hl-string">'ActualArrivalDate'):
             events.append({
                class="hl-string">'LogisticsOrder': order_number, class="hl-string">'ActivityName': class="hl-string">'Goods Unloaded at Destination',
                class="hl-string">'EventTime': ship.get(class="hl-string">'ActualArrivalDate'), class="hl-string">'RequestedDeliveryDate': None, 
                class="hl-string">'ActualDeliveryDate': ship.get(class="hl-string">'ActualDeliveryDate'), class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None, 
                class="hl-string">'ModeOfTransport': ship.get(class="hl-string">'ModeOfTransport'), class="hl-string">'LogisticsOrderStatus': class="hl-string">'Arrived', 
                class="hl-string">'User': ship.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
            })

        class=class="hl-string">"hl-comment"># Activity: Proof of Delivery Signed
        if ship.get(class="hl-string">'ProofOfDeliveryDate'):
             events.append({
                class="hl-string">'LogisticsOrder': order_number, class="hl-string">'ActivityName': class="hl-string">'Proof of Delivery Signed',
                class="hl-string">'EventTime': ship.get(class="hl-string">'ProofOfDeliveryDate'), class="hl-string">'RequestedDeliveryDate': None, 
                class="hl-string">'ActualDeliveryDate': ship.get(class="hl-string">'ProofOfDeliveryDate'), class="hl-string">'ProductCategory': None, class="hl-string">'SupplierName': None, 
                class="hl-string">'ModeOfTransport': ship.get(class="hl-string">'ModeOfTransport'), class="hl-string">'LogisticsOrderStatus': class="hl-string">'Delivered', 
                class="hl-string">'User': ship.get(class="hl-string">'LastUpdatedBy'), class="hl-string">'PurchaseOrderNumber': None, class="hl-string">'ItemNumber': None
            })

    class=class="hl-string">"hl-comment"># The following activities are often implicit or require more complex queries.
    class=class="hl-string">"hl-comment"># For this script, we are not fetching them directly, but stubs could be added here.
    print(class="hl-string">"Skipping 'Inventory Availability Checked' and 'Quality Control Performed' due to complexity...")
    class=class="hl-string">"hl-comment"># Note: To capture these, you would query order line status changes or the qualityInspections API.

    print(fclass="hl-string">"Total events extracted: {len(events)}")
    return pd.DataFrame(events)

class=class="hl-string">"hl-comment"># --- Script Execution ---
if __name__ == class="hl-string">"__main__":
    event_log_df = extract_scm_event_log()
    if not event_log_df.empty:
        class=class="hl-string">"hl-comment"># Sort by case and time for chronological order
        event_log_df[class="hl-string">'EventTime'] = pd.to_datetime(event_log_df[class="hl-string">'EventTime'], errors=class="hl-string">'coerce')
        event_log_df.dropna(subset=[class="hl-string">'EventTime'], inplace=True)
        event_log_df.sort_values(by=[class="hl-string">'LogisticsOrder', class="hl-string">'EventTime'], inplace=True)
        
        class=class="hl-string">"hl-comment"># Save to CSV
        output_file = class="hl-string">'oracle_scm_event_log.csv'
        event_log_df.to_csv(output_file, index=False)
        print(fclass="hl-string">"Event log successfully saved to {output_file}")
    else:
        print(class="hl-string">"No events were extracted. Check your configuration and date range.")

Your Supply Chain Management Data Template

Your Supply Chain Management Data Template

Supply Chain Management Attributes

Supply Chain Management Activities

Extraction Guides

Oracle BI Publisher Report for SCM Logistics Data

Steps

Configuration

a Sample Query sql

Bulk Extraction using BI Cloud Connector (BICC)

Steps

Configuration

a Sample Query config

Python Script Extraction via Oracle SCM REST APIs

Steps

Configuration

a Sample Query python

Ready to Get Started?

Master Your Oracle SCM: Boost Supply Chain Efficiency Now

Your Supply Chain Management Data Template

Your Supply Chain Management Data Template

Supply Chain Management Attributes

Supply Chain Management Activities

Extraction Guides

Oracle BI Publisher Report for SCM Logistics Data

Steps

Configuration

a Sample Query sql

Bulk Extraction using BI Cloud Connector (BICC)

Steps

Configuration

a Sample Query config

Python Script Extraction via Oracle SCM REST APIs

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Master Your Oracle SCM: Boost Supply Chain Efficiency Now