Results for “mo_glob_org_access_tmp”

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

Overview

MO_GLOB_ORG_ACCESS_TMP is a temporary staging table owned by the APPLSYS schema and registered under the FND – Application Object Library product in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name and column structure indicate that it exists to materialize a flattened mapping between inventory organizations and the legal entities to which they belong, supporting Multi-Org access control, security profile generation, and organization-access validation routines. Because both organization and legal entity attributes are denormalized into a single row — including the descriptive name columns — the object functions as a transient cache rather than as a durable transactional store. Rows are typically populated and consumed within the span of a single concurrent program or form session.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this table is identified as standalone, meaning it is not modeled as a hub, link, or satellite. That assessment is consistent with its nature as a temporary work structure: it carries no independent identity beyond its surrogate key and acts primarily as a denormalized projection of relationships that are authoritative elsewhere. From a modeling perspective, the persistent organization-to-legal-entity association would more properly reside in a link construct, with this table serving only as a build artifact.

Key Information Stored

The documented physical schema contains four columns, reflecting a deliberately narrow, purpose-built structure:

• ORGANIZATION_ID — the identifier of the inventory organization. This column is also the documented unique index (MO_GLOB_ORG_ACCESS_TMP_U1), making it the business-key candidate for the table and the effective driver of any lookup against it.
• ORGANIZATION_NAME — the descriptive name of the organization, denormalized here to avoid a join back to the organization definition during access-list construction.
• LEGAL_ENTITY_ID — the identifier of the legal entity associated with the organization. A documented foreign key resolves this column to FV_LEGAL_ENTITIES.
• LEGAL_ENTITY_NAME — the descriptive name of the legal entity, again carried inline for reporting and display convenience.

No columns outside this documented set are present in the 12.2.2 schema. There is no separately documented surrogate primary key distinct from the ORGANIZATION_ID unique index; the unique index effectively enforces one row per organization within the staged set.

Common Use Cases and Queries

The principal use cases center on resolving which legal entities a user's organization access set touches, and on validating that a requested organization belongs to an expected legal entity. A typical diagnostic query joins the staging table to the legal entity definition to confirm FK integrity:

• SELECT t.organization_id, t.organization_name, t.legal_entity_id, t.legal_entity_name FROM applsys.mo_glob_org_access_tmp t;
• SELECT t.* FROM applsys.mo_glob_org_access_tmp t, fv_legal_entities le WHERE t.legal_entity_id = le.legal_entity_id AND t.organization_id = :org_id;
• Detecting orphaned staging rows: SELECT t.legal_entity_id FROM applsys.mo_glob_org_access_tmp t WHERE NOT EXISTS (SELECT 1 FROM fv_legal_entities le WHERE le.legal_entity_id = t.legal_entity_id);

Because the table is temporary, any query should account for the possibility that it is empty outside the window in which the owning program runs. It is not a suitable source for historical or point-in-time reporting; persistent organization and legal entity relationships should be sourced from their base tables.

Related Objects

The following objects are most significant in relation to this table:

• FV_LEGAL_ENTITIES — referenced by the documented foreign key on LEGAL_ENTITY_ID; the authoritative source of legal entity definitions.
• HR_OPERATING_UNITS — the base definition of organizations and legal entities used to populate the staging rows.
• HR_ALL_ORGANIZATION_UNITS — supplies ORGANIZATION_ID and ORGANIZATION_NAME values.
• FND_ORG_SECURITY_PROFILES and related Multi-Org security profile tables — consume organization access sets that this structure supports.
• MO_GLOB_ORG_ACCESS (and related MO global access objects) — the persistent counterparts to this temporary staging structure.
• FND_CONCURRENT_PROGRAMS / FND_CONCURRENT_REQUESTS — the concurrent processing framework through which the populating and consuming routines are typically executed.

Joins to these objects should be performed on the documented keys — ORGANIZATION_ID for organization-based lookups and LEGAL_ENTITY_ID for legal entity-based lookups.