> 持续流程改进 > 采购到付款－发票处理 > Oracle Fusion Financials > 数据模板

您的采购到付款：发票处理数据模板

Oracle Fusion Financials

← 返回改进指南

采购到付款－发票处理属性 (20) 采购到付款－发票处理活动 (15) 提取指南 (3)

您的采购到付款：发票处理数据模板

此模板旨在指导您收集Oracle Fusion Financials中采购到付款流程，尤其是发票处理分析所需的关键数据。模板列出了重要属性和关键活动，并说明如何从系统中提取这些信息。使用此模板有助于准备准确、完整的事件日志，用于流程挖掘。

建议收集的属性
需要跟踪的关键活动
Oracle Fusion Financials数据提取指南

刚接触事件日志？了解如何创建流程挖掘事件日志.

下载模板

采购到付款－发票处理属性

以下是建议纳入事件日志的数据字段，用于全面分析采购到付款－发票处理流程。

3 必需 7 建议 10 可选

	名称	说明
	发票编号 InvoiceNumber	供应商发票的唯一标识符。
说明发票编号是主要案例标识，用于关联单张供应商发票从创建到最终付款的所有活动和事件。流程分析会将每张发票视为一个唯一的案例实例。在流程挖掘中，该属性是重建每张发票端到端历程的基础。它支持按发票分析流程、周期时间和变体，也是将验证、审批和付款等不同活动串联成完整流程脉络的关键。为什么重要这是连接所有相关流程步骤的核心案例标识符，可用于追踪发票的完整生命周期。获取位置通常位于AP_INVOICES_ALL表的INVOICE_NUM列。示例 INV-2023-001987654321ACME-FIN-5501
	开始时间 EventTime	表示活动或事件发生时间的时间戳。
说明该属性提供发票流程中每项活动的日期和时间，是所有基于时间的流程分析的关键，包括计算周期时间、持续时间和步骤间等待时间。流程挖掘工具可使用该时间戳按时间顺序排列事件，重建每张发票的准确活动序列。这支持计算“平均发票周期时间”等关键绩效指标，并帮助识别流程中耗时最多的阶段。为什么重要该时间戳对于计算周期时间、瓶颈等所有与持续时间和时间相关的绩效指标至关重要。获取位置该时间戳根据Oracle Fusion表中的多个日期字段得出，例如AP_INVOICES_ALL或相关工作流、付款表中的CREATION_DATE或LAST_UPDATE_DATE。示例 2023-04-15T10:00:00Z2023-04-16T14:35:10Z2023-04-20T09:05:00Z
	活动 ActivityName	发票流程中发生的业务活动或事件名称。
说明该属性描述发票生命周期中的具体步骤或状态变化，例如“发票已创建”、“发票已批准”或“付款已执行”。它构成流程中的事件顺序。分析活动的顺序和频率是流程挖掘的核心。通过分析，可以发现实际流程路径，识别活动延迟形成的瓶颈，并发现偏差或返工循环，例如发票在获批后被拒绝。为什么重要它定义流程步骤，对于展示流程图、分析流转差异和识别瓶颈至关重要。获取位置该属性通常根据Oracle Fusion Financials中的状态字段、审计表或工作流日志组合得出，例如AP_INVOICES_ALL.WFAPPROVAL_STATUS或相关工作流表。示例发票已验证发票已设置冻结发票已审批付款已执行
	付款到期日 PaymentDueDate	供应商应收到发票付款的截止日期。
说明付款到期日根据与供应商约定的付款条款计算。它是避免罚款、维护良好供应商关系并享受潜在提前付款折扣的付款截止时间。该属性对于“按时付款绩效”仪表板及其相关KPI至关重要。通过比较实际付款执行时间戳与付款到期日，分析可以将付款归类为按时或逾期，帮助企业监控并提升付款及时性。为什么重要这是衡量按时付款绩效的基准，也是供应商管理和财务健康状况的重要KPI。获取位置该日期通常位于AP_PAYMENT_SCHEDULES_ALL等与发票关联的付款排期表中。示例 2023-05-152023-06-012023-06-30
	供应商名称 VendorName	开具发票的供应商名称。
说明该属性标识发票所属的供应商实体，为财务交易提供关键业务背景。按供应商分析流程可以发现供应商关系和绩效方面的重要洞察。例如，可以识别哪些供应商的发票更容易出现匹配差异、冻结或延迟。这些信息可用于改进供应商准入、沟通和整体供应链效率，也可用于识别潜在的重复付款。为什么重要它支持按供应商分析流程，帮助识别导致延迟或异常的特定供应商问题。获取位置位于POZ_SUPPLIERS表。发票表AP_INVOICES_ALL包含VENDOR_ID，可用于与供应商表连接。示例 Acme CorporationGlobal Tech Inc.Office Supplies Co.
	公司代码 CompanyCode	处理发票的法人实体或公司的标识符。
说明公司代码代表组织内对发票承担财务责任的具体业务实体。在多公司组织中，这是基础性的组织数据。该属性支持按法人实体细分流程分析，便于比较企业不同部分的流程绩效，识别实体特有的瓶颈或合规问题，并确保KPI可以按公司层级报告。它通常也是确定正确审批工作流的因素之一。为什么重要它支持在组织内不同法人实体或业务部门之间进行流程比较和绩效基准分析。获取位置通常由AP_INVOICES_ALL中的LEGAL_ENTITY_ID或类似字段表示，可与总账表连接以获取代码或名称。示例 1001US01DE01
	发票状态 InvoiceStatus	发票在生命周期中的当前状态。
说明该属性反映发票最后已知的状态，例如“已验证”、“需要重新验证”、“已付款”或“已取消”。它可以显示发票在任意时点所处的流程位置。发票状态对于“当前发票状态分布”仪表板至关重要。该仪表板可帮助运营管理者识别积压，并监控发票处理管道的整体状况。分析状态随时间的变化，也可以更直观地了解流程。为什么重要它提供发票当前状态视图，是跟踪积压和工作负载的运营仪表板不可或缺的信息。获取位置请参阅Oracle Fusion Financials文档。状态可能根据AP_INVOICES_ALL中的WFAPPROVAL_STATUS等字段，或相关审批和付款表得出。示例已验证已付款已取消需要重新验证
	发票金额 InvoiceAmount	发票的货币总额。
说明发票金额表示发票列明的应付供应商总额。这是一项关键财务属性，会影响整个流程，通常决定审批路径、审核程度和付款优先级。在流程挖掘分析中，发票金额是重要的筛选和分组维度。例如，分析人员可以比较高金额和低金额发票的流程，判断其是否遵循不同路径或周期时间是否存在显著差异。它对于计算财务KPI以及评估延迟付款等流程低效造成的财务影响也至关重要。为什么重要该数值对于财务分析、了解基于金额的流程偏差，以及计算审批合规率等KPI至关重要。获取位置位于AP_INVOICES_ALL表的INVOICE_AMOUNT列。示例 1500.00250.75125000.50
	用户名 UserName	执行活动的用户名称。
说明该属性标识负责执行活动的具体用户或系统代理，例如验证发票、设置冻结或审批付款。它为流程提供人员或系统资源维度。按用户分析有助于了解工作负载分布、识别高绩效人员，并发现潜在的培训需求或合规问题。例如，可以发现某些用户是否持续参与返工循环，或特定审批步骤是否始终由同一人员处理，从而形成潜在的单点故障。为什么重要它支持资源绩效分析和工作负载平衡，并帮助识别参与特定流程步骤的用户或团队。获取位置这些信息通常存储在AP_INVOICES_ALL等表的CREATED_BY或LAST_UPDATED_BY等审计列中，也可能位于相关工作流日志中。示例 john.doejane.smithSystem.Admin
	结束时间 EndTime	表示活动或事件完成时间的时间戳。
说明结束时间标志着特定活动的完成。开始时间表示起点，结束时间提供终点，因此可以精确计算单个步骤的持续时间。在分析中，结束时间与开始时间之差就是每项活动的处理时间。这对于详细绩效分析至关重要，有助于区分实际处理时间和空闲等待时间。例如，可以衡量审批人员实际处理审批任务的时间，以及任务在其队列中等待的时间。为什么重要它支持精确计算活动处理时间，将实际工作时间与等待时间区分开来。获取位置这是一个概念属性，根据特定案例中后续事件的开始时间推导得出。示例 2023-04-15T10:05:12Z2023-04-16T15:00:00Z2023-04-20T09:15:30Z
	最后数据更新时间 LastUpdateDate	表示源系统中记录最后更新时间的时间戳。
说明该属性反映Oracle Fusion Financials中基础数据最近一次修改的时间。它用于管理增量数据加载，并确保流程挖掘模型保持最新。虽然该技术时间戳不直接用于顺序流分析，但对于维护数据的新鲜度和完整性至关重要。数据管道可以据此仅查询上次更新后新增或变更的记录，从而减少对源系统的负载。为什么重要确保数据管道能够高效执行增量处理，在无需完整重新加载的情况下保持流程分析最新。获取位置通常以LAST_UPDATE_DATE的形式存在于多个Oracle Fusion表中，包括AP_INVOICES_ALL。示例 2023-05-20T11:00:00Z2023-05-21T16:45:00Z
	冻结原因 HoldReason	发票被挂起或设置付款冻结的原因。
说明发票被挂起时，此属性用于说明原因，例如“价格不匹配”“数量差异”或“等待收货”。这有助于了解正常流程为何中断。此属性是“付款冻结趋势与分析”仪表板的主要维度。通过分析不同挂起原因的发生频率，企业可以识别并解决付款冻结的根本原因，例如采购流程问题或供应商开票准确性问题，最终减少处理延迟。为什么重要它揭示付款冻结的根本原因，支持有针对性地改进流程，从而减少挂起和付款延迟。获取位置挂起信息通常存储在AP_HOLDS_ALL表中。该表与发票关联，并包含挂起原因或代码。示例价格不匹配开票数量超过收货数量采购订单编号无效
	匹配差异原因 MatchingDiscrepancyReason	发票、采购订单与收货记录之间不匹配的具体原因。
说明此属性详细说明发票未通过自动匹配的原因。常见原因包括发票与对应采购订单或收货记录在价格、数量或物料代码方面存在差异。此信息对“发票匹配差异率”仪表板至关重要。通过对差异原因进行分类和分析，企业可以定位采购或收货流程中的系统性问题，并采取纠正措施，提高直通式、免人工干预的发票处理比例。为什么重要它说明发票未通过自动匹配的原因，为提高首次匹配率、减少人工返工提供必要洞察。获取位置请参阅Oracle Fusion Financials文档。该信息可能记录为AP_HOLDS_ALL中的特定挂起原因类型，或记录在相关匹配明细表中。示例单价与采购订单不一致开票数量＞收货数量发票中的物料无效
	发票日期 InvoiceDate	供应商发票单据上注明的日期。
说明此属性表示供应商正式开具发票的日期。它是源单据中的关键信息，并用于根据约定的付款条款计算付款到期日。发票日期不一定是内部流程的起点，但能提供重要背景信息。它与供应商名称和发票金额结合使用，有助于识别潜在的重复发票。分析发票日期与发票在系统中创建日期之间的延迟，还可以发现收发室或发票采集流程中的低效环节。为什么重要它是识别重复发票和计算付款到期日的关键数据。获取位置这是AP_INVOICES_ALL表中的标准字段，名称为INVOICE_DATE。示例 2023-04-102023-05-012023-05-25
	审批人员姓名 ApproverName	审批或拒绝发票人员的姓名。
说明该属性记录审批环节中采取操作的人员身份，适用于“Invoice Approved”或“Invoice Rejected”等活动。在分析中，审批人员姓名用于了解审批工作负载、衡量个人审批周期时间，并审计审批政策的合规性。对于“审批合规率”KPI，可以根据发票金额和公司代码，将该属性与授权委托规则进行核对。为什么重要它对于分析审批周期时间、确保遵循审批矩阵政策以及了解工作负载分布至关重要。获取位置这些信息位于与发票对象关联的Oracle Fusion工作流或审批历史表中。示例 David WilsonSarah JohnsonMichael Brown
	币种 InvoiceCurrencyCode	发票金额所使用的币种。
说明此属性指定发票计价币种，例如USD、EUR或GBP。它是理解发票金额字段的重要背景信息。对于全球化组织，按币种分析发票有助于财务报告，并了解不同地区的流程差异。这样可以确保正确解读金额，并支持按币种分析付款惯例或审批阈值。为什么重要它为所有财务金额提供必要背景，确保金额得到准确解读和分析，尤其适用于跨国运营。获取位置位于AP_INVOICES_ALL表的INVOICE_CURRENCY_CODE列。示例 USDEURGBPCAD
	是否按时付款 IsOnTimePayment	用于标识发票是否在到期日前完成付款的布尔标记。
说明如果付款在指定的付款到期日当天或之前执行，此标记为true，否则为false。它为每张已付款发票提供简单明确的分类。此计算属性直接支持按时付款率KPI及其对应仪表板。用户可以轻松筛选、计数和可视化逾期付款与按时付款的比例，无需临时执行日期比较，从而简化分析。这有助于快速识别付款延迟的规模，并跟踪一段时间内的改进情况。为什么重要它简化了付款及时性分析，并直接用于计算按时付款率KPI。获取位置这是一个计算属性，通过比较“付款执行”活动的时间戳与“PaymentDueDate”属性得出。示例 truefalse
	是否返工 IsRework	用于标识属于返工循环的活动的布尔标记。
说明对于表示偏离理想流程的活动，此标记为true，例如“发票已更正”，或发票被拒后再次出现“发票已验证”。它有助于明确标记并量化低效的流程循环。此属性是“返工与异常处理率”仪表板的重要基础。通过标记返工活动，分析人员可以轻松量化返工量及其成本，识别根本原因，并衡量旨在提高一次通过率的流程改进措施的影响。为什么重要它可以明确识别并量化返工，便于分析流程低效的发生频率、原因和影响。获取位置这是一个计算属性。相关逻辑在数据转换阶段定义，用于识别构成返工的活动序列。示例 truefalse
	源系统 SourceSystem	标识记录事件数据的源系统。
说明该属性指定生成数据的源应用或模块，例如Oracle Fusion Financials。在包含多个集成系统的环境中，该字段有助于区分不同流程步骤的来源。了解源系统有助于数据验证、故障排查，以及分析特定于某一系统的流程差异。在发票旅程跨越多个应用的复杂IT环境中，它可以确保数据来源清晰。为什么重要它提供数据来源的上下文，对于数据治理、故障排查和分析系统特定的流程行为十分重要。获取位置通常在数据提取过程中添加静态值，用于标记数据集来源。示例 Oracle Fusion FinancialsOracle Payables Cloud
	采购订单号 PurchaseOrderNumber	与发票关联的采购订单标识符。
说明此属性将发票关联到相应的采购订单（PO），该订单授权采购相关商品或服务。发票可以有PO支持，也可以没有PO支持。按PO进行分析，可以追溯到P2P流程中的采购环节。这有助于了解采购流程的合规程度，以及发票匹配差异等问题是否源于初始PO的问题。是否存在PO号，是区分和分析不同发票处理路径的主要方式。为什么重要它将发票追溯到采购流程，是分析有PO与无PO发票流的关键属性。获取位置将AP_INVOICE_LINES_ALL中的发票行项目通过PO_DISTRIBUTION_ID关联到PO分配记录，即可获取此信息。示例 PO-2023-5001600789PO-FIN-9981

必需建议可选

采购到付款－发票处理活动

以下是应纳入事件日志的关键流程步骤和里程碑，用于准确发现流程。

6 建议 9 可选

	活动	说明
	付款已执行	确认付款已完成并结清。对于支票，这是支票结清日期；对于电子付款，则是银行的确认时间。
为什么重要这是发票生命周期中的最后一个活动，标志着流程成功完成，也是计算“平均发票周期时间”和“按时付款率”的终点。获取位置可根据AP_CHECKS_ALL表中的付款状态更新为“Cleared”或“Reconciled”推断，并使用CLEARED_DATE；也可以通过现金管理模块中的银行对账数据（CE_STATEMENT_LINES）推断。采集根据AP_CHECKS_ALL中的状态更新或CE模块中的对账结果推断。事件类型 inferred
	发票已与采购订单匹配	该活动表示发票行已成功匹配到对应的采购订单行，确认发票所列商品或服务已被订购。通常这是系统记录的自动或手工操作。
为什么重要这是三方匹配的关键环节，涉及采购订单、收货记录和发票。此阶段失败是异常和延迟的主要来源。获取位置可根据AP_INVOICE_DISTRIBUTIONS_ALL表中新建的记录推断，该记录通过PO_DISTRIBUTION_ID将发票与采购订单分配关联。也可以使用AP_INVOICE_LINES_ALL中的行级匹配状态。采集根据发票行中采购订单分配数据的填充情况推断。事件类型 inferred
	发票已创建	表示系统中首次创建发票记录，可能通过手工录入、扫描或电子提交完成。通常在主发票表中插入新行时记录此事件。
为什么重要标志着发票处理生命周期的开始。分析从该事件开始的耗时，有助于了解数据录入效率和整体流程启动延迟。获取位置在Oracle Fusion Financials中，这对应于AP_INVOICES_ALL表中记录的创建时间戳，具体为CREATION_DATE列。采集 AP_INVOICES_ALL中的记录创建时间戳。事件类型 explicit
	发票已完成会计处理	发票已成功过账至总账，并生成日记账分录。该事件确认发票的财务影响已正式记录。
为什么重要这是关键的财务控制点，也是付款的前提。它确认发票已完成验证和审批，可以进行结算。获取位置可根据AP_INVOICE_DISTRIBUTIONS_ALL表中的状态（ACCRUAL_POSTED_FLAG=“Y”）推断，也可以检查总账表（如XLA_AE_HEADERS）中是否存在对应日记账分录。采集根据AP_INVOICE_DISTRIBUTIONS_ALL中的标记或关联的总账分录推断。事件类型 inferred
	发票已审批	发票已由工作流中所有必需审批人员完成审批。现在可以进行会计处理和付款排期。
为什么重要这是表明审批流程成功完成的重要里程碑。此步骤前的延迟通常是常见瓶颈。获取位置可根据AP_INVOICES_ALL表中的APPROVAL_STATUS变为“Approved”或“Workflow Approved”等最终批准状态推断。该字段的审计历史可提供时间戳。采集根据AP_INVOICES_ALL.APPROVAL_STATUS变为“Approved”推断。事件类型 inferred
	发票已提交审批	根据配置的业务规则，将发票提交至审批工作流。这标志着正式审批周期的开始。
为什么重要启动流程中的关键环节。跟踪该开始时间对于衡量和优化“发票审批周期时间”至关重要。获取位置可根据AP_INVOICES_ALL表中的状态变化推断，其中APPROVAL_STATUS变为“Initiated”或“Pending Approval”等状态。工作流表中也可能包含此事件。采集根据AP_INVOICES_ALL.APPROVAL_STATUS变为“Initiated”推断。事件类型 inferred
	付款已创建	系统已生成发票付款指令。可能包括创建支票、电子资金转账（EFT）文件或其他付款工具。
为什么重要此时企业已承诺用于付款的资金。这是资金离开银行账户前的关键里程碑。获取位置记录在AP_CHECKS_ALL表中，该表存储所有付款信息。CHECK_DATE表示付款凭证的创建时间。采集在AP_CHECKS_ALL表中创建一条记录。事件类型 explicit
	付款已排期	发票已被选中并纳入付款流程请求，通常称为付款运行或付款批次。现在已进入待付款队列。
为什么重要这是会计处理与实际付款之间的步骤。该阶段的持续时间会影响现金流预测以及享受提前付款折扣的能力。获取位置当付款记录已创建但尚未确认付款时，会记录在AP_INVOICE_PAYMENTS_ALL表中。也可以在IBY_PAYMENT_PROCESS_REQUESTS等付款批次表中找到。采集为已排期付款在AP_INVOICE_PAYMENTS_ALL中创建一条记录。事件类型 explicit
	发票冻结已解除	该事件表示此前对发票设置的冻结已解决。用户或自动化流程执行操作移除阻塞，使发票可以继续处理。
为什么重要从设置冻结到解除冻结之间的时间，是衡量异常处理效率的重要指标。这支持“平均异常解决时间”KPI。获取位置记录在AP_HOLDS_ALL表中。解除冻结后，RELEASE_LOOKUP_CODE和RELEASE_REASON字段会与LAST_UPDATE_DATE一同填充。采集更新AP_HOLDS_ALL表中的记录，将冻结标记为已解除。事件类型 explicit
	发票已取消	发票已作废或取消，不会继续处理或付款。这表示流程的终止状态。
为什么重要这是不会产生付款的发票的重要终点。分析取消情况可以发现重复发票或供应商提交错误等问题。获取位置可根据AP_INVOICES_ALL中的状态变化推断。CANCELLED_DATE列会填入取消时间戳。采集 AP_INVOICES_ALL表中的CANCELLED_DATE字段已填充。事件类型 explicit
	发票已拒绝	审批人员在审批工作流中拒绝了发票。该操作通常会将发票退回修改或取消，从而启动返工循环。
为什么重要表示负面结果，也是返工增加和周期时间延长的主要原因。跟踪拒绝情况有助于识别发票质量或采购订单合规问题。获取位置可根据AP_INVOICES_ALL表中的APPROVAL_STATUS变为“Rejected”推断。工作流历史会记录拒绝人员和时间等详细信息。采集根据AP_INVOICES_ALL.APPROVAL_STATUS变为“Rejected”推断。事件类型 inferred
	发票已更正	当用户修改发票时发生，通常是为了响应拒绝或修正数据录入错误。这代表流程中的人工返工步骤。
为什么重要该活动是返工的明确指标。分析其发生频率有助于量化流程低效，并支持“发票返工率”KPI。获取位置可通过跟踪发票在已验证或提交审批后的重大更新来推断。需要使用LAST_UPDATE_DATE时间戳及审计轨迹数据。采集通过比较拒绝或冻结后的LAST_UPDATE_DATE推断。事件类型 inferred
	发票已设置冻结	表示对发票设置任意冻结的通用活动，阻止其继续付款流程。原因可能包括匹配问题、资金不足或人工干预。
为什么重要该事件会直接影响周期时间，并可能导致延迟付款。分析冻结情况是识别和解决系统性流程问题、支持“付款阻塞趋势”分析的关键。获取位置明确记录在AP_HOLDS_ALL表中。每行代表一项冻结，包含创建日期（HOLD_DATE）和原因。采集在AP_HOLDS_ALL表中创建一条记录。事件类型 explicit
	发票已验证	表示发票已通过系统对抬头和行信息完整性、正确性的验证检查。通常可通过发票记录的状态变化推断。
为什么重要这是匹配和审批前的关键里程碑。此处出现延迟，可能表明发票数据质量或系统配置存在问题。获取位置可根据AP_INVOICES_ALL表中发票状态变为“Validated”推断。可使用VALIDATION_STATUS列的变更历史或审计轨迹。采集根据AP_INVOICES_ALL.VALIDATION_STATUS字段的变化推断。事件类型 inferred
	已识别匹配差异	当系统或用户发现发票、采购订单和收货信息之间存在价格或数量等不匹配时，就会发生此事件。通常会导致系统对发票设置付款冻结。
为什么重要突出显示需要人工干预的流程异常。跟踪这些事件对于“发票匹配差异率”KPI和根因分析至关重要。获取位置通常记录为对发票设置特定类型的冻结。请检查AP_HOLDS_ALL表中与匹配相关的冻结类型，例如“QTY REC”或“PRICE”。HOLD_DATE表示时间戳。采集在AP_HOLDS_ALL中创建一条包含匹配相关冻结类型的记录。事件类型 explicit

建议可选

提取指南

如何从Oracle Fusion Financials获取数据

步骤

登录Oracle Fusion Cloud：使用具有BI Cloud Connector Administrator角色（BICC_ADMIN）的用户访问Oracle Fusion Cloud环境。
进入BI Cloud Connector：在主导航菜单中依次选择Tools>BI Cloud Connector，打开BICC控制台。
选择Offering：在BICC控制台中选择与Financials数据对应的Offering，通常名为“Financials”。
配置外部存储：进入“Configure External Storage”部分，设置云存储连接，用于接收提取的CSV文件，例如Oracle Cloud Infrastructure（OCI）Object Storage。
启用提取Offering：进入“Manage Offerings and PVOs”或类似部分，选择“Financials”Offering并启用提取。
选择Public View Objects（PVO）：搜索并选择发票流程所需的PVO。关键PVO包括：FscmTopModelAM.FinApInvQuickInvoicesAM.InvoiceHeaderPVO、FscmTopModelAM.FinApInvHoldAM.InvoiceHoldPVO、FscmTopModelAM.FinApInvSharedAM.InvoiceApprovalHistoryPVO和FscmTopModelAM.FinApPmtsInvPmtsAM.PaymentPVO。
计划提取作业：进入“Manage Extract Schedules”，创建新作业并为其命名，然后选择上一步启用的所有PVO并设置运行计划。首次加载时，按所需历史日期范围运行；后续运行则根据LastUpdateDate配置增量提取。
监控并获取数据：在BICC控制台中监控作业进度。成功完成后，进入已配置的云存储位置。您将看到按PVO分别生成的一组压缩CSV文件。
将数据加载到暂存区：解压文件，并将CSV加载到暂存数据库或数据处理平台（如数据仓库或数据湖），以便执行SQL查询。每个CSV文件应加载到独立的表中。
将数据转换为事件日志：对暂存区中的表执行所提供的SQL查询。该查询会合并不同表中的数据，创建统一的事件日志表。
为ProcessMind导出：将SQL查询结果导出为单个CSV文件。确保列标题符合上传到ProcessMind应用所需的属性名称（InvoiceNumber、ActivityName、EventTime等）。

配置

关键Public View Objects（PVO）：提取依赖FinancialsOffering中的多个核心PVO。至少必须包含：
- FscmTopModelAM.FinApInvQuickInvoicesAM.InvoiceHeaderPVO：用于获取核心发票数据，以及创建、验证和取消活动。
- FscmTopModelAM.FinApInvHoldAM.InvoiceHoldPVO：用于获取所有发票挂起和解除挂起活动。
- FscmTopModelAM.FinApInvSharedAM.InvoiceApprovalHistoryPVO：用于记录提交、审批和拒绝等详细审批工作流步骤。
- FscmTopModelAM.FinApPmtsInvPmtsAM.PaymentPVO：用于获取付款创建和执行活动。
- FscmTopModelAM.FinApInvPmtsAM.InstallmentPVO：用于识别发票进入付款计划的时间。
增量提取：为持续监控配置BICC作业执行增量提取。使用大多数PVO中提供的LastUpdateDate列作为筛选条件，仅提取上次运行后新增或变更的记录。
日期范围筛选：首次加载历史数据时，建议提取可管理的时间段，例如最近6至12个月的数据。您可以在BICC作业计划中应用全局筛选器，将提取范围限制在指定日期区间内。
业务单元筛选：如需限制提取范围，请在BICC作业配置中按BusinessUnitName或类似属性进行筛选。在多实体环境中，这对控制数据量至关重要。
前提条件：您的用户账户需要具备相应角色，主要包括BICC Administrator（BICC_ADMIN）和Functional Setup User（FSM_IMPLEMENTATION_CONSULTANT），才能配置和运行提取作业。此外，还必须配置可访问的云存储位置，例如OCI Object Storage或UCM。

a 示例查询 sql

-- This script is designed to be run on the CSV files after they have been extracted by BICC and loaded into a staging database.
-- Each CTE (e.g., Invoices, Holds) represents a table created from a corresponding PVO's CSV file.

WITH Invoices AS (
    SELECT 
        InvoiceId,
        InvoiceNumber,
        InvoiceAmount,
        SupplierName AS VendorName,
        CreationDate,
        CreatedBy AS UserName, 
        LastUpdateDate, 
        LastUpdatedBy, 
        ValidatedDate,
        ApprovalStatus,
        WfApprovalStatus,
        PayablesAccountingStatus,
        CancelledDate,
        CancelledBy,
        BusinessUnitName AS CompanyCode
    FROM FscmTopModelAM_FinApInvQuickInvoicesAM_InvoiceHeaderPVO
    WHERE LastUpdateDate >= '[Specify Start Date]'
),
Holds AS (
    SELECT 
        InvoiceId,
        HoldDate,
        ReleasedDate,
        HoldReason,
        CreatedBy,
        LastUpdatedBy
    FROM FscmTopModelAM_FinApInvHoldAM_InvoiceHoldPVO
),
ApprovalHistory AS (
    SELECT
        InvoiceId,
        ActionDate,
        Action,
        Performer AS UserName
    FROM FscmTopModelAM_FinApInvSharedAM_InvoiceApprovalHistoryPVO
),
Installments AS (
    SELECT 
        InvoiceId,
        DueDate AS PaymentDueDate,
        PaymentStatusFlag,
        LastUpdateDate
    FROM FscmTopModelAM_FinApInvPmtsAM_InstallmentPVO
),
Payments AS (
    SELECT
        InvoiceId,
        PaymentId,
        CreationDate,
        CreatedBy AS UserName,
        PaymentDate
    FROM FscmTopModelAM_FinApPmtsInvPmtsAM_PaymentPVO
)

-- 1. Invoice Created
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Created' AS "ActivityName",
    i.CreationDate AS "EventTime",
    i.CreationDate AS "EndTime",
    i.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    i.ApprovalStatus AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId

UNION ALL

-- 2. Invoice Validated
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Validated' AS "ActivityName",
    i.ValidatedDate AS "EventTime",
    i.ValidatedDate AS "EndTime",
    i.LastUpdatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Validated' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE i.ValidatedDate IS NOT NULL

UNION ALL

-- 3. Invoice Matched to PO (Inferred from hold release)
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Matched to PO' AS "ActivityName",
    h.ReleasedDate AS "EventTime",
    h.ReleasedDate AS "EndTime",
    h.LastUpdatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    i.ApprovalStatus AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Holds h ON i.InvoiceId = h.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE h.HoldReason IN ('QTY ORD', 'AMT ORD', 'PRICE') AND h.ReleasedDate IS NOT NULL

UNION ALL

-- 4. Matching Discrepancy Identified
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Matching Discrepancy Identified' AS "ActivityName",
    h.HoldDate AS "EventTime",
    h.HoldDate AS "EndTime",
    h.CreatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'On Hold' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Holds h ON i.InvoiceId = h.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE h.HoldReason IN ('QTY ORD', 'AMT ORD', 'PRICE')

UNION ALL

-- 5. Hold Placed on Invoice
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Hold Placed on Invoice' AS "ActivityName",
    h.HoldDate AS "EventTime",
    h.HoldDate AS "EndTime",
    h.CreatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'On Hold' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Holds h ON i.InvoiceId = h.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId

UNION ALL

-- 6. Hold Released from Invoice
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Hold Released from Invoice' AS "ActivityName",
    h.ReleasedDate AS "EventTime",
    h.ReleasedDate AS "EndTime",
    h.LastUpdatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    i.ApprovalStatus AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Holds h ON i.InvoiceId = h.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE h.ReleasedDate IS NOT NULL

UNION ALL

-- 7. Invoice Sent for Approval
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Sent for Approval' AS "ActivityName",
    ah.ActionDate AS "EventTime",
    ah.ActionDate AS "EndTime",
    ah.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Initiated' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN ApprovalHistory ah ON i.InvoiceId = ah.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE ah.Action = 'SUBMITTED'

UNION ALL

-- 8. Invoice Approved
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Approved' AS "ActivityName",
    ah.ActionDate AS "EventTime",
    ah.ActionDate AS "EndTime",
    ah.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Workflow approved' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN ApprovalHistory ah ON i.InvoiceId = ah.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE ah.Action = 'APPROVED'

UNION ALL

-- 9. Invoice Rejected
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Rejected' AS "ActivityName",
    ah.ActionDate AS "EventTime",
    ah.ActionDate AS "EndTime",
    ah.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Rejected' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN ApprovalHistory ah ON i.InvoiceId = ah.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE ah.Action = 'REJECTED'

UNION ALL

-- 10. Invoice Corrected (Inferred from update after rejection)
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Corrected' AS "ActivityName",
    i.LastUpdateDate AS "EventTime",
    i.LastUpdateDate AS "EndTime",
    i.LastUpdatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    i.ApprovalStatus AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE i.WfApprovalStatus = 'WORKFLOW_REJECTED' AND i.LastUpdatedBy <> 'FUSION_APPS_PRC_SOA_APPID'

UNION ALL

-- 11. Invoice Accounted
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Accounted' AS "ActivityName",
    i.LastUpdateDate AS "EventTime",
    i.LastUpdateDate AS "EndTime",
    i.LastUpdatedBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Accounted' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE i.PayablesAccountingStatus = 'ACCOUNTED'

UNION ALL

-- 12. Payment Scheduled
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Payment Scheduled' AS "ActivityName",
    inst.LastUpdateDate AS "EventTime",
    inst.LastUpdateDate AS "EndTime",
    i.LastUpdatedBy AS "UserName", -- User who ran the PPR is not in this PVO
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Selected for Payment' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE inst.PaymentStatusFlag = 'Y'

UNION ALL

-- 13. Payment Created
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Payment Created' AS "ActivityName",
    p.CreationDate AS "EventTime",
    p.CreationDate AS "EndTime",
    p.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Paid' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Payments p ON i.InvoiceId = p.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId

UNION ALL

-- 14. Payment Executed
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Payment Executed' AS "ActivityName",
    p.PaymentDate AS "EventTime",
    p.PaymentDate AS "EndTime",
    p.UserName AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Paid' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
JOIN Payments p ON i.InvoiceId = p.InvoiceId
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE p.PaymentDate IS NOT NULL

UNION ALL

-- 15. Invoice Canceled
SELECT
    i.InvoiceNumber AS "InvoiceNumber",
    'Invoice Canceled' AS "ActivityName",
    i.CancelledDate AS "EventTime",
    i.CancelledDate AS "EndTime",
    i.CancelledBy AS "UserName",
    i.InvoiceAmount AS "InvoiceAmount",
    i.VendorName AS "VendorName",
    inst.PaymentDueDate AS "PaymentDueDate",
    'Cancelled' AS "InvoiceStatus",
    i.CompanyCode AS "CompanyCode"
FROM Invoices i
LEFT JOIN Installments inst ON i.InvoiceId = inst.InvoiceId
WHERE i.CancelledDate IS NOT NULL;

步骤

访问Oracle BI Publisher：使用具有BI Administrator或类似角色的用户登录Oracle Fusion Applications。打开Navigator菜单，依次选择Tools和Reports and Analytics，进入Reports and Analytics工具。
进入目录：在Reports and Analytics工作区中，点击Browse Catalog按钮，打开Oracle BI Publisher界面。
创建新数据模型：在BI Publisher目录中进入合适的文件夹，例如Shared Folders>Custom。点击New下拉菜单并选择Data Model。
定义SQL查询数据集：在Data Model编辑器中点击“+”图标添加新数据集，然后从列表中选择SQL Query。
配置数据集：在New Data Set对话框中输入名称，例如P2P_Invoice_Events。选择合适的数据源，财务数据通常使用ApplicationDB_FSCM。确保SQL类型设置为Standard SQL。
输入SQL查询：复制本文档query部分提供的完整SQL，并粘贴到SQL Query文本区域。
定义参数：查询使用参数进行筛选。在Data Model属性中创建三个参数：p_start_date、p_end_date和p_bu_name。将数据类型设置为String。运行报告时，用户将提供参数值，例如日期使用“2023-01-01”，并填写具体业务单元名称。
保存数据模型：将数据模型保存到自定义文件夹。点击“Data”选项卡并输入已创建的参数值，即可查看示例数据。
创建报告：返回目录，点击New下拉菜单并选择Report。在报告创建向导中选择“Use Data Model”选项，然后找到刚刚保存的数据模型。
配置报告布局和输出：在报告编辑器中，使用简单表格布局即可。最重要的是配置默认输出格式。点击“View a List”，确保CSV为默认格式且仅启用CSV。这样可以确保输出为整洁、无格式的数据文件。
计划报告：保存报告。您可以按需运行，也可以为提高性能将其安排在业务低峰期运行。计划可以配置为将CSV输出发送到指定位置，例如Universal Content Management（UCM）服务器，之后即可从该位置获取文件并上传。
导出并准备数据：报告作业完成后，下载生成的CSV文件。上传到流程挖掘工具前，请确认列标题符合所需属性名称（InvoiceNumber、ActivityName、EventTime等）。

配置

数据源：查询必须针对Fusion Financials应用数据库运行，通常通过BI Publisher中的ApplicationDB_FSCMJNDI数据源连接。
参数：数据模型应配置以下参数，以支持灵活提取数据：
- p_start_date：提取期间的开始日期，格式为“YYYY-MM-DD”。
- p_end_date：提取期间的结束日期，格式为“YYYY-MM-DD”。
- p_bu_name：用于筛选数据的业务单元名称（公司代码）。如需提取所有业务单元的数据，请使用“%”等通配符。
日期范围：首次提取建议使用3至6个月的数据。这能在数据代表性和提取性能之间取得平衡。
性能注意事项：一次提取较长时间段或所有业务单元的数据可能消耗大量资源，并导致超时。建议将大型提取拆分为较小的连续批次，例如按月提取，或安排在业务低峰期运行。
前提条件：创建和运行报告的用户需要具备访问BI Publisher工具的角色（例如BI Administrator），以及查看目标业务单元对应应付账款底层表（AP_INVOICES_ALL、AP_PAYMENTS_ALL等）所需的数据安全权限。

a 示例查询 sql

WITH INVOICE_BASE AS (
    SELECT 
        AIA.INVOICE_ID,
        AIA.INVOICE_NUM,
        AIA.INVOICE_AMOUNT,
        AIA.CREATION_DATE,
        AIA.CREATED_BY,
        AIA.LAST_UPDATE_DATE,
        AIA.LAST_UPDATED_BY,
        AIA.CANCELLED_DATE,
        AIA.CANCELLED_BY,
        AIA.WFAPPROVAL_STATUS,
        AIA.TERMS_DATE AS PAYMENT_DUE_DATE,
        PSV.VENDOR_NAME,
        FABUV.BU_NAME AS COMPANY_CODE
    FROM 
        AP_INVOICES_ALL AIA
    JOIN 
        POZ_SUPPLIERS_V PSV ON AIA.VENDOR_ID = PSV.VENDOR_ID
    JOIN
        FUN_ALL_BUSINESS_UNITS_V FABUV ON AIA.ORG_ID = FABUV.BU_ID
    WHERE 
        AIA.CREATION_DATE BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')
        AND FABUV.BU_NAME LIKE :p_bu_name
)
-- 1. Invoice Created
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Created' AS "ActivityName",
    CAST(IB.CREATION_DATE AS TIMESTAMP) AS "EventTime",
    CAST(IB.CREATION_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = IB.CREATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    INVOICE_BASE IB

UNION ALL

-- 2. Invoice Validated
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Validated' AS "ActivityName",
    CAST(AIA.LAST_UPDATE_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AIA.LAST_UPDATE_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AIA.LAST_UPDATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    AIA.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    AP_INVOICES_ALL AIA
JOIN 
    INVOICE_BASE IB ON AIA.INVOICE_ID = IB.INVOICE_ID
WHERE 
    AIA.WFAPPROVAL_STATUS IN ('VALIDATED', 'NEEDS REVALIDATION', 'STOPPED')

UNION ALL

-- 3. Invoice Matched to PO
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Matched to PO' AS "ActivityName",
    CAST(MIN(AID.CREATION_DATE) AS TIMESTAMP) AS "EventTime",
    CAST(MIN(AID.CREATION_DATE) AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = MIN(AID.CREATED_BY) AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    AP_INVOICE_DISTRIBUTIONS_ALL AID
JOIN 
    INVOICE_BASE IB ON AID.INVOICE_ID = IB.INVOICE_ID
WHERE
    AID.PO_DISTRIBUTION_ID IS NOT NULL
GROUP BY
    IB.INVOICE_NUM, IB.INVOICE_AMOUNT, IB.VENDOR_NAME, IB.PAYMENT_DUE_DATE, IB.WFAPPROVAL_STATUS, IB.COMPANY_CODE

UNION ALL

-- 4. Matching Discrepancy Identified & 5. Hold Placed on Invoice
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    CASE 
        WHEN AH.HOLD_LOOKUP_CODE IN ('QTY ORD', 'QTY REC', 'PRICE', 'AMT ORD', 'AMT REC') THEN 'Matching Discrepancy Identified'
        ELSE 'Hold Placed on Invoice'
    END AS "ActivityName",
    CAST(AH.HOLD_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AH.HOLD_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AH.CREATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    AP_HOLDS_ALL AH
JOIN 
    INVOICE_BASE IB ON AH.INVOICE_ID = IB.INVOICE_ID

UNION ALL

-- 6. Hold Released from Invoice
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Hold Released from Invoice' AS "ActivityName",
    CAST(AH.RELEASE_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AH.RELEASE_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AH.LAST_UPDATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    AP_HOLDS_ALL AH
JOIN 
    INVOICE_BASE IB ON AH.INVOICE_ID = IB.INVOICE_ID
WHERE 
    AH.RELEASE_LOOKUP_CODE IS NOT NULL AND AH.RELEASE_DATE IS NOT NULL

UNION ALL

-- 7. Invoice Sent for Approval, 8. Invoice Approved, 9. Invoice Rejected
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    CASE 
        WHEN AAH.ACTION = 'INITIATED' THEN 'Invoice Sent for Approval'
        WHEN AAH.ACTION = 'APPROVED' THEN 'Invoice Approved'
        WHEN AAH.ACTION = 'REJECTED' THEN 'Invoice Rejected'
    END AS "ActivityName",
    CAST(AAH.RESPONSE_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AAH.RESPONSE_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AAH.RESPONSE_ID AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    AP_INV_APRVL_HIST_ALL AAH
JOIN 
    INVOICE_BASE IB ON AAH.INVOICE_ID = IB.INVOICE_ID
WHERE
    AAH.ACTION IN ('INITIATED', 'APPROVED', 'REJECTED') AND AAH.RESPONSE_DATE IS NOT NULL

UNION ALL

-- 10. Invoice Corrected
SELECT DISTINCT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Corrected' AS "ActivityName",
    CAST(IB.LAST_UPDATE_DATE AS TIMESTAMP) AS "EventTime",
    CAST(IB.LAST_UPDATE_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = IB.LAST_UPDATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    INVOICE_BASE IB
WHERE
    IB.LAST_UPDATE_DATE > IB.CREATION_DATE
    AND IB.LAST_UPDATED_BY <> IB.CREATED_BY 
    AND EXISTS (
        SELECT 1 FROM AP_INV_APRVL_HIST_ALL AAH 
        WHERE AAH.INVOICE_ID = IB.INVOICE_ID AND AAH.ACTION = 'REJECTED' AND IB.LAST_UPDATE_DATE > AAH.RESPONSE_DATE
    )

UNION ALL

-- 11. Invoice Accounted
SELECT 
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Accounted' AS "ActivityName",
    CAST(MIN(XAH.ACCOUNTING_DATE) AS TIMESTAMP) AS "EventTime",
    CAST(MIN(XAH.ACCOUNTING_DATE) AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = MIN(XAH.CREATED_BY) AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM XLA_AE_HEADERS XAH
JOIN XLA_TRANSACTION_ENTITIES XTE ON XAH.ENTITY_ID = XTE.ENTITY_ID
JOIN INVOICE_BASE IB ON XTE.SOURCE_ID_INT_1 = IB.INVOICE_ID
WHERE XTE.APPLICATION_ID = 200
AND XTE.ENTITY_CODE = 'AP_INVOICES'
AND XAH.ACCOUNTING_ENTRY_STATUS_CODE = 'F' -- Final
GROUP BY
    IB.INVOICE_NUM, IB.INVOICE_AMOUNT, IB.VENDOR_NAME, IB.PAYMENT_DUE_DATE, IB.WFAPPROVAL_STATUS, IB.COMPANY_CODE

UNION ALL

-- 12. Payment Scheduled
SELECT 
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Payment Scheduled' AS "ActivityName",
    CAST(MIN(APISC.CREATION_DATE) AS TIMESTAMP) AS "EventTime",
    CAST(MIN(APISC.CREATION_DATE) AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = MIN(APISC.CREATED_BY) AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM AP_INV_SELECTION_CRITERIA_ALL APISC
JOIN AP_INVOICES_ALL AIA ON APISC.CHECKRUN_NAME = AIA.PAYMENT_STATUS_FLAG
JOIN INVOICE_BASE IB ON AIA.INVOICE_ID = IB.INVOICE_ID
GROUP BY
    IB.INVOICE_NUM, IB.INVOICE_AMOUNT, IB.VENDOR_NAME, IB.PAYMENT_DUE_DATE, IB.WFAPPROVAL_STATUS, IB.COMPANY_CODE

UNION ALL

-- 13. Payment Created
SELECT 
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Payment Created' AS "ActivityName",
    CAST(AIPA.CREATION_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AIPA.CREATION_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AIPA.CREATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM AP_INVOICE_PAYMENTS_ALL AIPA
JOIN INVOICE_BASE IB ON AIPA.INVOICE_ID = IB.INVOICE_ID

UNION ALL

-- 14. Payment Executed
SELECT 
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Payment Executed' AS "ActivityName",
    CAST(AC.CLEARED_DATE AS TIMESTAMP) AS "EventTime",
    CAST(AC.CLEARED_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = AC.LAST_UPDATED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM AP_INVOICE_PAYMENTS_ALL AIPA
JOIN AP_CHECKS_ALL AC ON AIPA.CHECK_ID = AC.CHECK_ID
JOIN INVOICE_BASE IB ON AIPA.INVOICE_ID = IB.INVOICE_ID
WHERE AC.CLEARED_DATE IS NOT NULL

UNION ALL

-- 15. Invoice Canceled
SELECT
    IB.INVOICE_NUM AS "InvoiceNumber",
    'Invoice Canceled' AS "ActivityName",
    CAST(IB.CANCELLED_DATE AS TIMESTAMP) AS "EventTime",
    CAST(IB.CANCELLED_DATE AS TIMESTAMP) AS "EndTime",
    (SELECT USERNAME FROM PER_USERS PU WHERE PU.USER_ID = IB.CANCELLED_BY AND ROWNUM = 1) AS "UserName",
    IB.INVOICE_AMOUNT AS "InvoiceAmount",
    IB.VENDOR_NAME AS "VendorName",
    IB.PAYMENT_DUE_DATE AS "PaymentDueDate",
    IB.WFAPPROVAL_STATUS AS "InvoiceStatus",
    IB.COMPANY_CODE AS "CompanyCode"
FROM
    INVOICE_BASE IB
WHERE
    IB.CANCELLED_DATE IS NOT NULL

步骤

前提条件：确保系统已安装Python3.6或更高版本，以及requests和pandas库。您可以使用pip安装：pip install requests pandas。
设置Oracle Fusion API：在Oracle Fusion实例中进入Security Console。创建新的机密应用以获取API访问权限，并记录分配的Client ID和Client Secret。确保应用用户具备读取发票和付款数据所需的角色，例如Financials - Payables Invoice Inquiry Duty角色。
配置Python脚本：将提供的Python脚本复制到文件中，例如extract_fusion_invoices.py。打开文件，填写脚本顶部的占位变量，包括CLIENT_ID、CLIENT_SECRET、TOKEN_URL、FUSION_HOST、START_DATE和END_DATE。FUSION_HOST应设置为Oracle Cloud应用的基础URL。
设置提取期间：修改START_DATE和END_DATE变量，定义数据提取的时间范围。建议先使用较短的期间，例如一个月，以测试脚本并验证输出。
执行脚本：在命令行或终端中进入脚本所在目录，输入python extract_fusion_invoices.py运行脚本。脚本将完成身份验证、获取数据，并在控制台显示进度信息。
身份验证流程：脚本首先使用客户端凭据向Oracle身份提供商（TOKEN_URL）发送请求，以获取OAuth访问令牌。随后，脚本会在所有API请求的标头中加入该令牌，以便向Fusion Financials API进行身份验证。
获取数据和分页：脚本查询invoicesREST API端点，获取指定日期范围内创建的记录。它会检查API响应中的hasMore标记，自动处理分页，并使用更新后的offset参数继续请求，直到获取全部发票数据。
获取详细数据：对于每张获取的发票，脚本会额外调用API获取关联明细。它查询/child/holds端点获取挂起和解除挂起信息，并按发票号筛选/payments端点以获取付款数据。
生成事件日志：脚本的核心逻辑会处理API返回的原始JSON数据。通过检查特定日期、状态和子记录，为15项所需业务活动分别生成数据行。例如，存在CancelledDate时会生成“发票已取消”活动。
检查输出：脚本完成后，会在同一目录中创建名为invoice_event_log.csv的文件。使用电子表格应用打开CSV文件并检查数据，确认所需列（InvoiceNumber、ActivityName、EventTime）及推荐属性均已存在。
准备上传：确保CSV文件中的列标题与所需属性名称一致。通常无需进一步格式化，文件即可上传到流程挖掘工具。

配置

身份验证凭据：需要在Oracle Fusion的Security Console中注册机密应用，并获取其Client ID和Client Secret。同时必须提供身份域的Token URL。
API主机URL：FUSION_HOST变量必须设置为Oracle Fusion实例的基础URL，例如https://[your-instance].fa.us2.oraclecloud.com。
日期范围：START_DATE和END_DATE变量用于控制提取范围，十分关键。首次分析建议提取3至6个月的数据，以平衡数据量和性能。
使用的API端点：脚本主要调用fscmRestApi/resources/11.13.18.05/invoices和fscmRestApi/resources/11.13.18.05/payments端点，同时使用/invoices/{InvoiceId}/child/holds子资源。
分页限制：脚本中的LIMIT变量控制每次API请求获取的记录数，默认值为100。提高该值可以减少API调用次数，但会增加单次请求的内存消耗。如果遇到超时错误，可能需要降低该值。
所需权限：与API凭据关联的用户账户需要具备读取应付发票、发票挂起、付款和供应商信息的权限。Payables Invoice Inquiry Duty角色通常可以提供足够的权限。

a 示例查询 python

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

class=class="hl-string">"hl-comment"># --- Configuration Settings ---
class=class="hl-string">"hl-comment"># Replace with your Oracle Fusion credentials and instance details
CLIENT_ID = class="hl-string">'[Your Client ID]'
CLIENT_SECRET = class="hl-string">'[Your Client Secret]'
TOKEN_URL = class="hl-string">'[Your Oracle Identity Cloud Service Token URL, e.g., https://idcs-....identity.oraclecloud.com/oauth2/v1/token]'
FUSION_HOST = class="hl-string">'[Your Fusion Host URL, e.g., https://your-fusion-instance.fa.ocs.oraclecloud.com]'

class=class="hl-string">"hl-comment"># --- Extraction Parameters ---
class=class="hl-string">"hl-comment"># Set the date range for the invoice extraction (YYYY-MM-DD)
START_DATE = class="hl-string">'2023-01-01'
END_DATE = class="hl-string">'2023-06-30'

class=class="hl-string">"hl-comment"># API request settings
LIMIT = 100

class=class="hl-string">"hl-comment"># --- Helper Functions ---
def get_access_token():
    class="hl-string">"""Authenticates and retrieves an OAuth2 access token."""
    headers = {class="hl-string">'Content-Type': class="hl-string">'application/x-www-form-urlencoded'}
    data = {
        class="hl-string">'grant_type': class="hl-string">'client_credentials',
        class="hl-string">'scope': class="hl-string">'urn:opc:resource:consumer::all'
    }
    try:
        response = requests.post(TOKEN_URL, headers=headers, data=data, auth=(CLIENT_ID, CLIENT_SECRET))
        response.raise_for_status()
        return response.json().get(class="hl-string">'access_token')
    except requests.exceptions.RequestException as e:
        print(fclass="hl-string">"Error getting access token: {e}")
        return None

def fetch_data(api_url, headers, params):
    class="hl-string">"""Fetches data from a given API endpoint with pagination handling."""
    all_items = []
    offset = 0
    has_more = True

    while has_more:
        params[class="hl-string">'offset'] = offset
        try:
            response = requests.get(api_url, headers=headers, params=params)
            response.raise_for_status()
            data = response.json()
            items = data.get(class="hl-string">'items', [])
            all_items.extend(items)
            has_more = data.get(class="hl-string">'hasMore', False)
            offset += len(items)
            print(fclass="hl-string">"Fetched {len(all_items)} records so far...")
        except requests.exceptions.RequestException as e:
            print(fclass="hl-string">"Error fetching data from {api_url}: {e}")
            print(fclass="hl-string">"Response content: {response.text}")
            break
    return all_items

class=class="hl-string">"hl-comment"># --- Main Extraction Logic ---
def main():
    class="hl-string">"""Main function to extract, transform, and save invoice data."""
    access_token = get_access_token()
    if not access_token:
        print(class="hl-string">"Could not obtain access token. Exiting.")
        return

    headers = {
        class="hl-string">'Authorization': fclass="hl-string">'Bearer {access_token}',
        class="hl-string">'Content-Type': class="hl-string">'application/vnd.oracle.adf.resourceitem+json'
    }

    event_log = []

    class=class="hl-string">"hl-comment"># 1. Fetch Invoices
    print(class="hl-string">"Starting invoice extraction...")
    invoice_url = fclass="hl-string">'{FUSION_HOST}/fscmRestApi/resources/11.13.18.05/invoices'
    invoice_params = {
        class="hl-string">'q': fclass="hl-string">'CreationDate between \'{START_DATE}T00:00:00.000Z\class="hl-string">' and \'{END_DATE}T23:59:59.999Z\class="hl-string">'',
        class="hl-string">'onlyData': class="hl-string">'true',
        class="hl-string">'limit': LIMIT,
        class="hl-string">'fields': class="hl-string">'InvoiceId,InvoiceNumber,InvoiceAmount,CreationDate,CreatedBy,LastUpdateDate,LastUpdatedBy,SupplierName,ValidationDate,CancelledDate,ApprovalStatus,AccountingDate,PaymentStatus,DueDate,InvoiceStatus,BusinessUnitName'
    }
    invoices = fetch_data(invoice_url, headers, invoice_params)
    print(fclass="hl-string">"Total invoices fetched: {len(invoices)}")

    class=class="hl-string">"hl-comment"># 2. Process each invoice to create events
    for inv in invoices:
        case_id = inv.get(class="hl-string">'InvoiceNumber')
        if not case_id:
            continue

        base_event = {
            class="hl-string">'InvoiceNumber': case_id,
            class="hl-string">'EndTime': None,
            class="hl-string">'InvoiceAmount': inv.get(class="hl-string">'InvoiceAmount'),
            class="hl-string">'VendorName': inv.get(class="hl-string">'SupplierName'),
            class="hl-string">'PaymentDueDate': inv.get(class="hl-string">'DueDate'),
            class="hl-string">'InvoiceStatus': inv.get(class="hl-string">'InvoiceStatus'),
            class="hl-string">'CompanyCode': inv.get(class="hl-string">'BusinessUnitName')
        }

        class=class="hl-string">"hl-comment"># Activity: Invoice Created
        if inv.get(class="hl-string">'CreationDate'):
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Created', class="hl-string">'EventTime': inv[class="hl-string">'CreationDate'], class="hl-string">'UserName': inv.get(class="hl-string">'CreatedBy')})

        class=class="hl-string">"hl-comment"># Activity: Invoice Validated
        if inv.get(class="hl-string">'ValidationDate'):
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Validated', class="hl-string">'EventTime': inv[class="hl-string">'ValidationDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})
        
        class=class="hl-string">"hl-comment"># Activities based on Approval Status
        if inv.get(class="hl-string">'ApprovalStatus') in [class="hl-string">'Initiated', class="hl-string">'Required']:
             event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Sent for Approval', class="hl-string">'EventTime': inv[class="hl-string">'LastUpdateDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})
        elif inv.get(class="hl-string">'ApprovalStatus') in [class="hl-string">'Approved', class="hl-string">'Not required', class="hl-string">'Workflow approved']:
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Approved', class="hl-string">'EventTime': inv[class="hl-string">'LastUpdateDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})
        elif inv.get(class="hl-string">'ApprovalStatus') == class="hl-string">'Rejected':
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Rejected', class="hl-string">'EventTime': inv[class="hl-string">'LastUpdateDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})
        
        class=class="hl-string">"hl-comment"># This is an inference, might represent corrections after rejection or validation failure
        if inv.get(class="hl-string">'InvoiceStatus') == class="hl-string">'Needs revalidation':
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Corrected', class="hl-string">'EventTime': inv[class="hl-string">'LastUpdateDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})

        class=class="hl-string">"hl-comment"># Activity: Invoice Accounted
        if inv.get(class="hl-string">'AccountingDate'):
             event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Accounted', class="hl-string">'EventTime': inv[class="hl-string">'AccountingDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})

        class=class="hl-string">"hl-comment"># Activity: Invoice Canceled
        if inv.get(class="hl-string">'CancelledDate'):
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Canceled', class="hl-string">'EventTime': inv[class="hl-string">'CancelledDate'], class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})
        
        class=class="hl-string">"hl-comment"># Activity: Matched to PO - Inference based on PaymentStatus which can indicate matching holds resolved
        if inv.get(class="hl-string">'PaymentStatus') == class="hl-string">'Available':
             event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Invoice Matched to PO', class="hl-string">'EventTime': inv.get(class="hl-string">'ValidationDate') or inv.get(class="hl-string">'LastUpdateDate'), class="hl-string">'UserName': inv.get(class="hl-string">'LastUpdatedBy')})

        class=class="hl-string">"hl-comment"># 3. Fetch Holds for the Invoice
        holds_url = fclass="hl-string">'{FUSION_HOST}/fscmRestApi/resources/11.13.18.05/invoices/{inv["InvoiceId"]}/child/holds'
        holds = fetch_data(holds_url, headers, {class="hl-string">'onlyData': class="hl-string">'true'})
        for hold in holds:
            class=class="hl-string">"hl-comment"># Activity: Hold Placed on Invoice
            event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Hold Placed on Invoice', class="hl-string">'EventTime': hold[class="hl-string">'HoldDate'], class="hl-string">'UserName': hold.get(class="hl-string">'LastUpdatedBy')})
            if hold.get(class="hl-string">'HoldReason') in [class="hl-string">'Price', class="hl-string">'Qty Ord', class="hl-string">'Qty Rec', class="hl-string">'Quality']:
                event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Matching Discrepancy Identified', class="hl-string">'EventTime': hold[class="hl-string">'HoldDate'], class="hl-string">'UserName': hold.get(class="hl-string">'LastUpdatedBy')})
            
            class=class="hl-string">"hl-comment"># Activity: Hold Released from Invoice
            if hold.get(class="hl-string">'ReleaseDate'):
                event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Hold Released from Invoice', class="hl-string">'EventTime': hold[class="hl-string">'ReleaseDate'], class="hl-string">'UserName': hold.get(class="hl-string">'LastUpdatedBy')})

        class=class="hl-string">"hl-comment"># 4. Fetch Payments for the Invoice
        if inv.get(class="hl-string">'PaymentStatus') in [class="hl-string">'Paid', class="hl-string">'Partially paid']:
            payment_url = fclass="hl-string">'{FUSION_HOST}/fscmRestApi/resources/11.13.18.05/payments'
            payment_params = {
                class="hl-string">'q': fclass="hl-string">'InvoiceNumber=\'{case_id}\class="hl-string">'',
                class="hl-string">'onlyData': class="hl-string">'true',
                class="hl-string">'fields': class="hl-string">'PaymentId,CreationDate,CreatedBy,ClearedDate,PaymentDate'
            }
            payments = fetch_data(payment_url, headers, payment_params)
            for pmt in payments:
                 class=class="hl-string">"hl-comment"># Activity: Payment Scheduled (Approximation using Payment Creation Date)
                 event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Payment Scheduled', class="hl-string">'EventTime': pmt[class="hl-string">'CreationDate'], class="hl-string">'UserName': pmt.get(class="hl-string">'CreatedBy')})
                 class=class="hl-string">"hl-comment"># Activity: Payment Created
                 event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Payment Created', class="hl-string">'EventTime': pmt[class="hl-string">'PaymentDate'], class="hl-string">'UserName': pmt.get(class="hl-string">'CreatedBy')})
                 class=class="hl-string">"hl-comment"># Activity: Payment Executed
                 if pmt.get(class="hl-string">'ClearedDate'):
                     event_log.append({**base_event, class="hl-string">'ActivityName': class="hl-string">'Payment Executed', class="hl-string">'EventTime': pmt[class="hl-string">'ClearedDate'], class="hl-string">'UserName': pmt.get(class="hl-string">'CreatedBy')})

    class=class="hl-string">"hl-comment"># 5. Create and Save DataFrame
    if not event_log:
        print(class="hl-string">"No events were generated. Please check your date range and API responses.")
        return

    df = pd.DataFrame(event_log)
    df.sort_values(by=[class="hl-string">'InvoiceNumber', class="hl-string">'EventTime'], inplace=True)
    df[class="hl-string">'EventTime'] = pd.to_datetime(df[class="hl-string">'EventTime']).dt.strftime(class="hl-string">'%Y-%m-%d %H:%M:%S')
    if class="hl-string">'EndTime' in df.columns:
         df[class="hl-string">'EndTime'] = pd.to_datetime(df[class="hl-string">'EndTime']).dt.strftime(class="hl-string">'%Y-%m-%d %H:%M:%S')

    output_filename = class="hl-string">'invoice_event_log.csv'
    df.to_csv(output_filename, index=False)
    print(fclass="hl-string">"Extraction complete. Event log saved to {output_filename}")

if __name__ == class="hl-string">'__main__':
    main()

准备好开始了吗？

使用此模板准备数据，开始优化发票处理流程。获取有价值的洞察，显著提升组织效率。

返回改进指南下载模板

立即优化P2P发票处理流程，周期缩短30%

消除Oracle Fusion Financials中的瓶颈，将周期时间缩短30%。

开始免费试用

无需信用卡，数日内即可看到结果。

您的采购到付款：发票处理数据模板

您的采购到付款：发票处理数据模板

采购到付款－发票处理属性

采购到付款－发票处理活动

提取指南

Oracle BI Cloud Connector（BICC）批量数据导出

步骤

配置

a 示例查询 sql

使用自定义SQL数据模型的Oracle BI Publisher报告

步骤

配置

a 示例查询 sql

使用Fusion Financials REST API提取数据的Python脚本

步骤

配置

a 示例查询 python

准备好开始了吗？

立即优化P2P发票处理流程，周期缩短30%

您的采购到付款：发票处理数据模板

您的采购到付款：发票处理数据模板

采购到付款－发票处理属性

采购到付款－发票处理活动

提取指南

Oracle BI Cloud Connector（BICC）批量数据导出

步骤

配置

a 示例查询 sql

使用自定义SQL数据模型的Oracle BI Publisher报告

步骤

配置

a 示例查询 sql

使用Fusion Financials REST API提取数据的Python脚本

步骤

配置

a 示例查询 python

准备好开始了吗？

立即优化P2P发票处理流程，周期缩短30%

我们重视您的隐私