Results for “gms_operating_units_v”

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

Overview

GMS_OPERATING_UNITS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMS – Grants Accounting product. Its purpose is to expose the set of operating units that are both defined within the MO: Security Profile framework and actively implemented for Grants Accounting. Because Grants functionality is enabled selectively per operating unit, the view acts as a filtered, security-aware list rather than a simple enumeration of all HR operating units.

The view has two responsibilities. First, it restricts the returned organizations to those for which the current user passes the MO_GLOBAL.CHECK_ACCESS security check, honoring the MO: Security Profile / MO: Operating Unit profile options. Second, it intersects that secured set with records present in GMS_IMPLEMENTATIONS_ALL, so only operating units that have an actual Grants implementation are returned. This makes it the canonical source for Grants-aware operating unit list-of-values, concurrent program parameters, and reporting prompts. The object is documented as VALID and follows the standard APPS view convention of joining secured HR operating units to a product-specific implementation table.

Underlying Base Objects

The view is defined over three documented base objects:

• HR_OPERATING_UNITS (VIEW) — supplies the authoritative list of operating units and their organization IDs and names within the HR foundation.
• GMS_IMPLEMENTATIONS_ALL (SYNONYM) — records which operating units have Grants Accounting implemented, driving the inner join that limits results to implemented organizations.
• MO_GLOBAL (PACKAGE) — provides the CHECK_ACCESS function, which evaluates the current user's MO: Security Profile access against a given organization ID.

The join condition is IMP.ORG_ID = HR.ORGANIZATION_ID, and access is enforced by the predicate MO_GLOBAL.CHECK_ACCESS(HR.ORGANIZATION_ID) = 'Y'. Because the security check is applied inside the view, any consumer query automatically inherits the Multiple Organizations (MO) access model without additional filtering. The view itself is owned by APPS and is therefore typically referenced with the APPS or a synonym prefix.

Key Columns

The view exposes two columns:

• ORG_ID — the HR organization identifier of the operating unit, aliased from HR.ORGANIZATION_ID. This is the value used in multi-org partitioning columns (ORG_ID) throughout Grants and other EBS tables.
• OPERATING_UNIT — the descriptive operating unit name, aliased from HR.NAME. This is the human-readable label presented in lists of values and report outputs.

Both columns derive directly from HR_OPERATING_UNITS; the view adds no computed columns. This simple two-column structure makes the view well suited for lookup and prompt purposes rather than transactional analysis.

Common Use Cases and Queries

Typical uses include populating operating unit parameters in Grants concurrent programs, driving list-of-values definitions for Grants forms, and validating that a given organization is both security-accessible and Grants-implemented. A basic listing retrieves all accessible, implemented operating units:

• SELECT org_id, operating_unit FROM apps.gms_operating_units_v ORDER BY operating_unit;
• SELECT operating_unit FROM apps.gms_operating_units_v WHERE org_id = :p_org_id;

A common pattern joins the view to other Grants data to resolve an operating unit name from a stored ORG_ID, or to confirm implementation status before processing Grants transactions. Note that results vary by user, since the MO_GLOBAL.CHECK_ACCESS predicate filters rows according to the session's security profile. If a user sees no rows, the cause is generally either missing MO security access or the absence of a GMS_IMPLEMENTATIONS_ALL record for that operating unit.