Search Results copy_structure_version_id




Overview
Explore in AI Chat

Overview

APPS.PER_ORG_STRUCTURE_VERSIONS_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that exposes organization structure version records maintained by Oracle HRMS (PER) modules. Organization structures define the hierarchical arrangements of organizations (for example, business groups, legal entities, operating units, and inventory organizations) used throughout EBS. Each structure can have multiple dated versions, and the version records are physically stored in PER_ORG_STRUCTURE_VERSIONS. This view presents those versions together with derived information about the source version from which a given version was copied. Because it is owned by APPS, it is accessible to concurrent programs, forms, and third-party integrations that connect with the APPS schema credentials.

The view is particularly relevant when a structure version has been created by copying an existing version — a common practice in HRMS and organization hierarchy maintenance. It resolves the copy reference so that consumers can identify the originating structure name and version number rather than working with a raw surrogate key.

Underlying Base Objects

Per the documented view definition, the view is constructed from three references: PER_ORGANIZATION_STRUCTURES and two instances of PER_ORG_STRUCTURE_VERSIONS. In the ETRM metadata these are recorded as synonyms (PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS) resolving to the underlying PER tables in the APPS schema.

The view aliases PER_ORG_STRUCTURE_VERSIONS twice as OSV1 (the primary version row) and OSV2 (the referenced copy source or, when no copy exists, the same row). The join condition is expressed as a disjunction: when COPY_STRUCTURE_VERSION_ID is populated, OSV1 joins to OSV2 on that key; when it is null, OSV1 joins to OSV2 on ROWID so the row effectively joins to itself. A further outer join to PER_ORGANIZATION_STRUCTURES (OS1) supplies the structure name, keyed by ORGANIZATION_STRUCTURE_ID. The use of an outer join (OS1.ORGANIZATION_STRUCTURE_ID(+)) means structure name may be null if no matching structure row is present, a condition normally masked by the DECODE logic.

Key Columns

  • ORG_STRUCTURE_VERSION_ID — Primary identifier of the organization structure version record in PER_ORG_STRUCTURE_VERSIONS.
  • ORGANIZATION_STRUCTURE_ID — Foreign key to the parent organization structure definition in PER_ORGANIZATION_STRUCTURES.
  • BUSINESS_GROUP_ID — Business group that owns the structure version.
  • COPY_STRUCTURE_VERSION_ID — The version identifier from which this version was copied; null when the version was created from scratch. This is the column most often searched by users investigating a copy operation.
  • VERSION_NUMBER — The version number of the current row.
  • DATE_FROM / DATE_TO — The effective date range for the version.
  • Derived structure name and copied version number — The DECODE expressions return the originating structure name (from OS1.NAME) and the copied version number (from OSV2.VERSION_NUMBER), each null when COPY_STRUCTURE_VERSION_ID is null.
  • TOPNode_POS_CTRL_ENABLED_FLAG — Flag indicating whether position control is enabled for the top node of the structure.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus concurrent request metadata (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical uses include auditing how organization structure versions were created, tracing a copied version back to its source, and reconciling HRMS structure definitions for integrations or data migrations.

To locate versions created by copying from a specific version:

  • SELECT ORG_STRUCTURE_VERSION_ID, ORGANIZATION_STRUCTURE_ID, VERSION_NUMBER, COPY_STRUCTURE_VERSION_ID FROM APPS.PER_ORG_STRUCTURE_VERSIONS_V WHERE COPY_STRUCTURE_VERSION_ID = :p_version_id;

To list all versions of a structure with their copy lineage and effective dates:

  • SELECT ORGANIZATION_STRUCTURE_ID, VERSION_NUMBER, DATE_FROM, DATE_TO, COPY_STRUCTURE_VERSION_ID FROM APPS.PER_ORG_STRUCTURE_VERSIONS_V WHERE ORGANIZATION_STRUCTURE_ID = :p_structure_id ORDER BY VERSION_NUMBER;

To find versions within a business group during a reporting period:

  • SELECT BUSINESS_GROUP_ID, ORGANIZATION_STRUCTURE_ID, VERSION_NUMBER FROM APPS.PER_ORG_STRUCTURE_VERSIONS_V WHERE BUSINESS_GROUP_ID = :p_bg_id AND DATE_FROM >= :p_start AND NVL(DATE_TO, :p_end) <= :p_end;

Because the source definition relies on a self-join, queries that filter on COPY_STRUCTURE_VERSION_ID are resolved efficiently by an index on that column in PER_ORG_STRUCTURE_VERSIONS. Reporting against this view is read-only and does not alter base HRMS data.