Results for “iinvoice_name”

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

Overview

APPS.ECE_INO_HEADER_V is a reporting and integration view in Oracle E-Business Suite that exposes outbound invoice (INVOICE OUT) header information used by the e-Commerce Gateway (ECE) and the EDI/transaction processing architecture. Its name reflects the "INO" (Invoice Out) document family, and the view consolidates transactional invoice header data drawn from Oracle Receivables together with trading partner configuration data held in the ECE tables. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as a flattened, EDI-oriented projection of a customer invoice header, presenting values in the terminology used by outbound interfacing: document codes, translator codes, trading partner identifiers, bill-to address data, and customer attributes. Users and developers searching for "iinvoice_name" typically encounter this view because the column IInvoice_Name (aliased from RA_CUST_TRX_TYPES.NAME) surfaces the receivable transaction type, which is the functional equivalent of an invoice name on the outbound document. The view is owned by APPS and is intended to be queried read-only; it is not a base table.

Underlying Base Objects

The view is defined over a combination of Receivables, ECE, and Trading Community (HZ) objects. The documented referenced base objects are: RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, RA_BATCH_SOURCES, RA_SALESREPS_ALL, RA_TERMS_B, RA_TERMS_LINES, RA_TERMS_TL, AR_PAYMENT_SCHEDULES, ECE_AR_TRANSACTION (package), ECE_TP_DETAILS, ECE_TP_HEADERS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. The join pattern is characteristic of ECE outbound views: the invoice header is sourced from RA_CUSTOMER_TRX (aliased RCT1) and its type from RA_CUST_TRX_TYPES (RCTT). Trading partner and translator configuration is drawn from ECE_TP_DETAILS (ETD) and ECE_TP_HEADERS (ETH). Bill-to party and address details come from HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. The ECE_AR_TRANSACTION package supplies EDI processing context, and AR_PAYMENT_SCHEDULES contributes payment/terms-related data. The view text shows explicit hints such as /*+ ordered */ and an index hint on RA_CUSTOMER_TRX, reflecting performance tuning for large invoice volumes.

Key Columns

• COMMUNICATION_METHOD — literal 'EDI', identifying the transmission channel.
• Test_Flag — from ETD.TEST_FLAG, indicating whether the trading partner detail is a test configuration.
• Tp_Document_ID — trading partner document identifier (ETD.DOCUMENT_ID).
• Document_Type — the ECE document type (RCTT.TYPE).
• IInvoice_Name — the receivable transaction type name (RCTT.NAME); this is the column users locate when searching "iinvoice_name".
• TP_DOCUMENT_CODE — the invoice transaction number (RCT1.TRX_NUMBER).
• Tp_Translator_Code, Tp_Location_Code_Ext, Tp_Description, Tp_Reference_Ext1/2 — trading partner mapping attributes.
• Bill-to columns — Bill_To_Customer_Name, Bill_To_Address1..4, Bill_To_City, Bill_To_Postal_Code, Bill_To_Country, Bill_To_State, Bill_To_Province, Bill_To_County, and Bill_To_Customer_SIC_Code.
• Customer attributes — Bill_To_Customer_Att_Category and Bill_To_Customer_Attribute1..11, sourced from RA_CUSTOMER_TRX attributes.
• Transaction_Date — SYSDATE at query execution for the generated document.

Common Use Cases and Queries

Typical use is to inspect or reconcile outbound invoice header content before or after an EDI run, or to diagnose why a particular transaction type name (IInvoice_Name) is not being produced. The following sample selects the core identifying columns:

SELECT IInvoice_Name, TP_DOCUMENT_CODE, Document_Type, Tp_Location_Code_Ext, Bill_To_Customer_Name, Transaction_Date FROM APPS.ECE_INO_HEADER_V WHERE IInvoice_Name = :p_type_name;

Other practical patterns include filtering by trading partner location code, validating bill-to address completeness for a given invoice, and auditing the attribute columns carried into the outbound message. Because the view is defined over multiple master-detail relationships and includes ECE configuration tables, queries should be constrained by invoice number or transaction type to avoid full scans across the large RA_CUSTOMER_TRX population.