Search Results hz_fin_reports_ext_b_u1

Overview

AR.HZ_FIN_REPORTS_EXT_B is a transactional extension table in the Oracle E-Business Suite Receivables (AR) schema that stores extensible attribute values for financial reports. It sits beneath the Oracle Trading Community Architecture (TCA) and Customer Relationship Management data model, and its name follows the TCA convention: the "_B" suffix denotes the base table that holds the primitive, language-independent column values, complemented by descriptive attribute columns. The table captures free-format characteristics of a financial report that the standard report definition does not accommodate, allowing implementers to attach client-specific data to a report record without modifying base schema objects.

The object is owned by AR, carries FND Design Data reference AR.HZ_FIN_REPORTS_EXT_B, and is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10. Its indexes reside in APPS_TS_TX_IDX. Under the heuristic Data Vault classification mined from its foreign-key structure, the table is satellite-leaning: it references a parent financial report through FINANCIAL_REPORT_ID, its foreign key targets HZ_FINANCIAL_REPORTS, and the foreign-key column is not itself the primary key of this table. From a modeling perspective, it is best treated as a satellite attached to the HZ_FINANCIAL_REPORTS hub, with EXTENSION_ID serving as the row-level key.

Key Information Stored

The physical schema documents 58 columns. The most significant are:

• EXTENSION_ID — NUMBER(15), the unique system-generated identifier. It is the column of unique index HZ_FIN_REPORTS_EXT_B_U1 and the table's primary key (HZ_FIN_REPORTS_EXT_B_PK).
• FINANCIAL_REPORT_ID — NUMBER(15), the identifier of the financial report for which extensible attribute values are entered. This is the foreign-key column to HZ_FINANCIAL_REPORTS and the leading column of non-unique index HZ_FIN_REPORTS_EXT_B_N1; it is the effective business-key candidate linking an extension to its parent report.
• ATTR_GROUP_ID — NUMBER(15), the attribute group identifier that groups a set of extensible attributes under a common context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns that provide audit tracking for every inserted and updated row.
• C_EXT_ATTR1 through C_EXT_ATTR20 — 20 character-based extensible attribute columns, each VARCHAR2(150).
• N_EXT_ATTR1 through N_EXT_ATTR20 — 20 numeric extensible attribute columns.
• D_EXT_ATTR1 through D_EXT_ATTR10 — 10 date-based extensible attribute columns.

The distinction between EXTENSION_ID and FINANCIAL_REPORT_ID is important: EXTENSION_ID is the surrogate primary key guaranteeing row uniqueness, while FINANCIAL_REPORT_ID is the documented business-key candidate through which consumers relate extension rows to their parent report.

Common Use Cases and Queries

The primary use case is joining the extension row to HZ_FINANCIAL_REPORTS to retrieve client-defined attribute values alongside the base report definition. The search phrase "joining report" aligns directly with this pattern.

A standard retrieval joins on the foreign key:

SELECT r.financial_report_id, e.extension_id, e.attr_group_id,
  e.c_ext_attr1, e.n_ext_attr1, e.d_ext_attr1
FROM hz_financial_reports r, hz_fin_reports_ext_b e
WHERE r.financial_report_id = e.financial_report_id;

Additional scenarios include filtering by ATTR_GROUP_ID to retrieve a specific context of extensible data, auditing changed extension rows using LAST_UPDATE_DATE, and extracting a subset of the 20 character, 20 numeric, and 10 date attribute slots into a downstream reporting or data-warehouse layer. Because the attribute columns are generic, the mapping from C_EXT_ATTR, N_EXT_ATTR, and D_EXT_ATTR to meaningful business terms must be derived from the configured attribute group definition rather than from the columns themselves.

Related Objects

The following objects are the most significant given the documented relationship data:

• AR.HZ_FINANCIAL_REPORTS — the parent table referenced by the foreign key HZ_FIN_REPORTS_EXT_B.FINANCIAL_REPORT_ID. It is the principal join partner for every query against the extension table.
• HZ_FIN_REPORTS_EXT_B_U1 — unique index on EXTENSION_ID in APPS_TS_TX_IDX, enforcing the primary key.
• HZ_FIN_REPORTS_EXT_B_N1 — non-unique index on FINANCIAL_REPORT_ID supporting the parent-child join.
• HZ_FIN_REPORTS_EXT_B_PK — the primary key constraint on EXTENSION_ID.
• Attribute group definitions — the configuration entity referenced conceptually by ATTR_GROUP_ID, which maps generic attribute columns to application meaning.

All access should respect the AR schema ownership and use the documented join column pair (FINANCIAL_REPORT_ID = HZ_FINANCIAL_REPORTS.FINANCIAL_REPORT_ID) to preserve referential integrity and index usage. The behavior is consistent across Oracle EBS 12.1.1 and 12.2.2, as the object remains VALID in the ETRM 12.2.2 documentation.