> Continuous Process Improvement > Returns & Refund Processing > Oracle Fusion SCM > Data Template

Your Returns & Refund Processing Data Template

Oracle Fusion SCM

Returns & Refund Processing Attributes (22) Returns & Refund Processing Activities (15) Extraction Guides (3)

Your Returns & Refund Processing Data Template

This template is designed to help you analyze your Returns & Refund Processing in Oracle Fusion SCM. It outlines the essential attributes to collect, the key activities to track, and provides clear guidance on how to extract this data. Use it to gain valuable insights into your process and identify areas for improvement.

Recommended attributes to collect
Key activities to track for process analysis
Step-by-step extraction guidance for Oracle Fusion SCM

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

Download Template

Returns & Refund Processing Attributes

These are the recommended data fields to include in your event log for a comprehensive analysis of your returns and refund processing within Oracle Fusion SCM.

5 Required 7 Recommended 10 Optional

	Name	Description
	Activity ActivityName	The name of a specific business step or event that occurred within the returns and refund process.
Description This attribute describes a single step or milestone in the return lifecycle, such as 'RMA Created', 'Item Inspected', or 'Refund Processed'. Each activity represents a distinct point in the process captured in the system's event logs. Analyzing the sequence and duration of these activities is the core of process mining. It allows for the visualization of process maps, identification of bottlenecks between steps, and calculation of activity-specific lead times. This data is critical for understanding process flow, rework loops, and compliance with standard operating procedures. Why it matters Activities form the backbone of the process map, enabling the visualization and analysis of the process flow, variations, and bottlenecks. Where to get Derived from event logs, status changes, or specific transaction records within Oracle Fusion SCM modules like Order Management and Inventory Management. Examples RMA CreatedItem ReceivedCredit Memo CreatedRefund Processed
	Event Time EventTime	The timestamp indicating when a specific activity or event occurred.
Description Event Time, or the start time, is the precise date and time that an activity was recorded in the source system. It provides the chronological context for every step in the process. This timestamp is essential for all time-based analysis. It is used to order events correctly, calculate cycle times between activities, measure the total duration of a case, and evaluate performance against service level agreements (SLAs). Without accurate timestamps, it is impossible to analyze process efficiency, identify delays, or understand process dynamics. Why it matters This attribute provides the chronological sequence of events, which is fundamental for calculating all duration-based metrics and discovering process bottlenecks. Where to get This information is typically found as a 'Creation Date', 'Timestamp', or 'Last Update Date' field associated with transaction or status records in Oracle Fusion SCM. Examples 2023-10-26T10:00:00Z2023-10-26T14:35:10Z2023-10-27T09:00:00Z
	Return Case ID ReturnCaseId	The primary identifier that links all activities associated with a specific customer return or refund request.
Description The Return Case ID serves as the unique case identifier for the entire returns and refund process. It connects every event, from the initial return merchandise authorization (RMA) creation to the final refund processing and case closure. In process mining analysis, this attribute is fundamental for reconstructing the end-to-end journey of each return. It allows analysts to track the complete lifecycle, measure total cycle times, and understand the variations in how different returns are handled. All other event-level data is grouped by this ID to form a cohesive process view. Why it matters This is the essential key to stitching together all related events into a single process instance, making end-to-end analysis possible. Where to get This identifier is typically generated within the Oracle Order Management or Service modules when a return request is initiated. Examples RMA-2023-00123RMA-2023-00456RMA-2023-00789
	Last Data Update LastDataUpdate	The timestamp when the data was last refreshed or extracted from the source system.
Description This attribute indicates the most recent time the dataset was updated. It provides a 'freshness' date for the entire dataset, not individual events. Knowing the last data update time is critical for users to understand the timeliness of the analysis. It helps them interpret dashboards and KPIs correctly, knowing whether they are looking at real-time information or data that is hours or days old. It is a key piece of metadata for any process mining project. Why it matters Informs users about the recency of the data, ensuring they understand the context and timeliness of their analysis. Where to get This timestamp is generated and added during the data extraction, transformation, and loading (ETL) process. Examples 2023-11-01T02:00:00Z2023-11-02T02:00:00Z
	Source System SourceSystem	The system from which the data was extracted.
Description This attribute identifies the originating information system where the event data was recorded. For this process, it would typically be 'Oracle Fusion SCM'. In environments with multiple integrated systems, this field is crucial for data lineage and troubleshooting. It helps confirm the data's origin and can be used to filter analysis for events from specific systems, ensuring data quality and context are maintained. Why it matters It provides crucial context about data origin, which is essential for data validation and analysis in multi-system environments. Where to get This is often a static value added during the data extraction, transformation, and loading (ETL) process to label the dataset's origin. Examples Oracle Fusion SCMOracle SCM Cloud
	Actual Refund Amount ActualRefundAmount	The final monetary amount that was actually processed and refunded to the customer.
Description This attribute represents the final, confirmed amount paid back to the customer after all inspections, adjustments, and fees have been applied. This value reflects the true financial outcome of the return case. This is a critical financial data point used in the 'Requested vs Actual Refund Amounts' dashboard. Comparing this to the requested amount is key to calculating the 'Refund Amount Discrepancy Rate' KPI and understanding the financial impact of return policies, item conditions, and processing adjustments. Why it matters Represents the true financial outcome of the return, enabling discrepancy analysis and financial reporting. Where to get This information would likely come from the Credit Memo or Accounts Payable transaction records linked to the return case in Oracle Fusion Financials. Examples 129.9940.000.00
	End Time EndTime	The timestamp indicating when an activity was completed.
Description The End Time marks the completion of an activity. While StartTime indicates when an event began, End Time is needed to calculate the actual processing time of that specific event. For instantaneous events, StartTime and End Time can be the same. In analysis, the difference between End Time and Start Time provides the 'Processing Time' for an activity. This is crucial for identifying which specific steps are time-consuming, as opposed to the waiting time between steps. It is essential for detailed bottleneck analysis and resource efficiency calculations. Why it matters This attribute is necessary for calculating the true processing time of individual activities, helping to distinguish active work time from waiting time. Where to get This may be a separate field in the source system logs or can be derived from the StartTime of the subsequent activity. Examples 2023-10-26T10:05:00Z2023-10-26T15:00:10Z2023-10-27T11:30:00Z
	Processing Agent ProcessingAgent	The user or agent responsible for executing a specific activity in the return process.
Description This attribute identifies the employee or system user who performed a given task, such as approving an RMA or processing a refund. It can also refer to a team or department if individual assignment is not tracked. Analyzing performance by agent is critical for operational management. This attribute enables the 'Return Processing Agent Performance' dashboard, allowing for comparisons of workload, activity duration, and rework rates among different agents. These insights can highlight training needs, identify top performers, and inform better resource allocation. Why it matters Enables performance analysis by user or team, helping to identify high-performers, training opportunities, and workload imbalances. Where to get Typically found in fields like 'USER_ID', 'PROCESSED_BY', or 'AGENT_NAME' in transaction logs within Oracle Fusion SCM. Examples j.doea.smithm.jones
	Refund SLA Target Date RefundSlaTargetDate	The date by which the refund is expected to be completed according to the service level agreement.
Description This attribute defines the deadline for completing the refund process for a given case. The SLA target is often determined by company policy, customer tier, or the reason for the return. This date is the benchmark for measuring timeliness and compliance. It is used directly in the 'Refund Policy SLA Compliance' dashboard and is essential for calculating the 'Refund SLA Conformance Rate' KPI. Comparing the actual refund completion date to this target allows for the identification of SLA breaches and helps prioritize cases that are at risk of being late. Why it matters Provides the benchmark for measuring on-time performance and is crucial for calculating SLA compliance KPIs. Where to get This may be a specific date field on the return case or may need to be derived by adding a predefined time period (e.g., 14 days) to the return initiation date. Examples 2023-11-10T23:59:59Z2023-11-15T23:59:59Z2023-11-20T23:59:59Z
	Requested Refund Amount RequestedRefundAmount	The monetary amount the customer initially requested for the return.
Description This attribute captures the value of the refund as requested by the customer at the beginning of the process. It is the baseline amount against which the final refund is compared. This data point is essential for the 'Requested vs Actual Refund Amounts' dashboard and the 'Refund Amount Discrepancy Rate' KPI. Analyzing the difference between requested and actual amounts can uncover issues such as incorrect item returns, restocking fees, or policy adjustments, providing valuable insights into financial accuracy and customer satisfaction. Why it matters Serves as the baseline for financial analysis, enabling the calculation of refund discrepancies and highlighting potential issues. Where to get This value should be stored on the RMA or return request header in Oracle Fusion SCM, likely in the Order Management module. Examples 129.9945.501200.00
	Return Reason ReturnReason	The reason provided by the customer for returning the item.
Description This attribute contains the reason for the return, typically selected by the customer from a predefined list, such as 'Defective Item', 'Wrong Size', or 'No Longer Needed'. Analyzing return reasons provides powerful insights into product quality, sales process accuracy, and customer behavior. This data can be used to identify products with high defect rates, improve product descriptions to reduce incorrect orders, and understand the root causes of returns. This analysis can drive strategic improvements that reduce the overall volume of returns. Why it matters Provides critical insight into why returns are happening, which can be used to drive improvements in products and sales processes. Where to get Typically stored as a code or text field on the RMA line item in Oracle Order Management. Examples DefectiveWrong Item ShippedArrived Too LateBetter Price Available
	Return Status ReturnStatus	The current or final status of the return case.
Description This attribute indicates the overall status of the return case at a given point in time or its final outcome, such as 'Closed - Refunded', 'Closed - Rejected', or 'In Progress'. Return Status is key for outcome analysis and monitoring. It allows for filtering cases based on their result, comparing the process flows of approved versus rejected returns, and powering the 'Current Return Case Status Dashboard'. Understanding the distribution of outcomes is essential for measuring process effectiveness. Why it matters Provides the outcome of a case, which is essential for filtering, comparative analysis, and understanding process success rates. Where to get Usually available as a status field on the main return or RMA header record in Oracle Order Management. Examples Awaiting ReceiptInspection CompleteClosed - RefundedClosed - Rejected
	Customer ID CustomerId	The unique identifier for the customer who initiated the return.
Description This attribute is the unique ID that identifies the customer associated with the return case. It links the return process to the customer database. Analyzing returns from a customer-centric view can reveal important patterns. For example, it can help identify customers with unusually high return frequencies, which might indicate satisfaction issues or potential fraud. It also enables analysis based on customer segments, helping to understand if certain groups have different return behaviors. Why it matters Enables customer-centric analysis, helping to identify repeat returners, segment behavior, and potential fraud. Where to get Found as a customer or party ID on the header of the original sales order or the return request in Oracle Order Management. Examples CUST-100589743ACC-54321
	Disposition Code DispositionCode	A code indicating the final handling of the returned physical item.
Description The Disposition Code specifies what happened to the returned product after inspection, for example, if it was returned to inventory, scrapped, sent for refurbishment, or returned to the vendor. This information is valuable for analyzing the financial and operational impact of returns. By analyzing disposition codes, a business can understand the cost associated with non-resalable goods and identify opportunities to improve refurbishment processes. It connects the return process to inventory and financial outcomes. Why it matters Connects the returns process to its physical outcome in inventory, providing insights into recovery rates and costs. Where to get This information is captured in Oracle Inventory Management or Warehouse Management modules after the inspection activity is complete. Examples RETURN_TO_STOCKSCRAPREFURBISHRETURN_TO_VENDOR
	End To End Refund Time EndToEndRefundTime	The total time elapsed from the initiation of the return request to the final processing of the refund.
Description This metric measures the complete duration of the refund process from the customer's point of view. It is calculated as the difference between the timestamp of the first event (e.g., 'RMA Created') and the timestamp of the refund completion event (e.g., 'Refund Processed'). As a primary KPI, this calculation is crucial for the 'Overall Refund Processing Cycle Time' dashboard and for monitoring customer experience. A high average time indicates systemic inefficiencies that need to be addressed. Analyzing the distribution of this value helps identify outliers and understand process performance at a high level. Why it matters This is a key performance indicator that directly measures the efficiency of the entire process and its impact on customer satisfaction. Where to get Calculated by subtracting the StartTime of the first activity from the StartTime of the 'Refund Processed' activity for each Return Case ID. Examples 10 days 4 hours21 days 8 hours5 days 0 hours
	Is Rework IsRework	A boolean flag indicating if an activity is part of a rework loop.
Description This flag identifies activities that are repetitions of earlier steps in the same case, indicating a process loop or rework. For example, if an item fails inspection and has to be re-inspected, the second inspection event would be flagged as rework. This attribute is fundamental for quantifying process inefficiency. It is used in the 'Return Processing Rework Rates' dashboard and for calculating the 'Return Rework Event Frequency' KPI. Identifying the amount and causes of rework is a primary goal of process mining, as it points directly to wasted effort, delays, and increased costs. Why it matters Directly flags process inefficiencies and loops, making it easy to quantify and analyze the causes of rework. Where to get This is a calculated attribute identified by the process mining software's algorithms that detect repeated activities within a single case. Examples truefalse
	Is SLA Compliant IsSlaCompliant	A boolean flag indicating whether the refund was processed within the defined SLA target.
Description This calculated attribute provides a simple true or false indicator of SLA conformance for each return case. It is determined by comparing the actual refund completion timestamp with the 'RefundSlaTargetDate'. This flag is essential for easily measuring and visualizing compliance rates. It powers the 'Refund Policy SLA Compliance' dashboard and simplifies the calculation of the 'Refund SLA Conformance Rate' KPI. It allows for quick filtering and root cause analysis to understand why certain cases fail to meet their SLA. Why it matters Simplifies SLA monitoring and reporting by converting a date comparison into a simple boolean metric. Where to get Calculated field. It is true if the 'Refund Processed' timestamp is on or before the 'RefundSlaTargetDate', and false otherwise. Examples truefalse
	Product ID ProductId	The unique identifier for the product being returned.
Description This attribute is the unique identifier, like an SKU or item number, for the specific product involved in the return. It links the return process to the product catalog. Product-level analysis is crucial for identifying problematic items. By filtering or dimensioning the process analysis by Product ID, companies can pinpoint products with high return rates, long inspection times, or specific defect patterns. This information is vital for quality control, supply chain management, and product development. Why it matters Links the return process to specific products, enabling analysis of product quality and return patterns. Where to get This would be the 'INVENTORY_ITEM_ID' or a similar field on the RMA line item in Oracle Order Management or Inventory modules. Examples PROD-5540-ASKU-98765ITEM-001-B
	Refund Amount Discrepancy RefundAmountDiscrepancy	The calculated difference between the requested refund amount and the actual refund amount.
Description This metric quantifies the monetary difference between what the customer asked for and what they received. It is calculated by subtracting the 'ActualRefundAmount' from the 'RequestedRefundAmount'. This calculated value is the basis for the 'Refund Amount Discrepancy Rate' KPI. A non-zero value indicates an adjustment was made during the process. Analyzing the reasons for these discrepancies, such as restocking fees or damage deductions, can provide insights into policy effectiveness and customer communication. Why it matters Quantifies financial adjustments in the refund process, helping to analyze the impact of policies and inspection outcomes. Where to get Calculated field: 'RequestedRefundAmount' - 'ActualRefundAmount'. Examples 0.005.50-10.00
	Return Type ReturnType	Categorizes the return based on the expected outcome, such as refund, exchange, or repair.
Description This attribute classifies the type of return being processed. The process flow and required steps can vary significantly depending on whether the customer is receiving a monetary refund, a replacement product, or a repaired item. Analyzing the process by Return Type is essential for understanding process variations. It allows for the creation of separate process maps for refunds versus exchanges, helping to identify unique bottlenecks and performance characteristics for each path. This segmentation is key to targeted process improvement efforts. Why it matters Allows for the segmentation of analysis based on different process paths, as exchanges and refunds often follow different steps. Where to get This is typically a category or type field on the RMA header or line in Oracle Order Management. Examples RefundExchangeRepair
	RMA Number RmaNumber	The unique identifier for the Return Merchandise Authorization transaction.
Description The RMA Number is a formal authorization for a customer to return a product. While it is often the same as the Return Case ID, in some systems it can be a separate, preceding identifier. This attribute serves as a key business reference number that is familiar to both internal users and customers. It can be used for searching and filtering cases and is often the primary number used in communication regarding the return. Why it matters Serves as a primary business reference number, crucial for operational tracking and communication with customers. Where to get This is the primary identifier on the Return Merchandise Authorization object within Oracle Order Management. Examples 789001789002789003
	Warehouse ID WarehouseId	The identifier of the warehouse or facility that received the returned item.
Description This attribute indicates the specific physical location, such as a distribution center or warehouse, where the customer's returned item was received and processed. Analyzing the process by warehouse is important for identifying location-specific performance issues. It enables comparison of inspection times, disposition outcomes, and overall cycle times between different facilities. This can highlight operational inefficiencies, staffing issues, or training needs at particular sites. Why it matters Enables performance analysis by location, helping to identify regional or facility-specific bottlenecks and inefficiencies. Where to get This field, often called 'ORGANIZATION_ID', is associated with the receipt transaction in Oracle Inventory Management. Examples WH-US-WESTWH-EU-CENTRALDC-01

Required Recommended Optional

Returns & Refund Processing Activities

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

7 Recommended 8 Optional

	Activity	Description
	Credit Memo Created	This is the financial activity where a credit memo is generated in Accounts Receivable to authorize a refund to the customer. This is an explicit event triggered by the returns process in Order Management.
Why it matters The creation of a credit memo is a definitive milestone indicating the company's commitment to refund the customer. It is the trigger for the entire financial settlement part of the process. Where to get This is an explicit transaction in Oracle Accounts Receivable. The event can be linked back to the original RMA via the sales order reference on the credit memo. Capture Use the creation date of the credit memo transaction in AR. Event type explicit
	Item Inspected	This activity signifies the completion of the item inspection process, where a quality assessment is recorded. It is typically an explicit transaction in Oracle Inventory Management or Quality Management that updates the RMA status.
Why it matters The outcome of the inspection directly influences the next steps, such as refund approval or rejection. The duration of the inspection activity itself is a key performance indicator for warehouse efficiency. Where to get Captured from the transaction timestamp when an inspector completes the inspection task against the RMA receipt in Oracle Inventory or Quality Management. Capture Use the completion timestamp of the inspection transaction. Event type explicit
	Item Received	This activity marks the physical receipt of the returned item at the warehouse or processing center. It is an explicit event captured in Oracle Fusion Inventory Management when the goods are scanned and recorded as received against the RMA.
Why it matters Receipt of the item is a crucial milestone that triggers subsequent inspection and processing steps. Measuring the time from 'RMA Approved' to 'Item Received' helps analyze logistics and shipping performance. Where to get This is an explicit transaction recorded in Oracle Inventory Management. The event corresponds to the transaction date of the RMA receipt. Capture Use the transaction timestamp of the RMA receipt in Inventory. Event type explicit
	Refund Processed	This activity marks the completion of the refund payment to the customer. It is an explicit event captured when the payment clearing transaction is recorded in Oracle Financials.
Why it matters This is a critical end-point for measuring the total refund cycle time from the customer's perspective. It confirms that the financial obligation to the customer has been met. Where to get This event is captured from the accounting or clearing date of the payment transaction in Oracle Accounts Payable or Treasury that settles the credit memo. Capture Use the clearing date of the payment transaction settling the credit memo. Event type explicit
	Return Case Closed	This is the final activity, signifying that all actions related to the RMA are complete, including receipt, disposition, and financial settlement. This is inferred from a final 'Closed' status on the RMA order.
Why it matters This event serves as the definitive end of the process, crucial for calculating the end-to-end cycle time and ensuring that no cases remain open indefinitely. Where to get Inferred from the timestamp when the RMA order header and all its lines reach a final 'Closed' status in Oracle Order Management. Capture Capture the last timestamp when the RMA header or line status changes to 'Closed'. Event type inferred
	RMA Approved	This key milestone signifies that the return request has been validated and approved according to business rules. This is generally inferred from a status change on the RMA, unlocking subsequent process steps like customer shipment.
Why it matters Approval is a critical gateway in the process. Delays here directly impact the total return cycle time and customer satisfaction. This activity is essential for analyzing approval bottlenecks. Where to get Inferred from the timestamp of the status change on the RMA order header or line moving to an 'Approved' or 'Awaiting Receiving' status. Capture Capture the timestamp when the RMA status is updated to an approved state. Event type inferred
	RMA Created	This activity marks the official start of the return process, where a Return Material Authorization (RMA) is created in Oracle Fusion SCM. This event is typically captured explicitly when a user or an automated process generates a new RMA sales order record.
Why it matters This is the primary start event for the entire returns process. Analyzing the time from this activity to others reveals overall process duration and helps identify initial delays. Where to get This is captured from the creation timestamp of the return order header in Oracle Fusion Order Management. The event corresponds to the initial save of the RMA document. Capture Track the creation date of the return order header record. Event type explicit
	Customer Notified	This represents the communication sent to the customer confirming the resolution of their return case, such as refund processed or exchange shipped. This is often captured from a communications log or a status update on the case.
Why it matters Timely customer communication is crucial for satisfaction. Analyzing this helps ensure service level agreements for communication are being met. Where to get Requires system analysis. This may be logged by an integrated CRM or communications platform, or it might be a manual status update on the RMA or a related service request. Capture Timestamp from an external communications system or a manual update. Event type inferred
	Exchange Order Created	This activity occurs in scenarios where the customer requested an exchange instead of a refund. It's an explicit event where a new sales order is generated, often linked to the original RMA.
Why it matters This activity identifies an important process variant. Separating exchange processes from refund processes is key to accurate cycle time analysis for each path. Where to get This is an explicit event, the creation of a new sales order document in Order Management. It needs to be linked back to the RMA via a reference field. Capture Use creation date of the new sales order linked to the RMA. Event type explicit
	Item Inspection Started	Indicates the beginning of the physical inspection of the returned item to assess its condition. This may be inferred from the item's location or status changing within the warehouse management module, or it could be an explicit scan.
Why it matters Measuring the time between item receipt and the start of inspection highlights queueing delays at the inspection station, a common bottleneck. Where to get This might be captured by a status change on the receipt line or a transaction moving the item to an inspection location in Oracle Inventory Management. It may require custom configuration to capture explicitly. Capture Timestamp of a status change or inventory transfer to an inspection area. Event type inferred
	Item Shipped By Customer	Represents the customer's action of shipping the return item back to the company. This event is often not captured directly in Oracle SCM but may be inferred from carrier integration data or a manual update.
Why it matters This activity provides insight into customer behavior and the time it takes for goods to be in transit. It helps distinguish between internal processing delays and delays caused by shipping. Where to get This may be an inferred event based on carrier shipping data linked to the RMA, or a manual status update in Oracle SCM. If no integration exists, this event may not be available. Capture Timestamp from an integrated carrier API or manual data entry field. Event type inferred
	Refund Initiated	This activity signifies that the payment process for the refund has begun. It is often inferred from a status change on the credit memo, moving from an open state to a state indicating it is being processed for payment.
Why it matters This activity helps separate the approval and creation of the credit memo from the actual payment processing, which may be handled by a different team or system and could be a source of delay. Where to get Inferred from a status change on the credit memo in Accounts Receivable, or from the creation of a payment record in Accounts Payable referencing the credit memo. Capture Identify timestamp when credit memo status changes to 'Pending Payment' or similar. Event type inferred
	Return Disposition Determined	Following inspection, this activity represents the decision on what to do with the returned item, such as 'Return to Stock' or 'Scrap'. This is captured through an explicit inventory transaction that moves the item to its final destination.
Why it matters This step is critical for inventory accuracy and financial reconciliation. Analyzing dispositions helps understand return reasons and product quality issues. Where to get Recorded as a transaction in Oracle Inventory Management, such as a subinventory transfer or item status update, following the inspection. Capture Track the timestamp of the inventory transaction that actions the disposition. Event type explicit
	RMA Approval Submitted	This represents the point when the created RMA is submitted for internal review and approval. It is often inferred from a status change on the RMA, indicating it has moved from a draft or entry state to a pending approval state.
Why it matters Tracking this helps measure the pre-approval phase duration. It separates the data entry time from the actual time spent waiting for an approver to take action. Where to get Inferred from the timestamp when the RMA order header or line status changes to a 'Pending Approval' or equivalent status within the Order Management approval workflow. Capture Identify the timestamp of the status change to 'Pending Approval'. Event type inferred
	RMA Rejected	Represents a terminal decision to reject the customer's return request. This is typically inferred from a status change on the RMA to 'Rejected' or 'Cancelled' during the approval phase.
Why it matters This is a critical exception path. Analyzing the frequency and reasons for rejections can reveal issues with return policies, customer expectations, or fraud attempts. Where to get Inferred from the timestamp of the status change on the RMA order header or line to a 'Rejected' or equivalent terminal status. Capture Identify timestamp of status change to 'Rejected' or 'Cancelled'. Event type inferred

Recommended Optional

Extraction Guides

How to get your data from Oracle Fusion SCM

Steps

Navigate to OTBI Analysis Editor: Log into your Oracle Fusion Cloud SCM instance. Use the Navigator menu to go to Tools, then select Reports and Analytics. Click the 'Create' button and choose 'Analysis' from the dropdown menu.
Select Subject Areas: In the 'Select Subject Area' popup, you must choose the primary subject areas that contain returns and refund data. Select "Sales - CRM All Lines" and "Receivables - Transactions Real Time". You will combine these to create a comprehensive view of the process.
Switch to Advanced Mode: After selecting the subject areas, the analysis editor will open. Immediately switch to the 'Advanced' tab to access the logical SQL editor, which is necessary for creating the required event log structure.
Construct the Event Log Query: Copy the complete logical SQL provided in the 'Query' section of this document and paste it into the 'SQL Query' text area on the Advanced tab. This query is structured with multiple UNION ALL clauses to retrieve each of the 15 required activities as separate rows.
Set Query Parameters: Modify the placeholder values within the query. Specifically, update the [START_DATE] and [END_DATE] placeholders to define the date range for your extraction. You may also need to adjust filters for specific Business Units or Return Order Types based on your organization's configuration.
Validate the Query: Click the 'Validate SQL' button to ensure the syntax is correct. The system will check the column names and structure against the selected subject areas.
Review the Results: Navigate to the 'Results' tab to preview the output. The data should appear in an event log format, with each row representing a distinct activity in the return process. Verify that columns like ReturnCaseId, ActivityName, and EventTime are populated as expected.
Save the Analysis: Once you are satisfied with the results, click the 'Save Analysis' icon. Give it a descriptive name, for example, 'ProcessMind Returns and Refund Extraction', and save it in a shared folder.
Create an Export Schedule: To automate the extraction, you can schedule the analysis to run regularly. From the Oracle BI home page, locate your saved analysis, click 'More', and select 'Schedule'.
Configure the Export Job: In the scheduling options, define the frequency (e.g., daily, weekly). In the 'Delivery' section, set the output format to CSV. Configure the destination, such as content server or email, where the output file will be sent. Activate the schedule to begin the automated extractions.

Configuration

Subject Areas: The primary subject areas for this analysis are "Sales - CRM All Lines" for RMA order headers, lines, and status history, and "Receivables - Transactions Real Time" for credit memo and refund payment details. Additional subject areas like "Inventory - Inventory Transactions Real Time" may be required if more granular details on inspection and disposition are needed.
Date Range Filtering: It is critical to apply a date range filter to limit the data volume and ensure the analysis completes successfully. We recommend extracting data for a period of 3 to 6 months at a time. The provided query filters on the RMA creation date.
Key Filters: Beyond the date range, you should filter on the Order Type to specifically select Return Material Authorization (RMA) orders. Filtering by a specific Business Unit or Legal Entity is also recommended to scope the data appropriately.
Logical SQL Mode: This extraction method requires using the 'Advanced' tab and writing a custom logical SQL query with UNION ALL statements. This approach is necessary to reshape the transactional data into the event log format required by ProcessMind.
Prerequisites: The user running this extraction needs a role with the necessary permissions to create and run OTBI analyses, such as the 'BI Author' role. Access to the specified Sales, Receivables, and potentially Inventory subject areas is also mandatory.

a Sample Query config

SELECT
    "Sales - CRM All Lines"."Order"."Order Number" AS "ReturnCaseId",
    'RMA Created' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Order"."Creation Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Order"."Created By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Order"."Header Status" AS "ReturnStatus",
    "Sales - CRM All Lines"."Order"."Order Amount" AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    "Sales - CRM All Lines"."Order"."Return Reason" AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Order Type" = 'Return'
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Approval Submitted' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Pending Approval' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Approved' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Awaiting Receiving' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Shipped By Customer' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: This event is not standard. Adapt if custom fields exist.
UNION ALL
SELECT
    "Sales - CRM All Lines"."Order"."Order Number" AS "ReturnCaseId",
    'Item Received' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Fulfillment Line"."Actual Arrival Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Fulfillment Line"."Last Updated By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Fulfillment Line"."Fulfillment Line Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Order Type" = 'Return' AND "Sales - CRM All Lines"."Fulfillment Line"."Actual Arrival Date" IS NOT NULL
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Inspection Started' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area or custom fields.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Inspected' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area or custom fields.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Return Disposition Determined' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area.
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Credit Memo Created' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Transaction Details"."Created By" AS "ProcessingAgent",
    "Receivables - Transactions Real Time"."Transaction Details"."Transaction Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Transaction Details"."Transaction Amount" AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo'
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Refund Initiated' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Receipt Application Details"."Application Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Created By" AS "ProcessingAgent",
    'Refund Initiated' AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Amount Applied" * -1 AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo'
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Refund Processed' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Receipt Application Details"."GL Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Created By" AS "ProcessingAgent",
    'Refund Processed' AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Amount Applied" * -1 AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo' AND "Receivables - Transactions Real Time"."Receipt Application Details"."GL Date" IS NOT NULL
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Customer Notified' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires integration with a notification or CRM system.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Return Case Closed' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Closed' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Rejected' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" IN ('Canceled', 'Rejected') AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Sales - CRM All Lines"."Order"."Return Reference Order Number" AS "ReturnCaseId",
    'Exchange Order Created' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Order"."Creation Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Order"."Created By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Order"."Header Status" AS "ReturnStatus",
    "Sales - CRM All Lines"."Order"."Order Amount" AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    "Sales - CRM All Lines"."Order"."Return Reason" AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Return Reference Order Number" IS NOT NULL
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'

Steps

Navigate to OTBI Analysis Editor: Log into your Oracle Fusion Cloud SCM instance. Use the Navigator menu to go to Tools, then select Reports and Analytics. Click the 'Create' button and choose 'Analysis' from the dropdown menu.
Select Subject Areas: In the 'Select Subject Area' popup, you must choose the primary subject areas that contain returns and refund data. Select "Sales - CRM All Lines" and "Receivables - Transactions Real Time". You will combine these to create a comprehensive view of the process.
Switch to Advanced Mode: After selecting the subject areas, the analysis editor will open. Immediately switch to the 'Advanced' tab to access the logical SQL editor, which is necessary for creating the required event log structure.
Construct the Event Log Query: Copy the complete logical SQL provided in the 'Query' section of this document and paste it into the 'SQL Query' text area on the Advanced tab. This query is structured with multiple UNION ALL clauses to retrieve each of the 15 required activities as separate rows.
Set Query Parameters: Modify the placeholder values within the query. Specifically, update the [START_DATE] and [END_DATE] placeholders to define the date range for your extraction. You may also need to adjust filters for specific Business Units or Return Order Types based on your organization's configuration.
Validate the Query: Click the 'Validate SQL' button to ensure the syntax is correct. The system will check the column names and structure against the selected subject areas.
Review the Results: Navigate to the 'Results' tab to preview the output. The data should appear in an event log format, with each row representing a distinct activity in the return process. Verify that columns like ReturnCaseId, ActivityName, and EventTime are populated as expected.
Save the Analysis: Once you are satisfied with the results, click the 'Save Analysis' icon. Give it a descriptive name, for example, 'ProcessMind Returns and Refund Extraction', and save it in a shared folder.
Create an Export Schedule: To automate the extraction, you can schedule the analysis to run regularly. From the Oracle BI home page, locate your saved analysis, click 'More', and select 'Schedule'.
Configure the Export Job: In the scheduling options, define the frequency (e.g., daily, weekly). In the 'Delivery' section, set the output format to CSV. Configure the destination, such as content server or email, where the output file will be sent. Activate the schedule to begin the automated extractions.

Configuration

Subject Areas: The primary subject areas for this analysis are "Sales - CRM All Lines" for RMA order headers, lines, and status history, and "Receivables - Transactions Real Time" for credit memo and refund payment details. Additional subject areas like "Inventory - Inventory Transactions Real Time" may be required if more granular details on inspection and disposition are needed.
Date Range Filtering: It is critical to apply a date range filter to limit the data volume and ensure the analysis completes successfully. We recommend extracting data for a period of 3 to 6 months at a time. The provided query filters on the RMA creation date.
Key Filters: Beyond the date range, you should filter on the Order Type to specifically select Return Material Authorization (RMA) orders. Filtering by a specific Business Unit or Legal Entity is also recommended to scope the data appropriately.
Logical SQL Mode: This extraction method requires using the 'Advanced' tab and writing a custom logical SQL query with UNION ALL statements. This approach is necessary to reshape the transactional data into the event log format required by ProcessMind.
Prerequisites: The user running this extraction needs a role with the necessary permissions to create and run OTBI analyses, such as the 'BI Author' role. Access to the specified Sales, Receivables, and potentially Inventory subject areas is also mandatory.

a Sample Query config

SELECT
    "Sales - CRM All Lines"."Order"."Order Number" AS "ReturnCaseId",
    'RMA Created' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Order"."Creation Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Order"."Created By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Order"."Header Status" AS "ReturnStatus",
    "Sales - CRM All Lines"."Order"."Order Amount" AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    "Sales - CRM All Lines"."Order"."Return Reason" AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Order Type" = 'Return'
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Approval Submitted' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Pending Approval' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Approved' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Awaiting Receiving' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Shipped By Customer' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: This event is not standard. Adapt if custom fields exist.
UNION ALL
SELECT
    "Sales - CRM All Lines"."Order"."Order Number" AS "ReturnCaseId",
    'Item Received' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Fulfillment Line"."Actual Arrival Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Fulfillment Line"."Last Updated By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Fulfillment Line"."Fulfillment Line Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Order Type" = 'Return' AND "Sales - CRM All Lines"."Fulfillment Line"."Actual Arrival Date" IS NOT NULL
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Inspection Started' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area or custom fields.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Item Inspected' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area or custom fields.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Return Disposition Determined' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires Inventory subject area.
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Credit Memo Created' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Transaction Details"."Created By" AS "ProcessingAgent",
    "Receivables - Transactions Real Time"."Transaction Details"."Transaction Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Transaction Details"."Transaction Amount" AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo'
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Refund Initiated' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Receipt Application Details"."Application Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Created By" AS "ProcessingAgent",
    'Refund Initiated' AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Amount Applied" * -1 AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo'
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Receivables - Transactions Real Time"."Transaction Details"."Reference Transaction Number" AS "ReturnCaseId",
    'Refund Processed' AS "ActivityName",
    CAST("Receivables - Transactions Real Time"."Receipt Application Details"."GL Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Created By" AS "ProcessingAgent",
    'Refund Processed' AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    "Receivables - Transactions Real Time"."Receipt Application Details"."Amount Applied" * -1 AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Receivables - Transactions Real Time"
WHERE "Receivables - Transactions Real Time"."Transaction Details"."Transaction Class" = 'Credit Memo' AND "Receivables - Transactions Real Time"."Receipt Application Details"."GL Date" IS NOT NULL
AND "Receivables - Transactions Real Time"."Transaction Details"."Transaction Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Customer Notified' AS "ActivityName",
    CAST(NULL AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime", NULL AS "ProcessingAgent", NULL AS "ReturnStatus", NULL AS "RequestedRefundAmount", NULL AS "ActualRefundAmount", NULL AS "ReturnReason", NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654 WHERE T4654."Order Type" = 'Return' AND 1=0 -- Placeholder: Requires integration with a notification or CRM system.
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'Return Case Closed' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" = 'Closed' AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    T4654."Order Number" AS "ReturnCaseId",
    'RMA Rejected' AS "ActivityName",
    CAST(T4663."Status Change Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    T4663."Updated By" AS "ProcessingAgent",
    T4663."New Status" AS "ReturnStatus",
    NULL AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    NULL AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines" T4649, "Sales - CRM All Lines"."Order" T4654, "Sales - CRM All Lines"."Header Status History" T4663
WHERE T4654."Order Key" = T4663."Order Key" AND T4654."Order Type" = 'Return' AND T4663."New Status" IN ('Canceled', 'Rejected') AND T4654."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'
UNION ALL
SELECT
    "Sales - CRM All Lines"."Order"."Return Reference Order Number" AS "ReturnCaseId",
    'Exchange Order Created' AS "ActivityName",
    CAST("Sales - CRM All Lines"."Order"."Creation Date" AS TIMESTAMP) AS "EventTime",
    'Oracle Fusion SCM' AS "SourceSystem",
    CURRENT_TIMESTAMP AS "LastDataUpdate",
    NULL AS "EndTime",
    "Sales - CRM All Lines"."Order"."Created By" AS "ProcessingAgent",
    "Sales - CRM All Lines"."Order"."Header Status" AS "ReturnStatus",
    "Sales - CRM All Lines"."Order"."Order Amount" AS "RequestedRefundAmount",
    NULL AS "ActualRefundAmount",
    "Sales - CRM All Lines"."Order"."Return Reason" AS "ReturnReason",
    NULL AS "RefundSlaTargetDate"
FROM "Sales - CRM All Lines"
WHERE "Sales - CRM All Lines"."Order"."Return Reference Order Number" IS NOT NULL
AND "Sales - CRM All Lines"."Order"."Creation Date" BETWEEN TIMESTAMP '[START_DATE]' AND TIMESTAMP '[END_DATE]'

Steps

Set Up Python Environment: Ensure you have Python 3.6 or newer installed. Install the necessary libraries using pip: pip install requests pandas.
Configure Oracle Fusion SCM Access: Obtain credentials for an Oracle Fusion user with the necessary roles to access REST APIs. Required roles typically include Order Manager and Accounts Receivable Manager. The user must have permissions to view sales orders (RMAs) and receivables credit memos.
Identify API Endpoints: Confirm the base URL for your Oracle Fusion SCM instance. The script uses the salesOrdersForOrderHub and receivablesCreditMemos REST resources. The version 11.13.18.05 may need to be adjusted to match your environment.
Customize the Python Script: Open the provided Python script. Update the placeholder variables at the top of the script: ORACLE_BASE_URL, ORACLE_USERNAME, and ORACLE_PASSWORD. Adjust the RMA_ORDER_TYPE variable to match the specific order type code used for RMAs in your system.
Define Extraction Period: Modify the START_DATE and END_DATE variables in the script to define the time window for the data extraction. It's recommended to start with a smaller period, for example, one month, to test the script.
Execute the Script: Run the script from your command line: python extract_oracle_returns.py. The script will connect to the Oracle APIs, fetch the data, process it, and print status updates to the console.
Retrieve the Event Log: Upon successful completion, the script will generate a file named returns_event_log.csv in the same directory. This file contains the extracted event log.
Review and Prepare for Upload: Open the returns_event_log.csv file in a spreadsheet application. Review the data for completeness and accuracy, paying special attention to the ActivityName and EventTime columns. Ensure the column headers match the requirements for your process mining tool.
Upload to ProcessMind: Upload the generated CSV file directly into ProcessMind. Map the columns from the CSV file to the corresponding attributes in ProcessMind (ReturnCaseId to Case ID, ActivityName to Activity, EventTime to Timestamp).

Configuration

API Endpoints: The script primarily uses two REST API endpoints: /fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub for RMA order data and /fscmRestApi/resources/11.13.18.05/receivablesCreditMemos for financial refund data.
Authentication: The script uses Basic Authentication. The provided username and password must be for a user account with API access and sufficient privileges to read order and receivables data.
Date Range: The extraction is filtered by the CreationDate of the RMA orders. Configure the START_DATE and END_DATE variables in the script. For initial loads, a period of 3-6 months is recommended. For ongoing refreshes, use a sliding window.
RMA Order Type Filter: It is critical to configure the RMA_ORDER_TYPE variable in the script. This ensures you are only extracting return orders and not standard sales orders. You can find your specific RMA order type code in the 'Manage Order Types' setup task in Oracle Fusion.
Status Code Mapping: The script maps Oracle's internal status codes (e.g., DOO_AWAITING_RECEIVING, DOO_CLOSED) to the business-friendly ActivityName values. This mapping may need to be customized based on your specific Oracle SCM configuration.
Prerequisites: Access to an Oracle Fusion SCM environment is required. The user account for the extraction must have roles like Order Manager (ORA_DOO_ORDER_MANAGER_JOB) and Accounts Receivable Manager (ORA_AR_ACCOUNTS_RECEIVABLE_MANAGER_JOB) or equivalent custom roles that grant access to the required REST APIs.

a Sample Query python

import requests
import pandas as pd
from datetime import datetime
import json

class=class="hl-string">"hl-comment"># --- Configuration Settings --- #
ORACLE_BASE_URL = class="hl-string">"https://[your_oracle_fusion_instance].fa.ocs.oraclecloud.com"
ORACLE_USERNAME = class="hl-string">"[your_api_user]"
ORACLE_PASSWORD = class="hl-string">"[your_api_password]"
RMA_ORDER_TYPE = class="hl-string">"ORA_RETURN_ORDER"  class=class="hl-string">"hl-comment"># IMPORTANT: Configure with your specific RMA Order Type Code
START_DATE = class="hl-string">"2023-01-01T00:00:00.000Z" class=class="hl-string">"hl-comment"># Format: YYYY-MM-DDTHH:MM:SS.sssZ
END_DATE = class="hl-string">"2023-06-30T23:59:59.000Z"

class=class="hl-string">"hl-comment"># --- Helper Functions --- #
def get_paginated_data(endpoint, params):
    class="hl-string">"""Fetches all data from a paginated Oracle REST API endpoint."""
    all_items = []
    url = fclass="hl-string">"{ORACLE_BASE_URL}{endpoint}"
    params[class="hl-string">'limit'] = 200 class=class="hl-string">"hl-comment"># Max limit can be up to 500
    params[class="hl-string">'offset'] = 0

    while True:
        print(fclass="hl-string">"Fetching data from {url} with offset {params['offset']}...")
        try:
            response = requests.get(url, auth=(ORACLE_USERNAME, ORACLE_PASSWORD), params=params)
            response.raise_for_status()
            data = response.json()
            items = data.get(class="hl-string">'items', [])
            if not items:
                break
            all_items.extend(items)
            if data.get(class="hl-string">'hasMore', False):
                params[class="hl-string">'offset'] += len(items)
            else:
                break
        except requests.exceptions.HTTPError as e:
            print(fclass="hl-string">"HTTP Error: {e}")
            print(fclass="hl-string">"Response content: {response.text}")
            break
        except json.JSONDecodeError as e:
            print(fclass="hl-string">"JSON Decode Error: {e}")
            print(fclass="hl-string">"Response content: {response.text}")
            break
    return all_items

class=class="hl-string">"hl-comment"># --- Main Extraction Logic --- #
if __name__ == class="hl-string">"__main__":
    event_log_records = []
    last_data_update = datetime.utcnow().isoformat() + class="hl-string">'Z'

    class=class="hl-string">"hl-comment"># 1. Fetch all RMA Orders
    print(class="hl-string">"Fetching RMA orders...")
    rma_params = {
        class="hl-string">'finder': class="hl-string">'findOrders',
        class="hl-string">'q': fclass="hl-string">"OrderTypeCode='{RMA_ORDER_TYPE}' and CreationDate between '{START_DATE}' and '{END_DATE}'",
        class="hl-string">'fields': class="hl-string">'OrderNumber,CreationDate,CreatedBy,LastUpdateDate,LastUpdatedBy,OrderStatus,ReturnReasonCode,CrossReference,lines',
        class="hl-string">'expand': class="hl-string">'lines.fulfillmentLines'
    }
    rma_orders = get_paginated_data(class="hl-string">"/fscmRestApi/resources/11.13.18.05/salesOrdersForOrderHub", rma_params)

    class=class="hl-string">"hl-comment"># 2. Fetch all related Credit Memos (can be optimized by filtering on creation date)
    print(class="hl-string">"Fetching Credit Memos...")
    cm_params = {
        class="hl-string">'fields': class="hl-string">'TransactionNumber,TransactionDate,Amount,CustomerTransactionId,SalesOrderNumber'
    }
    credit_memos = get_paginated_data(class="hl-string">"/fscmRestApi/resources/11.13.18.05/receivablesCreditMemos", cm_params)
    cm_map = {cm[class="hl-string">'SalesOrderNumber']: cm for cm in credit_memos if class="hl-string">'SalesOrderNumber' in cm}

    print(fclass="hl-string">"Processing {len(rma_orders)} RMA orders...")
    for rma in rma_orders:
        case_id = rma.get(class="hl-string">'OrderNumber')
        if not case_id:
            continue

        class=class="hl-string">"hl-comment"># Helper to add events
        def add_event(activity, timestamp, agent, status, reason=None, end_time=None):
            if timestamp:
                event_log_records.append({
                    class="hl-string">'ReturnCaseId': case_id,
                    class="hl-string">'ActivityName': activity,
                    class="hl-string">'EventTime': timestamp,
                    class="hl-string">'EndTime': end_time if end_time else timestamp,
                    class="hl-string">'SourceSystem': class="hl-string">'Oracle Fusion SCM',
                    class="hl-string">'LastDataUpdate': last_data_update,
                    class="hl-string">'ProcessingAgent': agent,
                    class="hl-string">'ReturnStatus': status,
                    class="hl-string">'ReturnReason': reason,
                    class="hl-string">'RequestedRefundAmount': None, class=class="hl-string">"hl-comment"># Placeholder
                    class="hl-string">'ActualRefundAmount': None, class=class="hl-string">"hl-comment"># Placeholder
                    class="hl-string">'RefundSlaTargetDate': None class=class="hl-string">"hl-comment"># Placeholder
                })

        class=class="hl-string">"hl-comment"># Activity: RMA Created
        add_event(class="hl-string">'RMA Created', rma.get(class="hl-string">'CreationDate'), rma.get(class="hl-string">'CreatedBy'), class="hl-string">'Draft', rma.get(class="hl-string">'ReturnReasonCode'))

        class=class="hl-string">"hl-comment"># Activities from Fulfillment Lines
        if class="hl-string">'lines' in rma and rma[class="hl-string">'lines']:
            for line in rma[class="hl-string">'lines'][class="hl-string">'items']:
                if class="hl-string">'fulfillmentLines' in line and line[class="hl-string">'fulfillmentLines']:
                    for ff_line in line[class="hl-string">'fulfillmentLines'][class="hl-string">'items']:
                        ff_status = ff_line.get(class="hl-string">'StatusCode')
                        last_update = ff_line.get(class="hl-string">'LastUpdateDate', rma.get(class="hl-string">'LastUpdateDate'))
                        agent = ff_line.get(class="hl-string">'LastUpdatedBy', rma.get(class="hl-string">'LastUpdatedBy'))

                        class=class="hl-string">"hl-comment"># The following is an inference based on typical status flows.
                        class=class="hl-string">"hl-comment"># Your specific statuses may vary.
                        if ff_status in [class="hl-string">'DOO_AWAIT_APPROVAL', class="hl-string">'DOO_SUBMITTED']:
                            add_event(class="hl-string">'RMA Approval Submitted', last_update, agent, ff_status)
                        elif ff_status == class="hl-string">'DOO_AWAIT_RECEIVING':
                            add_event(class="hl-string">'RMA Approved', last_update, agent, ff_status)
                        elif ff_status in [class="hl-string">'DOO_PARTIALLY_FULFILLED', class="hl-string">'DOO_SHIPMENT_CONFIRMED']:
                             add_event(class="hl-string">'Item Received', ff_line.get(class="hl-string">'ActualShipDate', last_update), agent, ff_status)
                             class=class="hl-string">"hl-comment"># Infer inspection events based on receipt
                             add_event(class="hl-string">'Item Inspection Started', ff_line.get(class="hl-string">'ActualShipDate', last_update), agent, class="hl-string">'Awaiting Inspection')
                             add_event(class="hl-string">'Item Inspected', last_update, agent, class="hl-string">'Inspection Complete')
                        elif ff_status == class="hl-string">'DOO_AWAIT_BILLING':
                            add_event(class="hl-string">'Return Disposition Determined', last_update, agent, ff_status)
                        elif ff_status == class="hl-string">'DOO_CLOSED':
                            add_event(class="hl-string">'Return Case Closed', last_update, agent, ff_status)
                        elif ff_status in [class="hl-string">'DOO_CANCELED', class="hl-string">'DOO_REJECTED']:
                            add_event(class="hl-string">'RMA Rejected', last_update, agent, ff_status)
                        
                        class=class="hl-string">"hl-comment"># Placeholder activities not directly available
                        add_event(class="hl-string">'Item Shipped By Customer', None, class="hl-string">'Customer', class="hl-string">'In Transit')
                        add_event(class="hl-string">'Customer Notified', None, class="hl-string">'System', class="hl-string">'Notification Sent')

        class=class="hl-string">"hl-comment"># Activity: Exchange Order Created
        if rma.get(class="hl-string">'CrossReference'):
             add_event(class="hl-string">'Exchange Order Created', rma.get(class="hl-string">'LastUpdateDate'), rma.get(class="hl-string">'LastUpdatedBy'), rma.get(class="hl-string">'OrderStatus'))

        class=class="hl-string">"hl-comment"># Activities from Credit Memos
        if case_id in cm_map:
            cm = cm_map[case_id]
            cm_date = cm.get(class="hl-string">'TransactionDate')
            cm_amount = cm.get(class="hl-string">'Amount')
            add_event(class="hl-string">'Credit Memo Created', cm_date, class="hl-string">'System', class="hl-string">'Credit Memo Issued')
            add_event(class="hl-string">'Refund Initiated', cm_date, class="hl-string">'System', class="hl-string">'Refund In Progress')
            class=class="hl-string">"hl-comment"># Assuming refund is processed shortly after creation for this example
            add_event(class="hl-string">'Refund Processed', cm_date, class="hl-string">'System', class="hl-string">'Refund Complete')

            class=class="hl-string">"hl-comment"># Update refund amounts on all events for this case
            for rec in event_log_records:
                if rec[class="hl-string">'ReturnCaseId'] == case_id:
                    rec[class="hl-string">'ActualRefundAmount'] = cm_amount
                    rec[class="hl-string">'RequestedRefundAmount'] = cm_amount class=class="hl-string">"hl-comment"># Assuming requested equals actual

    class=class="hl-string">"hl-comment"># 4. Create and Save DataFrame
    if not event_log_records:
        print(class="hl-string">"No events were generated. Check your configuration and date range.")
    else:
        df = pd.DataFrame(event_log_records)
        df[class="hl-string">'EventTime'] = pd.to_datetime(df[class="hl-string">'EventTime'], errors=class="hl-string">'coerce')
        df = df.dropna(subset=[class="hl-string">'EventTime'])
        df = df.sort_values(by=[class="hl-string">'ReturnCaseId', class="hl-string">'EventTime'])

        class=class="hl-string">"hl-comment"># Reorder columns
        column_order = [
            class="hl-string">'ReturnCaseId', class="hl-string">'ActivityName', class="hl-string">'EventTime', class="hl-string">'EndTime', class="hl-string">'SourceSystem', class="hl-string">'LastDataUpdate',
            class="hl-string">'ProcessingAgent', class="hl-string">'ReturnStatus', class="hl-string">'ReturnReason', class="hl-string">'RequestedRefundAmount', 
            class="hl-string">'ActualRefundAmount', class="hl-string">'RefundSlaTargetDate'
        ]
        df = df[column_order]

        df.to_csv(class="hl-string">'returns_event_log.csv', index=False)
        print(class="hl-string">"Successfully created returns_event_log.csv")

Your Returns & Refund Processing Data Template

Your Returns & Refund Processing Data Template

Returns & Refund Processing Attributes

Returns & Refund Processing Activities

Extraction Guides

Oracle Transactional Business Intelligence (OTBI) Export

Steps

Configuration

a Sample Query config

Oracle BI Cloud Connector (BICC) View Object Extraction

Steps

Configuration

a Sample Query config

Python Script using Oracle Fusion SCM REST APIs

Steps

Configuration

a Sample Query python

Ready to Get Started?

Stop Bottlenecks, Optimize Returns & Refund Processing Now

Your Returns & Refund Processing Data Template

Your Returns & Refund Processing Data Template

Returns & Refund Processing Attributes

Returns & Refund Processing Activities

Extraction Guides

Oracle Transactional Business Intelligence (OTBI) Export

Steps

Configuration

a Sample Query config

Oracle BI Cloud Connector (BICC) View Object Extraction

Steps

Configuration

a Sample Query config

Python Script using Oracle Fusion SCM REST APIs

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Stop Bottlenecks, Optimize Returns & Refund Processing Now