Search Results hr_owner_definitions




Overview
Explore in AI Chat

Overview

HR_OWNER_DEFINITIONS is a table in the HR schema of Oracle E-Business Suite, classified under the PAY (Payroll) product. Per the Oracle ETRM documentation, it "stores internal record for ownership of seed data." Seed data in EBS refers to the pre-delivered configuration rows that Oracle ships with applications—lookups, flexfield definitions, messages, and other foundational reference data required for the product to function. HR_OWNER_DEFINITIONS tracks which session or process owns specific seed data records, ensuring controlled and auditable management of that seeded configuration.

The object is marked VALID and exists across both EBS 12.1.1 and 12.2.2. Its role is largely internal and infrastructural rather than functional. Standard functional users and most reporting requirements will not touch this table directly; it primarily supports the ownership lifecycle of seeded records so that Oracle-delivered data can be distinguished from customer-created data and managed correctly during patching and upgrades. The heuristic Data Vault classification mined from foreign key structure is standalone, meaning it exposes no dependent relationships and functions as an independent entity in the modeled schema. Under a Data Vault modeling lens, it is best suggested as a hub-like or independent reference table rather than a satellite that depends on a parent entity.

Key Information Stored

The table is compact, with only 3 documented columns in the 12.2.2 physical schema:

  • SESSION_ID — Identifies the session or process under which seed data ownership is recorded. This is the principal identifier for the ownership context and forms part of the primary key.
  • PRODUCT_SHORT_NAME — The short name of the product (for example, a PAY or HR product abbreviation) that the seed data belongs to. Combined with SESSION_ID, it uniquely identifies an ownership record.
  • ZD_EDITION_NAME — The edition name, part of the Edition-Based Redefinition (EBR) model introduced with EBS 12.2. It appears in the unique index HR_OWNER_DEFINITIONS_PK alongside SESSION_ID and PRODUCT_SHORT_NAME and records the edition under which the row is defined. Under 12.1.1 EBR is not present, so this column does not exist there.

The surrogate primary key is HR_OWNER_DEFINITIONS_PK. In 12.2.2 the documented unique index encompasses (SESSION_ID, PRODUCT_SHORT_NAME, ZD_EDITION_NAME), which constitutes the business-key candidate. In 12.1.1, the same key is effectively composed of SESSION_ID and PRODUCT_SHORT_NAME, without the edition component. No foreign keys to other tables are documented.

Common Use Cases and Queries

Because this is internal seed-data tracking, direct usage is limited and typically arises during diagnostics, patching, upgrade reconciliation, or data lineage investigations. Typical scenarios include determining which session recorded ownership for a product's seed data, and comparing ownership records across editions in a 12.2 multitenant/EBR environment.

A representative query to inspect current ownership records:

SELECT session_id,
       product_short_name,
       zd_edition_name
FROM   hr.hr_owner_definitions
ORDER  BY product_short_name, session_id;

To isolate seed-data ownership for a specific product:

SELECT session_id, zd_edition_name
FROM   hr.hr_owner_definitions
WHERE  product_short_name = :p_product_short;

In 12.1.1 the third column is absent, so queries should exclude ZD_EDITION_NAME for that release. Reporting use cases are mainly audit-oriented: tracing ownership history, supporting upgrade verification, and reconciling seed data after patching. Because rows are process-generated, any SQL should be treated as read-only unless performed under Oracle guidance during controlled maintenance.

Related Objects

The ETRM metadata records no foreign key relationships, consistent with the standalone classification. Consequently there are no formally dependent tables, views, or APIs asserting FK constraints to HR_OWNER_DEFINITIONS. Related objects of significance therefore come from shared context rather than referential integrity:

  • Other HR/PAY seed-data management objects that carry SESSION_ID and PRODUCT_SHORT_NAME to identify product ownership.
  • The HR_OWNER_DEFINITIONS_PK unique index, which enforces the (SESSION_ID, PRODUCT_SHORT_NAME, ZD_EDITION_NAME) business key in 12.2.2.
  • EDR/EBR-related dictionary views (for example ZD_EDITION_NAME-aware ALL_TAB_COLUMNS) used to enumerate the table's columns per edition.
  • PAY product lookup and seed configuration repositories that rely on ownership tracking during patch application.

Because no join columns are documented, no reliable join paths can be asserted from the provided metadata. Any linkages to other seed or product configuration tables are logical and must be confirmed against a specific instance's data model.