Results for “al_class”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.IBE_INVOICE_HEADER_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IBE.IBE_INVOICE_HEADER_V. It exposes invoice header information drawn primarily from Oracle Receivables and Oracle iStore-related sources, presenting a denormalized, read-oriented projection of customer transaction data at the header level. The view is marked VALID with an internal view type, and Oracle explicitly designates it for internal use only: the documentation warns that Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs.

The view is intended for consumption by Oracle iStore and related application modules that need a concise invoice header record for display, integration, or reporting purposes. Because it is not referenced by any other database object, it functions as a terminal, consumer-facing object rather than a shared building block within the dependency chain. The column of particular interest to users searching for freight_original is FREIGHT_ORIGINAL, a NUMBER column that carries the original freight amount associated with the invoice header before any adjustments, applications, or credits are applied.

Underlying Base Objects

The view is defined over four documented base objects:

• RA_CUSTOMER_TRX_ALL (SYNONYM) — the core Oracle Receivables table holding customer transaction headers, including transaction number, date, currency, type, and original amount components such as freight.
• AR_PAYMENT_SCHEDULES_ALL (SYNONYM) — the Receivables payment schedule table, supplying amounts due, remaining balances, applied, credited, and adjusted figures.
• HZ_CUST_ACCOUNTS (SYNONYM) — the Trading Community Architecture customer account table, providing account identifiers and party linkage.
• AR_LOOKUPS (VIEW) — the Receivables lookup view, used to resolve transaction type and related code meanings into displayable values.

Conceptually, the view joins transaction headers to their payment schedules and customer account records, resolving lookup values along the way. This join structure explains both the breadth of header amounts it exposes and the join to customer identity columns such as PARTY_ID and CUST_ACCOUNT_ID.

Key Columns

The view returns a mix of identifiers, dates, amounts, and descriptive attributes:

• TRX_NUMBER, TRX_DATE, DUE_DATE — transaction number and key dates for the invoice header.
• INVOICE_CURRENCY_CODE, TYPE — invoice currency and the resolved transaction type description.
• PO_NUMBER, WAYBILL_NUMBER, SHIP_VIA — external references and shipment information.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING — original and outstanding balances from the payment schedule.
• AMOUNT_LINE_ITEMS_ORIGINAL, TAX_ORIGINAL, FREIGHT_ORIGINAL — original component amounts for goods, tax, and freight.
• AMOUNT_ADJUSTED, AMOUNT_APPLIED, AMOUNT_CREDITED, DISCOUNT_TAKEN_EARNED — adjustment, application, credit, and earned discount amounts.
• PARTY_ID, CUSTOMER_TRX_ID, CUST_ACCOUNT_ID — primary and foreign key identifiers linking to transaction, party, and account records.
• CREATED_BY, INTERFACE_HEADER_ATTRIBUTE1, ORG_ID — audit, interface, and multi-org context columns.

Common Use Cases and Queries

Typical uses include iStore invoice display, customer-facing statements, and integration extracts requiring freight, tax, and line amounts at the header level. To isolate freight values:

• Query by transaction number: SELECT trx_number, freight_original FROM apps.ibe_invoice_header_v WHERE trx_number = :trx_number;
• Aggregate freight by currency: SELECT invoice_currency_code, SUM(freight_original) FROM apps.ibe_invoice_header_v GROUP BY invoice_currency_code;
• Reconcile components: SELECT trx_number, amount_line_items_original, tax_original, freight_original FROM apps.ibe_invoice_header_v WHERE org_id = :org_id;

Because the view is documented as Oracle Internal Use Only, custom code should prefer supported Receivables interfaces where feasible. Where direct access is permitted, ORG_ID should always be supplied to preserve multi-org security.