> Continuous Process Improvement > Lead to Cash > Oracle CX Sales > Data Template

Your Lead to Cash Data Template

Oracle CX Sales

Lead to Cash Attributes (21) Lead to Cash Activities (14) Extraction Guides (2)

Your Lead to Cash Data Template

This template guides you through preparing your Lead to Cash data for process mining. It outlines the essential attributes to collect, key activities to track, and provides valuable guidance for extracting this information from Oracle CX Sales. By following this template, you can ensure a comprehensive and accurate analysis of your process.

Recommended attributes for Lead to Cash analysis
Key activities to track across your sales and payment cycles
Detailed guidance for data extraction from Oracle CX Sales

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

Download Template

Lead to Cash Attributes

These are the recommended data fields to include in your event log for a comprehensive analysis of your Lead to Cash process.

5 Required 5 Recommended 11 Optional

	Name	Description
	Activity Name ActivityName	The name of the business activity or event that occurred at a specific point in time for a sales opportunity.
Description This attribute describes a specific step or milestone in the Lead to Cash process, such as 'Lead Converted To Opportunity', 'Quote Created', or 'Payment Received'. These activities are the fundamental building blocks of the process map. Analyzing the sequence and frequency of these activities helps to visualize the process flow, identify common and alternative paths, and detect deviations or bottlenecks. It forms the basis for measuring transition times between steps and understanding how work is actually performed. Why it matters This attribute is fundamental for constructing the process map and understanding the sequence of events within the sales lifecycle. Where to get Typically derived from status changes, event logs, or specific task completion records associated with Opportunity, Quote, or Order objects. Examples Opportunity QualifiedQuote Sent To CustomerOrder FulfilledPayment Received
	Event Time EventTime	The timestamp indicating when a specific activity or event occurred.
Description The Event Time is the date and time that an activity was recorded. It is essential for ordering events chronologically and calculating the duration between different steps in the process. This timestamp is the basis for all time-based analysis, including calculating cycle times, identifying bottlenecks by measuring wait times, and monitoring performance against service level agreements. Accurate timestamps are critical for a reliable process mining analysis. Why it matters It provides the chronological order of events, which is essential for calculating all performance metrics like cycle times and durations. Where to get This corresponds to the creation date or last update date of records related to specific activities, such as status change timestamps. Examples 2023-04-15T10:00:00Z2023-05-01T14:30:00Z2023-05-20T09:15:00Z
	Sales Opportunity SalesOpportunity	The unique identifier for a sales opportunity, which serves as the case for the Lead to Cash process.
Description The Sales Opportunity is the central object that tracks a potential revenue-generating deal from its initial stage as a lead to its final resolution as a win or loss. It connects all related activities, such as qualification, quoting, ordering, and payment. In process mining analysis, this identifier is crucial for reconstructing the end-to-end journey of each deal. It allows for the analysis of the entire lifecycle, including cycle times between stages, conversion rates, and the identification of paths that lead to successful outcomes versus those that result in lost deals. Why it matters It is the essential Case ID that links all process events together, enabling a complete and accurate view of the entire sales lifecycle for each potential deal. Where to get This is a primary identifier in the Oracle CX Sales Opportunity object. Examples OPP-0012345OPP-0023456OPP-0034567
	Last Data Update LastDataUpdate	The timestamp when the data was last refreshed or extracted from the source system.
Description This attribute indicates the freshness of the data being analyzed. It shows the date and time of the last data pull from Oracle CX Sales. In dashboards and reports, this timestamp is critical for informing users about the timeliness of the data they are viewing. It helps manage expectations about whether the most recent activities are included in the analysis. Why it matters Informs users about the timeliness of the data, which is crucial for interpreting dashboards and making informed decisions. Where to get This timestamp is generated and added during the data extraction, transformation, and loading (ETL) process. Examples 2024-06-10T02:00:00Z
	Source System SourceSystem	The system from which the data was extracted.
Description This attribute identifies the origin of the process data, which is Oracle CX Sales in this context. In environments with multiple systems, this field helps distinguish data sources. For analysis, it provides context about the data's origin, which can be important when blending data from multiple systems or understanding system-specific behaviors. It is a standard field for data governance and traceability. Why it matters Provides essential context for data origin, ensuring traceability and helping to manage data from potentially multiple integrated systems. Where to get This is typically a static value added during the data extraction process to label the source of the data. Examples Oracle CX Sales
	Loss Reason LossReason	The reason cited for why an opportunity was lost.
Description When an opportunity is closed without a sale, the Loss Reason captures the primary cause, such as 'Lost to Competitor', 'Price', or 'No Decision'. This information is vital for strategic analysis and process improvement. This attribute is the cornerstone of the 'Opportunity Loss & Drop-Off Reasons' dashboard. Analyzing loss reasons in conjunction with the stage where the loss occurred helps businesses understand their competitive weaknesses and refine their sales strategy, product offerings, or pricing models. Why it matters Provides critical insights into why deals are not won, enabling strategic improvements to the sales process and product offerings. Where to get This is a standard field captured when an opportunity status is set to 'Closed Lost' in Oracle CX Sales. Examples PriceLost to CompetitorProduct FitNo Decision
	Opportunity Owner OpportunityOwner	The sales representative primarily responsible for the sales opportunity.
Description The Opportunity Owner is the individual user assigned to manage and close the deal. This attribute allows for performance analysis at the individual or team level. In process mining, filtering by Opportunity Owner can reveal different working patterns, performance benchmarks, and compliance with the standard sales process. It helps sales managers identify coaching opportunities and understand how top performers navigate the sales cycle. Why it matters Enables performance analysis by sales representative or team, helping to identify best practices and areas for coaching. Where to get Available as a standard 'Owner' or 'AssignedTo' field on the Opportunity object in Oracle CX Sales. Examples John SmithJane DoePeter Jones
	Opportunity Value OpportunityValue	The estimated or actual monetary value of the sales opportunity.
Description This attribute represents the potential or final revenue associated with a sales opportunity. It can be used to segment and prioritize opportunities throughout their lifecycle. In process mining, analyzing Opportunity Value helps to understand how different process variants impact high-value versus low-value deals. It is essential for dashboards that track revenue leakage, such as the 'Opportunity Loss & Drop-Off Reasons' analysis, by correlating process paths with financial outcomes. Why it matters It allows for the financial impact of process inefficiencies to be quantified and helps prioritize opportunities and improvement efforts. Where to get Likely available in a field such as 'Revenue' or 'Amount' on the Opportunity object in Oracle CX Sales. Examples 50000.00125000.0025000.00
	Region Region	The geographical region or sales territory associated with the opportunity.
Description The Region attribute categorizes opportunities based on their geographic location, such as 'North America', 'EMEA', or 'APAC'. This is a common dimension for segmenting business performance. This attribute is essential for the 'Regional Sales Performance Benchmarks' dashboard. It allows for comparing key metrics like sales cycle time, conversion rates, and process variants across different regions to identify high-performing areas and those requiring targeted improvements. Why it matters Enables comparison of process performance across different geographical areas, revealing regional variations and best practices. Where to get Often available as a standard or custom field on the Account or Opportunity object in Oracle CX Sales. Examples North AmericaEMEAAPACLATAM
	Sales Stage SalesStage	The current stage of the sales opportunity within the sales pipeline.
Description The Sales Stage indicates the progress of an opportunity through the defined sales process, with values like 'Qualification', 'Solution Proposed', or 'Negotiation'. It is a key attribute for understanding the state of an opportunity at any given time. This attribute is fundamental for building sales funnel visualizations and for the 'Stalled Opportunity Stage Analysis' dashboard. By analyzing the time spent in each stage, teams can identify where deals are slowing down and focus their efforts on unblocking the pipeline. Why it matters It is critical for sales funnel analysis and identifying bottlenecks where opportunities frequently stall or are lost. Where to get This is a standard field on the Opportunity object in Oracle CX Sales, often named 'SalesStage' or 'StageName'. Examples 01 - Qualification03 - Proposal05 - NegotiationClosed Won
	Customer Name CustomerName	The name of the customer or account associated with the sales opportunity.
Description This attribute identifies the prospective or existing customer for the deal. It is a fundamental dimension for segmenting and analyzing the sales process. Filtering by customer allows for a detailed analysis of the sales journey for specific accounts, which can be useful for key account management. It also enables segmentation of process performance by customer size, industry, or other characteristics to tailor sales approaches. Why it matters Allows for process analysis to be segmented by customer, which is key for understanding customer-specific behaviors and managing key accounts. Where to get The Account Name linked to the Opportunity object in Oracle CX Sales. Examples Global Tech Inc.Innovate Solutions LLCPioneer Corp
	Discount Percentage DiscountPercentage	The discount percentage applied to the sales quote or opportunity.
Description This attribute records the percentage discount given on a particular deal. It directly impacts the final price and profitability of the sale. Analyzing discount levels is crucial for the 'Average Discount Utilization' KPI. It helps businesses understand the impact of discounting on margins and can reveal if discounts are being applied inconsistently or without proper approval, highlighting potential issues in the quote approval workflow. Why it matters Helps in analyzing profitability and the effectiveness of discount strategies, and identifying potential uncontrolled discounting. Where to get Consult Oracle CX Sales documentation for a discount field on the Quote or Opportunity Product Line Item objects. Examples 0.050.100.150.20
	Invoice Before Fulfillment InvoiceBeforeFulfillment	A flag indicating if an invoice was generated before the order was fulfilled.
Description This boolean attribute is set to true if the 'Invoice Generated' event occurs before the 'Order Fulfilled' event for a particular case. This represents a non-compliant or risky process path. This attribute directly supports the 'Invoice Before Fulfillment Rate' KPI and is used in process compliance dashboards. Tracking this deviation helps organizations enforce proper billing procedures, reduce customer disputes, and mitigate revenue recognition risks. Why it matters Flags a critical process compliance violation where customers are billed before an order is fulfilled, which can lead to customer dissatisfaction and financial risk. Where to get Calculated by comparing the timestamps of the 'Invoice Generated' and 'Order Fulfilled' activities within the same case. Examples truefalse
	Invoice ID InvoiceId	The unique identifier for the invoice generated for a sales order.
Description The Invoice ID is the reference number for the billing document sent to the customer after an order is fulfilled. It is the key document in the final financial stages of the process. This identifier is essential for analyzing the 'Invoice Generation Cycle Time' and 'Payment Collection Cycle'. It allows for tracking each invoice from creation to final payment, which is critical for monitoring cash flow and accounts receivable performance. Why it matters Tracks the final financial transaction, which is essential for analyzing billing cycle times and payment collection efficiency. Where to get Consult Oracle CX Sales documentation or integrated ERP/financial system for the Invoice object identifier. Examples INV-2023-001INV-2023-002INV-2023-003
	Is Quote Rework IsQuoteRework	A flag indicating if a quote has been reworked or created more than once for the same opportunity.
Description This boolean attribute is set to true if an activity like 'Quote Reworked' or a second 'Quote Created' event occurs for a single sales opportunity. It helps to isolate instances of process inefficiency in the quoting stage. This flag is used to calculate the 'Quote Rework Rate' KPI and to power the 'Process Deviation & Rework Analysis' dashboard. Highlighting rework helps pinpoint issues with initial requirement gathering, pricing, or product configuration that lead to additional effort and delays. Why it matters Directly flags instances of inefficiency and deviation in the quoting process, helping to identify root causes of delays and repeated work. Where to get Calculated by analyzing the event log. It is true if the 'Quote Created' or 'Quote Reworked' activity appears more than once for a given Sales Opportunity. Examples truefalse
	Is Stalled IsStalled	A flag indicating if an opportunity has remained in the same sales stage for an excessive period.
Description This attribute is a boolean flag that is set to true when the time between two consecutive activities for an opportunity exceeds a predefined business threshold (e.g., 30 days). It is used to calculate the 'Stalled Opportunity Rate' KPI and is essential for the 'Stalled Opportunity Stage Analysis' dashboard. Identifying stalled deals allows sales managers to intervene proactively, provide support, and improve the overall velocity of the sales pipeline. Why it matters Helps to proactively identify deals that are at risk of being lost due to inaction, enabling timely intervention. Where to get Calculated by measuring the time between consecutive events for a case and comparing it against a defined threshold. Examples truefalse
	Order ID OrderId	The unique identifier for the sales order created from a won opportunity.
Description The Order ID is the reference for the official sales order that is sent for fulfillment after a customer accepts a quote and the opportunity is won. It marks a key transition from sales to operations. This identifier is critical for tracking the process from the 'Order Submitted For Fulfillment' activity onwards. It helps bridge the sales and fulfillment portions of the Lead to Cash cycle, enabling end-to-end analysis of order processing and fulfillment times. Why it matters Links the sales opportunity to the fulfillment process, enabling true end-to-end analysis from lead to final delivery. Where to get Consult Oracle CX Sales documentation or integrated ERP system for the primary identifier of the Sales Order object. Examples SO-554433SO-554434SO-554435
	Product Name ProductName	The primary product or service being sold in the opportunity.
Description This attribute specifies the product or product family associated with the sales opportunity. For opportunities with multiple products, this might represent the primary product of interest or be repeated for each product line item. Analyzing process flows by product can reveal whether certain products have longer or more complex sales cycles. This insight can inform product-specific sales strategies, training, and process optimization efforts. Why it matters Enables analysis of how the sales process differs for various products or services, highlighting product-specific bottlenecks. Where to get Found in the Product object, linked via the Opportunity Product Line Item in Oracle CX Sales. Examples Enterprise CRM LicenseCloud Storage Tier 1Professional Services Package
	Quote ID QuoteId	The unique identifier for a sales quote associated with an opportunity.
Description The Quote ID is the reference number for a specific sales quote document generated for an opportunity. An opportunity may have multiple quotes over its lifecycle, especially if rework occurs. Tracking this identifier is important for analyzing the 'Quote-to-Order Cycle Time' and 'Quote Rework Rate'. It allows for precise measurement of the time from quote issuance to acceptance and helps to distinguish between initial quotes and revised versions. Why it matters Uniquely identifies sales quotes, enabling accurate analysis of the quoting cycle, including rework and conversion times. Where to get This is the primary identifier of the Quote object in Oracle CX Sales, which is related to the Opportunity. Examples QUO-98765QUO-98766QUO-98767
	Sales Cycle Time SalesCycleTime	The total duration of the sales opportunity from creation to being closed.
Description This metric calculates the total time elapsed from the first event (e.g., 'Lead Converted To Opportunity') to the last event (e.g., 'Opportunity Won' or 'Opportunity Lost') for each case. This is a key performance indicator used in the 'End-to-End Sales Cycle Performance' dashboard. Analyzing its average and distribution helps identify systemic delays in the overall sales process and provides a high-level benchmark for process improvement initiatives. Why it matters Provides a critical KPI for measuring the overall efficiency and speed of the entire sales process. Where to get Calculated by subtracting the timestamp of the first event from the timestamp of the last event for each Sales Opportunity. Examples 30 days 10:05:0095 days 02:00:0045 days 12:30:00
	User Name UserName	The user who performed a specific activity or event.
Description This attribute identifies the specific person who executed a task, such as 'Quote Created' or 'Order Submitted'. While the Opportunity Owner is responsible for the overall deal, the User Name tracks who performed individual actions. This level of detail is useful for understanding resource allocation, workload distribution, and adherence to roles and responsibilities. It can help identify if certain users are process bottlenecks or if specific tasks are consistently handled by unauthorized personnel. Why it matters Tracks who performed each specific action, allowing for detailed workload analysis and auditing of activities. Where to get Typically found in 'CreatedBy' or 'LastUpdatedBy' fields on objects related to activities in Oracle CX Sales. Examples Alice WilliamsBob BrownCharlie Davis

Required Recommended Optional

Lead to Cash Activities

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

6 Recommended 8 Optional

	Activity	Description
	Lead Converted To Opportunity	Marks the creation of a Sales Opportunity from a qualified Sales Lead. This event is the starting point for the opportunity-centric process analysis and is explicitly triggered when a user converts a lead in the system.
Why it matters This is the primary start event for the process. Analyzing the volume and source of converted leads is crucial for understanding the effectiveness of lead generation and qualification efforts. Where to get This event is captured from the creation of a Sales Opportunity record (Opportunity object) where the 'LeadId' or a similar source field is populated, indicating its origin from a converted lead. Capture Capture the creation timestamp of the Opportunity object that has a non-null originating Lead reference. Event type explicit
	Opportunity Lost	Represents an unsuccessful outcome where the opportunity is closed without a sale. This is inferred when the opportunity's status is updated to 'Closed - Lost'.
Why it matters This is a critical failure endpoint. Analyzing when, why, and at what value opportunities are lost helps identify process weaknesses and market challenges. Where to get Inferred from an update to the 'StatusCode' on the Opportunity object to a 'LOST' value. The 'ReasonWonLostCode' field often provides context. Capture Detect when the Opportunity status field is updated to the system-defined 'Lost' status. Event type inferred
	Opportunity Won	Represents the successful closing of a deal, where the customer has committed to the purchase. This is inferred from the opportunity's status changing to a final 'Closed - Won' state.
Why it matters This is the primary success milestone in the sales funnel. It is the trigger for downstream fulfillment and billing processes. Where to get Inferred from an update to the 'StatusCode' on the Opportunity object to a 'WON' value. The 'WinProb' (Win Probability) field also typically changes to 100%. Capture Detect when the Opportunity status field is updated to the system-defined 'Won' status. Event type inferred
	Payment Received	Marks the final, successful completion of the Lead to Cash cycle where the customer's payment has been received and recorded. This event originates from a financial system.
Why it matters This is the final success endpoint of the process, signifying revenue realization. It is crucial for measuring the overall sales cycle time and cash flow efficiency. Where to get Sourced from an external Accounts Receivable or financial system. Data must be linked back to the Sales Opportunity to close the loop on the process analysis. Capture Event timestamp is from the payment application record in the financial system. Event type explicit
	Quote Accepted By Customer	Indicates the customer has formally agreed to the terms and pricing in the quote. This is a critical milestone, often captured by a status change on the Quote object to 'Accepted'.
Why it matters This is a key buying signal and a prerequisite for creating a sales order. It marks the successful conclusion of the negotiation phase and is a milestone in the Quote-to-Order cycle. Where to get Inferred from a status change on the Quote object to an 'Accepted' or 'Customer Approved' status. Capture Detect change in the Quote object's status field to a designated 'Accepted' value. Event type inferred
	Quote Created	Represents the generation of a formal price quote document associated with the opportunity. This is an explicit event marked by the creation of a new Quote record linked to the opportunity.
Why it matters This is a major milestone indicating serious sales intent. Analyzing the time from opportunity creation to quote creation helps measure sales velocity. Where to get Captured from the creation event of a Quote record (Q_Quote object) that is linked to the Sales Opportunity ID (OptyId). Capture Use the creation timestamp of the Quote object associated with the opportunity. Event type explicit
	Invoice Generated	Represents the creation of a customer invoice for the fulfilled order. This activity occurs in a billing or financial system, not Oracle CX Sales, and the data must be integrated.
Why it matters This event starts the payment collection cycle. Delays between fulfillment and invoicing can negatively impact cash flow and the 'Invoice to Payment Cycle Time' KPI. Where to get Sourced from an external ERP or Accounts Receivable system. The event data must be correlated with the Sales Opportunity ID for process analysis. Capture Event timestamp is sourced from the financial system's invoice creation log. Event type explicit
	Needs Analysis Completed	Signifies that the sales team has gathered and documented the customer's requirements. This is usually inferred from the opportunity's sales stage advancing past the discovery or analysis phase.
Why it matters This activity is a critical milestone before a solution can be proposed. Delays here can indicate issues with customer engagement or resource availability for technical deep dives. Where to get Inferred from a change in the 'Sales Stage' field on the Opportunity object, for instance, moving from '2 - Discovery' to '3 - Solution Building'. Capture Detect a change in the Opportunity's sales stage field to a status indicating discovery is complete. Event type inferred
	Opportunity Qualified	Represents the completion of the initial qualification stage for an opportunity. This is typically inferred when the sales stage of the opportunity is updated to reflect that initial vetting is complete and it's a viable opportunity.
Why it matters Tracking this milestone helps measure the efficiency of the early sales process and identifies how long opportunities spend in qualification, which is key for the Lead to Opportunity Conversion Rate KPI. Where to get Inferred from a change in the 'Sales Stage' field (StgId) on the Opportunity object to a value representing qualification, for example, moving from '1 - Qualification' to '2 - Discovery'. Capture Detect a change in the Opportunity's sales stage field to a designated 'Qualified' status. Event type inferred
	Order Fulfilled	Indicates that the products have been shipped or services have been delivered to the customer. This event data is not native to Oracle CX Sales and must be sourced from an integrated Order Management or ERP system.
Why it matters Marks the completion of the delivery promise to the customer and is the trigger for invoicing. It is essential for measuring fulfillment cycle times. Where to get Requires integration with an external ERP or fulfillment system. The data would need to be linked back to the originating Sales Opportunity ID. Capture Event timestamp is pulled from the fulfillment system via an integration. Event type explicit
	Order Submitted For Fulfillment	Marks the handoff from sales to the order fulfillment team. In Oracle CX Sales, this might be inferred when the opportunity is won, triggering a process to create a Sales Order in an integrated ERP system.
Why it matters This activity bridges the gap between sales and operations. Analyzing this handoff is critical for understanding and optimizing the 'Order Fulfillment Time' KPI. Where to get This event is often conceptual within CX Sales itself and represents the trigger for order creation in a separate system. It can be associated with the 'Opportunity Won' timestamp or a subsequent integration confirmation status. Capture Often uses the 'Opportunity Won' timestamp as a proxy, or requires data from an integrated Order Management system. Event type inferred
	Quote Reworked	Captures instances where a quote is revised and re-issued to the customer. This is inferred by observing multiple 'Quote Created' events for the same opportunity or versioning of a single quote record.
Why it matters Frequent rework can indicate inaccurate initial proposals or lengthy negotiations, extending the sales cycle. This directly supports the 'Quote Rework Rate' KPI and rework analysis dashboards. Where to get Inferred by detecting a new version of a Quote being created or a significant update to an existing quote (e.g., status reset to draft) after it has already been sent to the customer. Capture Identify subsequent 'Quote Created' events or version increments for the same opportunity. Event type inferred
	Quote Sent To Customer	Marks the point when a quote is formally delivered to the customer for review. This event is typically inferred from a status change on the Quote object itself, such as moving to 'Presented' or 'Sent'.
Why it matters This activity starts the clock on customer review and negotiation cycles. It's the starting point for measuring the 'Quote to Order Creation Time' KPI. Where to get Inferred from a status change on the Quote object associated with the opportunity. The status field may be named 'StatusCode' or similar. Capture Detect change in the Quote object's status field to a 'Sent' or 'Presented' value. Event type inferred
	Solution Proposed	Indicates that a formal solution or proposal has been presented to the customer. This activity is inferred when an opportunity moves into a 'Proposal' or 'Presentation' stage.
Why it matters Tracking this helps analyze the time taken to develop and propose solutions. It is also a key stage for the 'Stalled Opportunity Rate' KPI, as opportunities often linger here. Where to get Inferred from a change in the 'Sales Stage' field on the Opportunity object to a value like '4 - Proposal' or 'Presentation'. Capture Detect a change in the Opportunity's sales stage field to the proposal status. Event type inferred

Recommended Optional

Extraction Guides

How to get your data from Oracle CX Sales

Steps

Prerequisites and Authentication: Ensure you have a user account in Oracle CX Sales with the necessary privileges, such as Sales Administrator or a similar role, to access the REST APIs for opportunities and quotes. Obtain OAuth 2.0 client credentials (Client ID and Client Secret) from your Oracle Cloud administrator to authenticate API requests and generate a bearer token.
Environment Setup: Set up a Node.js environment on your local machine or a server. Install necessary libraries for making HTTP requests and handling CSV files. Open a terminal and run the following commands: npm install axios npm install json2csv
Identify API Endpoints: The primary endpoints for this extraction are for the Opportunity and Quote objects. The base URL will be specific to your Oracle instance, for example, https://[your-oracle-cx-cloud-host].fa.us2.oraclecloud.com. The key resources are:

Opportunities: /salesApi/resources/latest/opportunities
Quotes (as a child of Opportunity): /salesApi/resources/latest/opportunities/{OptyId}/child/Quote

Configure the Extraction Script: Copy the provided JavaScript code into a file, for example, extract.js. Update the placeholder variables at the top of the script with your specific Oracle CX Cloud host URL, client ID, client secret, and the desired date range for the extraction.
Execute the Script: Run the script from your terminal using the command: node extract.js. The script will first obtain an authentication token, then begin fetching opportunities page by page from the API.
Data Retrieval and Paging: The script automatically handles API pagination. It requests a set number of opportunities per call and uses the offset parameter to request subsequent pages until all opportunities within the specified date range have been retrieved.
Fetch Related Quote Data: For each opportunity retrieved, the script makes a secondary API call to fetch all associated quotes. This data is crucial for generating quote-related activities like 'Quote Created' and 'Quote Accepted'.
Data Transformation to Event Log: The core logic of the script processes each opportunity and its associated quotes. It transforms this hierarchical JSON data into a flat, tabular event log. It generates a distinct row for each business activity, inferring events from status codes, sales stages, and creation dates as required.
Handle External Data Dependencies: Note that activities like 'Order Fulfilled', 'Invoice Generated', and 'Payment Received' occur in external systems. The script generates placeholder activities for the sales-to-fulfillment handoff. You must extract data from your ERP or financial systems separately and merge it with this event log using SalesOpportunity as the common key.
Export to CSV: Once all data is fetched and transformed, the script uses the json2csv library to convert the final array of event log records into a CSV file named oracle_cx_sales_event_log.csv. This file will be saved in the same directory where the script was executed.
Prepare for Upload: Review the generated CSV file for correctness and completeness. The file is formatted with the required columns (SalesOpportunity, ActivityName, EventTime, etc.) and is ready to be uploaded to ProcessMind for analysis.

Configuration

API Host URL: The base URL for your Oracle CX Sales environment, for example, https://[your-instance].fa.us2.oraclecloud.com.
Authentication: The script uses OAuth 2.0 with a Client ID and Client Secret for server-to-server authentication. These credentials must be provisioned in your Oracle Cloud identity management settings.
Date Range: The script filters opportunities based on the LastUpdateDate field. It is recommended to start with a recent period, such as the last 3 to 6 months, to manage the data volume and API load. The format should be YYYY-MM-DD.
Field Selection: The script uses the fields query parameter to request only the necessary fields from the API. This significantly improves performance and reduces network traffic. If you use custom fields, they must be added to this parameter.
Pagination Limit: The limit parameter controls how many records are returned in a single API call. The script uses a limit of 500, which is a common maximum, to optimize the number of required API calls.
Required Privileges: The user or OAuth application credentials used must have read access to the 'Opportunity' and 'Quote' REST resources, including all standard and relevant custom fields.

a Sample Query javascript

const axios = require('axios');
const { Parser } = require('json2csv');
const fs = require('fs');

// --- Configuration --- //
const ORACLE_CX_HOST = 'https://[your-oracle-cx-cloud-host].fa.us2.oraclecloud.com';
const CLIENT_ID = '[Your Client ID]';
const CLIENT_SECRET = '[Your Client Secret]';
const START_DATE = '2023-01-01'; // YYYY-MM-DD
const END_DATE = '2023-06-30'; // YYYY-MM-DD
const PAGE_LIMIT = 500;
// --- End Configuration --- //

const tokenUrl = `${ORACLE_CX_HOST}/fscmRestApi/tokenrelay`;
const opportunitiesUrl = `${ORACLE_CX_HOST}/salesApi/resources/latest/opportunities`;

const getAuthToken = async () => {
    try {
        const response = await axios.post(tokenUrl, 'grant_type=client_credentials', {
            headers: {
                'Content-Type': 'application/x-www-form-urlencoded',
                'Authorization': `Basic ${Buffer.from(`${CLIENT_ID}:${CLIENT_SECRET}`).toString('base64')}`
            }
        });
        console.log('Successfully obtained authentication token.');
        return response.data.access_token;
    } catch (error) {
        console.error('Error fetching auth token:', error.response ? error.response.data : error.message);
        throw new Error('Authentication failed.');
    }
};

const fetchAllOpportunities = async (token) => {
    let allOpportunities = [];
    let hasMore = true;
    let offset = 0;

    console.log(`Fetching opportunities updated between ${START_DATE} and ${END_DATE}...`);

    while (hasMore) {
        const params = {
            q: `LastUpdateDate between '${START_DATE}' and '${END_DATE}'`,
            onlyData: true,
            limit: PAGE_LIMIT,
            offset: offset,
            fields: 'OptyId,CreationDate,LastUpdateDate,Name,SalesStage,StatusCode,RevnAmount,OwnerResourcePartyId,PrimaryContactPartyName,LossReasonCode,LeadId,OrganizationName,OptyNumber,OwnerName'
        };

        try {
            const response = await axios.get(opportunitiesUrl, { headers: { Authorization: `Bearer ${token}` }, params });
            const opportunities = response.data.items;
            if (opportunities && opportunities.length > 0) {
                allOpportunities.push(...opportunities);
                offset += opportunities.length;
                console.log(`Fetched ${opportunities.length} opportunities, total so far: ${allOpportunities.length}`);
            } else {
                 hasMore = false;
            }
            hasMore = response.data.hasMore;
        } catch (error) {
            console.error(`Error fetching opportunities at offset ${offset}:`, error.response ? error.response.data : error.message);
            hasMore = false; // Stop on error
        }
    }
    return allOpportunities;
};

const fetchQuotesForOpportunity = async (token, optyId) => {
    const quotesUrl = `${opportunitiesUrl}/${optyId}/child/Quote`;
    try {
        const response = await axios.get(quotesUrl, {
            headers: { Authorization: `Bearer ${token}` },
            params: { fields: 'QuoteId,CreationDate,LastUpdateDate,QuoteStatus,QuoteNumber', onlyData: true }
        });
        return response.data.items;
    } catch (error) {
        console.error(`Error fetching quotes for opportunity ${optyId}:`, error.response ? error.response.data : error.message);
        return [];
    }
};

const transformToEventLog = async (token, opportunities) => {
    const eventLog = [];
    const now = new Date().toISOString();

    for (const opp of opportunities) {
        const commonAttributes = {
            SalesOpportunity: opp.OptyNumber,
            SourceSystem: 'Oracle CX Sales',
            LastDataUpdate: now,
            OpportunityValue: opp.RevnAmount,
            SalesStage: opp.SalesStage,
            OpportunityOwner: opp.OwnerName,
            Region: opp.OrganizationName, // Example mapping, adjust as needed
            LossReason: opp.LossReasonCode
        };

        // Activity: Lead Converted To Opportunity
        if (opp.LeadId) {
            eventLog.push({ ...commonAttributes, ActivityName: 'Lead Converted To Opportunity', EventTime: opp.CreationDate });
        }
        
        // Inferred stage-based activities. Using LastUpdateDate as proxy.
        // A more accurate method requires audit trail data which is more complex to extract.
        const stageNumber = parseInt(opp.SalesStage?.split('-')[0], 10);
        if (stageNumber >= 2) {
             eventLog.push({ ...commonAttributes, ActivityName: 'Opportunity Qualified', EventTime: opp.LastUpdateDate });
        }
        if (stageNumber >= 3) {
             eventLog.push({ ...commonAttributes, ActivityName: 'Needs Analysis Completed', EventTime: opp.LastUpdateDate });
        }
        if (stageNumber >= 4) {
             eventLog.push({ ...commonAttributes, ActivityName: 'Solution Proposed', EventTime: opp.LastUpdateDate });
        }

        // Fetch and process quotes
        const quotes = await fetchQuotesForOpportunity(token, opp.OptyId);
        let quoteCreationCount = 0;
        for (const quote of quotes) {
            quoteCreationCount++;
            // Activity: Quote Created
            eventLog.push({ ...commonAttributes, ActivityName: 'Quote Created', EventTime: quote.CreationDate });
            // Activity: Quote Reworked (inferred from second or later quote creation)
            if (quoteCreationCount > 1) {
                 eventLog.push({ ...commonAttributes, ActivityName: 'Quote Reworked', EventTime: quote.CreationDate });
            }
            // Activity: Quote Sent To Customer
            if (['PRESENTED', 'SENT'].includes(quote.QuoteStatus)) {
                 eventLog.push({ ...commonAttributes, ActivityName: 'Quote Sent To Customer', EventTime: quote.LastUpdateDate });
            }
            // Activity: Quote Accepted By Customer
            if (quote.QuoteStatus === 'ACCEPTED') {
                 eventLog.push({ ...commonAttributes, ActivityName: 'Quote Accepted By Customer', EventTime: quote.LastUpdateDate });
            }
        }

        // Final Opportunity Status activities
        if (opp.StatusCode === 'WON') {
            eventLog.push({ ...commonAttributes, ActivityName: 'Opportunity Won', EventTime: opp.LastUpdateDate });
            // Activity: Order Submitted For Fulfillment (inferred from Opportunity Won)
            eventLog.push({ ...commonAttributes, ActivityName: 'Order Submitted For Fulfillment', EventTime: opp.LastUpdateDate });
            
            // Placeholder for events from external systems. Data should be merged from other sources.
            // eventLog.push({ ...commonAttributes, ActivityName: 'Order Fulfilled', EventTime: [Timestamp from ERP] });
            // eventLog.push({ ...commonAttributes, ActivityName: 'Invoice Generated', EventTime: [Timestamp from Financials] });
            // eventLog.push({ ...commonAttributes, ActivityName: 'Payment Received', EventTime: [Timestamp from Financials] });

        } else if (opp.StatusCode === 'LOST') {
            eventLog.push({ ...commonAttributes, ActivityName: 'Opportunity Lost', EventTime: opp.LastUpdateDate });
        }
    }
    return eventLog;
};

const main = async () => {
    try {
        const token = await getAuthToken();
        const opportunities = await fetchAllOpportunities(token);
        console.log(`Total opportunities to process: ${opportunities.length}`);

        if (opportunities.length > 0) {
            console.log('Transforming data into event log...');
            const eventLog = await transformToEventLog(token, opportunities);
            console.log(`Generated ${eventLog.length} event records.`);
            
            const parser = new Parser();
            const csv = parser.parse(eventLog);
            fs.writeFileSync('oracle_cx_sales_event_log.csv', csv);
            console.log('Event log saved to oracle_cx_sales_event_log.csv');
        }
    } catch (error) {
        console.error('An error occurred during the extraction process:', error.message);
    }
};

main();

Steps

Prepare Python Environment: Ensure you have Python installed on your system. Install the necessary libraries using pip: pip install requests pandas.
Obtain API Credentials: Log in to your Oracle CX Sales instance with an administrator account. Navigate to the Security Console (Navigator > Tools > Security Console) and create a new user with the 'Sales Representative' or a custom integration role. This user needs API access to the salesLeads, opportunities, quotes, and related objects. Note down the username and password.
Identify Your Oracle CX Domain: Find your specific Oracle CX Sales domain URL. It typically follows the format https://[your-pod-name].fa.em2.oraclecloud.com.
Configure the Script: Open the provided Python script in an editor. Replace the placeholder values for ORACLE_CX_DOMAIN, USERNAME, PASSWORD, START_DATE, and END_DATE with your actual credentials and desired date range for the extraction.
Customize API Endpoints and Fields: Review the API calls within the script. The fields requested (e.g., OptyId, Name, SalesStage, StatusCode) are standard. If you have custom fields (_c suffix) that are important for your analysis, add them to the fields parameter in the relevant API requests.
Implement External System Integration: The script includes placeholder functions (get_order_data_from_erp, get_invoice_data_from_finance, get_payment_data_from_finance) for activities that occur outside of Oracle CX Sales. You must replace the placeholder logic with actual API calls to your ERP and financial systems to retrieve data for Order Submitted, Order Fulfilled, Invoice Generated, and Payment Received events. This integration is critical for a complete Lead to Cash view.
Execute the Script: Run the script from your command line using python your_script_name.py. The script will make a series of API calls to Oracle CX Sales, process the data, and combine it into a single event log.
Review the Output: The script will generate a file named lead_to_cash_event_log.csv. Open this file in a spreadsheet application to verify its structure and content. Check for the expected columns: SalesOpportunity, ActivityName, EventTime, SourceSystem, etc.
Handle API Pagination: The provided script includes a basic pagination loop. For very large datasets, you may need to add more robust error handling or short pauses between requests to avoid hitting API rate limits.
Prepare for Upload: The final CSV file is structured for direct upload into ProcessMind. Ensure the column headers match the mapping in your ProcessMind project. No further formatting should be necessary.

Configuration

API Credentials: A dedicated API user with sufficient privileges to read Sales Lead, Sales Opportunity, and Quote objects is required. This includes access to historical data or audit trails for status and stage changes.
Oracle CX Domain: The base URL for your Oracle CX Sales instance must be correctly specified in the script.
Date Range: Set the START_DATE and END_DATE variables in the script to define the extraction window. A range of 3 to 6 months is recommended for initial analysis to balance data volume and performance.
Opportunity Filters: The script can be customized to filter opportunities based on specific criteria. For example, you can add query parameters to the API URL to filter by Organization_Id or custom fields to limit the extraction to specific business units or opportunity types.
External System Endpoints: You must provide the actual API endpoints, credentials, and logic for your ERP and financial systems to extract order, invoice, and payment data. The script assumes these systems can be correlated using the Sales Opportunity ID or a related Order ID.
Pagination Limit: The limit parameter in the API calls is set to 100. This can be adjusted, but higher values may increase the risk of timeouts for complex queries.

a Sample Query python

import requests
import pandas as pd
from requests.auth import HTTPBasicAuth
import datetime

class=class="hl-string">"hl-comment"># --- Configuration Settings ---
class=class="hl-string">"hl-comment"># Replace with your Oracle CX Sales domain, username, and password
ORACLE_CX_DOMAIN = class="hl-string">"https://[your-pod-name].fa.em2.oraclecloud.com"
USERNAME = class="hl-string">"[Your_API_Username]"
PASSWORD = class="hl-string">"[Your_API_Password]"

class=class="hl-string">"hl-comment"># Define the date range for the extraction (YYYY-MM-DD format)
START_DATE = class="hl-string">"2023-01-01"
END_DATE = class="hl-string">"2023-12-31"

class=class="hl-string">"hl-comment"># --- Helper Function for API Calls ---
def fetch_all_pages(endpoint, q_filter):
    all_items = []
    url = fclass="hl-string">"{ORACLE_CX_DOMAIN}/salesApi/resources/latest/{endpoint}"
    params = {
        class="hl-string">'q': q_filter,
        class="hl-string">'onlyData': class="hl-string">'true',
        class="hl-string">'limit': 100, class=class="hl-string">"hl-comment"># Max records per page
        class="hl-string">'offset': 0
    }
    
    while True:
        try:
            response = requests.get(url, auth=HTTPBasicAuth(USERNAME, 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'] += params[class="hl-string">'limit']
            else:
                break
        except requests.exceptions.RequestException as e:
            print(fclass="hl-string">"Error fetching {url}: {e}")
            break
    return all_items

class=class="hl-string">"hl-comment"># --- Placeholder Functions for External Systems ---
def get_order_data_from_erp(opportunity_ids):
    class=class="hl-string">"hl-comment"># CRITICAL: Replace this with actual API calls to your ERP system.
    class=class="hl-string">"hl-comment"># This function should return a list of dictionaries.
    class=class="hl-string">"hl-comment"># Each dictionary should have class="hl-string">'OptyId', class="hl-string">'EventTime', class="hl-string">'ActivityName'.
    print(class="hl-string">"Fetching placeholder Order data from ERP...")
    placeholder_data = []
    class=class="hl-string">"hl-comment"># Example: placeholder_data.append({class="hl-string">'OptyId': 12345, class="hl-string">'EventTime': class="hl-string">'2023-10-25T10:00:00Z', class="hl-string">'ActivityName': class="hl-string">'Order Submitted For Fulfillment'})
    class=class="hl-string">"hl-comment"># Example: placeholder_data.append({class="hl-string">'OptyId': 12345, class="hl-string">'EventTime': class="hl-string">'2023-10-28T14:00:00Z', class="hl-string">'ActivityName': class="hl-string">'Order Fulfilled'})
    return placeholder_data

def get_invoice_data_from_finance(opportunity_ids):
    class=class="hl-string">"hl-comment"># CRITICAL: Replace this with actual API calls to your financial system.
    print(class="hl-string">"Fetching placeholder Invoice data...")
    return [] class=class="hl-string">"hl-comment"># Example: [{class="hl-string">'OptyId': 12345, class="hl-string">'EventTime': class="hl-string">'2023-10-29T11:00:00Z', class="hl-string">'ActivityName': class="hl-string">'Invoice Generated'}]

def get_payment_data_from_finance(opportunity_ids):
    class=class="hl-string">"hl-comment"># CRITICAL: Replace this with actual API calls to your financial system.
    print(class="hl-string">"Fetching placeholder Payment data...")
    return [] class=class="hl-string">"hl-comment"># Example: [{class="hl-string">'OptyId': 12345, class="hl-string">'EventTime': class="hl-string">'2023-11-15T09:30:00Z', class="hl-string">'ActivityName': class="hl-string">'Payment Received'}]


class=class="hl-string">"hl-comment"># --- Main Extraction Logic ---
print(class="hl-string">"Starting Lead to Cash extraction...")

class=class="hl-string">"hl-comment"># 1. Fetch all relevant opportunities within the date range
date_filter = fclass="hl-string">"LastUpdateDate between '{START_DATE}' and '{END_DATE}'"
opportunities = fetch_all_pages(class="hl-string">'opportunities', date_filter)

if not opportunities:
    print(class="hl-string">"No opportunities found for the given date range. Exiting.")
    exit()

print(fclass="hl-string">"Found {len(opportunities)} opportunities to process.")
opp_ids = [opp[class="hl-string">'OptyId'] for opp in opportunities]

class=class="hl-string">"hl-comment"># DataFrame to hold all events
event_log_df = pd.DataFrame()

class=class="hl-string">"hl-comment"># 2. Extract activities from Opportunity and related objects
all_events = []

for opp in opportunities:
    opp_id = opp[class="hl-string">'OptyId']
    last_update = datetime.datetime.now().isoformat()

    base_attributes = {
        class="hl-string">'SalesOpportunity': opp_id,
        class="hl-string">'OpportunityValue': opp.get(class="hl-string">'Revenue'),
        class="hl-string">'SalesStage': opp.get(class="hl-string">'SalesStage'),
        class="hl-string">'OpportunityOwner': opp.get(class="hl-string">'OwnerResourcePartyName'),
        class="hl-string">'Region': opp.get(class="hl-string">'TerritoryName_c'), class=class="hl-string">"hl-comment"># Example custom field
        class="hl-string">'LossReason': opp.get(class="hl-string">'ReasonWonLostCode'),
        class="hl-string">'SourceSystem': class="hl-string">'Oracle CX Sales',
        class="hl-string">'LastDataUpdate': last_update
    }
    
    class=class="hl-string">"hl-comment"># Activity: Lead Converted To Opportunity (inference)
    if opp.get(class="hl-string">'PrimaryContactEmailAddress') and opp.get(class="hl-string">'SalesMethod') != class="hl-string">'Renewal': class=class="hl-string">"hl-comment"># Heuristic for lead-based opportunities
        all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Lead Converted To Opportunity', class="hl-string">'EventTime': opp.get(class="hl-string">'CreationDate')})
        
    class=class="hl-string">"hl-comment"># Activities from Sales Stage history
    stage_history = opp.get(class="hl-string">'ChildSalesStage', [])
    for stage in stage_history:
        stage_name = stage.get(class="hl-string">'SalesStageCode')
        event_time = stage.get(class="hl-string">'LastUpdateDate')
        activity = None
        if stage_name in [class="hl-string">'01-QUALIFICATION', class="hl-string">'QUALIFIED']: activity = class="hl-string">'Opportunity Qualified'
        elif stage_name in [class="hl-string">'02-DISCOVERY', class="hl-string">'ANALYSIS']: activity = class="hl-string">'Needs Analysis Completed'
        elif stage_name in [class="hl-string">'03-PROPOSAL', class="hl-string">'SOLUTION_PROPOSED']: activity = class="hl-string">'Solution Proposed'
        
        if activity:
            all_events.append({**base_attributes, class="hl-string">'ActivityName': activity, class="hl-string">'EventTime': event_time})

    class=class="hl-string">"hl-comment"># Activities: Opportunity Won / Lost
    if opp.get(class="hl-string">'StatusCode') == class="hl-string">'WON':
        all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Opportunity Won', class="hl-string">'EventTime': opp.get(class="hl-string">'LastUpdateDate')})
    elif opp.get(class="hl-string">'StatusCode') == class="hl-string">'LOST':
        all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Opportunity Lost', class="hl-string">'EventTime': opp.get(class="hl-string">'LastUpdateDate')})

    class=class="hl-string">"hl-comment"># Activities from Quotes
    quotes = opp.get(class="hl-string">'ChildQuote', [])
    quote_creation_dates = []
    for quote in quotes:
        quote_creation_dates.append(quote.get(class="hl-string">'CreationDate'))
        all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Quote Created', class="hl-string">'EventTime': quote.get(class="hl-string">'CreationDate')})
        
        class=class="hl-string">"hl-comment"># Infer other quote events from status or custom date fields
        if quote.get(class="hl-string">'QuoteStatus_c') == class="hl-string">'SENT' and quote.get(class="hl-string">'DateSent_c'):
            all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Quote Sent To Customer', class="hl-string">'EventTime': quote.get(class="hl-string">'DateSent_c')})
        if quote.get(class="hl-string">'QuoteStatus_c') == class="hl-string">'ACCEPTED' and quote.get(class="hl-string">'DateAccepted_c'):
            all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Quote Accepted By Customer', class="hl-string">'EventTime': quote.get(class="hl-string">'DateAccepted_c')})
    
    class=class="hl-string">"hl-comment"># Activity: Quote Reworked (inference)
    if len(quote_creation_dates) > 1:
        class=class="hl-string">"hl-comment"># Mark all but the first creation as a rework event
        sorted_dates = sorted(quote_creation_dates)
        for rework_date in sorted_dates[1:]:
            all_events.append({**base_attributes, class="hl-string">'ActivityName': class="hl-string">'Quote Reworked', class="hl-string">'EventTime': rework_date})

class=class="hl-string">"hl-comment"># 3. Add data from external systems
print(class="hl-string">"Fetching data from external systems...")
order_events = get_order_data_from_erp(opp_ids)
invoice_events = get_invoice_data_from_finance(opp_ids)
payment_events = get_payment_data_from_finance(opp_ids)

external_system_events = []
last_update = datetime.datetime.now().isoformat()

for event in order_events + invoice_events + payment_events:
    opp_id = event[class="hl-string">'OptyId']
    class=class="hl-string">"hl-comment"># Find the corresponding opportunity to get base attributes
    opp_data = next((item for item in opportunities if item[class="hl-string">"OptyId"] == opp_id), None)
    if opp_data:
         base_attributes = {
            class="hl-string">'SalesOpportunity': opp_id,
            class="hl-string">'OpportunityValue': opp_data.get(class="hl-string">'Revenue'),
            class="hl-string">'SalesStage': opp_data.get(class="hl-string">'SalesStage'),
            class="hl-string">'OpportunityOwner': opp_data.get(class="hl-string">'OwnerResourcePartyName'),
            class="hl-string">'Region': opp_data.get(class="hl-string">'TerritoryName_c'),
            class="hl-string">'LossReason': opp_data.get(class="hl-string">'ReasonWonLostCode'),
            class="hl-string">'SourceSystem': class="hl-string">'ERP/Finance',
            class="hl-string">'LastDataUpdate': last_update
        }
    else:
        base_attributes = {class="hl-string">'SalesOpportunity': opp_id, class="hl-string">'SourceSystem': class="hl-string">'ERP/Finance', class="hl-string">'LastDataUpdate': last_update}
    
    external_system_events.append({**base_attributes, class="hl-string">'ActivityName': event[class="hl-string">'ActivityName'], class="hl-string">'EventTime': event[class="hl-string">'EventTime']})

all_events.extend(external_system_events)

class=class="hl-string">"hl-comment"># 4. Finalize the DataFrame
if all_events:
    event_log_df = pd.DataFrame(all_events)
    class=class="hl-string">"hl-comment"># Standardize column names
    event_log_df = event_log_df.rename(columns={class="hl-string">'ActivityName': class="hl-string">'ActivityName', class="hl-string">'EventTime': class="hl-string">'EventTime'})
    
    class=class="hl-string">"hl-comment"># Ensure required columns exist
    required_cols = [class="hl-string">'SalesOpportunity', class="hl-string">'ActivityName', class="hl-string">'EventTime', class="hl-string">'SourceSystem', class="hl-string">'LastDataUpdate', class="hl-string">'OpportunityValue', class="hl-string">'SalesStage', class="hl-string">'OpportunityOwner', class="hl-string">'Region', class="hl-string">'LossReason']
    for col in required_cols:
        if col not in event_log_df.columns:
            event_log_df[col] = None
            
    class=class="hl-string">"hl-comment"># Select and order columns
    event_log_df = event_log_df[required_cols]
    
    class=class="hl-string">"hl-comment"># Clean up and sort
    event_log_df = event_log_df.dropna(subset=[class="hl-string">'SalesOpportunity', class="hl-string">'ActivityName', class="hl-string">'EventTime'])
    event_log_df[class="hl-string">'EventTime'] = pd.to_datetime(event_log_df[class="hl-string">'EventTime'])
    event_log_df = event_log_df.sort_values(by=[class="hl-string">'SalesOpportunity', class="hl-string">'EventTime'])
    
    class=class="hl-string">"hl-comment"># Save to CSV
    output_filename = class="hl-string">'lead_to_cash_event_log.csv'
    event_log_df.to_csv(output_filename, index=False, date_format=class="hl-string">'%Y-%m-%dT%H:%M:%S.%fZ')
    print(fclass="hl-string">"Extraction complete. Event log saved to {output_filename}")
else:
    print(class="hl-string">"No events were generated.")

Your Lead to Cash Data Template

Your Lead to Cash Data Template

Lead to Cash Attributes

Lead to Cash Activities

Extraction Guides

Oracle CX Sales REST API Direct Query Extraction

Steps

Configuration

a Sample Query javascript

Python Script using Oracle CX Sales REST API

Steps

Configuration

a Sample Query python

Ready to Get Started?

Boost Your Lead to Cash Win Rate by 20% Today

Your Lead to Cash Data Template

Your Lead to Cash Data Template

Lead to Cash Attributes

Lead to Cash Activities

Extraction Guides

Oracle CX Sales REST API Direct Query Extraction

Steps

Configuration

a Sample Query javascript

Python Script using Oracle CX Sales REST API

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Boost Your Lead to Cash Win Rate by 20% Today