Results for “base_currency_code”

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

Overview

ECE_INO_HEADER_V is a private view owned by the APPS schema within the Oracle e-Commerce Gateway (EC) product. Its documented purpose is to extract header-level information for the outbound Invoice transaction, associated with the 810 (ANSI X12) and INVOIC (EDIFACT) document standards. The view is registered in ETRM with the display name "Invoice Header View" and is categorized under the business entity AR_INVOICE, with lifecycle status active and product attribution to Oracle Receivables. It functions as a staging and extraction layer that transforms native Receivables transaction data into the flat, positional structure required by the e-Commerce Gateway translation engine for outbound invoice generation. Because it is marked private scope, it is intended for internal use by the EC extract programs rather than as a general-purpose reporting interface, though it is frequently queried directly for troubleshooting outbound invoice interfaces.

Underlying Base Objects

The view is defined over a substantial set of Receivables, Trading Community Architecture (TCA), and e-Commerce Gateway objects. The documented referenced base objects include AR_PAYMENT_SCHEDULES, ECE_AR_TRANSACTION (a package), ECE_TP_DETAILS, ECE_TP_HEADERS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES, RA_BATCH_SOURCES, RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, RA_SALESREPS_ALL, RA_TERMS_B, RA_TERMS_LINES, and RA_TERMS_TL. The invoice transaction header itself (RA_CUSTOMER_TRX) supplies the transaction number exposed as TP_DOCUMENT_CODE, while RA_CUST_TRX_TYPES provides the document type and invoice name. Trading partner and location details are drawn from ECE_TP_HEADERS, ECE_TP_DETAILS, and the TCA party, account, site, and location tables. The reference to RA_SALESREPS_ALL is significant for users searching on sales representative attributes, since salesperson data is sourced from that table and surfaced through the view's header extraction logic.

Key Columns

The projection begins with constant and control columns: COMMUNICATION_METHOD is set to the literal 'EDI', TEST_FLAG and DOCUMENT_STANDARD are carried from ECE_TP_DETAILS, and TP_DOCUMENT_ID, TP_TRANSLATOR_CODE, TP_DESCRIPTION, TP_REFERENCE_EXT1, and TP_REFERENCE_EXT2 support trading partner identification. TRANSACTION_DATE returns SYSDATE. The transaction identity columns include DOCUMENT_TYPE, IINVOICE_NAME, and TP_DOCUMENT_CODE (RCT1.TRX_NUMBER). Bill-to information is extensive: BILL_TO_CUSTOMER_CODE_INT from RA_CUSTOMER_TRX.ORIG_SYSTEM_REFERENCE, BILL_TO_CUSTOMER_NAME (truncated to 50 bytes using SUBSTRB), the address components ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, COUNTRY, STATE, PROVINCE, and COUNTY from HZ_LOCATIONS, plus BILL_TO_CUSTOMER_SIC_CODE (populated only for organizations) and BILL_TO_CUSTOMER_SALES_CHANNEL. Contact columns such as BILL_TO_CONTACT_LAST_NAME, FIRST_NAME, and JOB_TITLE are returned as NULL literals. Attribute category and ATTRIBUTE1 through ATTRIBUTE5 columns are exposed for both the trading partner detail and the customer, and additional descriptive flexfield segments continue beyond the excerpt. The presence of RA_SALESREPS_ALL among base objects indicates salesperson-related values, including primary sales representative name, are resolved through this view's header join.

Common Use Cases and Queries

The primary use case is diagnosing and validating outbound 810/INVOIC invoice data before or after the e-Commerce Gateway extract runs. A typical query retrieves the header identity and bill-to detail for a specific transaction:

• SELECT tp_document_code, invoice_name, bill_to_customer_name, bill_to_city, bill_to_country FROM apps.ece_ino_header_v WHERE tp_document_code = :trx_number;
• Filtering by trading partner attributes to confirm routing: WHERE tp_reference_ext1 = :partner_ref.
• Inspecting test versus production runs via WHERE test_flag = 'Y'.

Analysts searching for primary sales representative information typically join the view output back to RA_SALESREPS_ALL or query the underlying RA_CUSTOMER_TRX header, since the salesperson name is resolved from the salesrep table referenced in the view definition. The view is also used to reconcile interface errors, verify truncation behavior at 50 bytes for customer names, and confirm that flexfield attribute columns are populated as expected before the translated file is transmitted.