Results for “bis_secured_operating_units_v”

4 results




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

Overview

BIS_SECURED_OPERATING_UNITS_V is a security-related view in the Oracle E-Business Suite (EBS) Applications BIS product family. It exposes the set of operating units (organizations) that a given responsibility is authorized to access, resolving the ORG_ID profile option hierarchy into a flat result set of organization identifiers and names. The view is typically leveraged by Oracle Applications security and data-restriction frameworks to determine which operating units are visible within a given session context, and is commonly referenced in reporting, personalization, and integration code where row-level organization security must be enforced.

In EBS 12.1.1 and 12.2.2, the view is defined as a UNION of two queries against the FND profile option infrastructure. The first branch handles operating units assigned directly at the site level (LEVEL_ID = 10003), and the second branch handles operating units inherited through responsibility-level assignments (LEVEL_ID = 10001), excluding any organization that is superseded by an explicit site-level entry for the same responsibility. The ETRM documentation notes that the object is "not implemented in this database" in the ETRM reference instance, meaning the view may not exist in every environment and is created conditionally by the product's install scripts.

Underlying Base Objects

The view is defined over four documented base objects:

No additional base objects are documented in the ETRM metadata. The view references only these four sources, and its definition contains a correlated NOT EXISTS subquery against FND_PROFILE_OPTION_VALUES to prevent duplicate or conflicting rows between the two branches.

Key Columns

  • ORGANIZATION_ID — the numeric internal identifier of the operating unit, derived by trimming and converting the profile option value to a number.
  • NAME — the operating unit name taken from HR_ALL_ORGANIZATION_UNITS.NAME.
  • RESPONSIBILITY_ID — the responsibility associated with the operating unit assignment. For site-level entries the value reported is the profile level value; for responsibility-level entries it is FND_RESPONSIBILITY.RESPONSIBILITY_ID.

Because the first UNION branch returns LEVEL_VALUE as the responsibility identifier for site-level rows, callers should not assume Responsibility_ID is always a valid FND responsibility key; its meaning depends on the branch that produced the row.

Common Use Cases and Queries

Typical uses include validating which operating units a responsibility can transact in, driving secured LOVs and reports, and auditing profile option assignments across an environment. A representative query listing operating units for a given responsibility:

  • SELECT organization_id, name, responsibility_id FROM bis_secured_operating_units_v WHERE responsibility_id = :resp_id ORDER BY name;
  • SELECT DISTINCT organization_id, name FROM bis_secured_operating_units_v ORDER BY name; — produces the set of organizations visible across secured responsibilities.
  • SELECT organization_id, name FROM bis_secured_operating_units_v WHERE organization_id = :org_id AND responsibility_id = :resp_id; — verifies that a specific operating unit is reachable under a responsibility, useful in integration and REST/PL-SQL data-restriction checks.

Because the view is reported as not implemented in some instances and its definition depends on profile option data maintained by the Application Object Library, queries should guard against missing profile values and confirm the view exists in the target environment before deployment in custom code.