Search Results copied_pos_structure_id

Overview

APPS.PER_POS_STRUCTURE_VERSIONS_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as PER.PER_POS_STRUCTURE_VERSIONS_V. The view exposes version records for position structures (position hierarchies) defined in Oracle HRMS / Oracle Advanced Benefits and related Enterprise Resource Planning components. Its documented purpose is to simplify forms coding, meaning it presents a denormalized, forms-friendly projection of the underlying version data so that the Oracle Forms-based Position Structure window and related concurrent processes can retrieve version details without performing complex joins at runtime.

ETRM explicitly warns that this is not a supported reporting interface: Oracle does not recommend querying or altering data through this view, and its definition may change dramatically in subsequent minor or major releases. The view status is recorded as VALID in the 12.2.2 metadata, and the same object is present in 12.1.1. The user search term "copied_version_number" maps directly to the COPIED_VERSION_NUMBER column, which documents the version number of a source structure version from which the current record was copied.

Underlying Base Objects

The view is defined over two APPS synonyms:

• PER_POSITION_STRUCTURES — the header table storing the position structure definition that a version belongs to.
• PER_POS_STRUCTURE_VERSIONS — the transactional table holding dated version rows for each structure, including date-effective ranges, version numbering, and copy lineage.

The join is driven by the structure primary key shared between the header and its versions, with BUSINESS_GROUP_ID providing the operating unit / business group context. The view is referenced by APPS.PQH_ASG_WRAPPER (via two dependent code paths shown in the metadata), indicating that position structure versions are consumed during assignment wrapper processing, typically in payroll or HR assignment validation logic. The supplementary nature of the view means it is optimized for form block data sources rather than ad hoc SQL, and it does not add business logic beyond the underlying tables.

Key Columns

• POS_STRUCTURE_VERSION_ID — primary identifier of the version row.
• POSITION_STRUCTURE_ID — parent position structure to which the version belongs.
• VERSION_NUMBER — sequential version number for the structure.
• DATE_FROM / DATE_TO — effective date range during which the version is active.
• COPY_STRUCTURE_VERSION_ID — identifier of the source version from which this version was copied.
• COPIED_POS_STRUCTURE_ID — the position structure identifier of the copied source.
• COPIED_VERSION_NUMBER — the version number of the copied source structure version; this is the column most commonly searched together with the base table to trace version lineage.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns for the process that created or modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
• BUSINESS_GROUP_ID — business group security context.
• ROW_ID — ROWID of the underlying version row, used by Oracle Forms for row identification.

Common Use Cases and Queries

The principal use case is tracing which version a structure version was copied from, for auditing version lineage and validating copy operations. A sample query retrieving copy lineage is:

SELECT POS_STRUCTURE_VERSION_ID, POSITION_STRUCTURE_ID, VERSION_NUMBER, COPIED_POS_STRUCTURE_ID, COPIED_VERSION_NUMBER, DATE_FROM, DATE_TO FROM APPS.PER_POS_STRUCTURE_VERSIONS_V WHERE BUSINESS_GROUP_ID = :p_business_group_id AND COPIED_VERSION_NUMBER IS NOT NULL;

A second scenario identifies all versions copied from a given source version:

SELECT POS_STRUCTURE_VERSION_ID, COPIED_POS_STRUCTURE_ID, COPIED_VERSION_NUMBER FROM APPS.PER_POS_STRUCTURE_VERSIONS_V WHERE COPY_STRUCTURE_VERSION_ID = :p_source_version_id;

Because the view is supplementary and unsupported for direct querying, production reports should preferably query PER_POS_STRUCTURE_VERSIONS and PER_POSITION_STRUCTURES directly, replicating the view's join, to avoid exposure to definition changes across releases.