> Continuous Process Improvement > Accounts Payable Payment Processing > Oracle Fusion Financials > Data Template

Your Accounts Payable Payment Processing Data Template

Oracle Fusion Financials

Accounts Payable Payment Processing Attributes (20) Accounts Payable Payment Processing Activities (12) Extraction Guides (2)

Your Accounts Payable Payment Processing Data Template

This comprehensive template provides a structured approach to mapping your payment workflows within Oracle Fusion Financials. It outlines the specific data fields and process steps necessary to gain deep visibility into your entire payment cycle. By following this framework, you can identify bottlenecks and optimize your financial operations effectively.

Recommended attributes for detailed analysis
Standard process activities for event mapping
Step by step extraction guidance for Oracle Fusion Financials

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

Download Template

Accounts Payable Payment Processing Attributes

These recommended data fields allow you to capture essential transactional details from Oracle Fusion Financials for a deep dive into payment performance.

5 Required 10 Recommended 5 Optional

	Name	Description
	Activity Name ActivityName	The specific event or step performed in the process.
Description This attribute represents the name of the process step being executed, such as 'Invoice Created', 'Invoice Validated', or 'Payment Cleared'. It allows the process mining algorithm to reconstruct the sequence of events (control flow) for every invoice. These values are typically derived by unifying data from multiple transaction and history tables, tagging each record with a human-readable event name. Why it matters It defines the 'what' of the process, essential for mapping the process flow and discovering variants. Where to get Derived from AP_INVOICES_ALL status changes, AP_INV_APRVL_HIST_ALL, and AP_CHECKS_ALL Examples Invoice CreatedInvoice ValidatedPayment Created
	Event Timestamp EventDateTime	The date and time when the activity occurred.
Description This attribute records the exact timestamp for when an activity took place. It is used to sequence events chronologically and to calculate the duration between process steps. Precise timestamps are vital for accurate Cycle Time analysis and for identifying bottlenecks where invoices sit idle between steps. Why it matters It provides the temporal dimension necessary for performance analysis and process sequencing. Where to get CREATION_DATE or LAST_UPDATE_DATE from respective tables (e.g., AP_INVOICES_ALL, AP_CHECKS_ALL) Examples 2023-10-01T08:30:00Z2023-10-05T14:15:00Z2023-10-10T09:00:00Z
	Invoice Number InvoiceNumber	The unique identifier for the vendor invoice.
Description This attribute serves as the unique reference for a specific invoice submitted by a supplier. It acts as the central Case ID for the process mining analysis, grouping all subsequent activities such as approvals, holds, and payments together. In Oracle Fusion Financials, this field is critical for linking invoice headers to lines, payments, and purchase orders. Analysts use this identifier to trace the complete lifecycle of a liability from the moment it is recorded until the cash leaves the bank account. Why it matters It is the definitive case identifier required to reconstruct the end-to-end process instance. Where to get AP_INVOICES_ALL.INVOICE_NUM Examples INV-2023-00199887766OCT-SERVICE-04
	Last Data Update LastDataUpdate	The timestamp when the data was extracted or refreshed.
Description Indicates the specific time the data record was extracted from Oracle Fusion. This helps analysts understand how fresh the data is and aids in incremental data loading strategies. It differentiates between the actual event time and the time the data became available for analysis. Why it matters It ensures data currency and helps manage incremental data loads. Where to get System time at extraction Examples 2023-10-27T23:59:59Z
	Source System SourceSystem	The name of the system where the data originated.
Description Identifies the software system acting as the system of record for the event. In this context, it will typically be 'Oracle Fusion Financials'. This attribute is particularly useful in multi-system environments where data might be blended from ERP, procurement, and banking systems. Why it matters It ensures traceability of data lineage, especially in complex system landscapes. Where to get Hardcoded or derived from connection configuration Examples Oracle Fusion FinancialsOracle ERP CloudLegacy EBS
	Business Unit BusinessUnit	The operating unit or business entity responsible for the invoice.
Description Identifies the specific internal division or subsidiary processing the invoice. In Oracle Fusion, this maps to the Organization ID. This attribute is essential for the 'Global Process Variant Standardization' dashboard, enabling comparison of process efficiency across different regions or divisions. Why it matters It allows for comparative analysis of performance across different organizational entities. Where to get HR_ORGANIZATION_UNITS.NAME (joined via ORG_ID from AP_INVOICES_ALL) Examples US OperationsEMEA SalesAPAC Manufacturing
	Created By User CreatedByUserName	The user ID or name of the person who entered the invoice.
Description Identifies the user responsible for the initial data entry. This maps to the User Generic Data Model attribute. This data is used in 'Manual Intervention Rate' analysis to identify training needs or specific users associated with high rework rates. Why it matters It enables resource-level performance analysis and segregation of duties checks. Where to get AP_INVOICES_ALL.CREATED_BY (resolves to username via PER_USERS) Examples j.doesystem_integrationm.smith
	Due Date DueDate	The date by which the payment must be made to avoid penalties.
Description The calculated deadline for payment based on the Invoice Date and Payment Terms. This attribute is the primary benchmark for the 'Late Payment Rate' KPI. Monitoring this date against the actual Payment Date reveals compliance with vendor contracts and cash flow management effectiveness. Why it matters It is the critical target date for measuring on-time payment performance. Where to get AP_PAYMENT_SCHEDULES_ALL.DUE_DATE Examples 2023-10-302023-11-15
	Invoice Amount InvoiceAmount	The total monetary value of the invoice.
Description Represents the total amount to be paid for the invoice. This value is critical for the 'Low Value Invoice Efficiency Review', allowing organizations to correlate effort spent versus the financial value of the transaction. It is also used to prioritize high-value invoices for early payment discount realization. Why it matters It quantifies the financial impact of the case and supports risk prioritization. Where to get AP_INVOICES_ALL.INVOICE_AMOUNT Examples 1500.00250.5010000.00
	Invoice Date InvoiceDate	The date printed on the invoice by the supplier.
Description This date represents when the invoice was issued by the supplier, distinct from when it was received or entered into Oracle. It is the baseline for calculating payment due dates based on payment terms. Discrepancies between Invoice Date and entry date often indicate mailroom or scanning delays. Why it matters It is the reference point for payment term calculations and aging analysis. Where to get AP_INVOICES_ALL.INVOICE_DATE Examples 2023-09-152023-10-01
	Invoice Type InvoiceType	The classification of the invoice (e.g., Standard, Credit Memo).
Description Categorizes the invoice into types such as Standard, Prepayment, or Credit Memo. This maps to the CaseType generic attribute. Different invoice types follow different validation and approval paths, so segmentation by this attribute is necessary for accurate 'End to End Cycle Time Performance' baselining. Why it matters It allows for separating apples from oranges in process performance comparisons. Where to get AP_INVOICES_ALL.INVOICE_TYPE_LOOKUP_CODE Examples STANDARDCREDITPREPAYMENT
	Payment Date PaymentDate	The date the payment was actually executed or cleared.
Description Records when the funds were transferred or the check was cut. This is the endpoint for the 'Average Invoice to Pay Cycle Time' KPI. Comparing this date to the Due Date determines if a payment was late, on time, or early enough to capture a discount. Why it matters It marks the completion of the financial transaction and process lifecycle. Where to get AP_CHECKS_ALL.CHECK_DATE Examples 2023-10-282023-11-01
	Payment Terms PaymentTerms	The agreed conditions for payment timing and discounts.
Description Specifies the contractual terms governing the payment, such as 'Net 30' or '2/10 Net 30'. This attribute is the basis for the 'Early Payment Discount Realization' dashboard. It dictates the target Due Date and any potential savings available for expedited processing. Why it matters It defines the performance targets for payment timeliness and discount capture. Where to get AP_TERMS.NAME (joined via TERMS_ID from AP_INVOICES_ALL) Examples Net 30Immediate2% 10 Net 30
	Purchase Order Number PurchaseOrderNumber	The reference number of the associated purchase order.
Description Links the invoice to the upstream procurement process. This attribute is vital for 'PO Matching and Discrepancy Resolution' analysis. Invoices without a PO Number usually follow a different, often less efficient, approval workflow compared to PO-backed invoices. Why it matters It distinguishes between PO-backed and Non-PO invoices, which have different process behaviors. Where to get PO_HEADERS_ALL.SEGMENT1 (linked via AP_INVOICE_LINES_ALL) Examples PO-9988774500001234
	Supplier Name SupplierName	The name of the vendor or supplier issuing the invoice.
Description This attribute identifies the external entity requesting payment. In Oracle Fusion, this information is managed in the Supplier Master (POZ_SUPPLIERS) and linked to the invoice. Analyzing this attribute allows for Vendor Compliance and Throughput analysis, helping to identify vendors that frequently submit problematic invoices or cause rework. Why it matters It enables segmentation of process performance by vendor for relationship management. Where to get POZ_SUPPLIERS.VENDOR_NAME (joined via VENDOR_ID from AP_INVOICES_ALL) Examples Office Depot Inc.Oracle CorporationDell Services
	Approval Status ApprovalStatus	Current workflow status of the invoice.
Description Indicates whether the invoice is Required, Initiated, Rejected, or Approved. This attribute helps in 'Approval Workflow Bottleneck Analysis'. It provides a high-level snapshot of where the invoice sits in the authorization hierarchy. Why it matters It helps diagnose stalls in the approval chain. Where to get AP_INVOICES_ALL.WFAPPROVAL_STATUS Examples REQUIREDWFAPPROVEDNOT REQUIRED
	Currency Code CurrencyCode	The currency in which the invoice was issued.
Description The ISO currency code (e.g., USD, EUR) for the transaction. This is necessary for normalizing amounts in the 'Low Value Invoice Efficiency Review'. Process variants often differ significantly between domestic (local currency) and international (foreign currency) payments due to banking complexities. Why it matters It identifies cross-border complexity and is needed for financial normalization. Where to get AP_INVOICES_ALL.INVOICE_CURRENCY_CODE Examples USDEURGBP
	Days Overdue DaysOverdue	Number of days the payment was made after the due date.
Description A calculated number indicating how late a payment was. Positive values indicate lateness; negative values indicate early payment. This metric powers the 'Late Payment and Penalty Risk Tracker' dashboard, helping to quantify the severity of process delays. Why it matters It quantifies the magnitude of the late payment problem. Where to get Calculated: PaymentDate - DueDate Examples 5-20
	Discount Lost Amount DiscountLostAmount	The monetary value of the discount missed due to late payment.
Description Calculated as the difference between the full invoice amount and the discounted amount if the payment date exceeded the discount terms date. This supports 'Early Payment Discount Realization' analysis. It assigns a tangible dollar value to process inefficiencies. Why it matters It monetizes the cost of process delays. Where to get Calculated from InvoiceAmount and PaymentTerms Examples 50.000.00120.50
	Is Potential Duplicate IsPotentialDuplicate	Flag indicating if the invoice shares details with another invoice.
Description A calculated boolean flag that is true if the Vendor and Amount match another invoice within a specific time window. This supports the 'Duplicate Invoice Detection Analytics' dashboard. It acts as a proactive alert mechanism for auditors to review specific cases before payment release. Why it matters It is a key risk control attribute for preventing financial loss. Where to get Calculated based on window functions over InvoiceAmount and SupplierName Examples truefalse

Required Recommended Optional

Accounts Payable Payment Processing Activities

Track these critical process milestones to visualize the end to end journey of every payment from initial creation to final settlement.

7 Recommended 5 Optional

	Activity	Description
	Invoice Approved	The final approval is granted within the workflow. The invoice status updates to 'Workflow Approved' or 'Manually Approved'.
Why it matters A major milestone that clears the invoice for payment selection. Long gaps before this step indicate approval bottlenecks. Where to get AP_INV_APRVL_HIST_ALL table (latest approval action) or AP_INVOICES_ALL.WFAPPROVAL_STATUS = 'WFAPPROVED'. Capture Compare status field before/after Event type inferred
	Invoice Cancelled	The invoice is voided or cancelled, effectively ending the process instance without payment.
Why it matters Represents wasted effort. High cancellation rates usually point to upstream duplicate entry or poor vendor data quality. Where to get AP_INVOICES_ALL.CANCELLED_DATE is populated. Capture Logged when transaction X executed Event type explicit
	Invoice Created	The initial creation of the invoice record within the Oracle Fusion Payables system. This captures the timestamp when the invoice header is first committed to the database, whether entered manually or imported via IDR/interface.
Why it matters Establishes the process start time for cycle time calculations and aging analysis. Essential for measuring the lag between receipt and entry. Where to get AP_INVOICES_ALL table, CREATION_DATE column. Filter by INVOICE_ID. Capture Logged when transaction record created Event type explicit
	Invoice Hold Applied	A system or manual hold is placed on the invoice, preventing payment. This includes quantity variances, price variances, or manual 'Invoice Needs Review' holds.
Why it matters The primary indicator of process friction. Analyzing hold reasons helps identify vendor compliance issues or internal process gaps. Where to get AP_HOLDS_ALL table, CREATION_DATE. Indicates a stop in the process flow. Capture Logged when transaction X executed Event type explicit
	Invoice Line Matched	The association of an invoice line with a Purchase Order (PO) or Receipt. This indicates the 3-way or 2-way matching process has occurred during line entry.
Why it matters Critical for analyzing 'First Pass Yield' and identifying where automated matching fails. Low matching rates drive manual rework. Where to get AP_INVOICE_LINES_ALL table. Identify records where MATCH_TYPE is 'ITEM_TO_PO', 'PO_PRICE_ADJUSTMENT', etc. Capture Logged when transaction line created with link Event type explicit
	Invoice Validated	The invoice status changes to 'Validated', indicating it has passed system integrity checks, tax calculation, and matching rules. This is a prerequisite for approval and payment.
Why it matters Marks the transition from data entry to the approval/payment workflow. Delays here indicate data quality issues or configuration errors. Where to get Inferred from AP_INVOICES_ALL.VALIDATION_REQUEST_ID timestamp or by tracking status changes in AP_INVOICE_HISTORY (if enabled). Capture Compare status field before/after Event type inferred
	Payment Created	The payment document (Check, ETF, Wire) is generated. This reduces the liability and marks the execution of the payment.
Why it matters The 'Stop' timestamp for Cycle Time. Comparing this to Due Date determines 'Late Payment' and 'Discount Realization' metrics. Where to get AP_INVOICE_PAYMENTS_ALL table linked to AP_CHECKS_ALL. Use CREATION_DATE of the payment record. Capture Logged when transaction X executed Event type explicit
	Approval Initiated	The invoice is submitted to the approval workflow (AMX). This marks the beginning of the management authorization phase.
Why it matters Differentiates operational processing time from management approval lead time. Helps identify if delays are due to AP staff or approvers. Where to get AP_INV_APRVL_HIST_ALL table (Approval History) or inferred from AP_INVOICES_ALL.WFAPPROVAL_STATUS changing to 'INITIATED'. Capture Compare status field before/after Event type inferred
	Invoice Accounted	The invoice accounting entries are generated and transferred to the General Ledger. This confirms financial impact recording.
Why it matters Ensures financial compliance. Delays here can affect period-close activities and financial reporting accuracy. Where to get AP_INVOICE_DISTRIBUTIONS_ALL.POSTED_FLAG = 'Y' or via XLA_AE_HEADERS (Subledger Accounting) linked to the invoice. Capture Logged when transaction X executed Event type explicit
	Invoice Hold Released	The removal of a previously applied hold, allowing the invoice to proceed in the workflow. This represents the resolution of a discrepancy.
Why it matters Calculates the 'Rework Time' or 'Resolution Time'. High frequency suggests inefficiency in exception handling. Where to get AP_HOLDS_ALL table, LAST_UPDATE_DATE where RELEASE_LOOKUP_CODE is populated. Capture Logged when transaction X executed Event type explicit
	Payment Cleared	The payment is reconciled with the bank statement. The status changes to 'Cleared' or 'Reconciled'.
Why it matters True end of the cash cycle. Essential for cash flow forecasting and understanding the float time between issuance and clearing. Where to get AP_CHECKS_ALL.STATUS_LOOKUP_CODE changes to 'CLEARED'. Timestamp is CLEARED_DATE. Capture Logged when transaction X executed Event type explicit
	Payment Selected	The invoice is selected by a Payment Process Request (PPR). It is staged for payment but cash has not yet moved.
Why it matters Indicates the invoice has been picked up by a payment run. Gaps between this and 'Payment Created' suggest batch processing issues. Where to get AP_SELECTED_INVOICES_ALL (temporary) or inferred from AP_PAYMENT_SCHEDULES_ALL.CHECK_RUN_ID population. Capture Compare status field before/after Event type inferred

Recommended Optional

Extraction Guides

How to get your data from Oracle Fusion Financials

Steps

Step 1: Access Oracle BI Publisher

Log in to your Oracle Fusion Financials environment with a user that has BI Administrator or BI Author privileges.
Navigate to Tools > Reports and Analytics.
Click Browse Catalog to open the Oracle BI Publisher interface.

Step 2: Create Data Model

In the catalog, click New (top left) and select Data Model.
In the Data Model editor, click the New Data Set icon and select SQL Query.
Name the data set (e.g., AP_Process_Mining) and select the Data Source ApplicationDB_FSCM (Financials Supply Chain Management).

Step 3: Implement the Extraction Query

Paste the complete SQL code provided in the Query section below into the SQL Query text box.
This query utilizes UNION ALL to extract all 12 required activities into a single event log structure.
Click OK to save the query.

Step 4: Configure Parameters

The query uses placeholders :p_start_date and :p_end_date for the InvoiceDate filter. Go to the Parameters tab on the left.
Define both parameters as Date type with a display label (e.g., Start Date, End Date).
Ensure the parameter format matches the database format (typically DD-MON-YYYY or standard ISO).

Step 5: Validate and Export

Click the Data tab and click View. Select a small date range to verify data is returned.
Click Save as Sample Data to store the schema structure.
Save the Data Model to a Shared Folder (e.g., /Shared Folders/Custom/ProcessMining).
Create a Report based on this Data Model. Add a layout that simply lists all columns in a table.
Schedule the report via Report Job to output as CSV.
Download the CSV file and import it directly into ProcessMind.

Configuration

Data Source: ApplicationDB_FSCM (Standard Fusion Financials DB connection)
Date Range: Recommended 3-6 months sliding window for initial load. Use the Invoice Date or Creation Date as the filtering anchor.
Performance: The query is optimized with basic joins. For very high volumes (1M+ invoices), consider adding a filter for Business Unit (Org ID) to chunk the extraction.
Output Format: CSV is preferred. Ensure date formats are explicitly set to YYYY-MM-DD HH24:MI:SS in the report properties to avoid ambiguity.
Prerequisites: User requires access to AP tables (AP_INVOICES_ALL, AP_CHECKS_ALL, etc.) usually granted via the Accounts Payable Manager or BI Consumer roles.

a Sample Query sql

/* AP Payment Processing Event Log Extraction */
/* Parameter Requirements: :p_start_date, :p_end_date */

/* 1. Invoice Created */
SELECT
    aia.INVOICE_NUM AS InvoiceNumber,
    'Invoice Created' AS ActivityName,
    aia.CREATION_DATE AS EventDateTime,
    'Oracle Fusion' AS SourceSystem,
    SYSDATE AS LastDataUpdate,
    poz.PARTY_NAME AS SupplierName,
    aia.INVOICE_AMOUNT AS InvoiceAmount,
    aia.INVOICE_DATE AS InvoiceDate,
    hou.NAME AS BusinessUnit,
    apt.NAME AS PaymentTerms,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)) AS DueDate,
    NULL AS PaymentDate,
    NULL AS PurchaseOrderNumber,
    aia.CREATED_BY AS CreatedByUserName,
    aia.INVOICE_TYPE_LOOKUP_CODE AS InvoiceType
FROM AP_INVOICES_ALL aia
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 2. Invoice Line Matched (PO Match) */
SELECT
    aia.INVOICE_NUM,
    'Invoice Line Matched',
    aila.CREATION_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    poh.SEGMENT1,
    aila.CREATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INVOICE_LINES_ALL aila ON aia.INVOICE_ID = aila.INVOICE_ID
JOIN PO_HEADERS_ALL poh ON aila.PO_HEADER_ID = poh.PO_HEADER_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aila.PO_HEADER_ID IS NOT NULL
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 3. Invoice Validated (Proxy via Validation Request or Distribution Generation) */
SELECT
    aia.INVOICE_NUM,
    'Invoice Validated',
    NVL(aia.VALIDATION_REQUEST_DATE, aia.STATUS_EFFECTIVE_DATE),
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    aia.LAST_UPDATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE (aia.VALIDATION_REQUEST_DATE IS NOT NULL OR aia.STATUS_EFFECTIVE_DATE IS NOT NULL)
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 4. Invoice Hold Applied */
SELECT
    aia.INVOICE_NUM,
    'Invoice Hold Applied',
    aha.HOLD_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    aha.CREATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_HOLDS_ALL aha ON aia.INVOICE_ID = aha.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 5. Invoice Hold Released */
SELECT
    aia.INVOICE_NUM,
    'Invoice Hold Released',
    aha.LAST_UPDATE_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    aha.LAST_UPDATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_HOLDS_ALL aha ON aia.INVOICE_ID = aha.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aha.RELEASE_LOOKUP_CODE IS NOT NULL
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 6. Approval Initiated */
SELECT
    aia.INVOICE_NUM,
    'Approval Initiated',
    ap_hist.CREATION_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    ap_hist.CREATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INV_APRVL_HIST_ALL ap_hist ON aia.INVOICE_ID = ap_hist.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE ap_hist.RESPONSE = 'INITIATED'
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 7. Invoice Approved */
SELECT
    aia.INVOICE_NUM,
    'Invoice Approved',
    ap_hist.RESPONSE_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    ap_hist.APPROVER_NAME,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INV_APRVL_HIST_ALL ap_hist ON aia.INVOICE_ID = ap_hist.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE ap_hist.RESPONSE = 'APPROVED'
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 8. Invoice Accounted */
SELECT
    aia.INVOICE_NUM,
    'Invoice Accounted',
    MAX(aida.LAST_UPDATE_DATE),
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    'System',
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INVOICE_DISTRIBUTIONS_ALL aida ON aia.INVOICE_ID = aida.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aida.ACCRUAL_POSTED_FLAG = 'Y'
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date
GROUP BY aia.INVOICE_NUM, poz.PARTY_NAME, aia.INVOICE_AMOUNT, aia.INVOICE_DATE, hou.NAME, apt.NAME, aia.TERMS_DATE, apt.DUE_DAYS, aia.INVOICE_TYPE_LOOKUP_CODE

UNION ALL

/* 9. Payment Selected (Proxy using Payment Link Creation) */
SELECT
    aia.INVOICE_NUM,
    'Payment Selected',
    aipa.CREATION_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    aipa.CREATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INVOICE_PAYMENTS_ALL aipa ON aia.INVOICE_ID = aipa.INVOICE_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 10. Payment Created */
SELECT
    aia.INVOICE_NUM,
    'Payment Created',
    aca.CHECK_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    aca.CHECK_DATE,
    NULL,
    aca.CREATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INVOICE_PAYMENTS_ALL aipa ON aia.INVOICE_ID = aipa.INVOICE_ID
JOIN AP_CHECKS_ALL aca ON aipa.CHECK_ID = aca.CHECK_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 11. Payment Cleared */
SELECT
    aia.INVOICE_NUM,
    'Payment Cleared',
    aca.CLEARED_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    aca.CLEARED_DATE,
    NULL,
    aca.LAST_UPDATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN AP_INVOICE_PAYMENTS_ALL aipa ON aia.INVOICE_ID = aipa.INVOICE_ID
JOIN AP_CHECKS_ALL aca ON aipa.CHECK_ID = aca.CHECK_ID
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aca.CLEARED_DATE IS NOT NULL
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

UNION ALL

/* 12. Invoice Cancelled */
SELECT
    aia.INVOICE_NUM,
    'Invoice Cancelled',
    aia.CANCELLED_DATE,
    'Oracle Fusion',
    SYSDATE,
    poz.PARTY_NAME,
    aia.INVOICE_AMOUNT,
    aia.INVOICE_DATE,
    hou.NAME,
    apt.NAME,
    TRUNC(aia.TERMS_DATE + NVL(apt.DUE_DAYS, 0)),
    NULL,
    NULL,
    aia.LAST_UPDATED_BY,
    aia.INVOICE_TYPE_LOOKUP_CODE
FROM AP_INVOICES_ALL aia
JOIN POZ_SUPPLIERS poz ON aia.VENDOR_ID = poz.VENDOR_ID
JOIN HR_ORGANIZATION_UNITS hou ON aia.ORG_ID = hou.ORGANIZATION_ID
LEFT JOIN AP_TERMS_TL apt ON aia.TERMS_ID = apt.TERM_ID AND apt.LANGUAGE = USERENV('LANG')
WHERE aia.CANCELLED_DATE IS NOT NULL
AND aia.INVOICE_DATE BETWEEN :p_start_date AND :p_end_date

Steps

Prepare your Python environment by installing the necessary libraries. You will need requests for API calls, pandas for data manipulation, and json for parsing. Run pip install requests pandas in your terminal.
Obtain Oracle Fusion Cloud credentials. You require a user account with the Financials REST API roles. Gather your specific POD URL (e.g., https://fa-xxxx-saasfaprod1.fa.ocs.oraclecloud.com) and Base64 encoded credentials or set up an OAuth token.
Configure the script parameters provided in the Query section below. Update the base_url, username, and password variables. Set the start_date variable to define the historical extraction window (e.g., 2024-01-01).
The script initializes an empty list to store event dictionaries. It defines the primary endpoint for Invoices (/fscmRestApi/resources/11.13.18.05/invoices) and utilizes a loop to handle pagination, ensuring all records matching the query are retrieved.
For each invoice fetched, the script extracts Header Level activities. It creates an 'Invoice Created' event using the CreationDate. It checks the InvoiceStatus and ApprovalStatus fields to generate 'Invoice Validated' and 'Invoice Approved' events.
The script then performs nested API calls to fetch Invoice Lines. It iterates through lines to identify PO matching. If a POHeaderId is present, it generates an 'Invoice Line Matched' event.
The script performs nested API calls to the invoiceHolds child resource. It iterates through holds to generate 'Invoice Hold Applied' events based on creation time and 'Invoice Hold Released' events if a release date is present.
The script performs nested API calls to the installments child resource to find payment links. It follows the links to the Payment details to generate 'Payment Created' and 'Payment Cleared' events based on the check date and clearance status.
Data transformation occurs within the script. Dates are standardized to ISO 8601 format. The SourceSystem is hardcoded to 'Oracle Fusion'. All attributes are mapped to a flat structure.
The script compiles all event dictionaries into a Pandas DataFrame. It sorts the dataframe by InvoiceNumber and EventDateTime to ensure a chronological event log.
Run the script. Monitor the console output for progress logs (e.g., Processing Invoice: INV-12345). Depending on the volume and API rate limits, this may take time.
The final step in the script exports the DataFrame to a CSV file named oracle_fusion_ap_event_log.csv. Import this file directly into ProcessMind for visualization.

Configuration

API Base URL: Must match your specific Oracle Cloud pod instance (e.g., https://fa-eqmz.fa.us2.oraclecloud.com).
Authentication: Supports Basic Auth (Base64) or JWT Token. Basic Auth is used in the script for readability but OAuth is recommended for production.
Date Filtering: The script filters by CreationDate to limit the volume. Recommended range is the last 3-6 months for initial extraction.
Batch Size: REST APIs limit response sizes (default 25 or 50). The script sets a limit=499 (max is usually 500) to minimize pagination overhead.
Performance: This extraction uses the N+1 query pattern (fetching children for every parent). For high volumes (>100k invoices), consider using BI Publisher SQL extracts instead of REST.
Child Resources: The script explicitly fetches lines, holds, and installments. Ensure the user account has permissions to view these sub-resources.

a Sample Query python

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

class=class="hl-string">"hl-comment"># Configuration - UPDATE THESE VALUES
BASE_URL = class="hl-string">"https://fa-your-instance.fa.ocs.oraclecloud.com"
USERNAME = class="hl-string">"your_username"
PASSWORD = class="hl-string">"your_password"
START_DATE = class="hl-string">"2024-01-01"
OUTPUT_FILE = class="hl-string">"oracle_fusion_ap_event_log.csv"

class=class="hl-string">"hl-comment"># API Endpoints
INVOICES_ENDPOINT = class="hl-string">"/fscmRestApi/resources/11.13.18.05/invoices"

class=class="hl-string">"hl-comment"># Headers
auth_str = fclass="hl-string">"{USERNAME}:{PASSWORD}"
b64_auth = base64.b64encode(auth_str.encode()).decode()
HEADERS = {
    class="hl-string">"Authorization": fclass="hl-string">"Basic {b64_auth}",
    class="hl-string">"Content-Type": class="hl-string">"application/json"
}

class=class="hl-string">"hl-comment"># Event Log Storage
all_events = []

def get_all_pages(url, params=None):
    results = []
    current_url = url
    while current_url:
        try:
            print(fclass="hl-string">"Fetching: {current_url}")
            response = requests.get(current_url, headers=HEADERS, params=params)
            response.raise_for_status()
            data = response.json()
            
            if class="hl-string">'items' in data:
                results.extend(data[class="hl-string">'items'])
            
            class=class="hl-string">"hl-comment"># Handle Pagination
            current_url = None
            if class="hl-string">'links' in data:
                for link in data[class="hl-string">'links']:
                    if link[class="hl-string">'rel'] == class="hl-string">'next':
                        current_url = link[class="hl-string">'href']
            class=class="hl-string">"hl-comment"># Clear params after first call as next link contains them
            params = None
            
        except Exception as e:
            print(fclass="hl-string">"Error fetching data: {e}")
            break
    return results

def extract_invoice_data():
    class=class="hl-string">"hl-comment"># 1. Fetch Invoices created after start date
    params = {
        class="hl-string">"q": fclass="hl-string">"CreationDate > '{START_DATE}'",
        class="hl-string">"limit": 499,
        class="hl-string">"fields": class="hl-string">"InvoiceId,InvoiceNumber,InvoiceDate,InvoiceAmount,Supplier,CreationDate,CreatedBy,Description,InvoiceType,InvoiceStatus,ApprovalStatus,Accounted,PaymentStatus,BusinessUnit,PaymentTerms,TermsDate"
    }
    
    invoices = get_all_pages(fclass="hl-string">"{BASE_URL}{INVOICES_ENDPOINT}", params)
    print(fclass="hl-string">"Total Invoices Found: {len(invoices)}")

    for inv in invoices:
        invoice_id = inv.get(class="hl-string">'InvoiceId')
        invoice_num = inv.get(class="hl-string">'InvoiceNumber')
        print(fclass="hl-string">"Processing Invoice: {invoice_num}")

        common_attrs = {
            class="hl-string">"InvoiceNumber": invoice_num,
            class="hl-string">"SourceSystem": class="hl-string">"Oracle Fusion",
            class="hl-string">"SupplierName": inv.get(class="hl-string">'Supplier'),
            class="hl-string">"InvoiceAmount": inv.get(class="hl-string">'InvoiceAmount'),
            class="hl-string">"InvoiceDate": inv.get(class="hl-string">'InvoiceDate'),
            class="hl-string">"BusinessUnit": inv.get(class="hl-string">'BusinessUnit'),
            class="hl-string">"PaymentTerms": inv.get(class="hl-string">'PaymentTerms'),
            class="hl-string">"DueDate": inv.get(class="hl-string">'TermsDate'),
            class="hl-string">"CreatedByUserName": inv.get(class="hl-string">'CreatedBy'),
            class="hl-string">"InvoiceType": inv.get(class="hl-string">'InvoiceType'),
            class="hl-string">"LastDataUpdate": datetime.now().isoformat()
        }

        class=class="hl-string">"hl-comment"># ACTIVITY 1: Invoice Created
        all_events.append({
            **common_attrs,
            class="hl-string">"ActivityName": class="hl-string">"Invoice Created",
            class="hl-string">"EventDateTime": inv.get(class="hl-string">'CreationDate')
        })

        class=class="hl-string">"hl-comment"># ACTIVITY 2: Invoice Validated
        if inv.get(class="hl-string">'InvoiceStatus') == class="hl-string">'Validated':
            class=class="hl-string">"hl-comment"># Fusion doesn't expose ValidatedDate on header easily, using LastUpdate or approximation
            class=class="hl-string">"hl-comment"># In a real scenario, you might check a child class="hl-string">'history' resource if enabled
            all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Invoice Validated",
                class="hl-string">"EventDateTime": inv.get(class="hl-string">'LastUpdateDate', inv.get(class="hl-string">'CreationDate')) class=class="hl-string">"hl-comment"># Fallback
            })
        
        class=class="hl-string">"hl-comment"># ACTIVITY 3: Invoice Approved / Approval Initiated
        if inv.get(class="hl-string">'ApprovalStatus') in [class="hl-string">'WFAPPROVED', class="hl-string">'Manually Approved']:
            all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Invoice Approved",
                class="hl-string">"EventDateTime": inv.get(class="hl-string">'LastUpdateDate') class=class="hl-string">"hl-comment"># Approximation
            })
        elif inv.get(class="hl-string">'ApprovalStatus') == class="hl-string">'INITIATED':
            all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Approval Initiated",
                class="hl-string">"EventDateTime": inv.get(class="hl-string">'LastUpdateDate')
            })

        class=class="hl-string">"hl-comment"># ACTIVITY 4: Invoice Accounted
        if inv.get(class="hl-string">'Accounted') == class="hl-string">'Y':
             all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Invoice Accounted",
                class="hl-string">"EventDateTime": inv.get(class="hl-string">'LastUpdateDate') class=class="hl-string">"hl-comment"># Approximation used as AccountingDate field varies
            })

        class=class="hl-string">"hl-comment"># ACTIVITY 5: Invoice Cancelled
        if inv.get(class="hl-string">'InvoiceStatus') == class="hl-string">'Cancelled':
             all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Invoice Cancelled",
                class="hl-string">"EventDateTime": inv.get(class="hl-string">'LastUpdateDate')
            })

        class=class="hl-string">"hl-comment"># FETCH SUB-RESOURCES
        class=class="hl-string">"hl-comment"># ---------------------------------------------------------
        
        class=class="hl-string">"hl-comment"># ACTIVITY 6: Invoice Line Matched (Check Lines)
        lines_url = fclass="hl-string">"{BASE_URL}{INVOICES_ENDPOINT}/{invoice_id}/child/lines"
        lines = get_all_pages(lines_url, {class="hl-string">"fields": class="hl-string">"LineNumber,CreationDate,POHeaderId"})
        
        matched_po = False
        for line in lines:
            if line.get(class="hl-string">'POHeaderId'):
                matched_po = True
                all_events.append({
                    **common_attrs,
                    class="hl-string">"ActivityName": class="hl-string">"Invoice Line Matched",
                    class="hl-string">"EventDateTime": line.get(class="hl-string">'CreationDate'),
                    class="hl-string">"PurchaseOrderNumber": str(line.get(class="hl-string">'POHeaderId'))
                })

        class=class="hl-string">"hl-comment"># ACTIVITY 7 & 8: Holds (Applied and Released)
        holds_url = fclass="hl-string">"{BASE_URL}{INVOICES_ENDPOINT}/{invoice_id}/child/invoiceHolds"
        holds = get_all_pages(holds_url)
        
        for hold in holds:
            class=class="hl-string">"hl-comment"># Hold Applied
            all_events.append({
                **common_attrs,
                class="hl-string">"ActivityName": class="hl-string">"Invoice Hold Applied",
                class="hl-string">"EventDateTime": hold.get(class="hl-string">'CreationDate')
            })
            
            class=class="hl-string">"hl-comment"># Hold Released
            if hold.get(class="hl-string">'ReleaseDate'):
                all_events.append({
                    **common_attrs,
                    class="hl-string">"ActivityName": class="hl-string">"Invoice Hold Released",
                    class="hl-string">"EventDateTime": hold.get(class="hl-string">'ReleaseDate')
                })

        class=class="hl-string">"hl-comment"># ACTIVITY 9, 10, 11: Payments (Selected, Created, Cleared)
        class=class="hl-string">"hl-comment"># Note: In Fusion REST, we go Invoice -> Installments -> Payment Details
        installments_url = fclass="hl-string">"{BASE_URL}{INVOICES_ENDPOINT}/{invoice_id}/child/installments"
        installments = get_all_pages(installments_url)
        
        for inst in installments:
            class=class="hl-string">"hl-comment"># Check if paid
            if inst.get(class="hl-string">'PaymentStatusFlag') in [class="hl-string">'Y', class="hl-string">'P']: class=class="hl-string">"hl-comment"># Y=Fully Paid, P=Partially
                 all_events.append({
                    **common_attrs,
                    class="hl-string">"ActivityName": class="hl-string">"Payment Selected",
                    class="hl-string">"EventDateTime": inst.get(class="hl-string">'LastUpdateDate') class=class="hl-string">"hl-comment"># Proxy for selection time
                })
                
            class=class="hl-string">"hl-comment"># Attempt to fetch payment details if link exists
            class=class="hl-string">"hl-comment"># This is simplified; usually requires querying the class="hl-string">'apPayments' endpoint using the check_id found here
            class=class="hl-string">"hl-comment"># We simulate the extraction if fields are present
            class=class="hl-string">"hl-comment"># In a full script, you would perform a GET on the class="hl-string">'payment' link relation provided in the installment response
            
            class=class="hl-string">"hl-comment"># Placeholder logic for Payment Created (Check Date)
            if inst.get(class="hl-string">'FirstPaymentDate'):
                all_events.append({
                    **common_attrs,
                    class="hl-string">"ActivityName": class="hl-string">"Payment Created",
                    class="hl-string">"EventDateTime": inst.get(class="hl-string">'FirstPaymentDate'),
                    class="hl-string">"PaymentDate": inst.get(class="hl-string">'FirstPaymentDate')
                })
                
                class=class="hl-string">"hl-comment"># Placeholder for Cleared (assuming cleared if paid and time passed, or check status endpoint)
                class=class="hl-string">"hl-comment"># Real implementation requires querying /fscmRestApi/resources/11.13.18.05/payablesPayments
                class=class="hl-string">"hl-comment"># For this script, we record Payment Created.

class=class="hl-string">"hl-comment"># Execute Extraction
extract_invoice_data()

class=class="hl-string">"hl-comment"># Export to DataFrame and CSV
if all_events:
    df = pd.DataFrame(all_events)
    class=class="hl-string">"hl-comment"># Ensure datetime format
    df[class="hl-string">'EventDateTime'] = pd.to_datetime(df[class="hl-string">'EventDateTime'])
    df = df.sort_values(by=[class="hl-string">'InvoiceNumber', class="hl-string">'EventDateTime'])
    
    print(fclass="hl-string">"Exporting {len(df)} events to {OUTPUT_FILE}...")
    df.to_csv(OUTPUT_FILE, index=False)
    print(class="hl-string">"Done.")
else:
    print(class="hl-string">"No events extracted.")

Your Accounts Payable Payment Processing Data Template

Your Accounts Payable Payment Processing Data Template

Accounts Payable Payment Processing Attributes

Accounts Payable Payment Processing Activities

Extraction Guides

Oracle BI Publisher SQL Data Model Query

Steps

Step 1: Access Oracle BI Publisher

Step 2: Create Data Model

Step 3: Implement the Extraction Query

Step 4: Configure Parameters

Step 5: Validate and Export

Configuration

a Sample Query sql

Python REST API Extraction for Fusion AP

Steps

Configuration

a Sample Query python

Ready to Get Started?

Fix Your Accounts Payable Payment Processing Today

Your Accounts Payable Payment Processing Data Template

Your Accounts Payable Payment Processing Data Template

Accounts Payable Payment Processing Attributes

Accounts Payable Payment Processing Activities

Extraction Guides

Oracle BI Publisher SQL Data Model Query

Steps

Step 1: Access Oracle BI Publisher

Step 2: Create Data Model

Step 3: Implement the Extraction Query

Step 4: Configure Parameters

Step 5: Validate and Export

Configuration

a Sample Query sql

Python REST API Extraction for Fusion AP

Steps

Configuration

a Sample Query python

We value your privacy

Ready to Get Started?

Fix Your Accounts Payable Payment Processing Today