Results for “a_ship”

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

Overview

AR_INVOICE_HEADER_V is a seeded Oracle E-Business Suite view owned by the APPS schema within the Receivables (AR) product. It presents invoice header-level information by joining transaction records from RA_CUSTOMER_TRX to their transaction types, payment terms, bill-to and ship-to customer data, and printing/commitment attributes. The view is classified with a VALID status and is available in both 12.1.1 and 12.2.2. Its primary role is as a reporting and integration layer: it denormalizes header attributes scattered across Receivables, Oracle Trading Community Architecture (TCA), and terms tables into a single consumable projection for custom reports, concurrent programs, BI Publisher data templates, and outbound interfaces. Because it is a view rather than a table, it enforces no storage of its own and reflects the current committed state of the underlying receipts and transaction data at query time.

Underlying Base Objects

The ETRM documented metadata lists an extensive set of referenced objects. Transaction data originates from RA_CUSTOMER_TRX (SYNONYM) and RA_CUST_TRX_TYPES, while payment terms are resolved through RA_TERMS and RA_TERMS_LINES, supplemented by the AR_INVOICE_COUNT_TERMS_V view and AR_PAYMENT_SCHEDULES. Receipt and application context draws on AR_ADJUSTMENTS. The view relies on AR_LOOKUPS for lookup meaning resolution, AR_SYSTEM_PARAMETERS for environment defaults, and AR_INVOICE_SQL_FUNC_PUB for server-side logic. Customer and party information is sourced from the TCA synonym set: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_PROFILE_AMTS, HZ_CUST_SITE_USES, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS. Additional supporting objects include FND_TERRITORIES_VL, HZ_FORMAT_PUB, RA_BATCH_SOURCES, RA_SALESREPS, and ORG_FREIGHT. The view therefore sits atop a substantial join graph spanning Receivables, TCA, and shared application foundation tables.

Key Columns

Among the most significant columns exposed are CUSTOMER_TRX_ID (the primary transaction identifier) and TRX_NUMBER, the user-visible invoice number. TRX_DATE, SHIP_DATE_ACTUAL, SHIP_VIA, and WAYBILL_NUMBER describe transactional and shipping context, while INVOICE_CURRENCY_CODE identifies the currency. The purchase order attributes include PURCHASE_ORDER_NUMBER, PURCHASE_ORDER_REVISION, and PURCHASE_ORDER_DATE.

Of particular interest to the search term_sequence_number is the column TERM_SEQUENCE_NUMBER, computed as NVL(NVL(TL.SEQUENCE_NUM, PS.TERMS_SEQUENCE_NUMBER), 1). This expression resolves the effective installment sequence: it prefers the sequence number from RA_TERMS_LINES (TL.SEQUENCE_NUM), falls back to the terms sequence on the payment schedule (PS.TERMS_SEQUENCE_NUMBER), and defaults to 1 when neither is populated. RELATED columns include TERM_NAME, TERM_ID, TERM_DUE_DATE_FROM_PS (mapped from PS.DUE_DATE), and TERM_PERCENT, which is derived as NVL(TL.RELATIVE_AMOUNT,100) * (100/NVL(T.BASE_AMOUNT,100)). Bill-to details are provided through BILL_TO_CUSTOMER_ID, BILL_TO_CONTACT_ID, BILL_TO_SITE_USE_ID, BILL_TO_LOCATION, and BILL_TO_CUSTOMER_NUMBER. Printing attributes include PRINTING_COUNT, PRINTING_ORIGINAL_DATE, PRINTING_LAST_PRINTED, PRINTING_PENDING, and LAST_PRINTED_SEQUENCE_NUMBER.

Common Use Cases and Queries

Typical uses include receivable aging analysis, invoice register reporting, terms/installment reconciliation, and integration extracts for downstream systems. The TERM_SEQUENCE_NUMBER column is frequently queried when reconciling multiple payment terms lines against payment schedules, since it normalizes the sequence across both sources.

• Retrieve invoice header basics: SELECT TRX_NUMBER, TRX_DATE, INVOICE_CURRENCY_CODE FROM APPS.AR_INVOICE_HEADER_V WHERE TRX_NUMBER = :trx_num;
• Inspect term sequencing: SELECT TRX_NUMBER, TERM_NAME, TERM_SEQUENCE_NUMBER, TERM_PERCENT, TERM_DUE_DATE_FROM_PS FROM APPS.AR_INVOICE_HEADER_V ORDER BY TRX_NUMBER, TERM_SEQUENCE_NUMBER;
• Filter by bill-to customer: SELECT TRX_NUMBER, BILL_TO_CUSTOMER_NUMBER, BILL_TO_LOCATION FROM APPS.AR_INVOICE_HEADER_V WHERE BILL_TO_CUSTOMER_ID = :cust_id;

Because the view aggregates numerous base objects, queries should filter on CUSTOMER_TRX_ID, TRX_NUMBER, or date ranges to limit the join cost. Custom code should reference the APPS synonym rather than the underlying tables to preserve upgrade safety across 12.1.1 and 12.2.2.