> 持续流程改进 > 采购到付款：发票处理 > 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中底层数据最近一次修改的时间，用于管理增量数据加载，确保流程挖掘模型保持最新。虽然该时间戳不直接用于流程分析，但对于保持数据的时效性和完整性至关重要。数据管道可据此高效查询自上次更新以来新增或变更的记录，减轻源系统负载。重要性支持数据管道高效运行增量加载，让流程分析保持最新，无需完整重新加载。获取途径在许多Oracle Fusion表中，该字段通常名为LAST_UPDATE_DATE，例如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	批准或拒绝发票的人员姓名。
说明此属性记录审批步骤中采取操作的人员身份，适用于“发票已批准”或“发票已拒绝”等活动。分析时，审批人姓名可用于了解审批工作量、衡量个人审批周期时间，并审计审批政策的执行情况。对于“审批合规率”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）关联起来，该订单用于授权采购商品或服务。发票可以有采购订单，也可以没有采购订单。按采购订单分析可将发票流程与P2P流程中的采购环节关联起来。这有助于了解采购流程是否符合要求，以及发票匹配差异等问题是否源于采购订单本身。是否存在采购订单编号，是细分和分析不同发票处理路径的主要依据。重要性将发票与采购流程关联起来，是分析有采购订单与无采购订单发票流程的重要属性。获取途径可通过AP_INVOICE_LINES_ALL中的发票行项目与PO_DISTRIBUTION_ID关联采购订单分配信息。示例 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_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
	发票已记账	发票已成功过账至总账，并生成会计分录。此事件确认发票的财务影响已正式记录。
重要性这是重要的财务控制节点，也是付款的前提。它确认发票已完成验证和审批，可以进行结算。获取途径可根据AP_INVOICE_DISTRIBUTIONS_ALL表中的状态（ACCRUAL_POSTED_FLAG = 'Y'）推断，也可检查总账表（如XLA_AE_HEADERS）中是否存在对应的会计分录。采集根据AP_INVOICE_DISTRIBUTIONS_ALL中的标记或关联的总账分录推断。事件类型 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表中与匹配相关的冻结类型，例如“QTY REC”或“PRICE”。HOLD_DATE表示时间戳。采集 AP_HOLDS_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。获取途径如果发票已验证或提交审批，可通过跟踪之后AP_INVOICES_ALL中发票记录的重要更新来推断此事件。需要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

建议填写选填

数据提取指南

如何从Oracle Fusion Financials获取数据

步骤

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

配置

关键公共视图对象（PVO）：提取过程依赖Financials产品中的多个核心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。

查询示例 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，进入报表与分析工具。
打开目录：在报表与分析工作区中，点击Browse Catalog按钮，打开Oracle BI Publisher界面。
创建数据模型：在BI Publisher目录中，进入合适的文件夹，例如Shared Folders > Custom。点击New下拉菜单并选择Data Model。
定义SQL查询数据集：在数据模型编辑器中，点击“+”图标添加数据集，然后从列表中选择SQL Query。
配置数据集：在New Data Set对话框中输入名称，例如P2P_Invoice_Events。选择适当的数据源，财务数据通常使用ApplicationDB_FSCM。确保SQL类型设为Standard SQL。
输入SQL查询：复制本文档query部分提供的完整SQL，并粘贴到SQL Query文本框中。
定义参数：查询使用参数进行筛选。在数据模型属性中创建三个参数：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_FSCM JNDI数据源连接。
参数：数据模型应配置以下参数，以便灵活提取数据：
- 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等）所需的数据安全权限。

查询示例 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

步骤

前提条件：确保系统已安装Python 3.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身份验证。
获取数据和分页：脚本查询invoices REST API端点，获取指定日期范围内创建的记录。脚本会检查API响应中的hasMore标记，并使用更新后的offset参数继续请求，直至获取所有发票数据。
获取详细数据：对于获取的每张发票，脚本都会额外调用API获取相关详细信息。它会查询/child/holds端点获取冻结和解除冻结信息，并按发票编号筛选/payments端点以获取付款数据。
生成事件日志：脚本的核心逻辑会处理API返回的原始JSON数据，并根据特定日期、状态和子记录，为15项必需业务活动分别生成数据行。例如，存在CancelledDate时会生成“发票已取消”事件。
检查输出：脚本运行完成后，会在同一目录下生成invoice_event_log.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角色通常可提供足够权限。

查询示例 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）批量数据导出

步骤

配置

查询示例 sql

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

步骤

配置

查询示例 sql

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

步骤

配置

查询示例 python

准备好开始了吗？

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