> Continuous Process Improvement > Accounts Payable Payment Processing > SAP ECC > Data Template

Your Accounts Payable Payment Processing Data Template

SAP ECC

Accounts Payable Payment Processing Attributes (21) Accounts Payable Payment Processing Activities (13) Extraction Guides (3)

Your Accounts Payable Payment Processing Data Template

This template offers a structured approach to mapping your payment workflows in SAP ECC by identifying essential data points and milestones. It provides a comprehensive list of attributes and activities alongside practical extraction guidance to help you build a robust event log. By following this guide, you can pinpoint payment delays and streamline your financial operations effectively.

Essential data fields for payment analysis
Key process milestones for tracking workflows
Step-by-step extraction guidance for SAP ECC

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

Download Template

Accounts Payable Payment Processing Attributes

This table outlines the recommended data fields to capture from your SAP ECC system to enable a deep analysis of your payment lifecycle.

5 Required 10 Recommended 6 Optional

	Name	Description
	Activity Name ActivityName	The specific process step or action performed.
Description This attribute describes the event that occurred in the accounts payable process, such as 'Invoice Posted', 'Payment Block Applied', or 'Payment Run Executed'. It defines the nodes in the process map. In analysis, the sequence of these activities allows for the visualization of process variants, identification of rework loops (e.g., block removal followed by block re-application), and compliance checking against the standard approval workflow. Why it matters It determines the process flow and is required to visualize the journey of the invoice. Where to get Derived from Transaction Codes (TCODE), Change Document Object Classes (CDHDR), or Workflow Logs Examples Invoice PostedPayment Block RemovedPrice Change
	Event Timestamp EventTimestamp	The exact date and time when the activity occurred.
Description This attribute records the precise moment an action took place in the SAP system. It typically combines the system date and system time fields from the relevant tables (e.g., CPUDT and CPUTM). It is crucial for calculating all time-based KPIs, including Cycle Time, Approval Lead Time, and process throughput. Without accurate timestamps, it is impossible to determine the order of events or measure efficiency. Why it matters Essential for sequencing events and calculating duration metrics. Where to get SAP ECC tables BKPF (CPUDT/CPUTM) or CDHDR (UDATE/UTIME) Examples 2023-10-15T09:30:00Z2023-10-15T14:45:12Z2023-10-16T08:15:00Z
	Invoice Number InvoiceNumber	The unique identifier for the vendor invoice document.
Description This attribute serves as the central case identifier for the Accounts Payable process. In SAP ECC, this is technically a concatenation of the Client, Company Code, Fiscal Year, and Accounting Document Number (BELNR) to ensure global uniqueness across the system. It groups all activities related to a specific liability to a vendor. Analysis uses this field to track the end-to-end lifecycle of a payment obligation. It allows process mining tools to reconstruct the history of an invoice from the moment it is received or scanned until the final clearing entry is posted in the General Ledger. Why it matters It is the fundamental key for linking events, changing statuses, and financial postings into a single process instance. Where to get SAP ECC table BKPF field BELNR (combined with BUKRS and GJAHR) Examples 1000-2023-1900001234US01-2023-51000008922000-2024-1500004455
	Last Data Update LastDataUpdate	The timestamp of the most recent data extraction.
Description This attribute indicates when the data record was last refreshed from the source system. It is used to determine the freshness of the analysis and to manage incremental data loads. In dashboards, this helps users understand if they are looking at real-time data or a snapshot from a previous period, which is critical for operational monitoring of open invoices. Why it matters Provides context on data latency and reliability. Where to get ETL process metadata Examples 2023-11-01T00:00:00Z2023-11-01T12:00:00Z
	Source System SourceSystem	The identifier of the SAP ERP instance.
Description This attribute identifies the specific SAP ECC system or client from which the data was extracted. In multi-system landscapes, this is vital for segregating data and analyzing performance across different regions or business units. It helps users filter the process view to specific environments and ensures unique case identification when multiple SAP instances are ingested into the same process mining data model. Why it matters Ensures data uniqueness and context in multi-ERP environments. Where to get System configuration or extraction parameter Examples SAP_ECC_PRODERP_NASAP_P01
	Clearing Date ClearingDate	The date the invoice was cleared or paid in the system.
Description This attribute (AUGDT) records when the open item was cleared in the General Ledger, signifying the completion of the payment process. It is the end timestamp for the 'Average Invoice Cycle Time' KPI. Comparing this date to the Due Date determines if a payment was late or on time. Why it matters Marks the completion of the financial process. Where to get SAP ECC table BSEG field AUGDT Examples 2023-11-202023-12-05
	Company Code CompanyCode	The organizational unit for which the financial statements are created.
Description The Company Code (BUKRS) is the central organizational unit in SAP Financial Accounting. It represents a specific legal entity or subsidiary within the enterprise structure. This attribute is used to slice and dice process performance by subsidiary or region. It allows stakeholders to compare Late Payment Rates or Automation Rates across different business units to identify leaders and laggards. Why it matters Primary dimension for organizational benchmarking. Where to get SAP ECC table BKPF field BUKRS Examples 1000US01DE10
	Document Type DocumentType	Classifies the accounting document (e.g., Invoice, Credit Memo).
Description The Document Type (BLART) categorizes the accounting entry, distinguishing between standard vendor invoices (e.g., KR), credit memos (KG), or payments (KZ). Filtering by Document Type is essential for accurate cycle time analysis, as credit memos follow a different process flow than standard invoices. It ensures that the analysis compares like-for-like processes. Why it matters Distinguishes between different financial workflows like invoices and credit notes. Where to get SAP ECC table BKPF field BLART Examples KRREKG
	Invoice Amount InvoiceAmount	The total monetary value of the invoice in local currency.
Description This attribute represents the amount to be paid to the vendor (DMBTR or WRBTR). It is critical for assessing the financial impact of process inefficiencies. Used in the 'Activity Amount' mapping, this field allows for the calculation of value-weighted KPIs. For example, a late payment on a high-value invoice is more critical than on a low-value one. It helps prioritize work based on working capital impact. Why it matters Quantifies the financial magnitude of the process instance. Where to get SAP ECC table BSEG field DMBTR (Local Currency) or WRBTR (Document Currency) Examples 1500.00230.5010500.00
	Payment Block Code PaymentBlockCode	Indicates if and why an invoice is blocked for payment.
Description This attribute (ZLSPR) contains the code that prevents an invoice from being picked up by the automatic payment run (e.g., 'R' for Invoice Verification, 'A' for Locked). Monitoring this attribute is the core of the 'Payment Block and Hold Resolution' dashboard. It allows analysts to identify the most common reasons for payment delays and measure the duration invoices spend in a blocked state. Why it matters Primary indicator of process friction and manual intervention needs. Where to get SAP ECC table BSEG field ZLSPR Examples ARnull
	Payment Method PaymentMethod	The method used to pay the invoice (e.g., Check, Wire, ACH).
Description This attribute (ZLSCH) specifies how the payment is to be or was executed. It distinguishes between manual checks, bank transfers, and electronic payments. This field drives the 'Payment Method Automation Mix' dashboard and the 'Electronic Payment Adoption Rate' KPI. It helps organizations track their shift from high-cost manual checks to low-cost electronic transfers. Why it matters Tracks the efficiency and cost of the payment execution phase. Where to get SAP ECC table BSEG or BKPF field ZLSCH Examples CTU
	Payment Terms PaymentTerms	The code defining the conditions for payment and discounts.
Description This attribute stores the Key for Terms of Payment (ZTERM), which dictates when the invoice is due and if any cash discounts apply (e.g., 2% net 10). It is the baseline for calculating the 'Early Payment Discount Capture Rate'. Analysis uses this code to compute the target payment date and identify deviations that lead to lost discounts or penalties. Why it matters Defines the financial deadline and discount opportunities. Where to get SAP ECC table BSEG field ZTERM Examples Z001NT300002
	Purchase Order Number PurchaseOrderNumber	The reference to the purchasing document linked to the invoice.
Description This attribute contains the Purchase Order number (EBELN) if the invoice is PO-backed. It links the Accounts Payable process back to the Procurement process. It is vital for the 'PO Matching and Discrepancy Audit' dashboard. Analyzing this field helps calculate the 'PO-Backed Invoice Ratio' and compare the efficiency of PO-based versus non-PO-based invoice processing. Why it matters Connects AP to Procurement and identifies matching workflows. Where to get SAP ECC table BSEG field EBELN Examples 45000123894500099221null
	User Name UserName	The ID of the user who performed the activity.
Description This attribute identifies the SAP user ID (USNAM) responsible for the event. It is recorded in the transaction header or change log. It is mapped to the 'User' generic attribute to support 'Manual Touch Rate' analysis and resource utilization views. It helps distinguish between automated system users (batch jobs) and human users performing manual adjustments. Why it matters Enables resource analysis and automation rate calculation. Where to get SAP ECC table BKPF field USNAM or CDHDR field USERNAME Examples BSMITHWF-BATCHSAP_WORKER
	Vendor Number VendorNumber	Unique identifier for the supplier or creditor.
Description This attribute uniquely identifies the external vendor associated with the invoice (LIFNR). It is linked to the vendor master data which contains details like name, address, and payment terms. Vendor analysis is critical for negotiating better terms, consolidating spend, and resolving recurring issues. This field supports the 'Vendor Inquiry and Support Volume' dashboard by helping correlate process inefficiencies with specific suppliers. Why it matters Enables supplier-centric performance analysis. Where to get SAP ECC table BSEG field LIFNR or LFA1 Examples 0000100234VEND-5592102938
	Baseline Payment Date BaselinePaymentDate	The date from which payment terms are calculated.
Description This attribute (ZFBDT) is the starting point for calculating the net due date and discount due dates. It usually reflects the invoice receipt date or document date depending on configuration. Accurate analysis of 'Late Payment Rate' relies on this field. If the baseline date is incorrect, all subsequent due date calculations and late payment flags will be flawed. Why it matters The anchor date for all aging and due date calculations. Where to get SAP ECC table BSEG field ZFBDT Examples 2023-10-012023-11-15
	Currency Code CurrencyCode	The currency key for the invoice amount.
Description This attribute (WAERS) identifies the currency in which the invoice was issued (e.g., USD, EUR). It allows for the handling of multi-currency processes. In analysis, this is used to group spend by currency or to facilitate currency conversion for consolidated reporting in the 'Cash Flow and Payment Visibility' dashboard. Why it matters Required for correct financial interpretation of amounts. Where to get SAP ECC table BKPF field WAERS Examples USDEURGBP
	Is Late Payment IsLatePayment	Flag indicating if the payment occurred after the due date.
Description This boolean attribute is calculated by comparing the Clearing Date to the Net Due Date. If the Clearing Date is later, the flag is set to true. It is the direct driver for the 'Late Payment Rate' KPI. This pre-calculated flag simplifies dashboard creation by allowing users to simply count 'True' values rather than writing complex logic in the visualization layer. Why it matters Simplifies KPI reporting on schedule adherence. Where to get Calculated: ClearingDate > NetDueDate Examples truefalse
	Is PO Based IsPOBased	Flag indicating if the invoice is linked to a Purchase Order.
Description This boolean attribute is derived by checking if the Purchase Order Number field is populated. It segments the data into PO-backed (MM-LIV) and non-PO (FI-AP) flows. This segmentation is vital for the 'Non PO Processing Efficiency' analysis, as non-PO invoices typically require more manual approval steps and have longer cycle times. Why it matters Fundamental segmentation for process efficiency analysis. Where to get Derived: True if EBELN is not null/empty Examples truefalse
	Net Due Date NetDueDate	The calculated date by which the invoice must be paid.
Description This attribute represents the final deadline for payment. It is calculated by adding the maximum payment days from the Payment Terms to the Baseline Payment Date. It serves as the benchmark for the 'Late Payment and Penalty Monitor'. Without this calculated field, it is impossible to flag invoices that have breached their service level agreements. Why it matters The target deadline for the entire process. Where to get Calculated: BaselinePaymentDate + PaymentTerms(Days) Examples 2023-11-302023-12-15
	Reference Number ReferenceNumber	The vendor's invoice number as provided on the physical document.
Description The Reference Number (XBLNR) is the external identifier provided by the vendor. It is manually entered or captured via OCR during invoice creation. This attribute is the primary key for the 'Duplicate Payment Prevention' analysis. Algorithms check for multiple instances of the same Reference Number for the same Vendor and Amount to flag potential duplicate payments. Why it matters Critical for identifying duplicates and auditing specific vendor bills. Where to get SAP ECC table BKPF field XBLNR Examples INV-2023-00199887766OCT-BILLING

Required Recommended Optional

Accounts Payable Payment Processing Activities

These are the core process steps and status changes that you should track to visualize the end to end flow of your accounts payable payments.

7 Recommended 6 Optional

	Activity	Description
	Invoice Cleared	The accounting entry that matches the invoice line item to the payment document, balancing the open item to zero. This closes the lifecycle of the invoice.
Why it matters Process completion marker. Essential for calculating the 'End to End Cycle Time' and confirming the debt is extinguished. Where to get BSEG table, field AUGDT (Clearing Date) is populated. Capture Logged when transaction X executed Event type explicit
	Invoice Created	Marks the moment the invoice data is technically entered into SAP ECC. This timestamp represents the start of the digital process within the ERP.
Why it matters Critical for calculating the internal processing time versus the total vendor wait time. High latency between Receipt and Creation indicates upstream intake bottlenecks. Where to get BKPF table, field CPUDT (Entry Date) and CPUTM (Entry Time). Capture Logged when transaction X executed Event type explicit
	Invoice Posted	Signifies that the invoice has been successfully posted to the General Ledger and sub-ledgers. This action creates the liability in the system.
Why it matters The invoice is now officially recognized as a debt. This serves as the trigger for standard payment aging and due date calculations. Where to get BKPF table creation where BSTAT is empty (posted standard). Capture Logged when transaction X executed Event type explicit
	Invoice Receipt Recorded	Captures the date stated on the vendor invoice document as the reference date. This is derived from the Document Date field in the accounting document header.
Why it matters Establishes the baseline for aging analysis and vendor payment term compliance. Differences between this date and the entry date reveal mailroom or scanning delays. Where to get BKPF table, field BLDAT (Document Date). Capture Logged when transaction X executed Event type explicit
	Payment Block Applied	Records the application of a payment block key to an invoice line item. This prevents the invoice from being picked up by the automatic payment program.
Why it matters A primary cause of late payments and missed discounts. Analyzing the block reason code helps identify if delays are due to price variances, missing goods receipts, or manual holds. Where to get Change documents (CDHDR/CDPOS) for object BELEG, field BSEG-ZLSPR (Payment Block Key). Capture Compare status field before/after Event type inferred
	Payment Block Removed	Records the removal of a payment block, making the invoice eligible for the next payment run. This acts as a proxy for 'Approval' in many SAP configurations.
Why it matters Represents the resolution of issues preventing payment. The duration between Block Applied and Block Removed is the 'resolution time' bottleneck. Where to get Change documents (CDHDR/CDPOS) where New Value for BSEG-ZLSPR is empty. Capture Compare status field before/after Event type inferred
	Payment Posted	The execution of the payment run where the bank transfer is initiated or check is printed. A payment document is generated in the system.
Why it matters The point of no return for cash outflow. This timestamp is used to calculate actual payment cycle time and check against discount deadlines. Where to get BKPF table for the payment document (Document Type 'ZP' or similar). Capture Logged when transaction X executed Event type explicit
	Discount Due Date Passed	A computed event indicating that the current date has surpassed the validity period for Cash Discount 1 or 2. This suggests a missed opportunity for savings.
Why it matters Directly supports the 'Discount Capture Performance' dashboard. Helps quantify the financial loss due to process delays. Where to get Calculated by adding BSEG-ZBD1T (Days) to BKPF-BLDAT (Document Date) and comparing to current date/payment date. Capture Derive from comparing field X to Y Event type calculated
	Due Date Passed	A computed event indicating the invoice remains open past its net due date. This flags the invoice as overdue.
Why it matters Supports 'Late Payment' analysis. Monitoring this helps prevent vendor friction and potential late fees. Where to get Calculated by adding BSEG-ZBD3T (Net Days) to baseline date and comparing to current date. Capture Derive from comparing field X to Y Event type calculated
	Invoice Data Changed	Captures manual modifications to invoice header or line item data after initial posting. Common changes include reference numbers, text fields, or tax codes.
Why it matters Indicates rework and manual intervention in the process. Frequent changes suggest data quality issues at the source or insufficient validation during initial entry. Where to get Change documents (CDHDR/CDPOS) for object BELEG, excluding block key changes. Capture Logged when transaction X executed Event type explicit
	Invoice Parked	Indicates that an invoice has been saved as a draft without creating financial postings. This status allows for data entry interruption or review before final posting.
Why it matters Identifies invoices sitting in a preliminary state which delays the payment clock. High volumes here suggest inefficient data entry or unclear approval requirements. Where to get VBKPF table or BKPF where BSTAT equals 'V'. Capture Compare status field before/after Event type inferred
	Payment Proposal Created	Indicates the invoice has been selected by the Automatic Payment Program (F110) for a potential payment. It is now on a preliminary list to be paid.
Why it matters Signals the transition from 'Payable' to 'Being Paid'. Visibility here helps treasury manage cash requirements before funds actually leave the account. Where to get REGUH table (Settlement Data from Payment Program) creation date. Capture Logged when transaction X executed Event type explicit
	Payment Term Changed	Specific rework event where the terms of payment are altered manually. This changes the due date and cash discount parameters.
Why it matters Often done to artificially extend payment windows or correct master data errors. This directly impacts cash flow forecasting and discount capture metrics. Where to get Change documents (CDHDR/CDPOS) for field BSEG-ZTERM. Capture Logged when transaction X executed Event type explicit

Recommended Optional

Extraction Guides

How to get your data from SAP ECC

Steps

Access transaction code SQVI (QuickViewer) in your SAP ECC system.
Enter a name for your view (e.g., Z_AP_MINING) and click Create. In the Data Source popup, select Table Join.
In the Join definition screen, go to Edit, Insert Table. Add table BKPF (Accounting Document Header) and table BSAK (Accounting: Secondary Index for Vendors). Note that BSAK contains cleared items; if open items are required, you would typically need a separate extraction or a union with table BSIK, but this guide focuses on the cleared history in BSAK.
Verify the link conditions between BKPF and BSAK. Ensure they are joined by Company Code (BUKRS), Accounting Document Number (BELNR), and Fiscal Year (GJAHR). The system usually proposes these automatically.
Navigate back to the main definition screen to select your Output Fields (List fields) and Selection Fields (Filter fields).
From the Available Fields list on the left, select the following critical columns for the List fields: BKPF-BELNR (Invoice Number), BKPF-BUKRS (Company Code), BKPF-GJAHR (Fiscal Year), BKPF-BLDAT (Document Date), BKPF-BUDAT (Posting Date), BKPF-CPUDT (Entry Date), BKPF-CPUTM (Entry Time), BKPF-USNAM (User Name), BKPF-XBLNR (Reference/Invoice ID), BKPF-AWKEY (Object Key), BSAK-LIFNR (Vendor), BSAK-AUGDT (Clearing Date), BSAK-AUGBL (Clearing Doc), BSAK-DMBTR (Amount), BSAK-WAERS (Currency), BSAK-ZFBDT (Baseline Date), BSAK-ZBD1T (Terms 1), BSAK-ZLSPR (Payment Block), BSAK-ZLSCH (Payment Method).
Save the QuickView and click Execute (F8).
On the selection screen, input your Company Code and a relevant Fiscal Year or Posting Date range (e.g., last 12 months).
Execute the report to generate the list. Once displayed, go to List, Export, Spreadsheet to save the raw data as an Excel or CSV file.
Since SQVI produces a flat list (one row per invoice), you must transform this data into an event log format (one row per activity) to meet ProcessMind requirements. Use the SQL logic provided in the Query section below to transform your exported spreadsheet.

Configuration

Join Configuration: Inner Join between BKPF (Header) and BSAK (Vendor Cleared Items) on BUKRS, BELNR, and GJAHR.
Date Range: Recommended to filter by Posting Date (BUDAT) for the past 6-12 months to manage list size.
Scope: This extraction focuses on BSAK, meaning only invoices that have completed the cycle (cleared/paid) will appear. Open invoices (BSIK) are excluded in this specific configuration.
Field Selection: Ensure Document Date, Posting Date, Entry Date, and Clearing Date are all selected to drive the event timestamps.
Authorization: Requires access to transaction SQVI and display authorization for financial tables.

a Sample Query config

/* 
  POST-EXTRACTION TRANSFORMATION SCRIPT
  Apply this SQL logic to the raw Excel export from SQVI to generate the Event Log.
  Input Table Name: [Raw_SQVI_Export]
*/

/* 1. Invoice Receipt Recorded */
SELECT
  "Invoice Number" AS InvoiceNumber,
  'Invoice Receipt Recorded' AS ActivityName,
  CAST("Document Date" AS DATETIME) AS EventTimestamp,
  'SAP ECC' AS SourceSystem,
  GETDATE() AS LastDataUpdate,
  "Company Code" AS CompanyCode,
  "Vendor" AS VendorNumber,
  "Amount" AS InvoiceAmount,
  "Currency" AS Currency
FROM [Raw_SQVI_Export]
WHERE "Document Date" IS NOT NULL

UNION ALL

/* 2. Invoice Created */
SELECT
  "Invoice Number",
  'Invoice Created',
  CAST(CONCAT("Entry Date", ' ', "Entry Time") AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Entry Date" IS NOT NULL

UNION ALL

/* 3. Invoice Parked */
/* Limitation: Historical park status is not preserved in BSAK. Utilizing Entry Date as proxy if distinct from Posting. */
SELECT
  "Invoice Number",
  'Invoice Parked',
  CAST(CONCAT("Entry Date", ' ', "Entry Time") AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Entry Date" < "Posting Date"

UNION ALL

/* 4. Invoice Posted */
SELECT
  "Invoice Number",
  'Invoice Posted',
  CAST("Posting Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Posting Date" IS NOT NULL

UNION ALL

/* 5. Payment Block Applied */
/* Limitation: Only shows current block status (ZLSPR) on the cleared item. */
SELECT
  "Invoice Number",
  'Payment Block Applied',
  CAST("Posting Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Payment Block" IS NOT NULL AND "Payment Block" <> ''

UNION ALL

/* 6. Invoice Data Changed */
/* Limitation: Cannot be extracted via SQVI BKPF/BSAK join. Requires CDHDR table. Row excluded or placeholder. */
SELECT
  "Invoice Number",
  'Invoice Data Changed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 7. Payment Term Changed */
/* Limitation: Requires Change Log extraction. */
SELECT
  "Invoice Number",
  'Payment Term Changed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 8. Payment Block Removed */
/* Limitation: Requires Change Log extraction. */
SELECT
  "Invoice Number",
  'Payment Block Removed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 9. Payment Proposal Created */
/* Proxy: Uses Clearing Date minus 1 day as estimation since REGUH table is not in join. */
SELECT
  "Invoice Number",
  'Payment Proposal Created',
  DATEADD(day, -1, CAST("Clearing Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL

UNION ALL

/* 10. Payment Posted */
/* Logic: Uses Clearing Date as the effective payment date. */
SELECT
  "Invoice Number",
  'Payment Posted',
  CAST("Clearing Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL AND "Clearing Doc" IS NOT NULL

UNION ALL

/* 11. Invoice Cleared */
SELECT
  "Invoice Number",
  'Invoice Cleared',
  CAST("Clearing Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL

UNION ALL

/* 12. Discount Due Date Passed */
/* Logic: Checks if Clearing Date > (Baseline Date + Term 1 Days). */
SELECT
  "Invoice Number",
  'Discount Due Date Passed',
  DATEADD(day, CAST("Terms 1" AS INT), CAST("Baseline Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" > DATEADD(day, CAST("Terms 1" AS INT), CAST("Baseline Date" AS DATETIME))

UNION ALL

/* 13. Due Date Passed */
/* Logic: Checks if Clearing Date > Net Due Date. */
SELECT
  "Invoice Number",
  'Due Date Passed',
  DATEADD(day, CAST("Terms 1" AS INT) + CAST("Terms 2" AS INT), CAST("Baseline Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" > DATEADD(day, CAST("Terms 1" AS INT) + CAST("Terms 2" AS INT), CAST("Baseline Date" AS DATETIME))

Steps

Prerequisites Setup: Ensure Python is installed with the pyrfc and pandas libraries. You will need the SAP NetWeaver RFC SDK installed on the machine where the script runs. The SAP user account must have authorizations for function module RFC_READ_TABLE and read access to tables BKPF, BSAK, BSIK, REGUH, CDHDR, CDPOS, and VBKPF.
Connection Configuration: Update the connection parameters in the script (lines 15-22) with your specific SAP ECC host, system number, client, user, and password. Set the TargetCompanyCode and DateFrom/DateTo variables to define the scope of extraction.
Script Logic Overview: The script performs a sequential extraction. First, it fetches invoice headers (BKPF) and line items (BSAK/BSIK) to build the base population. It then queries payment data (REGUH) and change logs (CDHDR/CDPOS) filtering specifically for the documents found in the first step to minimize data transfer.
Handling Table Width Limits: The standard RFC_READ_TABLE function often has a 512-byte row limit. The script includes a helper function that requests specific columns to ensure the response fits within this limit. It creates a pandas DataFrame for each table.
Data Transformation: The script merges header and line item data to create a 'Process Object'. It then iterates through this object to generate standard timestamps for Created, Posted, and Receipt activities. It calculates due dates and discount deadlines based on payment terms.
Change Log Parsing: The script processes CDHDR and CDPOS data to identify specific field changes. It maps 'ZLSPR' changes to Payment Block Applied/Removed activities and 'ZTERM' changes to Payment Term Changed activities.
Event Log Construction: All derived activities are appended to a main event list. This list is converted into a final pandas DataFrame containing the required columns: InvoiceNumber, ActivityName, EventTimestamp, SourceSystem, etc.
Export: The final step of the script exports the DataFrame to a CSV file named sap_ap_event_log.csv. This file is formatted and ready for upload into ProcessMind.
Run the Script: Execute the script via command line: python sap_ap_extraction.py. Monitor the console for progress logs indicating the number of records fetched from each table.
Validation: Open the generated CSV file. Check that dates are in ISO format and that 'Invoice Amount' is properly formatted as a float. Verify that the 'ActivityName' column contains a mix of the 13 defined activity types.

Configuration

RFC_READ_TABLE: This standard function module must be active and accessible. If your system uses a custom copy (e.g., /SAPDS/RFC_READ_TABLE) to support wider rows, update the function name in the script.
Date Range: Recommended extraction window is 3 to 6 months. Fetching CDHDR/CDPOS for periods longer than 6 months via RFC can be extremely slow and may time out.
Company Code Filter: Always filter by Company Code (BUKRS) to limit the dataset to relevant financial entities.
Chunking: For high-volume systems, modify the script to loop through dates day-by-day rather than querying a large range at once to avoid memory issues.
Change Log Objects: The script filters CDHDR using Object Class 'BELEG'. Ensure your financial document changes are logged under this standard object class.

a Sample Query python

import sys
from datetime import datetime, timedelta
import pandas as pd
from pyrfc import Connection

class=class="hl-string">"hl-comment"># === CONFIGURATION ===
SAP_CONN_PARAMS = {
    class="hl-string">'user': class="hl-string">'YOUR_USER',
    class="hl-string">'passwd': class="hl-string">'YOUR_PASSWORD',
    class="hl-string">'ashost': class="hl-string">'YOUR_SAP_HOST',
    class="hl-string">'sysnr': class="hl-string">'00',
    class="hl-string">'client': class="hl-string">'100',
    class="hl-string">'lang': class="hl-string">'EN'
}

TARGET_COMPANY_CODE = class="hl-string">'1000'
DATE_FROM = class="hl-string">'20230101'
DATE_TO = class="hl-string">'20230131'
SOURCE_SYSTEM_ID = class="hl-string">'SAP_ECC_01'

class=class="hl-string">"hl-comment"># === RFC HELPER ===
def read_table(conn, table_name, fields, options, row_limit=0):
    class="hl-string">"""Reads SAP table via RFC_READ_TABLE and returns a DataFrame."""
    print(fclass="hl-string">"Reading {table_name}...")
    
    class=class="hl-string">"hl-comment"># Format fields for RFC
    rfc_fields = [{class="hl-string">'FIELDNAME': f} for f in fields]
    
    class=class="hl-string">"hl-comment"># Call RFC
    try:
        result = conn.call(class="hl-string">'RFC_READ_TABLE',
                           QUERY_TABLE=table_name,
                           DELIMITER=class="hl-string">';',
                           FIELDS=rfc_fields,
                           OPTIONS=[{class="hl-string">'TEXT': o} for o in options],
                           ROWCOUNT=row_limit)
    except Exception as e:
        print(fclass="hl-string">"Error reading {table_name}: {e}")
        return pd.DataFrame()

    class=class="hl-string">"hl-comment"># Parse output
    data = []
    headers = [f[class="hl-string">'FIELDNAME'] for f in result[class="hl-string">'FIELDS']]
    
    for line in result[class="hl-string">'DATA']:
        class=class="hl-string">"hl-comment"># Simple split by delimiter; robust parsing handles fixed width if delimiter fails, 
        class=class="hl-string">"hl-comment"># but semicolon is standard for this approach.
        values = line[class="hl-string">'WA'].split(class="hl-string">';')
        class=class="hl-string">"hl-comment"># Handle cases where split might be shorter if trailing fields are empty
        if len(values) < len(headers):
            values += [class="hl-string">''] * (len(headers) - len(values))
        data.append(dict(zip(headers, values)))
        
    return pd.DataFrame(data)

def main():
    class=class="hl-string">"hl-comment"># 1. Connect to SAP
    try:
        conn = Connection(**SAP_CONN_PARAMS)
    except Exception as e:
        print(fclass="hl-string">"Connection failed: {e}")
        return

    class=class="hl-string">"hl-comment"># 2. Extract BKPF (Header)
    class=class="hl-string">"hl-comment"># Filters: Company Code and Entry Date (CPUDT)
    bkpf_fields = [class="hl-string">'BUKRS', class="hl-string">'BELNR', class="hl-string">'GJAHR', class="hl-string">'BLART', class="hl-string">'BLDAT', class="hl-string">'BUDAT', class="hl-string">'CPUDT', class="hl-string">'CPUTM', class="hl-string">'USNAM']
    bkpf_opts = [
        fclass="hl-string">"BUKRS = '{TARGET_COMPANY_CODE}' AND CPUDT >= '{DATE_FROM}' AND CPUDT <= '{DATE_TO}'"
    ]
    df_bkpf = read_table(conn, class="hl-string">'BKPF', bkpf_fields, bkpf_opts)
    
    if df_bkpf.empty:
        print(class="hl-string">"No documents found.")
        return

    class=class="hl-string">"hl-comment"># 3. Extract Vendor Line Items (BSAK - Cleared, BSIK - Open)
    class=class="hl-string">"hl-comment"># To avoid huge queries, we filter BSIK/BSAK by the same date range or join later.
    class=class="hl-string">"hl-comment"># For robustness in RFC, we filter by BUKRS and Date range on CPU date or BUDAT similar to BKPF
    item_fields = [class="hl-string">'BUKRS', class="hl-string">'BELNR', class="hl-string">'GJAHR', class="hl-string">'BUZEI', class="hl-string">'LIFNR', class="hl-string">'DMBTR', class="hl-string">'WAERS', class="hl-string">'ZFBDT', class="hl-string">'ZTERM', class="hl-string">'ZBD1T', class="hl-string">'ZBD2T', class="hl-string">'ZLSPR', class="hl-string">'AUGDT', class="hl-string">'AUGBL']
    
    class=class="hl-string">"hl-comment"># Note: BSIK/BSAK are huge. In production, chunk by BELNR list derived from BKPF or Date.
    class=class="hl-string">"hl-comment"># Here we use the date range on BUDAT for simplicity of the example.
    item_opts = [
        fclass="hl-string">"BUKRS = '{TARGET_COMPANY_CODE}' AND BUDAT >= '{DATE_FROM}' AND BUDAT <= '{DATE_TO}'"
    ]
    
    df_bsik = read_table(conn, class="hl-string">'BSIK', item_fields, item_opts)
    df_bsak = read_table(conn, class="hl-string">'BSAK', item_fields, item_opts)
    
    class=class="hl-string">"hl-comment"># Combine Open and Cleared items
    df_items = pd.concat([df_bsik, df_bsak], ignore_index=True)
    
    class=class="hl-string">"hl-comment"># Filter items to only those present in our BKPF fetch (Inner Join logic)
    df_items = df_items[df_items[class="hl-string">'BELNR'].isin(df_bkpf[class="hl-string">'BELNR'])]

    class=class="hl-string">"hl-comment"># 4. Extract Payment Data (REGUH)
    class=class="hl-string">"hl-comment"># Filter by Date range roughly matching the process
    reguh_fields = [class="hl-string">'LAUFD', class="hl-string">'LAUFI', class="hl-string">'XVORL', class="hl-string">'VBLNR', class="hl-string">'LIFNR']
    reguh_opts = [
        fclass="hl-string">"LAUFD >= '{DATE_FROM}'"
    ]
    df_reguh = read_table(conn, class="hl-string">'REGUH', reguh_fields, reguh_opts)

    class=class="hl-string">"hl-comment"># 5. Extract Change History (CDHDR/CDPOS)
    class=class="hl-string">"hl-comment"># This is expensive. Filter by OBJECTCLAS class="hl-string">'BELEG' and Date.
    cdhdr_fields = [class="hl-string">'OBJECTCLAS', class="hl-string">'OBJECTID', class="hl-string">'CHANGENR', class="hl-string">'UDATE', class="hl-string">'UTIME', class="hl-string">'USERNAME']
    cdhdr_opts = [
        fclass="hl-string">"OBJECTCLAS = 'BELEG' AND UDATE >= '{DATE_FROM}'"
    ]
    df_cdhdr = read_table(conn, class="hl-string">'CDHDR', cdhdr_fields, cdhdr_opts)
    
    class=class="hl-string">"hl-comment"># Filter CDHDR to only relevant Invoice Numbers (OBJECTID usually contains BELNR + GJAHR)
    class=class="hl-string">"hl-comment"># Construct OBJECTID list from BKPF
    valid_object_ids = set(df_bkpf[class="hl-string">'BELNR'] + df_bkpf[class="hl-string">'GJAHR'])
    df_cdhdr = df_cdhdr[df_cdhdr[class="hl-string">'OBJECTID'].isin(valid_object_ids)]
    
    if not df_cdhdr.empty:
        class=class="hl-string">"hl-comment"># Get CDPOS for these changes
        class=class="hl-string">"hl-comment"># Cannot pass thousands of CHANGENR. Split if needed. 
        class=class="hl-string">"hl-comment"># Here assuming volume allows single fetch or loop.
        change_nums = df_cdhdr[class="hl-string">'CHANGENR'].unique().tolist()
        class=class="hl-string">"hl-comment"># Chunking needed for production
        cdpos_fields = [class="hl-string">'OBJECTCLAS', class="hl-string">'OBJECTID', class="hl-string">'CHANGENR', class="hl-string">'TABNAME', class="hl-string">'FNAME', class="hl-string">'VALUE_NEW', class="hl-string">'VALUE_OLD']
        df_cdpos = pd.DataFrame()
        
        class=class="hl-string">"hl-comment"># Simple chunk loop
        chunk_size = 100
        for i in range(0, len(change_nums), chunk_size):
            chunk = change_nums[i:i + chunk_size]
            chunk_str = class="hl-string">"'".join(chunk)
            opts = [fclass="hl-string">"OBJECTCLAS = 'BELEG' AND CHANGENR IN ('{chunk_str}')"]
            df_chunk = read_table(conn, class="hl-string">'CDPOS', cdpos_fields, opts)
            df_cdpos = pd.concat([df_cdpos, df_chunk])
            
        class=class="hl-string">"hl-comment"># Merge CDHDR and CDPOS
        df_changes = pd.merge(df_cdpos, df_cdhdr, on=[class="hl-string">'OBJECTCLAS', class="hl-string">'OBJECTID', class="hl-string">'CHANGENR'])
    else:
        df_changes = pd.DataFrame(columns=[class="hl-string">'OBJECTID', class="hl-string">'FNAME', class="hl-string">'VALUE_NEW', class="hl-string">'VALUE_OLD', class="hl-string">'UDATE', class="hl-string">'UTIME', class="hl-string">'USERNAME'])

    class=class="hl-string">"hl-comment"># === PROCESS EVENTS ===
    events = []

    class=class="hl-string">"hl-comment"># Join Headers and Items
    class=class="hl-string">"hl-comment"># Ensure key columns are strings for merging
    df_full = pd.merge(df_bkpf, df_items, on=[class="hl-string">'BUKRS', class="hl-string">'BELNR', class="hl-string">'GJAHR'])

    for _, row in df_full.iterrows():
        invoice_num = row[class="hl-string">'BELNR']
        vendor = row[class="hl-string">'LIFNR']
        amount = row[class="hl-string">'DMBTR']
        
        class=class="hl-string">"hl-comment"># Common attributes
        base_attrs = {
            class="hl-string">'InvoiceNumber': invoice_num,
            class="hl-string">'SourceSystem': SOURCE_SYSTEM_ID,
            class="hl-string">'CompanyCode': row[class="hl-string">'BUKRS'],
            class="hl-string">'VendorNumber': vendor,
            class="hl-string">'InvoiceAmount': amount,
            class="hl-string">'DocumentType': row[class="hl-string">'BLART'],
            class="hl-string">'LastDataUpdate': datetime.now().isoformat()
        }

        class=class="hl-string">"hl-comment"># 1. Invoice Created
        events.append({
            **base_attrs,
            class="hl-string">'ActivityName': class="hl-string">'Invoice Created',
            class="hl-string">'EventTimestamp': fclass="hl-string">"{row['CPUDT']}T{row['CPUTM']}",
            class="hl-string">'UserName': row[class="hl-string">'USNAM']
        })

        class=class="hl-string">"hl-comment"># 2. Invoice Receipt Recorded
        if row[class="hl-string">'BLDAT']:
            events.append({
                **base_attrs,
                class="hl-string">'ActivityName': class="hl-string">'Invoice Receipt Recorded',
                class="hl-string">'EventTimestamp': fclass="hl-string">"{row['BLDAT']}T00:00:00",
                class="hl-string">'UserName': row[class="hl-string">'USNAM']
            })

        class=class="hl-string">"hl-comment"># 3. Invoice Posted
        if row[class="hl-string">'BUDAT']:
            events.append({
                **base_attrs,
                class="hl-string">'ActivityName': class="hl-string">'Invoice Posted',
                class="hl-string">'EventTimestamp': fclass="hl-string">"{row['BUDAT']}T00:00:00",
                class="hl-string">'UserName': row[class="hl-string">'USNAM']
            })

        class=class="hl-string">"hl-comment"># 4. Invoice Cleared
        if row[class="hl-string">'AUGDT'] and row[class="hl-string">'AUGDT'] != class="hl-string">'00000000':
            events.append({
                **base_attrs,
                class="hl-string">'ActivityName': class="hl-string">'Invoice Cleared',
                class="hl-string">'EventTimestamp': fclass="hl-string">"{row['AUGDT']}T00:00:00",
                class="hl-string">'ClearingDate': row[class="hl-string">'AUGDT']
            })
            
            class=class="hl-string">"hl-comment"># 5. Payment Posted (Proxy via Clearing)
            class=class="hl-string">"hl-comment"># If cleared by payment document, assume Payment Posted same day
            events.append({
                **base_attrs,
                class="hl-string">'ActivityName': class="hl-string">'Payment Posted',
                class="hl-string">'EventTimestamp': fclass="hl-string">"{row['AUGDT']}T23:59:59"
            })

        class=class="hl-string">"hl-comment"># 6. Payment Proposal Created
        class=class="hl-string">"hl-comment"># Check REGUH
        class=class="hl-string">"hl-comment"># Logic: REGUH contains payment proposals. We link via VBLNR (Payment Doc) or LIFNR matches
        class=class="hl-string">"hl-comment"># Simplified: if we find a proposal for this vendor in the range
        class=class="hl-string">"hl-comment"># In practice, need tighter link via BSAK-AUGBL = REGUH-VBLNR
        if row[class="hl-string">'AUGBL']:
            prop = df_reguh[df_reguh[class="hl-string">'VBLNR'] == row[class="hl-string">'AUGBL']]
            if not prop.empty:
                 for _, p_row in prop.iterrows():
                    events.append({
                        **base_attrs,
                        class="hl-string">'ActivityName': class="hl-string">'Payment Proposal Created',
                        class="hl-string">'EventTimestamp': fclass="hl-string">"{p_row['LAUFD']}T00:00:00"
                    })

        class=class="hl-string">"hl-comment"># 7. Parked (Check if originally parked - simplified logic)
        class=class="hl-string">"hl-comment"># Requires VBKPF check or document status history. Omitted for brevity in this block, 
        class=class="hl-string">"hl-comment"># usually involves checking if document ID exists in VBKPF list.

        class=class="hl-string">"hl-comment"># 8-11. Change Log Activities
        class=class="hl-string">"hl-comment"># Filter changes for this document
        obj_id = row[class="hl-string">'BELNR'] + row[class="hl-string">'GJAHR']
        doc_changes = df_changes[df_changes[class="hl-string">'OBJECTID'] == obj_id]
        
        for _, chg in doc_changes.iterrows():
            ts = fclass="hl-string">"{chg['UDATE']}T{chg['UTIME']}"
            fname = chg[class="hl-string">'FNAME']
            
            if fname == class="hl-string">'ZLSPR':
                if chg[class="hl-string">'VALUE_OLD'] == class="hl-string">'' and chg[class="hl-string">'VALUE_NEW'] != class="hl-string">'':
                    events.append({**base_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Block Applied', class="hl-string">'EventTimestamp': ts, class="hl-string">'PaymentBlockCode': chg[class="hl-string">'VALUE_NEW']})
                elif chg[class="hl-string">'VALUE_OLD'] != class="hl-string">'' and chg[class="hl-string">'VALUE_NEW'] == class="hl-string">'':
                    events.append({**base_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Block Removed', class="hl-string">'EventTimestamp': ts})
            elif fname == class="hl-string">'ZTERM':
                events.append({**base_attrs, class="hl-string">'ActivityName': class="hl-string">'Payment Term Changed', class="hl-string">'EventTimestamp': ts})
            else:
                events.append({**base_attrs, class="hl-string">'ActivityName': class="hl-string">'Invoice Data Changed', class="hl-string">'EventTimestamp': ts})

        class=class="hl-string">"hl-comment"># 12. Due Date Passed (Calculated)
        class=class="hl-string">"hl-comment"># Calculate Net Due Date = Baseline Date (ZFBDT) + Max Days (ZBD1T or ZBD2T or ZBD3T)
        try:
            zfbdt = datetime.strptime(row[class="hl-string">'ZFBDT'], class="hl-string">'%Y%m%d')
            days = float(row[class="hl-string">'ZBD1T']) if row[class="hl-string">'ZBD1T'] else 0
            due_date = zfbdt + timedelta(days=days)
            
            class=class="hl-string">"hl-comment"># If today > due_date and not cleared (or cleared after due date)
            clearing_date = datetime.strptime(row[class="hl-string">'AUGDT'], class="hl-string">'%Y%m%d') if (row[class="hl-string">'AUGDT'] and row[class="hl-string">'AUGDT'] != class="hl-string">'00000000') else None
            check_date = clearing_date if clearing_date else datetime.now()
            
            if check_date > due_date:
                 events.append({
                    **base_attrs,
                    class="hl-string">'ActivityName': class="hl-string">'Due Date Passed',
                    class="hl-string">'EventTimestamp': due_date.isoformat()
                })
        except ValueError:
            pass class=class="hl-string">"hl-comment"># Handle date parsing errors

        class=class="hl-string">"hl-comment"># 13. Discount Due Date Passed
        class=class="hl-string">"hl-comment"># Logic similar to Due Date using discount terms

    class=class="hl-string">"hl-comment"># Finalize
    df_events = pd.DataFrame(events)
    print(fclass="hl-string">"Generated {len(df_events)} events.")
    df_events.to_csv(class="hl-string">'sap_ap_event_log.csv', index=False)

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

Steps

Access transaction code SQVI (QuickViewer) in your SAP ECC system.
Enter a name for your view (e.g., Z_AP_MINING) and click Create. In the Data Source popup, select Table Join.
In the Join definition screen, go to Edit, Insert Table. Add table BKPF (Accounting Document Header) and table BSAK (Accounting: Secondary Index for Vendors). Note that BSAK contains cleared items; if open items are required, you would typically need a separate extraction or a union with table BSIK, but this guide focuses on the cleared history in BSAK.
Verify the link conditions between BKPF and BSAK. Ensure they are joined by Company Code (BUKRS), Accounting Document Number (BELNR), and Fiscal Year (GJAHR). The system usually proposes these automatically.
Navigate back to the main definition screen to select your Output Fields (List fields) and Selection Fields (Filter fields).
From the Available Fields list on the left, select the following critical columns for the List fields: BKPF-BELNR (Invoice Number), BKPF-BUKRS (Company Code), BKPF-GJAHR (Fiscal Year), BKPF-BLDAT (Document Date), BKPF-BUDAT (Posting Date), BKPF-CPUDT (Entry Date), BKPF-CPUTM (Entry Time), BKPF-USNAM (User Name), BKPF-XBLNR (Reference/Invoice ID), BKPF-AWKEY (Object Key), BSAK-LIFNR (Vendor), BSAK-AUGDT (Clearing Date), BSAK-AUGBL (Clearing Doc), BSAK-DMBTR (Amount), BSAK-WAERS (Currency), BSAK-ZFBDT (Baseline Date), BSAK-ZBD1T (Terms 1), BSAK-ZLSPR (Payment Block), BSAK-ZLSCH (Payment Method).
Save the QuickView and click Execute (F8).
On the selection screen, input your Company Code and a relevant Fiscal Year or Posting Date range (e.g., last 12 months).
Execute the report to generate the list. Once displayed, go to List, Export, Spreadsheet to save the raw data as an Excel or CSV file.
Since SQVI produces a flat list (one row per invoice), you must transform this data into an event log format (one row per activity) to meet ProcessMind requirements. Use the SQL logic provided in the Query section below to transform your exported spreadsheet.

Configuration

Join Configuration: Inner Join between BKPF (Header) and BSAK (Vendor Cleared Items) on BUKRS, BELNR, and GJAHR.
Date Range: Recommended to filter by Posting Date (BUDAT) for the past 6-12 months to manage list size.
Scope: This extraction focuses on BSAK, meaning only invoices that have completed the cycle (cleared/paid) will appear. Open invoices (BSIK) are excluded in this specific configuration.
Field Selection: Ensure Document Date, Posting Date, Entry Date, and Clearing Date are all selected to drive the event timestamps.
Authorization: Requires access to transaction SQVI and display authorization for financial tables.

a Sample Query config

/* 
  POST-EXTRACTION TRANSFORMATION SCRIPT
  Apply this SQL logic to the raw Excel export from SQVI to generate the Event Log.
  Input Table Name: [Raw_SQVI_Export]
*/

/* 1. Invoice Receipt Recorded */
SELECT
  "Invoice Number" AS InvoiceNumber,
  'Invoice Receipt Recorded' AS ActivityName,
  CAST("Document Date" AS DATETIME) AS EventTimestamp,
  'SAP ECC' AS SourceSystem,
  GETDATE() AS LastDataUpdate,
  "Company Code" AS CompanyCode,
  "Vendor" AS VendorNumber,
  "Amount" AS InvoiceAmount,
  "Currency" AS Currency
FROM [Raw_SQVI_Export]
WHERE "Document Date" IS NOT NULL

UNION ALL

/* 2. Invoice Created */
SELECT
  "Invoice Number",
  'Invoice Created',
  CAST(CONCAT("Entry Date", ' ', "Entry Time") AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Entry Date" IS NOT NULL

UNION ALL

/* 3. Invoice Parked */
/* Limitation: Historical park status is not preserved in BSAK. Utilizing Entry Date as proxy if distinct from Posting. */
SELECT
  "Invoice Number",
  'Invoice Parked',
  CAST(CONCAT("Entry Date", ' ', "Entry Time") AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Entry Date" < "Posting Date"

UNION ALL

/* 4. Invoice Posted */
SELECT
  "Invoice Number",
  'Invoice Posted',
  CAST("Posting Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Posting Date" IS NOT NULL

UNION ALL

/* 5. Payment Block Applied */
/* Limitation: Only shows current block status (ZLSPR) on the cleared item. */
SELECT
  "Invoice Number",
  'Payment Block Applied',
  CAST("Posting Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Payment Block" IS NOT NULL AND "Payment Block" <> ''

UNION ALL

/* 6. Invoice Data Changed */
/* Limitation: Cannot be extracted via SQVI BKPF/BSAK join. Requires CDHDR table. Row excluded or placeholder. */
SELECT
  "Invoice Number",
  'Invoice Data Changed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 7. Payment Term Changed */
/* Limitation: Requires Change Log extraction. */
SELECT
  "Invoice Number",
  'Payment Term Changed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 8. Payment Block Removed */
/* Limitation: Requires Change Log extraction. */
SELECT
  "Invoice Number",
  'Payment Block Removed',
  NULL,
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE 1=0

UNION ALL

/* 9. Payment Proposal Created */
/* Proxy: Uses Clearing Date minus 1 day as estimation since REGUH table is not in join. */
SELECT
  "Invoice Number",
  'Payment Proposal Created',
  DATEADD(day, -1, CAST("Clearing Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL

UNION ALL

/* 10. Payment Posted */
/* Logic: Uses Clearing Date as the effective payment date. */
SELECT
  "Invoice Number",
  'Payment Posted',
  CAST("Clearing Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL AND "Clearing Doc" IS NOT NULL

UNION ALL

/* 11. Invoice Cleared */
SELECT
  "Invoice Number",
  'Invoice Cleared',
  CAST("Clearing Date" AS DATETIME),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" IS NOT NULL

UNION ALL

/* 12. Discount Due Date Passed */
/* Logic: Checks if Clearing Date > (Baseline Date + Term 1 Days). */
SELECT
  "Invoice Number",
  'Discount Due Date Passed',
  DATEADD(day, CAST("Terms 1" AS INT), CAST("Baseline Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" > DATEADD(day, CAST("Terms 1" AS INT), CAST("Baseline Date" AS DATETIME))

UNION ALL

/* 13. Due Date Passed */
/* Logic: Checks if Clearing Date > Net Due Date. */
SELECT
  "Invoice Number",
  'Due Date Passed',
  DATEADD(day, CAST("Terms 1" AS INT) + CAST("Terms 2" AS INT), CAST("Baseline Date" AS DATETIME)),
  'SAP ECC',
  GETDATE(),
  "Company Code",
  "Vendor",
  "Amount",
  "Currency"
FROM [Raw_SQVI_Export]
WHERE "Clearing Date" > DATEADD(day, CAST("Terms 1" AS INT) + CAST("Terms 2" AS INT), CAST("Baseline Date" AS DATETIME))

Your Accounts Payable Payment Processing Data Template

Your Accounts Payable Payment Processing Data Template

Accounts Payable Payment Processing Attributes

Accounts Payable Payment Processing Activities

Extraction Guides

SAP QuickViewer SQVI Table Join Extraction

Steps

Configuration

a Sample Query config

Python Script using RFC_READ_TABLE Protocol

Steps

Configuration

a Sample Query python

Theobald Xtract Universal Delta Extraction

Steps

Configuration

a Sample Query config

Ready to Get Started?

Optimize Your Accounts Payable Payment Processing Now

Your Accounts Payable Payment Processing Data Template

Your Accounts Payable Payment Processing Data Template

Accounts Payable Payment Processing Attributes

Accounts Payable Payment Processing Activities

Extraction Guides

SAP QuickViewer SQVI Table Join Extraction

Steps

Configuration

a Sample Query config

Python Script using RFC_READ_TABLE Protocol

Steps

Configuration

a Sample Query python

Theobald Xtract Universal Delta Extraction

Steps

Configuration

a Sample Query config

We value your privacy

Ready to Get Started?

Optimize Your Accounts Payable Payment Processing Now