Results for “position_control_structure_flg”

50+ results




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

Overview

PER_ORG_STRUCTURES_LOV is an APPS-owned view in the Oracle E-Business Suite Human Resources (PER) product. As its name implies, it is a list-of-values (LOV) support view rather than a transactional or reporting entity in its own right. The ETRM documentation states its purpose succinctly: it is "used to support user interface." In practice this means the view supplies the rows displayed in organization structure selection windows, flexfields, and related Forms-based LOVs within Oracle HRMS, and it is equally available to SQL*Plus, Oracle Reports, BI Publisher, and external integrations that need to resolve a valid organization structure identifier.

The view is significant because it presents a single, de-normalized row per organization structure version, combining the structure's business name and primary-structure indicator with the version's effective dates and its position-control attribute. This spares callers the effort of joining PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_VERSIONS, and FND_LOOKUPS themselves. The status is VALID in both EBS 12.1.1 and 12.2.2, and the documented metadata is consistent across those releases.

Underlying Base Objects

The view text joins three objects:

The documented metadata also lists FND_GLOBAL (PACKAGE) among the referenced base objects. FND_GLOBAL is the standard EBS context package used to return session values such as BUSINESS_GROUP_ID and ORG_ID; although it does not appear in the excerpted view text, it is commonly referenced by the surrounding UI logic and by dependent objects that consume this LOV. Joins are equi-joins on ORGANIZATION_STRUCTURE_ID between the structures and versions tables, and on LOOKUP_CODE to PRIMARY_STRUCTURE_FLAG.

Key Columns

  • BUSINESS_GROUP_ID — the business group that owns the structure; the primary partitioning key for HRMS queries.
  • ORGANIZATION_STRUCTURE_ID — the unique identifier of the structure.
  • NAME — the user-visible name of the organization structure.
  • PRIMARY_STRUCTURE_FLAG — Y/N flag indicating whether this is the primary structure for its purpose.
  • MEANING — the decoded Yes/No description of PRIMARY_STRUCTURE_FLAG from FND_LOOKUPS.
  • ORG_STRUCTURE_VERSION_ID — identifier of the specific dated version returned by the join.
  • DATE_FROM / DATE_TO — the version's effective start and end dates; DATE_TO is NVL'd to 31-12-4712, the standard EBS "open ended" sentinel.
  • POSITION_CONTROL_STRUCTURE_FLG — indicates whether the structure is a position-control structure, i.e. the hierarchy against which position and incumbent validation is performed. This is the column users most often search for when investigating position control configuration.

Common Use Cases and Queries

Typical scenarios include populating an LOV of position-control structures, validating that an organization structure exists for a given business group, and joining the view to PER_POSITIONS or PER_ALL_POSITIONS to confirm the controlling structure. Because multiple versions may satisfy the join, callers should generally restrict by date and primary flag.

List position-control structures for a business group:

  • SELECT organization_structure_id, name, date_from, date_to FROM per_org_structures_lov WHERE business_group_id = :p_bg_id AND position_control_structure_flg = 'Y' AND TRUNC(SYSDATE) BETWEEN date_from AND date_to ORDER BY name;

Retrieve the primary structure and its decoded flag:

  • SELECT organization_structure_id, name, meaning, date_from, date_to FROM per_org_structures_lov WHERE business_group_id = :p_bg_id AND primary_structure_flag = 'Y';

Always constrain by BUSINESS_GROUP_ID and effective dates; apply the Multi-Org / business group security context established by FND_GLOBAL to avoid returning structures outside the caller's access.