Results for “hz_financial_numbers”

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

Overview

HZ_FINANCIAL_NUMBERS is a Receivables (AR) schema table within Oracle E-Business Suite that stores the detailed definition of individual financial report numbers belonging to a financial report. The object sits within the Oracle Trading Community Architecture (TCA) / party data model and supports the capture and organization of financial reporting line items used by credit, collections, and customer financial profiling functionality. It is owned by the AR schema and carries a VALID status across the 12.1.1 and 12.2.2 releases, with a documented physical structure of 23 columns in the 12.2.2 ETRM extract.

From a Data Vault modeling perspective, the mined foreign key topology classifies this object as hub-leaning. That classification should be treated as a heuristic suggestion rather than a normative design directive: the table anchors on a single surrogate identity, FINANCIAL_NUMBER_ID, and is referenced by dependent child tables, which is characteristic of a hub surrounded by satellites rather than a pure transactional link.

Key Information Stored

The primary key of the table is the surrogate identifier FINANCIAL_NUMBER_ID, enforced by the unique index HZ_FINANCIAL_NUMBERS_PK. Two unique indexes are documented, and both represent business-key candidates. HZ_FINANCIAL_NUMBERS_U1 covers FINANCIAL_NUMBER_ID alone, while HZ_FINANCIAL_NUMBERS_U2 is a composite over FINANCIAL_REPORT_ID and FINANCIAL_NUMBER_NAME, indicating that the natural business identity of a financial number is scoped to its parent report and its named value.

• FINANCIAL_NUMBER_ID — surrogate primary key for the row, referenced by all child and extension tables.
• FINANCIAL_REPORT_ID — foreign key to HZ_FINANCIAL_REPORTS; the owning report that groups this number.
• FINANCIAL_NUMBER — the reported numeric value for the item.
• FINANCIAL_NUMBER_NAME — the label or display name of the financial item; participates with FINANCIAL_REPORT_ID in the U2 business key.
• FINANCIAL_UNITS_APPLIED — the unit or scale descriptor applied to the number.
• FINANCIAL_NUMBER_CURRENCY — the currency in which the reported amount is denominated.
• PROJECTED_ACTUAL_FLAG — distinguishes projected figures from actual reported figures.
• STATUS — lifecycle or validity state of the financial number record.
• CONTENT_SOURCE_TYPE and ACTUAL_CONTENT_SOURCE — describe the origin or sourcing classification of the content.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the TCA/AR framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and accountability columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program and request metadata identifying the process that last wrote the row.

Common Use Cases and Queries

Typical scenarios involve reporting financial figures captured against a customer or party financial profile, reconciling projected versus actual values, and extracting report content by currency or unit of measure. Because the table is a parent to extension and staging objects, it is commonly joined upward to HZ_FINANCIAL_REPORTS and outward to the extension tables.

A representative query retrieving all numbers for a given report, ordered by name, follows:

• SELECT fn.financial_number_id, fn.financial_number_name, fn.financial_number, fn.financial_number_currency, fn.projected_actual_flag FROM hz_financial_numbers fn WHERE fn.financial_report_id = :report_id ORDER BY fn.financial_number_name;
• Joining to the parent report: SELECT fr.report_name, fn.financial_number_name, fn.financial_number FROM hz_financial_reports fr, hz_financial_numbers fn WHERE fr.financial_report_id = fn.financial_report_id;
• Detecting changed rows for incremental extraction using the audit and request columns: SELECT financial_number_id, last_update_date FROM hz_financial_numbers WHERE last_update_date > :high_water_mark;
• Filtering only actual figures: SELECT financial_number_id FROM hz_financial_numbers WHERE projected_actual_flag = 'A';

These patterns are suited to data-warehouse loads, TCA financial profiling reports, and audit queries that trace which concurrent program populated a financial number.

Related Objects

The documented relationship graph is compact but unambiguous. The table references its parent and is referenced by three dependent objects.

• HZ_FINANCIAL_REPORTS — parent table; joined on HZ_FINANCIAL_NUMBERS.FINANCIAL_REPORT_ID = HZ_FINANCIAL_REPORTS.FINANCIAL_REPORT_ID.
• HZ_FIN_NUMBERS_EXT_B — base extension table referencing HZ_FINANCIAL_NUMBERS.FINANCIAL_NUMBER_ID.
• HZ_FIN_NUMBERS_EXT_TL — translatable (language) extension table joining on FINANCIAL_NUMBER_ID, supplying localized name and description content.
• HZ_IMP_FINNUMBERS_SG — interface/staging table used by import processes, joining on FINANCIAL_NUMBER_ID.

Collectively these objects form the financial-number cluster: a hub-like parent (HZ_FINANCIAL_NUMBERS), a base satellite (HZ_FIN_NUMBERS_EXT_B), a translated satellite (HZ_FIN_NUMBERS_EXT_TL), and an inbound staging path (HZ_IMP_FINNUMBERS_SG). Extraction and reporting logic should respect the primary key and the U2 composite unique index when deduplicating source records.