Search Results link_content_to_query

Overview

The APPS.JTF_FM_QUERY_LINK_PKG package is a PL/SQL utility that belongs to the Oracle E-Business Suite Foundation (JTF) module, specifically the Foundation Query Management (FM) subsystem. Its principal business function is to manage the association — the linking and unlinking — between stored query definitions and the content objects (such as documents, records, or knowledge artifacts) that are attached to those queries. In EBS terminology, a "query" is a reusable, named search definition persisted in the JTF query repository, and "content" represents related information that end users wish to associate with that query for reference, retrieval, or contextual display.

The package is registered in the APPS schema with a VALID status, confirming it compiles and is available at runtime. It is classified as an OTHER API, meaning it is an internal utility rather than a public, supported integration point. Its dependencies include the standard FND_API package and the SYS STANDARD package, indicating that it follows Oracle's error-handling and API conventions. Importantly, the metadata records that the package is referenced by zero other packages, positioning it as a leaf-level component invoked primarily from the form or UI layer rather than from other PL/SQL APIs.

Key Procedures and Functions

ETRM documents two callable procedures within this package:

• LINK_CONTENT_TO_QUERY — Establishes an association between a content object and a specific query definition. When invoked, it records the relationship so that the content is recognized as belonging to (or presented alongside) the target query within the Foundation Query Management framework.
• UNLINK_CONTENT_TO_QUERY — Performs the inverse operation, removing a previously established association between content and a query. This supports maintenance scenarios in which a content attachment is no longer relevant to the query.

Both procedures encapsulate the insert/delete or status-update logic against the underlying link tables, ensuring that referential relationships remain consistent. Parameter signatures are not enumerated in the ETRM metadata excerpt and should not be assumed; developers requiring exact arguments must inspect the live package specification in the APPS schema.

Tables Accessed

The package operates against two documented tables, reached through APPS synonyms:

• JTF_FM_QUERIES_ALL — The master repository of query definitions. The package references this table to validate that the target query exists and is valid before creating or removing a content association.
• JTF_FM_QUERY_MES — The query-membership / linkage table that stores the actual many-to-many relationships between queries and their associated content. The link and unlink procedures write to and delete from this table respectively.

Usage Notes

Because it is a leaf component with no downstream package dependencies, JTF_FM_QUERY_LINK_PKG is typically invoked from the Foundation Query Management forms or from custom extensions that need to programmatically manage query-content relationships. It is not registered as a concurrent program entry point. When integrating, developers should call the procedures within a properly managed transaction, honoring the FND_API error-handling model and checking the returned status before committing, since the package participates in the standard EBS savepoint and rollback conventions.

Given the limited public documentation, custom code should treat the package as an internal API: callers must verify the specification for exact parameter names and datatypes, and should avoid hard-coding dependencies where an officially documented alternative exists. Testing in both 12.1.1 and 12.2.2 is recommended, as the JTF schema is shared across these releases with minimal structural variance.