Results for “org_access”

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

Overview

BIS_ORGANIZATIONS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite release 12.1.1 and 12.2.2. It is registered under the BIS (Applications BIS) product family and carries a VALID status in the ETRM repository. The view consolidates the set of inventory organizations that a given responsibility is permitted to access, resolving both explicitly granted organizations and implicitly available organizations into a single, query-friendly result set.

Functionally, the view serves the same purpose as the ORG_ACCESS table but broadens the result by unioning two distinct populations: organizations that have been explicitly assigned to a responsibility through the ORG_ACCESS security mechanism, and organizations that exist in MTL_PARAMETERS but have not been explicitly assigned to any responsibility, which are therefore considered accessible to all responsibilities. This dual logic makes the view the canonical source of truth for organization-level access checks in custom reports, concurrent programs, and integrations that must respect inventory organization security.

The view's relevance to a search for "org_access" is direct: ORG_ACCESS is the primary security table it consumes, so any requirement to enumerate or validate organizational access typically resolves to BIS_ORGANIZATIONS_V rather than to the base table itself.

Underlying Base Objects

The documented view metadata lists four referenced base objects:

• ORG_ACCESS (SYNONYM) — the security table that maps responsibilities to inventory organizations. It supplies the explicitly granted organizations in the first branch of the UNION.
• MTL_PARAMETERS (SYNONYM) — identifies valid inventory organizations. It supplies the second branch of the UNION, subject to the NOT IN filter against ORG_ACCESS.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — the translated organization unit table, joined to obtain the organization NAME in the user's session language.
• FND_GLOBAL (PACKAGE) — the standard EBS context package used to supply the responsibility identifier and session language.

The view text joins ORG_ACCESS to HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL on ORGANIZATION_ID, filtering the TL table by USERENV('LANG') so the returned names match the runtime language setting.

Key Columns

• ID — the organization identifier, exposed as TO_CHAR(O.ORGANIZATION_ID). Returned as a character string rather than a number, which is important when joining to numeric ORGANIZATION_ID columns elsewhere.
• VALUE — the organization name sourced from HR_ALL_ORGANIZATION_UNITS_TL.NAME, resolved in the session language and suitable for display in LOVs and reports.
• RESPONSIBILITY_ID — the responsibility to which the organization access applies, taken from ORG_ACCESS.RESPONSIBILITY_ID in the first branch and from FND_RESPONSIBILITY_VL.R.RESPONSIBILITY_ID in the second.

Common Use Cases and Queries

The view is typically used to populate organization LOVs, to validate whether a responsibility may transact in a given inventory organization, and to drive security-aware reporting.

• Enumerating accessible organizations for the current responsibility:

SELECT id, value
FROM   apps.bis_organizations_v
WHERE  responsibility_id = fnd_global.resp_id
ORDER  BY value;

• Listing all responsibility-to-organization assignments for auditing:

SELECT responsibility_id, id, value
FROM   apps.bis_organizations_v
ORDER  BY responsibility_id, value;

• Validating access before processing a transaction:

SELECT COUNT(*)
FROM   apps.bis_organizations_v
WHERE  responsibility_id = :p_resp_id
AND    id = TO_CHAR(:p_org_id);

Because the view embeds the union logic for unassigned organizations, consumers should not re-implement the ORG_ACCESS check independently; querying BIS_ORGANIZATIONS_V ensures consistent behavior with standard EBS organization security.