Results for “breakdown_result_id”

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

Overview

GHR_BREAKDOWN_RESULTS is a table owned by the HR schema within the GHR — US Federal Human Resources product family of Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, it is a temporary (transient, session-scoped) table used to produce the breakdown report, a Statutory reporting facility that aggregates workforce data by protected demographic characteristics for US federal Equal Employment Opportunity (EEO) and related compliance reporting.

The table acts as a staging or scratch area rather than a permanent transactional store. Rows are populated by a reporting process, consumed by the breakdown report, and are expected to be purged or overwritten on subsequent runs. Under the heuristic Data Vault classification derived from its foreign-key structure, GHR_BREAKDOWN_RESULTS is classified as satellite-leaning. This should be treated as a modeling suggestion only: the table has a composite primary key that includes a session surrogate and a result identifier, and it carries descriptive attributes (demographic and SQL fragment columns) rather than representing a business relationship between two hubs. In Data Vault terms, it most closely resembles a descriptive satellite attached to a breakdown criteria parent, with the session identifier playing a degenerate or run-scoped role.

Key Information Stored

The documented physical schema contains thirteen columns. The most significant are:

• SESSION_ID — Part of the composite primary key (GHR_BREAKDOWN_RESULTS_PK). Identifies the report execution session that produced the result set, enabling multiple concurrent or historical runs to coexist without collision.
• BREAKDOWN_RESULT_ID — The second component of the composite primary key. Provides the unique identifier for an individual result row within a session.
• BREAKDOWN_CRITERIA_ID — The foreign key to GHR_BREAKDOWN_CRITERIA, linking each result row to the criterion definition that generated it.
• SEX — The gender classification used as a breakdown dimension in the report output.
• ETHNIC_ORIGIN — The race and ethnicity classification used as a breakdown dimension.
• FOR_CLAUSE — The SQL FOR clause fragment generated for the reporting query, typically used with ROLLUP or CUBE to produce subtotals across the breakdown dimensions.
• WITHIN_CLAUSE — The SQL WITHIN clause fragment driving ordering or windowing semantics of the aggregate query.
• BY_CLAUSE — The SQL BY clause fragment defining the grouping or ordering keys applied to the generated query.
• AUDIT_Columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE follow the standard Oracle EBS WHO-column convention and record row-level audit metadata.

The primary key is a surrogate-style composite key (SESSION_ID, BREAKDOWN_RESULT_ID); the documented unique index aligns with this key. No separate business-key unique index is documented beyond the primary key, which is consistent with the table's temporary nature — business keys are not enforced because the content is run-scoped output rather than durable master or transactional data.

Common Use Cases and Queries

The table is not intended for direct end-user querying, but it is commonly inspected during report troubleshooting, performance analysis, and data validation. Typical access patterns include retrieving the most recent session's output, joining to the criteria table for labels, and inspecting the generated SQL fragments.

• Current session output: SELECT * FROM hr.ghr_breakdown_results WHERE session_id = (SELECT MAX(session_id) FROM hr.ghr_breakdown_results);
• Criteria-labelled breakdown: SELECT r.session_id, c.criteria_name, r.sex, r.ethnic_origin FROM hr.ghr_breakdown_results r, hr.ghr_breakdown_criteria c WHERE r.breakdown_criteria_id = c.breakdown_criteria_id AND r.session_id = :p_session;
• Inspect generated SQL clauses: SELECT breakdown_result_id, for_clause, within_clause, by_clause FROM hr.ghr_breakdown_results WHERE session_id = :p_session;
• Demographic aggregation: Grouping by SEX and ETHNIC_ORIGIN to validate headcount distribution across protected categories for EEO reporting.
• Housekeeping and growth control: Detecting orphaned sessions that were never purged by comparing distinct SESSION_ID values against expected report runs, since transient accumulation here can affect tablespace usage.
• Audit reconciliation: Using CREATED_BY and CREATION_DATE to confirm which concurrent request and user generated a given result set.

Because rows are transient, queries should always be scoped by SESSION_ID or a recent date predicate to avoid returning stale results from prior executions.

Related Objects

• GHR_BREAKDOWN_CRITERIA — The parent table referenced by GHR_BREAKDOWN_RESULTS.BREAKDOWN_CRITERIA_ID. This is the only documented foreign-key relationship and the principal join path.
• GHR_BREAKDOWN_RESULTS_PK — The primary key constraint/index over (SESSION_ID, BREAKDOWN_RESULT_ID), enforcing row uniqueness within a report session.
• HR schema WHO/audit conventions — The standard EBS audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) link behaviorally to FND_USER and related audit infrastructure.
• Breakdown report concurrent program — The report process that writes to and reads from this table; it owns the lifecycle of each SESSION_ID.
• EEO/Statutory reporting outputs — Downstream report layouts and extracts that consume the aggregated demographic rows produced here.

Because the documented relationship set is deliberately narrow, GHR_BREAKDOWN_RESULTS should be treated as a leaf-level reporting staging object rather than a hub in the integration model.