Search Results ai_vat_code

Overview

The AP_INVOICE_EXTRACT_HEADER_V view is a Payables module extraction object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents invoice header data from Oracle Payables in a flattened, integration-oriented format intended to feed downstream systems such as E-Business Tax, subledger accounting, or external data warehouses. Rather than exposing raw transactional columns, the view applies naming conventions and DECODE logic to normalize values for consumption by event-driven extraction processes. The presence of EVENT_ID, tied to XLA_EVENTS_GT, indicates that the view is designed to be queried in the context of subledger accounting events, making it a bridge between Payables transaction tables and the accounting/extraction layer. It is not a transactional entry view; it is a read-only reporting and integration object.

Underlying Base Objects

The view is defined over several documented base objects, all accessed through APPS synonyms. AP_INVOICES_ALL supplies the invoice header attributes such as invoice number, dates, amounts, currency, and descriptive flexfield columns. AP_BATCHES_ALL provides AP_BATCH_NAME, linking each invoice to its batch. AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL supply supplier and supplier site identity, used in the DECODE expressions to derive INV_PARTY_TYPE, THIRD_PARTY_TYPE, AI_VENDOR_ID, and AI_VENDOR_SITE_ID. FND_DOCUMENT_SEQUENCES supplies DOC_SEQUENCE_NAME, keyed to the invoice document sequence. HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES provide trading community location and party context. XLA_EVENTS_GT supplies EVENT_ID, anchoring the extraction to subledger accounting events. The join across these objects produces one row per qualifying invoice header event.

Key Columns

Key columns fall into several functional groups:

• Identity and sequence: EVENT_ID, AI_INVOICE_ID, INV_TRANSACTION_NUMBER (invoice number), INV_DOC_SEQUENCE_IDENTIFIER, INV_DOC_SEQUENCE_VALUE, INV_DOC_SEQUENCE_CATEGORY, and DOC_SEQUENCE_NAME.
• Party: INV_PARTY_TYPE, THIRD_PARTY_TYPE, AI_VENDOR_ID, and AI_VENDOR_SITE_ID.
• Financial: AI_INVOICE_AMOUNT, AI_INVOICE_BASE_AMOUNT, INV_AMOUNT_PAID, INV_DISCOUNT_AMOUNT_TAKEN, INV_DISTRIBUTION_TOTAL, and AI_INVOICE_CURRENCY_CODE.
• Dates and status: AI_INVOICE_DATE and AI_CANCELLED_DATE.
• Classification: AI_INVOICE_TYPE_LOOKUP_CODE, AI_VAT_CODE, AI_VOUCHER_NUM, INVESTIGATE and AWT_GROUP_ID.
• Descriptive flexibility: AI_ATTRIBUTE_CATEGORY, AI_ATTRIBUTE1 through AI_ATTRIBUTE15, plus INV_GLOBAL_ATTRIBUTE_CATEGORY and INV_GLOBAL_ATTRIBUTE_n columns.

Notably, the ETRM metadata does not surface a column named INV_EXCHANGE_DATE, despite the user's search term. Invoice exchange date information is not part of the documented header extract; if needed, it must be sourced from AP_INVOICES_ALL directly, such as via EXCHANGE_DATE columns on related distributions or from the invoice currency conversion setup.

Common Use Cases and Queries

This view is typically used to extract invoice headers for subledger accounting, tax reporting, or reconciliation against general ledger and payment data. A representative query joins the view back to XLA events to isolate a specific event:

• Retrieve all invoice headers for a given org and date range: SELECT AI_INVOICE_ID, INV_TRANSACTION_NUMBER, AI_INVOICE_DATE, AI_INVOICE_AMOUNT FROM APPS.AP_INVOICE_EXTRACT_HEADER_V WHERE AI_ORG_ID = :p_org AND AI_INVOICE_DATE BETWEEN :p_start AND :p_end;
• Tie an invoice to its subledger event: SELECT EVENT_ID, INV_TRANSACTION_NUMBER, INV_DOC_SEQUENCE_VALUE FROM APPS.AP_INVOICE_EXTRACT_HEADER_V WHERE EVENT_ID = :p_event;
• Report supplier exposure: SELECT INV_PARTY_TYPE, AI_VENDOR_ID, SUM(AI_INVOICE_AMOUNT) FROM APPS.AP_INVOICE_EXTRACT_HEADER_V GROUP BY INV_PARTY_TYPE, AI_VENDOR_ID;

Because the view pre-applies DECODE logic and naming aliases, it is best treated as a stable extraction contract rather than a substitute for querying AP_INVOICES_ALL directly when additional header fields are required.