Search Results inv_party_type

Overview

APPS.AP_INVOICE_EXTRACT_HEADER_V is a reporting and integration view in the Oracle E-Business Suite Payables module. It presents invoice header-level data in a flattened, denormalized form suitable for extraction, third-party system feeds, and custom reporting. The view is registered in FND Design Data under the application product SQLAP and carries a VALID status, indicating that it compiles successfully against the base tables in both Oracle EBS 12.1.1 and 12.2.2. The columns in this view are largely prefixed with AI_, denoting the underlying AP_INVOICES_ALL attributes, alongside INV_ columns that expose derived or transactional fields such as party type, document sequencing, payment totals, and withholding group information.

The view is oriented toward outbound integration scenarios, where invoice header attributes are consolidated into a single row per invoice or invoice event. It carries an EVENT_ID column, linking it conceptually to the Subledger Accounting (XLA) events model, and includes document sequencing fields that are relevant for statutory sequential numbering requirements in countries with fiscal document regulations.

Underlying Base Objects

The view is defined over the following documented base objects:

• AP_INVOICES_ALL — the primary source of invoice header attributes, supplying AI_INVOICE_ID, AI_ORG_ID, AI_VENDOR_ID, AI_VENDOR_SITE_ID, AI_INVOICE_AMOUNT, AI_INVOICE_DATE, and the AI_ATTRIBUTE1–15 and AI_GLOBAL_ATTRIBUTE columns.
• AP_BATCHES_ALL — provides the invoice batch context via AB_BATCH_NAME.
• AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL — supply supplier and supplier site identifiers used to resolve party and third-party type information.
• HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS — the Trading Community Architecture (TCA) tables used to derive party type and location attributes.
• FND_DOCUMENT_SEQUENCES — the source for INV_DOC_SEQUENCE_IDENTIFIER, INV_DOC_SEQUENCE_VALUE, INV_DOC_SEQUENCE_CATEGORY, and DOC_SEQUENCE_NAME.
• XLA_EVENTS_GT — a global temporary table used within the Subledger Accounting event framework, contributing EVENT_ID.

Key Columns

The columns of principal interest include:

• EVENT_ID — identifies the associated XLA accounting event.
• INV_PARTY_TYPE and THIRD_PARTY_TYPE — classify the counterparty on the invoice, supporting reporting by party classification.
• AI_INVOICE_ID, AI_ORG_ID, AI_VENDOR_ID, AI_VENDOR_SITE_ID — core invoice and supplier keys.
• AI_INVOICE_AMOUNT, AI_INVOICE_BASE_AMOUNT, AI_INVOICE_CURRENCY_CODE — invoice amount and currency context.
• AI_INVOICE_DATE, AI_CANCELLED_DATE, AI_VOUCHER_NUM, AI_INVOICE_TYPE_LOOKUP_CODE — invoice dating, cancellation, voucher numbering, and invoice type.
• INV_AMOUNT_PAID, INV_DISCOUNT_AMOUNT_TAKEN, INV_DISTRIBUTION_TOTAL — payment and distribution totals used for reconciliation.
• INV_DOC_SEQUENCE_IDENTIFIER, INV_DOC_SEQUENCE_VALUE, INV_DOC_SEQUENCE_CATEGORY, DOC_SEQUENCE_NAME — fiscal document sequencing data.
• AI_ATTRIBUTE1–15 and INV_GLOBAL_ATTRIBUTE_1–10 — descriptive flexfield and global descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include extracting invoice header data for a data warehouse, feeding AP invoice information to a third-party tax or archival system, and reporting on party type distributions. A representative query searching on party type is:

• SELECT ai_invoice_id, ai_vendor_id, inv_party_type, third_party_type, ai_invoice_amount, ai_invoice_currency_code FROM apps.ap_invoice_extract_header_v WHERE inv_party_type = :p_party_type;

Additional scenarios include reconciling distribution totals against invoice amounts using INV_DISTRIBUTION_TOTAL and INV_AMOUNT_PAID, and extracting document sequence values for statutory audit. Because the view is a reporting object, callers should apply org and date filters via the AI_ORG_ID and AI_INVOICE_DATE columns to constrain result sets.