Results for “org_name”

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

Overview

The PJI_DIS_SEC_ORG_V view belongs to the PJI (Project Intelligence) product family within Oracle E-Business Suite. The product is flagged as obsolete in the ETRM documentation, indicating that it is retainedfor backward compatibility or historical reference rather than active development. The view is described as a "Discoverer view of operating units viewable by the currency user," which identifies its primary purpose: to expose a security-filtered list of operating units for consumption by Oracle Business Intelligence Discoverer reports and similar reporting tools.

In the Oracle EBS reporting architecture, security over operating units is a recurring requirement. Reports and analytical queries frequently must restrict data to the set of operating units a given user is authorized to access. PJI_DIS_SEC_ORG_V serves as the presentation layer for that security model, translating the authorized set of operating units into a simple two-column result set that a Discoverer workbook or a custom report can join against. Because the product is obsolete, the view should be regarded as a legacy artifact. Organizations on 12.1.1 or 12.2.2 that still run Project Intelligence Discoverer workbooks may encounter it, but new development should not depend on it.

Underlying Base Objects

The documented definition of the view is minimal and is expressed entirely in terms of a single base object, PJI_PMV_ORG_DIM_TMP. The view text is documented as selecting ORG_ID and ORG_NAME from that temporary table and aliasing ID to ORG_ID and NAME to ORG_NAME. The ETRM metadata records no other referenced base objects and lists the owner as undocumented.

The naming convention of the underlying object, with the TMP suffix, strongly suggests it is a temporary or staging table populated at runtime by the Project Intelligence security and dimension-building logic. The PMV segment of the name is consistent with Project Management views or materialized structures used by Project Intelligence. As a consequence, the view has no persistent data of its own; it reflects whatever rows the population process has placed into PJI_PMV_ORG_DIM_TMP for the current session or run. The ETRM documentation explicitly notes "Not implemented in this database," meaning that in the environment from which the metadata was extracted the view was not physically present. This is consistent with an obsolete product whose database objects have been removed during upgrade or installation cleanup.

Key Columns

The view exposes exactly two columns, both derived from the temporary base table:

• ORG_ID — the operating unit identifier. The view text selects the base column ID and aliases it to ORG_ID. This is the value that reporting queries use to join to operating-unit-aware transactional tables such as project, expenditure, or invoice fact tables.
• ORG_NAME — the operating unit name. The base column NAME is aliased to ORG_NAME. This is the descriptive label rendered in Discoverer reports, dashboards, and parameter lists, and it is the column most likely to be returned when a user searches for "org_name" in the context of this view.

There is no additional filtering, aggregation, or derived logic documented beyond the column aliasing. The security filtering implied by the view's description is therefore applied upstream, during the population of PJI_PMV_ORG_DIM_TMP, rather than within the view definition itself.

Common Use Cases and Queries

The typical use case is to drive an operating unit selection list or to constrain a report query to the set of authorized operating units. A simple lookup of the available operating units is the most direct application:

• SELECT org_id, org_name FROM pji_dis_sec_org_v; — returns the full set of operating units visible to the current user.
• SELECT org_name FROM pji_dis_sec_org_v WHERE org_id = :p_org_id; — resolves an operating unit identifier to its display name.
• SELECT d.org_id, d.org_name, SUM(f.amount) FROM pji_dis_sec_org_v d, some_project_fact f WHERE f.org_id = d.org_id GROUP BY d.org_id, d.org_name; — aggregates project or expenditure facts while automatically enforcing operating unit security.

Because the view is obsolete and was not implemented in the documented database, practical queries should first verify its existence in the target instance. If it is absent, the underlying temporary table or its replacement security mechanism must be used instead, and the query logic should be migrated to a supported Project Intelligence or Project Portfolio Management construct.