Results for “primary_structure_flag”

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

Overview

HRI_CL_ORG_HRCY_BX_V is a read-only Oracle EBS view owned by the APPS schema and validated against both 12.1.1 and 12.2.2 environments. It belongs to the HRI — Human Resources Intelligence product family, which is documented as obsolete in current ETRM releases but whose objects frequently remain deployed in legacy instances. The view exposes organization hierarchy definitions sourced from PER_ORGANIZATION_STRUCTURES, presenting each structure as a selectable list entry with an identifier, display name, effective date range, owning responsibility, business group, and — most relevant to the search term supplied — a PRIMARY_STRUCTURE_FLAG indicator. In practice, the view functions as a secured list-of-values source for organization hierarchy pickers used by HRMS reporting and integration components. It does not store data; it is a projection over the organization structure table with a security predicate layered on top, and it is defined WITH READ ONLY to signal that no DML is permitted through it.

Underlying Base Objects

The view is defined primarily over PER_ORGANIZATION_STRUCTURES (aliased OST), from which it draws ORGANIZATION_STRUCTURE_ID, NAME, PRIMARY_STRUCTURE_FLAG, and BUSINESS_GROUP_ID. Supporting objects referenced in the ETRM metadata include:

• FND_GLOBAL (package) — supplies RESP_ID for the RESPONSIBILITY_ID column, enabling downstream responsibility-scoped filtering.
• HR_BIS (package) — its GET_SEC_PROFILE_BG_ID function drives the business group security predicate in the WHERE clause.
• HR_GENERAL (package) — provides START_OF_TIME and END_OF_TIME constants for the synthetic DATE_FROM and DATE_TO columns.
• HRI_OLTP_VIEW_SECURITY (package) — the documented security package associated with this view family.
• HRI_CL_ORG_HRCY_N_V (view) — a related sibling view listed among the referenced objects, typically the non-secured or alternate presentation of the same hierarchy data.

The WHERE clause applies NVL and DECODE logic so that rows with a NULL business group resolve to -1, and rows whose business group does not match the security profile result of HR_BIS.GET_SEC_PROFILE_BG_ID are excluded. This means a session only sees structures belonging to its permitted business group, or those with no business group at all.

Key Columns

• ID — maps to ORGANIZATION_STRUCTURE_ID; the unique key for the hierarchy definition.
• VALUE — maps to NAME; the human-readable structure name shown in LOVs and reports.
• DATE_FROM / DATE_TO — populated with HR_GENERAL.START_OF_TIME and END_OF_TIME, deliberately wide bounds rather than true date-tracked values.
• RESPONSIBILITY_ID — the current FND_GLOBAL.RESP_ID at query time.
• PRIMARY_STRUCTURE_FLAG — carries PER_ORGANIZATION_STRUCTURES.PRIMARY_STRUCTURE_FLAG, identifying whether the row represents the primary organization hierarchy for its business group. This is the column referenced by the user's search and is the standard discriminator when a single "main" hierarchy must be selected.
• BUSINESS_GROUP_ID — the owning business group, or NULL when unassigned.

Common Use Cases and Queries

The most frequent requirement is retrieving the primary organization hierarchy for the session's business group:

• SELECT id, value, primary_structure_flag FROM apps.hri_cl_org_hrcy_bx_v WHERE primary_structure_flag = 'Y';
• SELECT id, value FROM apps.hri_cl_org_hrcy_bx_v ORDER BY value; — populates a hierarchy selection list.
• SELECT DISTINCT business_group_id FROM apps.hri_cl_org_hrcy_bx_v; — confirms which business groups the current responsibility can see.

Because the view is READ ONLY and security-filtered at execution time, results vary by responsibility and business group context; queries should always be executed under the intended application session rather than as a privileged schema user. Given the obsolete status of the HRI product line, consumers should validate behavior on their specific patch level and plan for migration to supported HRMS hierarchy views where feasible.