Results for “pa_adw_oper_units_v”

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

Overview

PA_ADW_OPER_UNITS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) product family. It exposes the set of operating unit dimension values used by the Projects Analytics/Data Warehouse (ADW) layer. In Oracle EBS, the operating unit is a core Multi-Org partitioning construct: it determines which ledger, legal entity, and organization context a transaction or project belongs to. Reporting and integration tools — including the Projects data warehouse, Discoverer workbooks, OBIEE repository loads, and custom extracts — consume this view to resolve the operating unit dimension into a clean, denormalized row of descriptive attributes.

The view is documented as VALID and structured for read-only consumption. It does not store data itself; it presents a curated projection of the underlying base view PA_ADW_OPER_UNITS_B_V, adding a stable column list (including the ten generic USER_COL1 through USER_COL10 slots) that downstream extracts can depend upon without coupling to the volatile internals of the base object.

Underlying Base Objects

Per the ETRM metadata, PA_ADW_OPER_UNITS_V is defined over PA_ADW_OPER_UNITS_B_V, and the object is further associated with the HR_GENERAL and HR_SECURITY packages. The view text selects the following columns from the base view: ORGANIZATION_ID, ORGANIZATION, LEGAL_ENTITY, SET_OF_BOOK, USER_COL1, USER_COL2, USER_COL3, USER_COL4, USER_COL5, USER_COL6, USER_COL7, USER_COL8, USER_COL9, and USER_COL10.

The naming convention is significant: the trailing "_B_V" on the base object typically denotes the "base" view, while PA_ADW_OPER_UNITS_V is the public or "final" view. This pattern is common in EBS ADW objects, where security predicates — driven here by the HR_GENERAL and HR_SECURITY packages — restrict the rows returned according to the session's organization and security profile. The base view performs the underlying joins and lookups; the public view normalizes the column list and applies the standard projection. Because security is enforced through HR_SECURITY, query results are automatically filtered to the operating units the running user is authorized to see.

Key Columns

• ORGANIZATION_ID — The unique identifier of the operating unit, joining to HR_OPERATING_UNITS and related Org tables.
• ORGANIZATION — The descriptive name of the operating unit.
• LEGAL_ENTITY — The legal entity associated with the operating unit, used for statutory and tax reporting.
• SET_OF_BOOK — The ledger (set of books) mapped to the operating unit, anchoring accounting reporting.
• USER_COL1 … USER_COL10 — Ten generic, customer-configurable attribute columns. USER_COL10 is the tenth of these. These slots allow customers to map additional operating-unit attributes (for example, region, business group, or reporting hierarchy) into the ADW dimension without modifying the delivered view definition.

Common Use Cases and Queries

The most frequent use is populating the operating unit dimension in the Projects data warehouse or a custom analytics model. A typical lookup joins a fact table to this view on ORGANIZATION_ID to enrich rows with the operating unit name, legal entity, and ledger.

To list all operating units and their user attributes visible to the current user:

SELECT organization_id, organization,
       legal_entity, set_of_book,
       user_col10
FROM   apps.pa_adw_oper_units_v
ORDER BY organization;

To resolve the ranking or classification stored in USER_COL10 for a specific operating unit:

SELECT organization, user_col1, user_col10
FROM   apps.pa_adw_oper_units_v
WHERE  organization_id = :p_org_id;

Because rows are filtered by HR_SECURITY, results depend on the responsibility and security profile. USER_COL10 has no delivered meaning; its semantics are entirely customer-defined and must be documented locally before being relied upon in reports.