Results for “per_org_structure_versions”

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

Overview

PER_ORG_STRUCTURE_VERSIONS is an Oracle Human Resources (PER) table that stores version control information for organization hierarchies in Oracle E-Business Suite 12.1.1 and 12.2.2. Organization structures in EBS are rarely static; they are reorganized over time as business units, departments, cost centers, and reporting lines shift. Rather than mutating hierarchy definitions in place, EBS models each structural revision as a discrete version record, and PER_ORG_STRUCTURE_VERSIONS is the header table that anchors those revisions. Each row represents one dated, numbered version of a hierarchy defined in PER_ORGANIZATION_STRUCTURES, scoped to a specific business group.

This table is the parent of the hierarchy detail table PER_ORG_STRUCTURE_ELEMENTS, which holds the individual node placements belonging to a given version. Together they allow the application to reconstruct the state of an organization tree as of any effective date. A large number of downstream objects — recruiting, payroll cost allocation, performance management, learning management, and budget control — pin themselves to a specific structure version so their calculations and eligibility rules remain deterministic.

From a dimensional modeling perspective, the table's characteristics (a stable primary key, descriptive and effective-dating attributes, and a single natural parent) suggest a hub-leaning classification with satellite behavior. This is a heuristic suggestion rather than a normative EBS design statement; in practice the table is treated as both a version registry and a transactional/date-tracked entity.

Key Information Stored

The surrogate primary key, ORG_STRUCTURE_VERSION_ID, is generated by the sequence behind PER_ORG_STRUCTURE_VERSIONS_PK, which is the only documented unique index and therefore the sole business-key candidate available for reliable row identification. All foreign relationships to this table hinge on this single column.

• ORG_STRUCTURE_VERSION_ID — surrogate primary key; the join column used by nearly every dependent table.
• ORGANIZATION_STRUCTURE_ID — foreign key to PER_ORGANIZATION_STRUCTURES, identifying which logical hierarchy this version belongs to.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS; enforces the multi-tenant business group boundary that governs security and data access.
• VERSION_NUMBER — the human-readable ordinal of the revision within its parent structure.
• DATE_FROM / DATE_TO — the effective date range during which this version is current. DATE_TO is typically null for the active version.
• COPY_STRUCTURE_VERSION_ID — self-referencing pointer recording which prior version a new version was copied from, preserving lineage across reorganizations.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context, indicating which batch process or concurrent request created or last updated the version.
• TOPNODE_POS_CTRL_ENABLED_FLAG — indicates whether top-node position control is enabled for the version, affecting establishment and headcount validation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns supporting change tracking and BI extract incremental loads.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Object Library (OAF) framework to prevent concurrent update conflicts.

Common Use Cases and Queries

The most frequent requirement is resolving "the hierarchy as of a date" for reporting or a point-in-time reconstruction of an employee's reporting line. The canonical pattern joins the version header to its elements:

• Current active version lookup — SELECT org_structure_version_id, version_number FROM per_org_structure_versions WHERE organization_structure_id = :p AND SYSDATE BETWEEN date_from AND NVL(date_to, SYSDATE) AND business_group_id = :bg.
• Full hierarchy rebuild — join to PER_ORG_STRUCTURE_ELEMENTS on ORG_STRUCTURE_VERSION_ID to obtain parent/child node placements for the selected version.
• Version lineage tracing — recursively follow COPY_STRUCTURE_VERSION_ID to audit how a hierarchy evolved across successive reorganizations.
• Impact analysis before restructuring — query dependents (for example PA_PROJECT_ASSIGNMENTS.SEARCH_EXP_ORG_STRUCT_VER_ID or PQH_BUDGETS.ORG_STRUCTURE_VERSION_ID) to determine which downstream records are pinned to a version that is about to be end-dated.
• Batch reconciliation — filter on REQUEST_ID or PROGRAM_UPDATE_DATE to confirm that a mass realignment or mass transfer process wrote the expected version records.

Because several consumer objects (PA_IMPLEMENTATIONS_ALL, IGW_IMPLEMENTATIONS_ALL) can hold multiple version references, joins should always constrain by business group and by an explicit effective-date predicate to avoid fanning out across historical rows.

Related Objects

The table participates in a dense web of foreign key relationships. The most significant are listed below with their documented join columns.

• PER_ORGANIZATION_STRUCTURES — parent definition table, joined on ORGANIZATION_STRUCTURE_ID.
• HR_ALL_ORGANIZATION_UNITS — business group context, joined on BUSINESS_GROUP_ID.
• PER_ORG_STRUCTURE_ELEMENTS — the primary child table, joined on ORG_STRUCTURE_VERSION_ID; holds node-level detail for the version.
• PQH_BUDGETS — budget definitions in Oracle Public Sector/HR Budgeting, joined on ORG_STRUCTURE_VERSION_ID.
• PA_PROJECT_ASSIGNMENTS — project resource assignments, joined on SEARCH_EXP_ORG_STRUCT_VER_ID.
• PA_IND_RATE_SCHEDULES_ALL_BG and PA_IND_RATE_SCH_REVISIONS — project costing rate schedules, joined on ORG_STRUCTURE_VERSION_ID.
• GHR_MASS_REALIGNMENT and GHR_MASS_TRANSFERS — mass reorganization processes, joined on OLD_ORG_STRUCTURE_VERSION_ID, capturing the version replaced by the change.
• IGW_IMPLEMENTATIONS_ALL — grants administration, joined on both APR_ORG_STRUCTURE_VERSION_ID and PRP_ORG_STRUCTURE_VERSION_ID.
• PER_PERF_MGMT_PLANS, PER_CALENDAR_ENTRIES — performance management and HR calendar objects, both joined on ORG_STRUCTURE_VERSION_ID.
• OTA_USER_GROUP_ELEMENTS, OTA_MANDATORY_ENR_REQUESTS, OTA_EVENT_ASSOCIATIONS — Oracle Learning Management objects, all joined on ORG_STRUCTURE_VERSION_ID.

Because so many modules reference this table, end-dating or deleting a version record has cross-application consequences; implementations should treat ORG_STRUCTURE_VERSION_ID as a durable, referenced key rather than a disposable one.