Results for “lgl_phys_map_id”

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

Overview

JTF_DSP_LGL_PHYS_MAP is a CRM Foundation (JTF) table within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the logical-to-physical media mapping based on site and language. In practical terms, the table resolves a logical content or media reference into the concrete physical asset that should be presented to a user, taking into account the operating unit or site context and the user's language. It is one of the mapping tables that support the multi-site, multi-language delivery of CRM content such as attachments, messages, and library items that would otherwise be stored only in their logical form.

From a Data Vault modeling perspective, the FK structure mined from the object metadata suggests a link classification. This is a heuristic suggestion rather than a documented fact: the table carries foreign keys to three separate parents (attachments, sites, and items) plus a security group, which is characteristic of a link or association entity resolving many-to-many style relationships. The table is marked VALID in the JTF schema and is owned by JTF.

Key Information Stored

The table is documented with fourteen columns. The most significant are summarized below.

• LGL_PHYS_MAP_ID — the surrogate primary key, defined by the JTF_DSP_LGL_PHYS_MAP_PK constraint. It is the sole component of the primary key.
• ITEM_ID — foreign key to JTF_AMV_ITEMS_B; identifies the logical library or media item being mapped.
• ATTACHMENT_ID — foreign key to JTF_AMV_ATTACHMENTS; identifies the physical attachment associated with the logical item.
• MSITE_ID — foreign key to JTF_MSITES_B; identifies the site (or mini-site) context for which the mapping applies.
• LANGUAGE_CODE — the language in which the mapping is valid, enabling language-specific physical media selection.
• DEFAULT_LANGUAGE — indicates whether the row represents the fallback language mapping.
• DEFAULT_SITE — indicates whether the row represents the fallback site mapping.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces the multi-tenant or responsibility-based data segregation used throughout CRM Foundation tables.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns recording the most recent modification.
• LAST_UPDATE_LOGIN — the login context under which the last update was made.

Business-key candidates are captured by the unique index JTF_DSP_LGL_PHYS_MAP_U1, which spans ITEM_ID, MSITE_ID, LANGUAGE_CODE, DEFAULT_LANGUAGE, and DEFAULT_SITE. This combination enforces that a given logical item maps to at most one physical attachment for a given site and language, with the two DEFAULT flags distinguishing the fallback obligations from the specific ones.

Common Use Cases and Queries

The most common requirement is to resolve the correct physical attachment for a logical item given a site and language. A typical query joins the mapping table to the item and attachment tables, preferring exact site/language matches and falling back to the DEFAULT_SITE or DEFAULT_LANGUAGE rows.

Reporting use cases include auditing which sites have explicit mappings versus relying on defaults, identifying items with no mapping at all, and reviewing the language coverage of CRM content. A representative pattern is:

• SELECT m.item_id, m.msite_id, m.language_code, m.attachment_id FROM jtf_dsp_lgl_phys_map m WHERE m.item_id = :p_item_id AND m.msite_id = :p_msite_id ORDER BY m.default_site, m.default_language;
• SELECT item_id, COUNT(*) FROM jtf_dsp_lgl_phys_map GROUP BY item_id HAVING COUNT(*) > 1; — used to inspect items with multiple site or language variants.
• SELECT m.* FROM jtf_dsp_lgl_phys_map m WHERE m.security_group_id = :p_security_group_id; — restricting results to the caller's security context.

Because OBJECT_VERSION_NUMBER is present, any direct updates should increment it to preserve OAF concurrency behavior. Direct DML is generally discouraged in favor of the owning CRM Foundation application logic.

Related Objects

The FK metadata identifies the following principal parents and related objects, with the join columns used.

• JTF_AMV_ITEMS_B — joined on ITEM_ID; holds the logical media or library item definitions.
• JTF_AMV_ATTACHMENTS — joined on ATTACHMENT_ID; holds the physical attachment records.
• JTF_MSITES_B — joined on MSITE_ID; holds site (mini-site) definitions.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; provides the security grouping used across CRM Foundation.
• JTF_DSP_LGL_PHYS_MAP_PK / JTF_DSP_LGL_PHYS_MAP_U1 — the primary key and unique index that constrain access paths and enforce the business key.

Collectively, these objects form the logical-to-physical delivery chain for CRM content in EBS 12.1.1 and 12.2.2.