Search Results p_dcname




Overview
Explore in AI Chat

Overview

JTF_PHY_MEDIA_PVT is a private PL/SQL package in the Oracle E-Business Suite Trading Community and CRM foundation layer, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its responsibility is to resolve the physical media associated with a legal content object in the Oracle iMarketing and product catalog domain. In practical terms, the package translates a logical content reference — an object identifier, a category identifier, a display context name, a site, and a language — into a concrete attachment record, returning the file name, item description, and file identifier that an application or web page can then use to render or download the media.

The package is classified as PVT (private), which in Oracle EBS naming convention indicates that it is an internal implementation layer and is not part of the published, supported public API surface. It was last touched in the 12.1.x code line (header revision 120.2, dated 2005), and it remains present and callable in 12.2.2 within the JTF (Java Technology Foundation / CRM Foundation) product family. Because it is private, Oracle does not guarantee its signature across releases, and direct customer invocation carries upgrade risk.

Key Procedures and Functions

The ETRM metadata documents a single callable unit:

  • GET_MEDIA — Retrieves the physical media record corresponding to a supplied logical content context. It accepts the standard Oracle API conformance parameters (API version, initialization message list flag, and the return status / message count / message data out parameters) plus a set of content-identification inputs: the object identifier (p_pid), the category identifier (p_catgid), the display context access name (p_dcname), the site identifier (p_siteid), and the language code (p_langcode). It returns the resolved file name (x_filename), the item description (x_description), and the attachment file identifier (x_fileid). The p_dcname parameter, which is the term most commonly used when searching for this package, is typed against jtf_dsp_context_b.access_name, meaning it identifies a named display context under which the media is published.

No other public or documented procedures or functions exist in this package.

Tables Accessed

The package reads from the following tables through APPS synonyms, all of which belong to the JTF display and attachment schema:

  • JTF_DSP_CONTEXT_B — Supplies display context definitions; its access_name column provides the data type for the p_dcname input.
  • JTF_DSP_OBJ_LGL_CTNT — Maps logical content objects and categories; its object_id column types the p_pid and p_catgid inputs.
  • JTF_DSP_LGL_PHYS_MAP — Provides the logical-to-physical mapping, including site and language attributes that type p_siteid and p_langcode.
  • JTF_AMV_ATTACHMENTS — Stores the actual attachment rows, supplying file_name and file_id for the out parameters, and joined to JTF_AMV_ITEMS_VL for the description.

The package reads these tables; no insert, update, or delete behavior is documented.

Usage Notes

GET_MEDIA is invoked internally by Oracle iMarketing and CRM content-serving components when a page or portlet must display or link to media tied to a specific display context. Typical callers are JSP or PL/SQL servlet layers rather than Oracle Forms. Because the package is PVT, it is not intended for direct customer extension; custom code that calls it should be treated as an unsupported dependency and should be re-validated on every upgrade from 12.1.1 to 12.2.2 and beyond. The ETRM metadata records no dependent packages referencing it, indicating a leaf-level utility. When troubleshooting, developers commonly search on p_dcname because the display context access name is the most business-meaningful input and the value most often mismatched between setup and invocation.