Results for “position_structure_id”

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

Overview

The APPS.PO_EMPLOYEE_HIERARCHIES view is a reporting and integration object within the Oracle E-Business Suite Purchasing (PO) module. It exposes approval and reporting hierarchy relationships between employees, capturing the superior-to-subordinate structure along with positional and organizational context. The object is documented in ETRM as VALID under Oracle EBS 12.1.1 and 12.2.2, and its metadata is annotated as "Retrofitted," indicating that the view was introduced or reconciled during a release upgrade cycle to preserve backward compatibility with existing customizations, reports, or integrations that depended on hierarchy data.

The view functions as a business-group-scoped façade over the underlying multi-org table. Rather than exposing all rows across every business group, it filters records so that only those matching the current Financials System Parameters business group are returned. This makes the view suitable for single-business-group reporting sessions and for code that should operate within the context of the logged-in operating unit or business group.

Underlying Base Objects

The view is defined over two referenced objects, both accessed through APPS synonyms:

• PO_EMPLOYEE_HIERARCHIES_ALL — the base multi-org table holding the full employee hierarchy data set, including BUSINESS_GROUP_ID and ORG_ID for row-level ownership.
• FINANCIALS_SYSTEM_PARAMETERS — the financials setup table that holds the current business group identifier (FSP.BUSINESS_GROUP_ID) used in the view's filter predicate.

The view text selects all documented columns from PO_EMPLOYEE_HIERARCHIES_ALL and restricts rows with a predicate of the form: BUSINESS_GROUP_ID IN ( SELECT NVL(FSP.BUSINESS_GROUP_ID, 0) FROM FINANCIALS_SYSTEM_PARAMETERS FSP ). The NVL default of 0 ensures that rows with a null business group are still eligible when the system parameter is unset. Because the view is not a secured synonym with row-level security policies, access control is inherited through the APPS schema grants on the view itself.

Key Columns

The view exposes the following columns, which mirror the base table structure:

• EMPLOYEE_ID and SUPERIOR_ID — the subordinate and the superior in a reporting relationship.
• POSITION_STRUCTURE_ID — identifies the position hierarchy structure that governs the relationship, distinguishing between alternate hierarchy versions or structures.
• EMPLOYEE_POSITION_ID and SUPERIOR_POSITION_ID — position identifiers corresponding to the employee and superior rows.
• SUPERIOR_LEVEL — the depth or level of the superior within the hierarchy.
• ORG_ID and BUSINESS_GROUP_ID — organizational and business group ownership columns supporting multi-org reporting.
• Audit and concurrent program columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

The POSITION_STRUCTURE_ID column is particularly significant for users searching on that term, as it links hierarchy rows to a specific position structure definition, enabling filtering by structure when multiple hierarchies exist.

Common Use Cases and Queries

Typical uses include approval routing analysis, organizational reporting, and feeding external workflow or BI systems with hierarchy relationships. A common query retrieves all direct reports for a given employee within a specific position structure:

• SELECT EMPLOYEE_ID, SUPERIOR_ID, POSITION_STRUCTURE_ID, SUPERIOR_LEVEL FROM APPS.PO_EMPLOYEE_HIERARCHIES WHERE SUPERIOR_ID = :superior_id AND POSITION_STRUCTURE_ID = :structure_id;
• SELECT BUSINESS_GROUP_ID, ORG_ID, COUNT(*) FROM APPS.PO_EMPLOYEE_HIERARCHIES GROUP BY BUSINESS_GROUP_ID, ORG_ID;
• SELECT * FROM APPS.PO_EMPLOYEE_HIERARCHIES WHERE EMPLOYEE_ID = :employee_id AND ROWNUM = 1;

Because the view restricts output to the business group defined in FINANCIALS_SYSTEM_PARAMETERS, queries against it automatically observe that setup context and avoid cross-business-group contamination in reporting output.