Results for “num_value3”

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

Overview

HR_SUMMARY is a Human Resources (PER) module table in Oracle E-Business Suite, owned by the HR schema and stored in the HR.HR_SUMMARY schema object. According to the ETRM documentation, the table "holds all data for the Generic Summary Process." In practical terms, HR_SUMMARY functions as a flexible, generic staging and consolidation repository used by Oracle HRMS to store summarized or aggregated results that do not warrant a dedicated, purpose-built table. Rather than defining a rigid set of columns for every conceivable summary, the Generic Summary Process writes into this single table using a set of generic value columns (TEXT_VALUE1–7, NUM_VALUE1–3, DATE_VALUE1–3, and FK_VALUE1–3), allowing diverse summary types to share one physical structure.

The table is classified under the ETRM's heuristic Data Vault mining as "satellite-leaning." This suggests a modeling interpretation in which HR_SUMMARY behaves as a satellite structure: it carries descriptive and measured attributes that hang off a business key, with the primary key HR_SUMMARY_PK (ID_VALUE) acting as the surrogate identifier and TYPE distinguishing the category of summary being stored.

Key Information Stored

The documented physical schema for 12.2.2 lists 25 columns. The most significant are:

• ID_VALUE — Surrogate primary key; the single column forming HR_SUMMARY_PK.
• TYPE — Classifies the kind of summary record, allowing one table to serve many summary processes.
• BUSINESS_GROUP_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS; scopes the row to a business group.
• OBJECT_VERSION_NUMBER — Optimistic locking / concurrency control column used by the OAF framework.
• FK_VALUE1, FK_VALUE2, FK_VALUE3 — Generic foreign-key holders referencing whatever entity the summary relates to.
• TEXT_VALUE1 – TEXT_VALUE7 — Generic descriptive/text payload columns.
• NUM_VALUE1 – NUM_VALUE3 — Generic numeric measures (for example, counts, totals, or amounts).
• DATE_VALUE1 – DATE_VALUE3 — Generic date attributes (for example, effective or summary dates).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns present on nearly all EBS tables.

The unique index HR_SUMMARY_PK on ID_VALUE is the documented business-key candidate; the design is intentionally generic, so TYPE plus the FK_VALUE and VALUE columns combine to give each row its business meaning.

Common Use Cases and Queries

Typical usage involves retrieving summarized HRMF results by type and business group. A common pattern is to filter by TYPE and BUSINESS_GROUP_ID and join the generic FK columns back to their source entities. For example:

• Reporting all summaries of a given TYPE: SELECT * FROM hr.hr_summary WHERE type = :p_type AND business_group_id = :p_bg;
• Aggregating numeric measures: SELECT fk_value1, SUM(num_value1) FROM hr.hr_summary WHERE type = :p_type GROUP BY fk_value1;
• Auditing recent changes: SELECT id_value, type, last_update_date, last_updated_by FROM hr.hr_summary WHERE last_update_date > SYSDATE-7;

Because the table is generic, developers must first determine the meaning of TYPE, the FK columns, and the value columns for the specific summary process before writing queries. The OBJECT_VERSION_NUMBER supports concurrent updates through OAF-based forms and pages.

Related Objects

The documented foreign key establishes a dependency on HR_ALL_ORGANIZATION_UNITS via HR_SUMMARY.BUSINESS_GROUP_ID. The most significant related objects are:

• HR_ALL_ORGANIZATION_UNITS — joined on BUSINESS_GROUP_ID.
• HR_SUMMARY_PK — the primary key constraint/index on ID_VALUE.
• HR_ALL_ORGANIZATION_UNITS (Organization) — provides the business group context and security scope.
• PER Generic Summary Process — the concurrent/API process that populates and reads HR_SUMMARY.
• OAF/Forms summary pages — application entities that consume and maintain these rows.

Where additional summary detail is required, the generic TEXT_VALUE, NUM_VALUE, and DATE_VALUE columns can be interpreted against the corresponding source HRMS entities referenced by FK_VALUE1–3.