Search Results topnode_pos_ctrl_enabled_flag

Overview

PER_ORG_STRUCTURE_VERSIONS_V is an APPS-owned view within the Oracle E-Business Suite Human Resources (PER) product module. It is classified as a user-interface support view, meaning its primary purpose is to supply data to Oracle Forms and OAF-based HR pages rather than to serve as a standalone reporting interface. The view exposes organization structure version records together with descriptive context about copied (source) structure versions, enabling the HR organization hierarchy functionality to display version history, effective dates, and lineage when structures are duplicated or revised over time.

For report developers and integrators, the view offers a denormalized, ready-to-query representation of Org Structure Versions, joining version rows to their parent organization structure definition and to the source version when a copy operation occurred. Because APPS views are not always documented as public APIs, consumers should treat PER_ORG_STRUCTURE_VERSIONS_V as a supported read-only data source and avoid DML against it.

Underlying Base Objects

The documented view text reveals two referenced base objects, both exposed through APPS synonyms:

• PER_ORG_STRUCTURE_VERSIONS (aliased OSV1 as the driving table, and self-joined as OSV2 to resolve copy lineage)
• PER_ORGANIZATION_STRUCTURES (aliased OS1, joined on ORGANIZATION_STRUCTURE_ID as an outer join)

The self-join logic is central to the view: when COPY_STRUCTURE_VERSION_ID is populated, OSV2 is resolved through the matching ORG_STRUCTURE_VERSION_ID, and the copied version number and copied structure name are returned. When COPY_STRUCTURE_VERSION_ID is null, the ROWID comparison (OSV1.ROWID = OSV2.ROWID) causes the row to effectively self-reference, producing null copied attributes. The outer join to PER_ORGANIZATION_STRUCTURES ensures a version row survives even if its parent structure definition cannot be matched.

Key Columns

• ORG_STRUCTURE_VERSION_ID — Primary surrogate key identifying a specific version of an organization structure.
• ORGANIZATION_STRUCTURE_ID — Foreign key linking the version to its parent structure, and the column most commonly used to search or filter the view.
• BUSINESS_GROUP_ID — Business group (legislative data group) owning the version; critical for multi-org security filtering.
• VERSION_NUMBER and DATE_FROM / DATE_TO — Version sequencing and effective date range for the structure definition.
• COPIED_ORG_STRUCTURE_ID / COPIED_VERSION_NUMBER — Descriptive attributes about the source version when a copy was performed; null otherwise.
• COPY_STRUCTURE_VERSION_ID — The underlying identifier of the copied source version.
• TOPNODE_POS_CTRL_ENABLED_FLAG — Indicates whether position control is enabled for the top node of the structure version.
• Audit and concurrency columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include enumerating all versions of a given organization structure, identifying which structures were copied from which source versions, and validating effective date ranges. A standard query filtering by the headline search term is:

• SELECT organization_structure_id, org_structure_version_id, version_number, date_from, date_to, copied_version_number FROM per_org_structure_versions_v WHERE organization_structure_id = :p_structure_id ORDER BY version_number;

To trace copied lineage:

• SELECT org_structure_version_id, copy_structure_version_id, copied_org_structure_id, copied_version_number FROM per_org_structure_versions_v WHERE copy_structure_version_id IS NOT NULL AND business_group_id = :p_bg_id;

Because the view is UI-oriented, always constrain on BUSINESS_GROUP_ID where org security applies, and prefer joining to PER_ORGANIZATION_STRUCTURES for the structure name rather than relying on the view's decoded copy name.