Results for “ece_ino_header_1_v”

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

Overview

The view ECE_INO_HEADER_1_V is an APPS-owned database view within the Oracle E-Business Suite e-Commerce Gateway (EC) module. Its role is to extract additional header-level information used when generating the outbound Invoice transaction (ANSI X12 810 / UN/EDIFACT INVOIC). The view is classified as a private, active business entity under the Receivables (AR) product, with the display name Invoice Header Attributes View and category AR_INVOICE.

Within the e-Commerce Gateway architecture, each outbound transaction is assembled from a set of interface views that map Oracle application data to the flat-file segments and records of an EDI document. ECE_INO_HEADER_1_V supplies supplementary header attributes — including transaction flexfield attributes, interface attributes, shipping origin codes, and line-level linking identifiers — that complement the core invoice header extraction. Because it exposes these elements as named columns, it allows the EDI mapping layer, and by extension user-configured translation maps, to reference invoice header attributes that are not otherwise surfaced by the primary header view.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over the following documented base objects:

• RA_CUSTOMER_TRX (synonym) — the Receivables transaction header, supplying transaction flexfield and interface attribute columns.
• RA_CUSTOMER_TRX_LINES (synonym) — the transaction lines, supplying the line identifier and line type used in the view.
• MTL_PARAMETERS (synonym) — referenced to derive the ship-from organization code.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL (synonyms) — organization definitions and translations used to resolve organization codes.
• HR_ORGANIZATION_INFORMATION (synonym) — organization classification and detail attributes.
• HR_SECURITY (package) — the organization security package, used to restrict visible organizations according to the user's security profile.
• GL_SETS_OF_BOOKS (view) — the accounting books definition, referenced in the join chain.

The view therefore joins the AR invoice header and line tables to HR/MTL organization data, resolving an organization code (for example, SHIP_FROM_CODE_INT) while honouring organization-level security. This makes it a read-only, reporting-oriented projection over the transactional Receivables data.

Key Columns

• TRANSACTION_ID — derived from RA_CUSTOMER_TRX.CUSTOMER_TRX_ID; links the row to the invoice header.
• SHIP_FROM_CODE_INT — the ship-from organization code resolved from MTL_PARAMETERS.ORGANIZATION_CODE.
• ROUTING_INSTRUCTIONS — exposed as a placeholder, defined in the view text as NULL (character). It is included for positional/mapping compatibility with the invoice document layout, not as a populated value.
• EQUIPMENT_PREFIX, EQUIPMENT_NUMBER, PACKING_SLIP_NUMBER — also defined as NULL placeholders.
• CUSTOMER_TRX_LINE_ID and LINE_TYPE — carried from RA_CUSTOMER_TRX_LINES to link header rows to their lines.
• PICKING_LINE_ID — placeholder column defined as NULL.
• INTERFACE_ATTRIBUTE_CATEGORY and INTERFACE_ATTRIBUTE1..25 — sourced from RA_CUSTOMER_TRX.INTERFACE_HEADER_CONTEXT and the corresponding interface header attribute columns.
• TRANSACTION_ATTRIBUTE_CATEGORY and TRANSACTION_ATTRIBUTE1..15+ — sourced from the standard RA_CUSTOMER_TRX descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1…).

The distinction between interface attributes and transaction attributes is significant: interface attributes carry EDI-specific values supplied during inbound/outbound processing, whereas transaction attributes carry descriptive flexfield data captured on the Receivables transaction itself.

Common Use Cases and Queries

The view is principally used to populate attribute segments of the outbound 810/INVOIC flat file and to support reconciliation reporting. A typical query verifying header attributes for a given invoice is:

• SELECT transaction_id, ship_from_code_int, routing_instructions, interface_attribute1, transaction_attribute1 FROM apps.ece_ino_header_1_v WHERE transaction_id = :p_trx_id;
• Joining back to RA_CUSTOMER_TRX to reconcile the extracted attribute context against the source invoice.
• Auditing interface attribute usage across a batch of outbound invoices to confirm the EDI map populated the expected segments.

Because several columns resolve to NULL, queries should treat them as structural placeholders, and users requiring populated routing or equipment data must source it from other EC views or from the translation map configuration.