Search Results ibe_invoice_header_v




Overview
Explore in AI Chat

Overview

IBE_INVOICE_HEADER_V is a reporting view owned by the APPS schema within the IBE (iStore) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a denormalized, read-only projection that consolidates invoice header attributes from Oracle Receivables and Oracle Trading Community Architecture sources into a single queryable structure for iStore-facing reporting and integration. The view is registered as VALID in ETRM metadata and presents one row per customer transaction header, combining Receivables transaction data, payment schedule balances, customer account identifiers, and a translated transaction class description.

The view is particularly relevant where a user searches on interface_header_attribute1, because that column is exposed here directly as INTERFACE_HEADER_ATTRIBUTE1. It originates from RA_CUSTOMER_TRX_ALL.INTERFACE_HEADER_ATTRIBUTE1, which is populated during AutoInvoice import from the RA_INTERFACE_LINES_ALL staging table. Exposing this column in IBE_INVOICE_HEADER_V allows iStore pages and integrations to read back custom, externally sourced header-level values without querying the base Receivables table directly.

Underlying Base Objects

The view is defined over four documented base objects, joined as follows:

  • RA_CUSTOMER_TRX_ALL (SYNONYM) — the primary transaction table, aliased CT. It supplies transaction number, date, currency, purchase order, waybill, ship-via, customer transaction ID, created-by, ORG_ID, and INTERFACE_HEADER_ATTRIBUTE1.
  • AR_PAYMENT_SCHEDULES_ALL (SYNONYM) — aliased PS, joined on CUSTOMER_TRX_ID. It supplies due date, original and remaining amounts due, line, tax and freight originals, adjusted, applied and credited amounts, and discount taken.
  • HZ_CUST_ACCOUNTS (SYNONYM) — aliased ACCT, joined on CT.BILL_TO_CUSTOMER_ID. It supplies PARTY_ID and CUST_ACCOUNT_ID.
  • AR_LOOKUPS (VIEW) — aliased AL_CLASS, joined on PS.CLASS = AL_CLASS.LOOKUP_CODE where LOOKUP_TYPE = 'INV/CM', translating the payment schedule class into a readable transaction TYPE.

Key Columns

Common Use Cases and Queries

Typical scenarios include iStore order and invoice inquiry pages, receivables reconciliation reports, and integrations that must match an external document to its EBS transaction.

To locate a transaction by an interface identifier:

  • SELECT trx_number, trx_date, type, po_number, amount_due_remaining, customer_trx_id, org_id FROM ibe_invoice_header_v WHERE interface_header_attribute1 = :p_attr1;

To list open balances for a customer account:

  • SELECT trx_number, trx_date, due_date, invoice_currency_code, amount_due_original, amount_due_remaining FROM ibe_invoice_header_v WHERE cust_account_id = :p_cust_account_id AND amount_due_remaining > 0 ORDER BY due_date;

Because the view is not org-stripped internally in the documented text, queries should filter by ORG_ID where operating unit isolation is required, and should be aware that the join to AR_PAYMENT_SCHEDULES_ALL may produce multiple rows for transactions with multiple payment schedules.