Results for “org_access”

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

Overview

The INV.ORG_ACCESS table is the organization access rules table within Oracle E-Business Suite's Inventory (INV) module. It serves as the authoritative mapping that controls which operating units (organizations) a given responsibility is permitted to access. In EBS, a single responsibility frequently spans multiple inventory organizations, and ORG_ACCESS is the mechanism that defines and enforces that scope. When a user navigates to an Inventory form or submits a concurrent request that requires an organization context, EBS resolves the list of accessible organizations by querying this table for the active responsibility.

The table resides in the INV schema and holds a VALID status in ETRM 12.1.1 and 12.2.2. From a dimensional modeling perspective, heuristic analysis of the foreign key structure classifies this object as satellite-leaning. This classification is a modeling suggestion rather than a formal declaration: ORG_ACCESS behaves as a descriptive attribute table hanging off the responsibility dimension, recording the qualifying relationship between a responsibility and an organization rather than acting as a standalone transactional hub.

Key Information Stored

ORG_ACCESS contains 14 documented columns. The most functionally significant are the three key columns that define the access relationship itself:

• RESP_APPLICATION_ID and RESPONSIBILITY_ID — Together these identify the responsibility to which an access rule applies, joining to FND_RESPONSIBILITY.
• ORGANIZATION_ID — The inventory organization whose access is granted or restricted by the rule.
• DISABLE_DATE — The effective end date of the rule; a null or future date indicates the access is currently active.
• COMMENTS — Free-text justification or notes describing the rule.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program audit columns capturing which request and program last modified the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns maintained by EBS.

The surrogate primary key is ORG_ACCESS_PK, defined over (RESP_APPLICATION_ID, RESPONSIBILITY_ID, ORGANIZATION_ID). A separate unique index, ORG_ACCESS_U1, is defined over the same three columns, making it a business-key candidate that mirrors the natural uniqueness of the responsibility-to-organization pairing.

Common Use Cases and Queries

The primary operational scenario is determining which organizations a responsibility can see. A typical reporting query joins ORG_ACCESS to FND_RESPONSIBILITY to resolve the responsibility name:

• Listing accessible organizations for a responsibility: SELECT RESPONSIBILITY_ID, ORGANIZATION_ID FROM INV.ORG_ACCESS WHERE DISABLE_DATE IS NULL;
• Auditing access scope by responsibility name through a join to FND_RESPONSIBILITY on RESP_APPLICATION_ID and RESPONSIBILITY_ID.
• Detecting duplicate or overlapping rules using the ORG_ACCESS_U1 key columns.
• Identifying disabled rules by filtering on DISABLE_DATE.

Related Objects

• FND_RESPONSIBILITY — Joined on ORG_ACCESS.RESP_APPLICATION_ID and ORG_ACCESS.RESPONSIBILITY_ID; the parent responsibility definition.
• FND_APPLICATION and FND_RESPONSIBILITY_VL — Provide application and translatable responsibility context.
• ORG_ORGANIZATION_DEFINITIONS — Resolves ORGANIZATION_ID to a human-readable organization name and code.
• INV_ORGANIZATION_PARAMETERS and HR_OPERATING_UNITS — Define the operating units and organization-level parameters governed by these rules.