Results for “jtf_dsp_lgl_phys_map_v”

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

Overview

The JTF_DSP_LGL_PHYS_MAP_V view is a read-only reporting object owned by the APPS schema within the JTF (CRM Foundation) product family. Its purpose is to expose the relationship between legal entities and physical sites (MSites) as maintained by the JTF Display and Mapping layer, joined to descriptive information from the multi-site and language reference views. The view is defined WITH READ ONLY, confirming that it is intended strictly for query, reporting, and integration consumption rather than for DML operations. In Oracle EBS 12.1.1 and 12.2.2, such views are commonly referenced by CRM-facing components, concurrent programs, and third-party integrations that need to resolve site names and language descriptions without querying the underlying transactional tables directly.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over three referenced objects:

• JTF_DSP_LGL_PHYS_MAP (SYNONYM) — the primary mapping table supplying the identity and default flag columns (LGL_PHYS_MAP_ID, ATTACHMENT_ID, ITEM_ID, MSITE_ID, DEFAULT_SITE, LANGUAGE_CODE, DEFAULT_LANGUAGE).
• JTF_MSITES_VL (VIEW) — the multi-site view providing MSITE_NAME and the active-date columns. The join restricts results to sites where START_DATE_ACTIVE is on or before SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE) is on or after SYSDATE, ensuring only currently active sites appear.
• FND_LANGUAGES_VL (VIEW) — the language reference view supplying LANGUAGE_DESCRIPTION via a join on LANGUAGE_CODE.

The join logic is an inner join across all three objects, keyed on MSITE_ID and LANGUAGE_CODE respectively.

Key Columns

• LGL_PHYS_MAP_ID — primary identifier of the legal/physical mapping record.
• ATTACHMENT_ID — reference to an associated attachment record.
• ITEM_ID — identifier of the related CRM item.
• MSITE_ID — identifier of the multi-site (physical site).
• MSITE_NAME — the descriptive name of the multi-site; this is the column most frequently searched for by users researching "msite_name".
• DEFAULT_SITE — flag indicating whether the mapping designates the site as the default.
• LANGUAGE_CODE — language code associated with the mapping record.
• LANGUAGE_DESCRIPTION — descriptive name of the language, sourced from FND_LANGUAGES_VL.
• DEFAULT_LANGUAGE — flag indicating the default language for the mapping.

Common Use Cases and Queries

Typical usage includes resolving the human-readable site name behind an MSITE_ID, validating which mapping records reference currently active sites, and surfacing language descriptions for multilingual CRM deployments.

To retrieve all active mappings with site names:

• SELECT MSITE_ID, MSITE_NAME, DEFAULT_SITE, LANGUAGE_CODE, LANGUAGE_DESCRIPTION FROM APPS.JTF_DSP_LGL_PHYS_MAP_V;

To locate a specific mapping by site name:

• SELECT LGL_PHYS_MAP_ID, ITEM_ID, MSITE_NAME FROM APPS.JTF_DSP_LGL_PHYS_MAP_V WHERE MSITE_NAME = :p_msite_name;

Because the view already filters on active site dates, no additional date predicate is required, simplifying reporting queries and integration extracts. All access should be granted through the APPS schema or a synonym exposed to the calling application.